
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.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We’ve improved the GitHub Projects onboarding flow to help you get started faster, with options to connect and import items from a repository, set a default repository for new issues, use new default workflows to set up your project, and more.
🚀 Key improvements
Import items from a repository
import_items.mp4
During onboarding, you can now choose to import open issues, open pull requests, or both from a specified repository. The selected items are automatically imported when the project is created, so you can start with your existing content right away.
Set a default repository
default_repo.mp4
In project settings, you can now select a default repository. All new issues created in this project will be automatically associated with the selected repository.
Pull request linked to issue workflow
linked_PRs_workflow.mp4
A new default workflow, Pull request linked to issue, automatically sets the status of an issue to "In progress" whenever a linked pull request exists.
🛠 Additional onboarding improvements
🤖 API improvements
We've made improvements to the Projects GraphQL API making it easier to automate your project workflows.
project_v2_item_status_changed,added_to_project_v2,removed_from_project_v2, andconverted_from_draftevents. These events allow you to understand information such as how long an item was "In progress" before moving to "Done".queryargument with any project filter. Check out the ProjectsV2 GraphQL documentation for more details.🌟Leave a comment!
Join the discussion and leave feedback in the comments below!
Beta Was this translation helpful? Give feedback.
All reactions