Re: [Distutils] Please don't impose additional barriers to participation (was: build system abstraction PEP)

2015-11-01 Thread Nick Coghlan
On 1 November 2015 at 02:08, Barry Warsaw wrote: > On Oct 29, 2015, at 10:52 PM, Marcus Smith wrote: > >>> If python-dev ends up adopting GitLab for the main PEPs repo, then we >>> should be able to move the whole process there, rather than needing to >>> maintain a separate copy. >>> >>will that

Re: [Distutils] Please don't impose additional barriers to participation (was: build system abstraction PEP)

2015-10-31 Thread Barry Warsaw
On Oct 29, 2015, at 10:52 PM, Marcus Smith wrote: >> If python-dev ends up adopting GitLab for the main PEPs repo, then we >> should be able to move the whole process there, rather than needing to >> maintain a separate copy. >> >will that be as open as pypa/interoperability-peps? if it's closed

Re: [Distutils] Please don't impose additional barriers to participation (was: build system abstraction PEP)

2015-10-30 Thread Brett Cannon
On Thu, 29 Oct 2015 at 22:53 Marcus Smith wrote: > > >> If python-dev ends up adopting GitLab for the main PEPs repo, then we >> should be able to move the whole process there, rather than needing to >> maintain a separate copy. >> > will that be as open as pypa/interoperability-peps? > Proof of

Re: [Distutils] Please don't impose additional barriers to participation (was: build system abstraction PEP)

2015-10-29 Thread Marcus Smith
> If python-dev ends up adopting GitLab for the main PEPs repo, then we > should be able to move the whole process there, rather than needing to > maintain a separate copy. > will that be as open as pypa/interoperability-peps? if it's closed off such that only python devs can log PRs against PEPs o

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread Paul Moore
On 28 October 2015 at 20:15, Ralf Gommers wrote: > It's the "Watch" button on the right top of > https://github.com/pypa/interoperability-peps Doh. Thanks. Paul ___ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/list

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread Ralf Gommers
On Wed, Oct 28, 2015 at 9:12 PM, Paul Moore wrote: > On 28 October 2015 at 18:44, Donald Stufft wrote: > > On October 28, 2015 at 2:42:19 PM, Paul Moore (p.f.mo...@gmail.com) > wrote: > >> > >> [1] If I'm supposed to be getting notifications for comments on the PR > >> (as a member of the PyPA g

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread Paul Moore
On 28 October 2015 at 18:44, Donald Stufft wrote: > On October 28, 2015 at 2:42:19 PM, Paul Moore (p.f.mo...@gmail.com) wrote: >> >> [1] If I'm supposed to be getting notifications for comments on the PR >> (as a member of the PyPA group, shouldn't I be?) then it's not >> happening... I know I can

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread Donald Stufft
On October 28, 2015 at 2:42:19 PM, Paul Moore (p.f.mo...@gmail.com) wrote: > > [1] If I'm supposed to be getting notifications for comments on the PR > (as a member of the PyPA group, shouldn't I be?) then it's not > happening... I know I can subscribe to the PR, but I'm not clear why I > should

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread M.-A. Lemburg
On 28.10.2015 19:33, Ian Cordasco wrote: > On Wed, Oct 28, 2015 at 3:31 AM, M.-A. Lemburg wrote: >> On 28.10.2015 06:02, Ben Finney wrote: >>> Marcus Smith writes: >>> 1) *Please*, *please*, *please* let's start doing PEP conversations as PRs to pypa/interoperability-peps : ) >>> >>> Pl

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread Paul Moore
On 28 October 2015 at 18:27, Ionel Cristian Mărieș wrote: > On Wed, Oct 28, 2015 at 10:31 AM, M.-A. Lemburg wrote: >> >> I agree with Ben. Discussions on PEPs need to happen on mailing lists, >> not hidden away on some issue tracker or PR ticket. > > > I think some balance is needed here. Every s

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread Paul Moore
On 28 October 2015 at 18:33, Ian Cordasco wrote: > Also nothing precludes mailing list discussions, so without details > about your objections, I don't see why this should be held up. One immediate question - not at all FUD, nor intended as provocative, it's a genuine question. I thought right n

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread Ian Cordasco
On Wed, Oct 28, 2015 at 3:31 AM, M.-A. Lemburg wrote: > On 28.10.2015 06:02, Ben Finney wrote: >> Marcus Smith writes: >> >>> 1) *Please*, *please*, *please* let's start doing PEP conversations as >>> PRs to pypa/interoperability-peps : ) >> >> Please keep the conversation on a mailing list where

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread Ionel Cristian Mărieș
On Wed, Oct 28, 2015 at 10:31 AM, M.-A. Lemburg wrote: > I agree with Ben. Discussions on PEPs need to happen on mailing lists, > not hidden away on some issue tracker or PR ticket. > ​I think some balance is needed here. Every so often discussions on the mailing list get so disorganized and sli

Re: [Distutils] Please don't impose additional barriers to participation (was: build system abstraction PEP)

2015-10-28 Thread Nick Coghlan
On 28 Oct 2015 09:32, "Marcus Smith" wrote: > > my intention certainly wasn't to try to exclude anybody. for me, it's the practical matter of the PR UI being more effective than a mailing list thread (in this case referring to a gist), and that we can track proposals easier and link to them from

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-28 Thread M.-A. Lemburg
On 28.10.2015 06:02, Ben Finney wrote: > Marcus Smith writes: > >> 1) *Please*, *please*, *please* let's start doing PEP conversations as >> PRs to pypa/interoperability-peps : ) > > Please keep the conversation on a mailing list where one can participate > without needing to sign up with any pa

Re: [Distutils] Please don't impose additional barriers to participation (was: build system abstraction PEP)

2015-10-28 Thread Marcus Smith
my intention certainly wasn't to try to exclude anybody. for me, it's the practical matter of the PR UI being more effective than a mailing list thread (in this case referring to a gist), and that we can track proposals easier and link to them from issues (in that same repo) and other PyPA docs.

Re: [Distutils] Please don't impose additional barriers to participation

2015-10-27 Thread Ben Finney
Robert Collins writes: > On 28 October 2015 at 18:02, Ben Finney wrote: > > Please keep the conversation on a mailing list where one can > > participate without needing to sign up with any particular service > > provider. > > One has to sign up with the mailing list, so there's no functional > d

Re: [Distutils] Please don't impose additional barriers to participation (was: build system abstraction PEP)

2015-10-27 Thread Robert Collins
On 28 October 2015 at 18:02, Ben Finney wrote: > Marcus Smith writes: > >> 1) *Please*, *please*, *please* let's start doing PEP conversations as >> PRs to pypa/interoperability-peps : ) > > Please keep the conversation on a mailing list where one can participate > without needing to sign up with

[Distutils] Please don't impose additional barriers to participation (was: build system abstraction PEP)

2015-10-27 Thread Ben Finney
Marcus Smith writes: > 1) *Please*, *please*, *please* let's start doing PEP conversations as > PRs to pypa/interoperability-peps : ) Please keep the conversation on a mailing list where one can participate without needing to sign up with any particular service provider. Your proposal would hav