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.

Codezero Microkernel 1.) What is Codezero? Codezero is an L4 microkernel that has been written from scratch. It targets embedded systems and its purpose is to act as a secure embedded hypervisor. It aims to become the most modern L4 implementation by evolving the L4 microkernel API into the future. In a nutshell, Codezero provides all the basic mechanism to abstract away the hardware, build OS services, isolate applications and fine-grain security in a single package. 2.) Why the name Codezero? The project philosophy is to create the simplest and leanest microkernel that is generic and applicable to many different applications. Feature creep is what we don't have in Codezero. Simple, elegant design is the project philosophy. 3.) Why use Codezero? Codezero aims to be technically cutting-edge. It's design is open and improves by evolution. It is also easy-to-use, well-documented and portable, mostly maturing on the ARM architecture. These might be the appealing reasons from a technical point-of-view. It is also backed by a responsive team, in case you have more demanding requirements. 4.) What is the license? The current release is distributed under GNU General Public License Version 3. For contributions we ask for a copyright share agreement and you may freely contribute to the project this way. We also have commercial licensing options available. This is our current model for keeping the project design and development completely open, while thriving it by professional funding. If you feel this is too restrictive, feel free to mention your ideas in our mailing list. The third party source code under the directories loader/ tools/ libs/c libs/elf have their own copyright and licenses, separate from this project. All third party source code is open source in the OSI definition. Please check these directories for their respective licenses.