307 captures

25 May 2000 - 01 Jun 2025

Apr	JUN	Jul
	01
2022	2023	2024

success

fail

About this capture

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: Archive Team: URLs

TIMESTAMPS

GCC: About

These pages are maintained by the GCC team and it's easy to contribute.

The web effort was originally led by Jeff Law. For the last two decades or so Gerald Pfeifer has been leading the effort, but there are many contributors .

The web pages are under git control. The pages on gcc.gnu.org are updated directly after a change has been committed. www.gnu.org is updated once a day at 4:00 -0700 (PDT).

Please send feedback, problem reports and patches to our mailing lists, ideally putting the string "[wwwdocs]" at the beginning of the mail subject.

Want to contribute? Any help concerning the items below is welcome, as are suggestions. Suggestions accompanied by patches have a higher chance of being implemented soon. ;-)

• Improve navigation, with a consistent (short) menu on every page.
• Set up a system that automatically checks the mirrors list.

  It should detect mirrors that have gone away, are persistently down, or very out of date (the last being easy to do for those carrying snapshots, harder for those with releases only). DJ Delorie <[email protected]> has some scripts to do this already.

Using the git repository

Assuming you have both git and SSH installed, you can check out the web pages via

git clone git+ssh://username@gcc.gnu.org/git/gcc-wwwdocs.git

where username is your user name at gcc.gnu.org.

For anonymous access, use

git clone git://gcc.gnu.org/git/gcc-wwwdocs.git

Validating a change

To validate any changes, you can use the W3 Validator. Just use the "Validate by File Upload" functionality.

Checking in a change

We recommend you list files explicitly to avoid accidental checkins and prefer that each checkin be of a complete, single logical change.

1. Sync your sources with the master repository via "git pull". This will also identify any files in your local tree that you have modified.
2. We recommend reviewing the output of "git diff".
3. Use "git commit" and "git push origin master" to check in the patch.
4. Upon checkin a message will be sent to the gcc-cvs-wwwdocs mailing list.

As changes are checked in, the respective pages are preprocessed via the script wwwdocs/bin/preprocess which in turn uses a tool called MetaHTML. Among others, this preprocessing adds CSS style sheets, XML and HTML headers, and our standard footer. The MetaHTML style sheet is in wwwdocs/htdocs/style.mhtml.