2 ms·
If I click on the source tab, I want to see the source. Great, so there's one extra click to get to it. And even that is only because we consciously chose to
by mindcrime 14y ago
If I click on the source tab, I want to see the source.
Great, so there's one extra click to get to it. And even that is only because we consciously chose to use Google Code to serve as the "project/community home" because GitHub is lousy at serving as that. Of course, all this was setup before GitHub Pages, IIRC. We could look into scrapping the Google Code presence now, probably, but it's a fairly low priority relative to about a bazillion other things.
GitHub gets this right. Google just presents you with boilerplate garbage.
To be fair to Google Code, they do support git, and keeping a reference to Subversion was a conscious decision that we made. You may hate Subversion with a passion, but not everybody does.
Anyway, the point is, with GitHub, by default, ALL you get is "the source tab". But there's a lot more to a project than just source code.
... GitHub are examples of how to organize the user experience better.
GitHub may be better from strictly a "how to get my hands on the source" perspective, but I think it's very weak from the "How do I get an overview of the project and the community as a whole" perspective.