
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.
Businesses should be able to submit a proposal for a project to be worked on by our members.
Definitions
client- an Operation Code member that needs work to be doneproposal- a unit of work to be doneadmin- an Operation Code member that will be maintaining the jobs portalmember- an Operation Code member interested in working on a proposalScenarios
As a client
As an admin
As a member
Proposals
In order to maintain quality each new proposal should move through several states.
When a proposal first comes in it should be in the
Newstate. An email should be sent to admins for each new proposal.The next state will be
In review. Admins will be reviewing the proposal to make sure it's valid and for more complex proposals possibly contact the client to identify milestones and timelines.After the proposal is valid it will be moved to the
Client Reviewstate. In this state contacts will be drawn up and the client can verify the final proposal.From 'Client Review' the client can chose to go to either the 'Ready' state or the 'Published' state. The only difference between the two states is
Readywon't show up in the user proposal list, wherePublishedwill. A user should be able to transition fromReadytoPublishedat any time.During the
Publishedstate members will be able to apply to the proposal. Admins should contact each applicant to make sure they're capable of the required tasks and to determine what resources they might need.From the
Publishedstate a client should be able to move to theCanceledstate. This will close the proposal and no more actions can be taken.From the
Publishedstate an admin should be able to move to theAcceptedstate. This means members have applied and been approved to work on the project and work can begin.From the
Acceptedstate an admin should be able to move to theIn Progressstate. This means members have begun work.From the
Acceptedstate an admin should be able to move to theClient Acceptancestate. At this point work will be demonstrated to the client.From
Client Acceptancea client should be able to move to theClient Acceptedstate. This means the work demonstrated is valid and the project is complete. Any code or artifacts should be delivered.From
Client Acceptancea client should be able to move to theChanges Requestedstate. This means changes are needed to meet the client's needs. Admins should be notified to make sure the changes still fit the scope of the proposal.From
Changes Requestedthe client should be able to move to theClient Acceptedstate.From
Client Acceptedan admin should be able to move to theBillingstate.From the
Billingstate an admin should be able to move to theCompletedstate.MVP Criteria