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.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Go through devguide file-by-file for GitHub migration #39
Labels
Milestone
Comments
This was referenced Oct 6, 2016
|
Now that there are separate issues for the remaining pages, the GitHub milestone can be used to track what's left to do. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to go through the entire devguide for the GitHub migration. Having a module marked off as done means that it is ready to go in the
githubbranch or a separate issue to track what needs to be done for a page has been created. The key point is that once every page is checked off there will be a clear understanding of what is left to do for the GitHub migration.committing.rst(#44)coredev.rst(#45)devcycle.rst(#46)developers.rst(#47)faq.rst(#27, #48)gitdevs.rst(#49)index.rst(#50)patch.rst(#51)setup.rst(#52)triaging.rst(#53)buildbots.rstbuildslave.rstclang.rstcommunication.rstcompiler.rstcoverage.rstcoverity.rstdocquality.rstdocumenting.rstexperts.rstfixingissues.rstgdb.rstgrammar.rsthelp.rstlangchanges.rstmotivations.rstruntests.rstsilencewarnings.rststdlibchanges.rsttracker.rstThe text was updated successfully, but these errors were encountered: