Hi, > I agree with Gianluca. If it was my repo, I'd have it on my own > site.
Is that for autonomy reasons? If so, would hosting a fairly-constantly- updated read-only backup of the gitorious repo help? > But you're the lead, Chris, and I don't really care where the > trunk lives ;). But on the other hand, you've made far more commits than anyone else, so we shouldn't pick a scheme that discourages you. I'm interested in organizing contributions only to the extent that it means more of them happen than would if I didn't. :-) > Gitorious hosting would encourage Gitorious integration though, > which would definately help with mindshare once it happens. Yeah, that would be huge if we can pull it off somehow. Hopefully it won't require rewriting be in Ruby! Separately, I do think there's often a general increase in developer participation with these sites, whereby it becomes obvious that you don't need any permission to branch off and send a merge request. In a way, having your repo on Gitorious can be seen a general policy statement of "we want your code too, and it's easy to send it to us". > I'm not really sure what their features are good for, once you > get past "free hosting" and possibly greater visibility. Having > a single server would, for example, make it easier to auto-build > the Sphinx docs after every commit. There's an RSS feed for commits, so I agree it's harder, but not impossible. (They seem to be working on some "web hooks" scheme too.) > Are you suggesting moving to a joint trunk? I'm still a fan of > "pull what you want" development ;). No, not necessarily -- I was just suggesting that some of us could start sending it merge requests from (our own) gitorious repos rather than external ones, to see what we think of gitorious. Thanks, - Chris. -- Chris Ball <[email protected]> One Laptop Per Child _______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
