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.
ArchiveBot is an IRC bot designed to automate the archival of smaller websites (e.g. up to a few hundred thousand URLs). You give it a URL to start at, and it grabs all content under that URL, records it in a WARC, and then uploads that WARC to ArchiveTeam servers for eventual injection into the Internet Archive (or other archive sites).
To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.
We just published our vision for GitHub accessibility at accessibility.github.com. Here’s the TL;DR: the prime directive of the GitHub accessibility program is to empower people with disabilities to build cool technology.
There are more than one billion people in the world with disabilities. I’m proud to be one of them. However, those of us with disabilities encounter barriers every day. From transportation to civic participation, from education to employment, and from entertainment to healthcare, people with disabilities must overcome a myriad of environmental and attitudinal barriers to live the lives we want to live.
On August 23, I started the next chapter in my professional journey as Head of Accessibility at GitHub. I am absolutely thrilled to be here because GitHub is a critical point of leverage for improving accessibility and disability inclusion globally. Based on my personal experience, one of the most effective ways to improve the accessibility of software, and build more bridges across the Disability Divide, is to include people with disabilities in the development process.
We just published our vision for GitHub accessibility at accessibility.github.com. Here’s the TL;DR: the prime directive of the GitHub accessibility program is to empower people with disabilities to build cool technology. We will do that by focusing on the following pillars:
Our Workplace. Our commitment to accessibility starts at home, with our employees. We are working to hire more people with lived experiences, upskill all Hubbers on accessibility best practices, and strengthen our culture of inclusion for people with disabilities within GitHub.
Our Offerings. As the home for all developers, we want every developer to feel welcome. In addition to lowering barriers for building on GitHub, we’re engaged with developers that live with various types of disabilities to understand the challenges and opportunities that are unique to them, so we can build the solutions they need to do their best work.
Our Impact. We are eager to increase our impact through collaboration with partners and the open source community. Our opportunities for impact include expanding disability inclusion in the open source community, growing the pipeline of developers with disabilities, and fostering innovation of access technologies.
Our Promise. GitHub is at the beginning of a new and exciting phase of our journey towards becoming the most accessible and inclusive platform possible. Our promise is to make consistent progress towards our commitment to accessibility, share that progress transparently, and listen and respond to community feedback in a timely manner.
Do we expect every person with a disability to become a developer? No, but we firmly believe in the principle of “nothing about us without us.” Technology is ubiquitous. We want to make tools, processes, and communities that develop technology inclusive, along every dimension of identity, to ensure the resulting technologies benefit all of humanity. We know people with disabilities have a role to play in the future of software development, and we want to help them do it.
I invite you to bookmark accessibility.github.com and stay tuned for additional updates on our work in the near future.
✕
Wait! Don't Go Yet 🚀
Get our FREE eBook "10 Programming Tips That Changed Everything" when you subscribe!
GitHub is in an exciting phase of our journey as the developer community grows significantly every day, and the needs of the community grow and change with it. Today we’re introducing our new Chief Product officer.