I'm a little late to this party, it seems, but I wanted to throw in my vote.

> 1. The web site
> 2. Trac
> 3. Wiki
> 4. Repositories
> 5. Buildbot
> 6. Mailing lists
>

I think these + code review make for a pretty good list, and I'd fight
hard to claim code review integrated with a bug tracker should be a
requirement. Personally, I'm a big +1 on moving everything to either
github or code.google.com, which seems like the best of the choices.
If people really think the geographic restrictions are a problem, I
guess I'm fine with dropping code.google.com off the list -- but just
for the sake of completeness, are there any features code.google.com
has that github doesn't? (Or vice-versa?) Are they things we'd ever be
likely to notice?

I'm also more than happy to switch to git for Cython, especially in
light of the hg-on-git stuff Dag mentioned. My sense is that github
definitely seems to be the "new hotness" -- I'll admit that there's
something about this I don't "get," but if that just means more people
might notice Cython, I'd say that's a win. I have one or two questions
to put out there:

 * Does github have any sort of mailing list support? I'd love to see
cython-dev migrated to something with better searchability, linking,
archives, etc -- I don't know that there's any special link between
google groups and code.google.com, so this is really orthogonal to the
project hosting question. I know the decision to use codespeak was
made as an explicit decision against google groups, but my
understanding is that whatever objections there were are now gone. Is
that still the case?

 * 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.)

 * Are there a bunch of examples of projects that host basically
everything out of github? I'd be curious to check one out, just for
the sake of it.

 * 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?

-cc
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to