project infrastructure

I updated the roundup package on bluesock (the server that hosts the 
Pyblosxom bug tracker) and inadvertently stomped on the fix I made to 
roundup.  Then I started getting lots of error emails from roundup because 
it's "helpful".  Took me about 30 minutes to figure out how I fixed it the 
last time and re-fix it.  Irritating.

That got me thinking.  A while back, when we talked about switching to git 
and picking a host, I remember a lot of people said they already had 
github accounts.  I picked gitorious because at the time is was close 
enough feature-wise and it was Free Software.  I picked roundup because it 
seemed like a decent choice.

At this point, I want to revisit those decisions.  I'm thinking of moving 
things around in this way:

1. Move from gitorious to github.  In doing this, we gain post-commit 
hooks some of which are wildly useful, an issue tracker, inline comments 
for pull requests, probably an order of magnitude more people who already 
have github accounts and who are used to drive-by-fixes, and probably some 
other github features I haven't yet discovered.

2. Move the Pyblosxom manual to ReadTheDocs.  We're already using Sphinx. 
If we switch to github, then it's a post-commit hook to update it 
everytime something gets checked in.  This would be really nice.

3. Ditch roundup and use the github issue tracker.

After that we can see where things are at.

Any thoughts on this?  Is anyone against it?  If not, I'm going to do this 
before releasing 1.5 since I want to update the urls everywhere. 
Hopefully before the end of this year.

/will

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d