
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.
Co-authored-by: Jean Burellier [email protected]
Signed-off-by: Michael Dawson [email protected]
This PR is a result of work done by the Next-10 team - https://github.com/nodejs/next-10 and those who participated in the mini-summit - nodejs/next-10#76.
The goal is to agree on a documented set of priorities that we believe are important to the future success of Node.js. Submitting this PR is intended to get review/discussion from the broader collaborator base and then serve to document the consensus we reach.
One of the follow on efforts will be to document what we should be/are doing for each of the priorities and to figure out the best way to capture and share the info.
For some of the priority areas we already have people doing what's needed (for example a big thank you to @targos for all his work on keeping v8 up to date which supports "Up to date ES JavaScript Support" and reporting on it as a strategic initiative - https://github.com/nodejs/node/blob/master/doc/guides/strategic-initiatives.md. Another good example is ongoing work related to https://github.com/nodejs/undici by @ronag and @mcollina.
For other areas the Next-10 team is planning a deeper dive to discuss/capture specific items/work that we believe the project should be doing to support that priority. If people comment on this issue that they'd like to be involved in the discussion of specific priorities we will at mention when we set up the session for the deep dive on that topic.
As always the the work done going forward will depend on what individual collaborators have time to prioritize. It is still important for us as a project to have a documented agreement on the key priorities we think are important so that we can promote and support collaboration on these priorities.
We are looking forward to your comments/input on the priorities listed in the PR and would also welcome people joining the next-10 effort to keep things moving forward. We currently have this doodle open to find a new meeting time so if you are interested please add your info: https://doodle.com/poll/a46canyfppq9mcht?utm_source=poll&utm_medium=link
The text was updated successfully, but these errors were encountered: