I agree with Stefan, and everything is in one place. Personally, I believe that is important.
It also has several features that Google can't provide. You can link to branches, commits and lines of code in a neat way. You can also close issues by committing. For full explanation see: https://github.com/blog/831-issues-2-0-the-next-generation (Especially part "Commits + Issues"). If you set them up, you can also label issues: https://github.com/github/training.github.com/issues There are scripts that migrates "Google Code Issues" to github, with small restrictions. Then Google Code Issues can be turned off :) - Stadtpirat ----- Original Message ----- From: Stefan de Konink <[email protected]> To: [email protected] Cc: Sent: Monday, December 10, 2012 1:52 PM Subject: Re: [Cherokee] A joined community On 12/10/12 13:49, Daniel Lo Nigro wrote: > The one on Google Code is good, but I find it wierd because Cherokee > has nothing to do with Google. Doesn't that also cause a lot more > effort? That's from a non-developers point of view, so it might be > inaccurate. I can't really do a constructive critic, it's just an > observation. > > Google Code is Google's code hosting service (much like Github) - It's > where Cherokee used to be hosted, I believe. There's a lot more > historical data in the Google Code tracker so it might be worth just > turning off the Github one? The best thing from the Github one is direct endorsing participation, which doesn't happen on the Google code one... so turning it off doesn't seem to be a very good idea. Stefan _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
