SF Migration Update

Hi all,

Quick progress report on the SF -> Github migration effort.

The Player repository, as well as the Papers and Website repositories, 
have been exported from SVN and uploaded to github.  There is one snag - 
some of the email addresses in the author file were wrong when I 
exported the Player code, and I didn't catch it until after I pushed it 
to github.  Fixing that error means re-writing the git history and force 
pushing over top of the exisitng repository.  This is not great, but 
since the repository hasn't really been advertised yet I'm going to just 
push the fixed history and get it over with.  Any forked repositories 
and clones will have to fetch the new history and do similar.  I think 
there's only one fork at the moment (Kevin's) so the impact should be 
small.  If nobody has any issues with this, I'll do it this weekend.

I checked the bug and patch trackers on Sourceforge, and there aren't 
many open issues left for Player.  It looks like it's easy enough to 
import the issues to github[1].  I'll run the import script and then 
triage any remaining issues (there are a few that belong to Stage and 
Gazebo that won't make sense in the new Player-only tracker.)

I haven't made much headway on the site/documentation issues, other than 
learning how ReadTheDocs and sphinx work.  That means there's still a 
few ways the site could go:
1. host on github, combine site and wiki, re-write site using Jekyll 
(seems like a blog platform, maybe not a good fit)
2. host on github, combine site and wiki, re-write site using Doxygen or 
sphinx & import generated html
3. host on ReadTheDocs, combine site and wiki, re-write site using sphinx
4. host privately, keep site and wiki as-is
5. host privately, merge site into wiki, host wiki
6. host privately, re-write site/wiki however we want

I do like the idea of combining the site and the wiki, as I always felt 
having both was a bit redundant.  In the past I was starting to move the 
FAQ and tutorials from the static site to the wiki, so that there was 
less overlap and so they could be improved by anyone.  Unfortunately 
re-writing the site will complicate any redirecting from the SF hosting 
location.  I am leaning towards option 2, but would like to hear if 
anyone has any other opinions.

Mailing lists are tricky.  It's possible to export the mailing SF list 
history from mailman.  We could start a new pair of mailing lists at 
google groups, and there's a hacky way to import the existing history 
there[2].  If we go the self-hosting route, we could set up our own 
mailman instance and import the entire history.  I think google groups 
would be easiest.

So next steps are:
- Push updated Player history with corrected email addresses
- Export SF bug tracker info, import issues to github
- Determine hosting solution for site and mailing list
    - Import/Export mailing lists
    - Merge site & wiki, host combined site
- Announce migration and new site

Rich

[1] https://github.com/cmungall/gosf2github
[2] https://github.com/wojdyr/fityk/wiki/MigrationToGoogleGroups

------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors 
network devices and physical & virtual servers, alerts via email & sms 
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o