On Thu, Nov 18, 2010 at 12:13 AM, Craig Citro <[email protected]> wrote: > * Has anyone actually been an admin on a github project? The tools > sure sound good from the outside, but are they fairly pleasant to use? > Trading writing our own apache configs for regularly fighting with, > say, flaky web interfaces is decidedly *not* a win. (I've done some > minor admin on a code.google.com project, and generally had good > experiences.)
Modulo my irritation with their bug tracker, everything else so far has been pretty pleasant. And I guess I also dislike their default gh-pages implementation, but as indicated above, the workaround was so easy that I don't think about it anymore. > * I do have one minor worry about github, which may have something to > do with me not understanding why it's such a phenomenon. The whole > model seems to really take the D in DVCS to the extreme -- so much so > that I often have a hard time deciding what the "central" repo for a > project is (in cases where there is such a thing) just based on what I > see on github, or how to get there when I happen to end up in a random > person's branch (say from a google search). My vague impression is > that the model for code.google.com is "project-centric," whereas the > github model is much more "developer-centric." Is there something I'm > missing? This was a very real issue, but their implementation of 'organizations' is extremely good, and takes care of it. IPython for example is an organization: http://github.com/ipython/ that hosts the official ipython repo: http://github.com/ipython/ipython/ It has teams, repos, and permissions can be assigned to teams as needed. The setup is very, very easy and pleasant to work with. It's similar to launchpad's project/team concept but actually done right: LP allowed the Unix user/group permission model leak out into their website design, and it's a disaster (you can't assign individuals permissions to share a branch without making a whole new team -aka Unix group- for it). In contrast, github's organization setup makes it very easy to have separate repos in a project (say core development, website sources, old branches, etc), have separate teams that work on each repo, and have the individual developers keep their personal branches from which they do pull requests into the official repo. HTH, f _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
