Re: [Twisted-Python] Twisted on PyPI

On 02:19 am, gl...@twistedmatrix.com wrote: On Jun 1, 2013, at 5:00 AM, exar...@twistedmatrix.com wrote: Well, someone seems to have done so now, though I don't see how to find out who or when from the PyPI user interface. As I said in my message, it was Thomas; if that's ambiguous, I meant T

[Twisted-Python] github, again

Hi Twisted developers, This weekend I had a discussion with many Twisted developers, both local to and visiting San Francisco. The topic came up of how to get more long-term contributors to participate more regularly in the project - particularly, doing code reviews, but also, developing and c

Re: [Twisted-Python] github, again

Hi Glyph, That is great news. I already helped with Braid and would be interested in contributing some work in this area. Cheers, Jonathan On Jun 3, 2013, at 16:59, Glyph wrote: > Hi Twisted developers, > > This weekend I had a discussion with many Twisted developers, both local to > and vi

Re: [Twisted-Python] github, again

On 2013-06-03 22:59, Glyph wrote: Hi Twisted developers, [..] > One suggestion that almost everybody made immediately was: we should use Github for code reviews. As mentioned on IRC, the only comment I have is about the lack of proper e-mail addresses associated with commits. Tom is investi

Re: [Twisted-Python] github, again

Am 03.06.2013 22:59, schrieb Glyph: > Another objection is that Github is proprietary software, and an > externally-maintained service that we'd be depending upon. > > One solution to the "proprietary software" thing is the availability of > the MIT-licensed . It's a largely fe

Re: [Twisted-Python] github, again

On Mon, Jun 3, 2013 at 3:59 PM, Glyph wrote: > > One suggestion that almost everybody made immediately was: we should use > Github for code reviews. > I'm +1 on the whole proposition as described. Finally, my own minor concern: Github has no notion of a "code review" as a > unit of work. A pul

Re: [Twisted-Python] github, again

Hi, On Mon, Jun 3, 2013 at 4:48 PM, Christopher Armstrong wrote: > On Mon, Jun 3, 2013 at 3:59 PM, Glyph wrote: >> One suggestion that almost everybody made immediately was: we should use >> Github for code reviews. > > I'm +1 on the whole proposition as described. Me too. >> Finally, my own m

Re: [Twisted-Python] github, again

On Jun 3, 2013, at 5:35 PM, Jamu Kakar wrote: > Hi, > > On Mon, Jun 3, 2013 at 4:48 PM, Christopher Armstrong > wrote: >> On Mon, Jun 3, 2013 at 3:59 PM, Glyph wrote: >>> One suggestion that almost everybody made immediately was: we should use >>> Github for code reviews. >> >> I'm +1 on the

Re: [Twisted-Python] github, again

Christian Kampka writes: > Although gitlab is great for internal projects, this lack of a proper > support for public features makes it imo not that suitable for open > projects. Sorry to butt in, but to add to this Gitlab doesn't support the "fork and pull request" model of GitHub -- instead th

Re: [Twisted-Python] github, again

I sent most of the below off-list to Glyph earlier, as my comments were a bit half-assed and I'm not really (or not at all) a Twisted contributor. Glyph suggested I mail them to the list anyway, and to try adding some more concrete reasons for being +1 on the suggested change. --- [ Original mail

Re: [Twisted-Python] github, again

On Mon, Jun 3, 2013 at 8:48 PM, meejah wrote: > > It sounds like aspects of this are currently in the latest stuff, > however, so it might work like github in this respect "soon": > > https://github.com/gitlabhq/gitlabhq/pull/3597 > > Whoah. Did anyone else notice that "coveralls" bot? that is p

Re: [Twisted-Python] github, again

Hi, what about Bitbucket (www.bitbucket.org) and mercurial ? Don't they provide the same features ? I'm asking because we are in Python land. ;-) Regards, Wolfgang ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twisted