<div class="gmail_quote">On Fri, Jul 1, 2011 at 8:00 PM, Kevin Horn <span dir="ltr"><<a href="mailto:kevin.horn@gmail.com">kevin.horn@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div> * Does Github's ticketing system have the kind of integration with Git <br> that Twisted has built for Trac+SVN? Bitbucket has some similar stuff, <br>
so I would be surprised if Github didn't, but I just don't know.<br></div></div></blockquote><div><br>Stuff like refs/closes interacts with the ticketing system yes. You can have as many hooks as you like for topfiles.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div> * Git is annoying. It's a pretty horrible piece of software in my <br>
opinion, and made some bad design decisions.<br></div></div></blockquote><div><br>magit makes it a lot more pleasant if you use emacs, by the way.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div> * Git essentially makes Windows a second-class environment (as did <br> Combinator). We already have trouble recruiting Windows people, and <br> IMO one of Twisted's strengths is that you can usually run things on <br>
Linux/MacOSX/Windows with very few cahnges, if any.<br></div></div></blockquote><div><br>I've been told this has *vastly* improved, but I don't know for sure since I'm not a Windows user.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div> * For me, Bitbucket has always been pretty comparable to Github. I know <br> others will disagree, and point out all kinds of features that Github <br> has over Bitbucket, but apparently I never use those features. Perhaps<br>
those features (whatever they are) are more important in projects<br> of Twisted's size and/or history.<br></div></div></blockquote><div><br>Yes, many features are comparable, the main feature differences are polish, but the killer difference is community size.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div> * I have been told, but not actually experienced, that using the hg-git <br>
plugin for Mercurial makes using Git for your repository into "an<br>
implementation detail", and the user basicaly doesn't even really <br> have to care that they aren't using Hg. If true, this would make me <br> pretty happy...but I'm not entirely sure that it _is_ true.<br>
</div></div></blockquote><div> </div><div>Although I've never tried this, I've been assured this is the case.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div> * it is unclear how Github would work with UQDS with regards to having a <br> ticket for all new work. IMO this is even more important than code <br> reviews. Would we just say: no pull requests will be accepted unless<br>
</div></div></blockquote><div><br>Your question got cut off. I think you wanted to say "there's a ticket for that"?<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div>
* How would running buildbot over a git/bzr/hg branch work? Would Github's <br> hooks be able to drive this? Would we be able to tell buildbot to "go <br> run tests on this branch"?<br></div></div></blockquote>
<div><br>Although I've never tried this, I've been assured this is the case.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div> <br> * Assuming a change like this would take place, what would the plan be <br>
for transition? Would all the branches that are out there be <br> migrate-able? What about all the Trac tickets, wiki, etc?<br></div></div></blockquote><div><br>The first thing I thought right after I thought "we're going to need a trac to markdown converter" is "khorn is going to jump off a cliff next" ;-)<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div><br> * How does this affect the Sphinx transition plan? (I don't really know <br>
that it would affect it at all...).<br></div></div></blockquote><div><br>I don't see how it would. <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div> <br> * Since Twisted's current web presence _is_ a Trac site, who's going to <br> step up and build a new website? Github/Bitbucket/Launchpad is _NOT_<br> a replacement for an actual "marketing" or "home page" type site.<br>
<br></div></div></blockquote><div>Absolutely not. I am *not* advocating replacing this site, simply having something similar that isn't trac and isn't involved in the site development. If anything, this separates the concerns of "home page style site" and development site even clearer, IMO.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div>Overall, this is probably a good plan, but it's going to bea harder and take <br>
more work than people think.<br><br>Also, I agree with Itamar's comments that while switching to a DVCS might <br>ameliorate Twisted's social/organizational issues somewhat, but is unlikely <br>
to wholly fix them. That stuff needs to be discussed and worked on as well.<br></div></div></blockquote><div><br>There's no silver bullet. Not making new potential contributors bend over, and having all contributions trivially easy to put in version control, regardless of their contributor status, sounds like a good start.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div><br>Kevin Horn <br></div></div><br></blockquote></div>
cheers<div>
lvh</div><br>