| Jun | JUL | Aug |
| 26 | ||
| 2014 | 2015 | 2016 |
COLLECTED BY
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.
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.
GitHub is the largest code host on the planet with over 25 million repositories. Large or small, every repository comes with the same powerful tools. These tools are open to the community for public projects and secure for private projects.
A flexible issue tracker lets you stay on top of bugs and focus on features.
Your project’s issues page can be as simple or as sophisticated as you like. Filter by open and closed issues, assignees, labels, and milestones. Sort by issue age, number of comments, and update time.
Labels are another way to organize your issues and can be customized with your own colors.
Milestones are great at helping everyone work towards a goal. Set a due date, name your milestone, then start grouping issues together.
View the milestones page for twbs/bootstrap.
Further streamline your workflow by closing issues right from your commit messages.
The syntax is basic: if you want to close issue #35, put closes #35 somewhere in your commit message. Once the commit is in your default branch (usually master), the issue will be closed.
Supported keywords: closes, fixes, resolves, and more
Anyone with write access to your repository may close an issue or leave a note.
Issues know all about commits and other issues. Type in a commit SHA or an issue number and it will automatically be linked.
Code review is an essential part of the GitHub workflow. After creating a branch and making one or more commits, a Pull Request starts the conversation around the proposed changes. Additional commits are commonly added based on feedback before merging the branch.
Pull Requests are living conversations that streamline the process of discussing, reviewing, and managing changes to code.
Each Pull Request takes into account not only what you would like pulled, but also where you intend those changes to be applied. From there, your team can discuss the changes as a whole, individual parts, or even specific lines. Later commits addressing concerns or ideas appear as part of the conversation.
GitHub allows you and your teammates to have a detailed discussion about every commit that is pushed to your project. Should it be included? Was it done correctly? Should something else be added? Talk about changes to your code with everyone involved before releasing or incorporating them.
You can have conversations on entire commits as well as individual lines of code.
With GitHub you can easily and efficiently compare any two branches in your project or network. See what work is unique to a branch with respect to another branch—that is, if you were to merge the branches together, what changes would be applied?
The GitHub compare view shows a list of all the commits unique to a branch, the sum of all the files changed across all of those commits, and a unified or split diff of those changes to clearly summarize what the branch represents.
Whether you’re running an open source project or a Fortune 500 company, organizations simplify team management.
With teams, you can give your developers as much or as little power as they need — from the ability to create projects on behalf of your organization to read-only access on existing projects. Members can be granted read, read-write, or admin-level access to repositories.
When you mention a team, all team members receive a notification.
Rather than dozens of buttons, we rely on the simplicity of GitHub Flavored Markdown for formatting text. The autocompleter makes quick work of mentioning people and teams, creating links to other issues, and adding the perfect Emoji. 
Adding images is as simple as dragging and dropping from your desktop. For an even more distraction-free writing experience, you can use the fullscreen Zen Mode.
Our syntax highlighting currently supports over 200 programming languages. Data is as important to us as code, so we're always looking for new ways to render formats like STL 3D models, CSV files, and GeoJSON maps in the browser.
This button is used throughout the website, offering a quick way to view code in your installed GitHub app.
If you prefer the command line or another native client, you can use those as well.
SSL, HTTPS, and SSH data transmission and two-factor authentication are core elements of security at GitHub.
The GitHub API documentation has everything you need to integrate your tool or application with GitHub.
Discover applications and tools that integrate with GitHub to help you and your team build software better, together.
Using GitHub Pages you can quickly and easily publish and host websites with us.
By the way, every GitHub repository is also a Subversion repository.
Use your favorite SVN tools to checkout, branch, and commit to GitHub repositories.
View commit comments for jquery/jquery.