The steering council has implemented a new idea called sponsors to the PEP
process (added in
https://github.com/python/peps/commit/c58d32c33bd06eb386d3f33963a1434510528f68).
The thinking is that to help make sure PEPs from non-core developers
receive appropriate guidance through the PEP process, a
Does this apply to existing draft PEPs or only new ones?
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Hi,
Le mar. 5 mars 2019 à 02:53, Brett Cannon a écrit :
> The steering council has implemented a new idea called sponsors to the PEP
> process (...). The thinking is that to help make sure PEPs from non-core
> developers receive appropriate guidance through the PEP process (...)
Hum, this isn'
> because if a single core dev won't sign on to help then what chance does
the PEP have of being accepted?
If this is the justification, then I feel like it is a barrier that could
be disassembled, rather than one people need to be granted permission to
climb over.
I am named on one PEP with two
On 2019-03-05 14:05, Calvin Spealman wrote:
I'm worried this creates a gatekeeping perception that will scare away
contributors.
+1
I also expressed this worry at https://github.com/python/peps/pull/903
You could keep the positive part of the sponsoring idea (somebody acting
as mentor) but d
I have to say, this is sort of surprising for what seems like the first
official action of the steering committee. Are there really *that many *PEPs
that a team that is now, what, 5x the size of the BFDL model is worried
that they'll be able to keep up? As a long-time lurker, this hardly seems
to
On 05Mar2019 0620, James Edwards wrote:
I have to say, this is sort of surprising for what seems like the first
official action of the steering committee. Are there really /that many
/PEPs that a team that is now, what, 5x the size of the BFDL model is
worried that they'll be able to keep up?
On Mon, Mar 4, 2019 at 10:13 PM Jeroen Demeyer wrote:
> Does this apply to existing draft PEPs or only new ones?
>
Only new ones; this is not retroactive.
-Brett
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailm
On Tue, Mar 5, 2019 at 5:33 AM Jeroen Demeyer wrote:
> On 2019-03-05 14:05, Calvin Spealman wrote:
> > I'm worried this creates a gatekeeping perception that will scare away
> > contributors.
>
It might, but if people are not prepared properly for the PEP process then
it's best to spare them and
On Tue, Mar 5, 2019 at 3:36 AM Victor Stinner wrote:
> Hi,
>
> Le mar. 5 mars 2019 à 02:53, Brett Cannon a écrit :
> > The steering council has implemented a new idea called sponsors to the
> PEP process (...). The thinking is that to help make sure PEPs from
> non-core developers receive approp
On 2019-03-05 18:14, Steve Dower wrote:
However, if you don't have
*a single* core developer on board from python-ideas, chances are the
whole team is going to reject the proposal.
Sure, I couldn't agree more. But this is something that a PEP mentor
(instead of sponsor) also could deal with. A
On Tue, Mar 5, 2019 at 11:59 AM Jeroen Demeyer wrote:
> On 2019-03-05 18:14, Steve Dower wrote:
> > However, if you don't have
> > *a single* core developer on board from python-ideas, chances are the
> > whole team is going to reject the proposal.
>
> Sure, I couldn't agree more. But this is som
On Wed, Mar 6, 2019 at 7:41 AM Brett Cannon wrote:
>
>
>
> On Tue, Mar 5, 2019 at 11:59 AM Jeroen Demeyer wrote:
>>
>> On 2019-03-05 18:14, Steve Dower wrote:
>> > However, if you don't have
>> > *a single* core developer on board from python-ideas, chances are the
>> > whole team is going to rej
On 05Mar2019 1245, Chris Angelico wrote:
How much effort does it take to sponsor a PEP? I'm not a core dev, but
I can help someone with the work of writing and publishing. So if, in
that hypothetical situation, some (very busy) core dev were willing to
say "yeah, go ahead, put my name on it", wou
On Tue, Mar 5, 2019 at 9:04 PM Steve Dower wrote:
> On 05Mar2019 1245, Chris Angelico wrote:
> > How much effort does it take to sponsor a PEP? I'm not a core dev, but
> > I can help someone with the work of writing and publishing. So if, in
> > that hypothetical situation, some (very busy) core
Just to clarify a key point here which is covered in PEP 1 but based on
offline conversations is being missed, the need for a sponsor only kicks in
for committing it to the peps repo which typically kicks in when
transitioning from python-ideas to python-dev (although if one gets a
sponsor sooner t
As a non core-dev, my enthusiasm for submitting a pep has been diminished
by some 40%.
yours,
Abdur-Rahmaan Janhangeer
http://www.pythonmembers.club | https://github.com/Abdur-rahmaanJ
Mauritius
___
Python-Dev mailing list
Python-Dev@python.org
https://
On Mar 6, 2019, at 10:28, Abdur-Rahmaan Janhangeer wrote:
>
> As a non core-dev, my enthusiasm for submitting a pep has been diminished by
> some 40%.
I’m sorry to hear that.
I think it’s worth keeping in mind that successfully navigating the PEP process
can be quite daunting an demoralizing
i think that "should have at least a mentor guiding you" sounds a lot more
better than
a core developer needs to sign on to be a sponsor
that sounds a lot more that without backing, you can't submit a pep, i
guess the core devs wanted to make things easier but the sponsor thing etc
put me off.
f
On Wed, Mar 6, 2019 at 8:58 PM Abdur-Rahmaan Janhangeer <
arj.pyt...@gmail.com> wrote:
> i think that "should have at least a mentor guiding you" sounds a lot more
> better than
>
> a core developer needs to sign on to be a sponsor
>
> that sounds a lot more that without backing, you can't submit
thon-Dev list=sdamon@python.org> On Behalf Of Brett Cannon
> Sent: Monday, March 4, 2019 8:44 PM
> To: python-dev
> Subject: [Python-Dev] PEPs from non-core devs now need a sponsor
>
> The steering council has implemented a new idea called sponsors to the PEP
> process (added
On 3/8/19 8:09 AM, Alex Walters wrote:
> I'm confused about this. Didn't you need someone with merge permissions
> already to merge a pep into the pep repo? Isn't this just adding a layer of
> paperwork to something that was already the case for all practical purposes?
>
>
I would say the diffe
On Fri, Mar 8, 2019 at 5:46 AM Richard Damon
wrote:
> On 3/8/19 8:09 AM, Alex Walters wrote:
> > I'm confused about this. Didn't you need someone with merge permissions
> already to merge a pep into the pep repo? Isn't this just adding a layer
> of paperwork to something that was already the ca
23 matches
Mail list logo
