
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Summary
The GitHub developer research team, led by Dr. Nicole Forsgren, has continued to show that Software Delivery Metrics are the best way for teams to track and monitor team productivity. In this release, Insights will incorporate two of the most important product velocity metrics: Deployment Frequency and Lead Time for Changes. Engineering leaders will be able to use these metrics to identify opportunities to improve their organizational practices and culture. Through ongoing research that leverages the vast dataset of GitHub projects, benchmarks will receive refinements to give teams even better comparison points.
Artwork is for illustrative purposes. Actual experience may differ at launch.
Intended Outcome
Providing Engineering Directors and other engineering leaders essential product velocity metrics will enable them to improve organizational culture and see the impact of changes. Teams will be able to use benchmarks for making more meaningful comparisons and identifying opportunities to improve.
How will it work?
New dashboards and reports tracking Deployment Frequency and Lead Time for Changes will be added to the organization level Insights views. Drill-down experiences to view report details will provide additional insights. Benchmarks will include new options and more granularity of data, enabling more detailed comparisons.
The text was updated successfully, but these errors were encountered: