| Jul | AUG | Sep |
| 28 | ||
| 2018 | 2019 | 2020 |
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.
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.
There is a dashboard running for the archivebot process at http://www.archivebot.com.
ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.

92% of applications developed today contain open source components. Yet the vast majority are not maintained to the standard you would expect of commercial software. And understandably so, since most open source maintainers haven’t traditionally been paid for their work.
Like any software, without careful maintenance, entropy sets in and things start to go wrong: broken builds, licensing mistakes, security incidents. Without someone else accountable to do the work, the burden of unmaintained dependencies falls on your team, slowing you down and taxing your capacity to build new things.
What if you could have the flexibility to build with open source together with the confidence of commercial-grade software? Maybe you could move fast and not break things.A managed open source subscription backed by the creators and maintainers who built the packages you depend on.

Erlend Sogge Heggen, VP of Community at Discourse
“Discourse has become a Tidelift subscriber not only to benefit from professional-grade assurances around software that’s integral to our business, but to constructively partner with the individuals who create those packages. Paying the maintainers is something we know is effective, and it’s also an urgent priority for our business, since it ensures the technology we rely on is maintained and dependable.”
A way to get paid for the value you create, simply by keeping your projects well maintained.

Evan You, founder of Vue
“Tidelift has a really interesting approach to funding open source work. It’s a pretty simple concept: maintainers get paid and the organizations who use their projects get the support and dependability they need in return. I believe that this model helps us move closer to a future where many more maintainers like me can afford to work on their projects full time."
