COLLECTED BY

Organization: Archive Team

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.

Collection: ArchiveBot: The Archive Team Crowdsourced Crawler

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.

TIMESTAMPS

The Wayback Machine - https://web.archive.org/web/20201020000444/https://docs.github.com/en/enterprise-server@2.20/github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards

GitHub Docs

Permission levels for user-owned project boards

A project board owned by a user account has two permission levels: the project board owner and collaborators.

In this article

Permissions overview
Owner and admin permissions for a user-owned project board
Read and write permissions for a user-owned project board
Project board visibility
Further reading

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.

Permissions overview

There is only one owner of a user-owned project board; this permission cannot be shared with another user account. In addition to the owner, other people can collaborate on project boards.

There are three levels of permissions for project board collaborators:

Read, which gives people permission to view a project board.
Write, which gives people permission to view a project board, link repositories to a project board, and interact with a project board. For more information, see "Linking a repository to a project board."
Admin, which gives people permission to view a project board, interact with a project board, manage project board settings, and manage other people's access to the project board.

Owner and admin permissions for a user-owned project board

The project board owner and collaborators with admin access have full control of the project board. In addition to all the permissions allowed by project board collaborators, a project board owner and collaborator with admin access can:

Read and write permissions for a user-owned project board

Collaborators with read access to a user-owned project board can:

View a project board
Copy a project board
Filter cards on a project board

Collaborators with write access to a user-owned project board can:

View a project board
Copy a project board
Filter cards on a project board
Edit a project board
Link a repository to a project board
Configure automation for project boards
Copy a project board
Add issues and pull requests to a project board
Add notes to a project board
Track progress on your project board
Archive cards on a project board

Project board visibility

You can change the project board's visibility from private to public and back again. By default, user-owned project boards are private. For more information, see "Changing project board visibility."

Further reading

"Managing access to your user account's project boards"

Did this doc help you?

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.