| May | JUN | Jul |
| 11 | ||
| 2017 | 2018 | 2019 |
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.
Collection: Archive Team: The Github Hitrub
Fetching latest commit…
Cannot retrieve the latest commit at this time.
| Failed to load latest commit information. | |||
|
meetings | ||
|
|
test_tools | ||
|
|
tools | ||
|
|
.gitignore | ||
|
|
.gitreview | ||
|
|
.zuul.yaml | ||
|
|
README.rst | ||
|
|
bindep.txt | ||
|
|
meetingindex.jinja | ||
|
|
sample.yaml | ||
|
|
test-requirements.txt | ||
|
|
tox.ini | ||
project: the name of the project
●meeting_id: the name given to the #startmeeting meetbot command
●agenda_url the URL to the page with the agenda for the meeting,
usually in the wiki
●schedule: a list of schedule each consisting of
●time: time string in UTC
●day: the day of week the meeting takes place
●irc: the irc room in which the meeting is held
●frequency: frequent occurrence of the meeting
●chair: name of the meeting's chair
●description: a paragraph description about the meeting
The file name should be a lower-cased, hyphenated version of the meeting name,
ending with .yaml . For example, Keystone team meeting should be
saved under keystone-team-meeting.yaml.
project: Nova Team MeetingThe schedule is a list of dictionaries each consisting of time in UTC, day of the week, the irc meeting room, and the frequency of the meeting. Options for the frequency are weekly, biweekly-even, and biweekly-odd at the moment.
schedule:
- time: '1400'
day: Thursday
irc: openstack-meeting-alt
frequency: biweekly-even
- time: '2100'
day: Thursday
irc: openstack-meeting
frequency: biweekly-odd
The chair is just a one liner. The might be left empty if there is not a
chair. It's recommended to mention his/her IRC nick.
chair: Russell Bryant (russellb)The project description is as follows. Use > for paragraphs where new lines are folded, or | for paragraphs where new lines are preserved.
description: >
This meeting is a weekly gathering of developers working on OpenStack.
Compute (Nova). We cover topics such as release planning and status,
bugs, reviews, and other current topics worthy of real-time discussion.
sample.yaml and
editing as appropriate.
●© 2018 GitHub, Inc.
●Terms
●Privacy
●Security
●Status
●Help
●Contact GitHub
●API
●Training
●Shop
●Blog
●About
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.
You signed out in another tab or window. Reload to refresh your session.