title: Project management to go with GitHub
body: <p>(EDIT: This question is now outdated for my particular issue, as Google Code supports git now and I've converted Protocol Buffers to Mercurial anyway. However, it's still of general interest, IMO.)</p>
  
  <p>My <a href="http://github.com/jskeet/dotnet-protobufs/tree/master" rel="noreferrer">C# Protocol Buffers Port</a> uses github for its source control, and I'm beginning to really enjoy using git. However, as far as I can tell, github doesn't provide any project management tools: defect and feature tracking, discussions, feature requests, docs etc. Given my affiliations, <a href="http://code.google.com" rel="noreferrer">Google Code</a> would be a natural choice, but it would seem odd to create a project there but host the source on github.</p>
  
  <p><a href="https://stackoverflow.com/questions/39186/should-i-use-githubfogbugz-or-assembla">This question about Fogbugz/Assembla</a> seems to mostly focus on the defect tracking. I was wondering what experiences others have had when it comes to a more "complete" project management solution. Does Fogbugz actually do everything I need? (Using a wiki for docs has its advantages, although I also want to be able to distribute documentation with the code.) Beyond the explicit features mentioned in the first paragraph, are there other project aspects I <em>should</em> be considering which I may have missed?</p>
  
  <p>This will definitely stay an open source project, and although I'd rather not pay I don't mind if a small fee is required. Currently I'm the only developer, but that may change and there may very well be lots of people filing bugs and feature requests. (In other words, I  hope and expect it to be popular, but with me doing most of the work.)</p>
  
  <p>Previously I've <em>contributed</em> to various open source projects, but haven't done much in the way of running a very visible and active one. (<a href="http://pobox.com/~skeet/csharp/miscutil" rel="noreferrer">MiscUtil</a> is currently still "hosted" on my website, with occasional releases - the actual source control is on my local NAS.)</p>
  
  <p>Anyone care to share their experiences?</p>
  
  <p>EDIT: Another option I'm now considering is a Google Code project (I really would like to be loyal to my employer) and an occasional merge from git to svn (at the very least, every time I do a release). This would allow non-git users to get hold of the source easily too.</p>