Pretty much all of those can be supported with GitHub: they can POST to a generic website as a commit hook[0], along with a number of other integrated services[1].
The only thing that I can think of is that GitHub issues doesn't have hooks, so we'd have to poll if we wanted an IRC bot for GitHub issues. Thankfully, they have an API for issues[2] that should make it easier. re: Mercurial, I didn't like it when I used it. If someone can tell me how to do this[3] in hg, I'd be more inclined to play along. And that said, I think we'd get a much better reception and amount of contributors if we're on GitHub, if only due to the scale compared to LP/BB. I think we're all familiar with the "denied" story :). On Tue, Jul 5, 2011 at 2:49 AM, Tim Allen <screwt...@froup.com> wrote: > On Tue, Jul 05, 2011 at 09:41:12AM +0300, anatoly techtonik wrote: >> To know if Github is terrible or not, you need some data - examples, >> use cases. The first step in planning is to look at the current >> workflow and gather a list of ways current Trac+SVN is used and see >> where Github has advantages and where it suxx. Usually, people realize >> the latter when it's too late. > > As has been mentioned in earlier in this thread: > > http://twistedmatrix.com/trac/wiki/WorkflowRequirements > > (which I have updated with some of the website requirements that Glyph > mentioned in one of his posts). > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > [0] http://help.github.com/post-receive-hooks/ [1] https://github.com/github/github-services [2] http://developer.github.com/v3/issues/ [3] http://people.gnome.org/~federico/news-2008-08.html#git-rebase-interactive -- Jasper _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python