[Fab-user] [README] Migrating code.fabfile.org to Github

[Jeff Forcier]

Hi all,

Either tonight or tomorrow I plan to pull the trigger on migrating our
Redmine instance at http://code.fabfile.org over to
https://github.com/fabric/fabric/issues . What this means for you:

* Once the script is done, Github will be the place to open new issues
or pull requests, and code.fabfile.org will be read-only:
    * No more having to point people back over to code.fabfile!
    * We'll be able to take advantage of Github's collaboration
features as well, though it may take a little time to arrive at best
practices.
* Package maintainers will need to switch their source packages to
pull from the appropriate Github tgz-generation URLs for both past and
future milestones.
    * I may try to set up HTTP redirects for the old Redmine file
download URLs if it's feasible, but anybody who is still actively
maintaining should switch to the Github URLs anyways.


This is the specific action plan:

* The Redmine instance will be made read-only in some fashion prior to
the migration, probably by disabling all accounts and account
creation;
* All existing issues/pull requests on Github will be removed (they
should all exist on Redmine at this point, so no data loss);
* The migration script will run, copying issues and their comments
(and any textual attachments) to Github Issues. All useful metadata
(milestone, category, tracker, etc) will be copied as labels;
* The Redmine instance will remain active & read-only until it is
replaced with redirects from e.g.
http://code.fabfile.org/issues/show/222 to
https://github.com/fabric/fabric/issues/222 ;


Anybody looking for history on the switch can check out the
above-mentioned issue #222, it contains rationales and links to
related discussions. The tl;dr is at the top of that ticket's
description block.

Thanks,
Jeff

-- 
Jeff Forcier
Unix sysadmin; Python/Ruby engineer
http://bitprophet.org