In the "old days", projects would have a webpage with some instructions, screenshots and downloadable binaries. The effort required to do this would pay off in terms of polish and would attract more users.
Today, people find out about this supposedly nice piece of software, and proceed to find only a source file listing, no documentation (not even a half-decent README), no screenshots and, worst of all, the need to build from source. I'm a technical person with a fair amount of curiosity for these things, and I find myself frequently bummed out and give up when I see a link to github.
Even when these "artifacts" exist, just the look of the site is enough to put regular users off.
Sharing code is not only about dumping a source tree online. It's about polishing all that surrounds it and makes it a "product". Without users a source tree has no value.
Frankly, the current situation is making the open-source community more and more closed in on itself. The first step for irrelevance.
Github's UI admittedly doesn't make for a great experience for someone browsing around looking for software to download. A project that is trying to appeal to regular users should set up a wiki page, or even better, use Github Pages to build a site.
Though, I really hate it when I follow a link to a Rails app on Github that left the default "Welcome to Rails" readme.
1. Is the library stable/complete? 2. Is the API stable? 3. If not, how frequently/how much does it change?
With a decent project page, I can have these questions answered either directly or by looking at the available downloads history (even if they are source-only downloads) and version numbers. With github projects I frequently can't answer any of those questions.
Libraries are products, just like any other piece of software.
I'm not saying that github isn't good for developer collaboration. I'm saying it's no good for developer-user relations. It has the necessary features, but it doesn't encourage its use by the very nature of its interface.
Number of followers/watchers is usually a good indication of how well-liked a project is. And as with any other open-source software, without sniffing in the code a little bit you never know what you're getting, regardless of how good the docs are or how sleek the project hosting pages are.
I like how most bigger projects are doing it nowadays: a separate page/mini-website, often using GitHub pages, that is user-centric and usually has a direct download link, and then GitHub for fellow developers.
You really don't go to GitHub and Bitbucket to download your favorite binary. That is what sourceforge, Top100 xyz, and Cnet is for.
The projects that are popular have people willing to help (read: contribute) to the project in classic open source engagement.
On top of that, GitHub & BitBucket enable the single/small group maintainer to write a readme that gets displayed.
I use both.
If your fav project doesn't have Mom+Pop friendly page with <download here> by all means please fork + contribute.
See:
http://documentcloud.github.com/backbone/
For a regular user (where "regular" depends on the type of software and the technical skill it requires), this is going way back to the days of source sharing on Usenet, way before the open-source term was mainstream (or even coined).
Please, an example.
Example: https://github.com/rack/rack homepage url points to http://rack.rubyforge.org/
https://github.com/tenderlove/nokogiri => http://nokogiri.org/
https://github.com/mxcl/homebrew => http://mxcl.github.com/homebrew/
https://github.com/joyent/node => http://nodejs.org/
etc, etc.
It also seems fairly common to put the 'consumer' url near the top or bottom of the README.
(That said, I agree pull requests would be cool.)
When a user thus opts for this functionality what then is the differential factor in comparing it to GitHub?
both can host project homepages in a variety of ways. GC gives you a navigable and clean and usable project landing page by default, while github makes you work a bit harder. neither service prevents you from doing what you want, but if you care about your non-developer users, you'll find better conversions using google code. fact.
to the OPs point, there is no reason why you can't make your GC project page have more content for developers. it is a wiki. everybody loves wikis.
the OP of this thread is clearly trolling, though.
-Issues? Github has that. -Wiki? Same.
I don't see anything feature wise that Google brings to the table that GitHub or Bitbucket doesn't out of the box or manually with even greater control.
I really want to understand what the issues are, help me understand.
i've run svn gc projects, and projects on github, and found the gc stack to be generally more robust, cohesive, flexible, and methodically designed. ex: compare the rich functionality of the gc issue tracker to github and you'll find them incomparable. or, create a project and browse the "advanced" tab of your project and you'll probably find you have more control than it feels like, with little effort.
regarding "can actually host content" - prolly a red herring because both let you host content. they just present a different ui for it.
http://mxcl.github.com/homebrew/
Are there any non-google sites that do this on google code? As far as I can tell, all of them look like this:
Which is fine, but I'd hardly say that a new user would find that less daunting than the Homebrew page. There's a lot going on, and it's trying to cater to both people who want to use waf and people who want to work on waf.
the contents of your repositories are hosted available at projectname.googlecode.com, and you can serve HTML just like you can code. example: http://json-template.googlecode.com/svn/trunk/doc/On-Design-...
the urls are not as nice but github's aren't great either.
I still find Github's detached gh-pages branches to be really clever and convenient.
Personally my projects are still on Google code, but Github is becoming more and more tempting.
Plus, you really get this feeling of activity while browsing projects and code on GitHub. Google Code and SourceForge seem so abandoned in comparison.
1. I get much more engagement from random developers on Github. On Github, random people will fork and add features, do code reviews and leave comments. All of these things are technically possible on Google Code but nobody does it—probably due to the usability but possibly also a cultural problem. Github has a strong culture of collaboration because they strongly emphasize it in the user's experience.
2. Managing forks and pull requests is easier on Github. I want my life as a maintainer to be as easy as possible.
3. Notifications: For a long time, Google Code notifications simply didn't work for me, at all. I'd randomly stumble on one of my older projects and noticed 5 new issues opened that I didn't know about, I felt like I betrayed my users for 6+ months. Now they seem like they do, but some trust has been lost.
4. Multiple choices of documentation markup on Github is appealing.
5. The code browsing feature on Google Code feels like its own application. When you open a Github project, first thing you see is the code. On Google Code it takes 2 more clicks (that's 1 more click than Bitbucket). Think about what's the most important thing here—the code, and Github got it right.
As far as version control goes, I'm happy with either Git or Mercurial.