Re: [Python-Dev] PEPs from non-core devs now need a sponsor
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 then great as getting mentoring on how to handle the process is always beneficial) . This should not be a barrier to presenting an idea or writing up a proto-PEP for python-ideas if people are too shy to ask upfront for a sponsor until their idea shows merit (and remember that we already ask people to fork the peps repo and get feedback on their proto-PEPs in their own fork instead of in the official repo). Nor should this impact slow-burning ideas which people have to warm up to as that typically happens before a PEP is written anyway. I also don't see this preventing PEPs written to be explicitly rejected either. I personally am happy to sponsor such PEPs as I'm sure several other core devs are as well. On Mon, Mar 4, 2019 at 5:43 PM Brett Cannon wrote: > 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 core developer > needs to sign on to be a sponsor of the PEP. Being a sponsor does *not* > preclude the core dev from eventually becoming a co-author or BDFL-delegate > later on (but obviously not both), but the expectation is the sponsor is > supportive of the idea (because if a single core dev won't sign on to help > then what chance does the PEP have of being accepted?). > > If this doesn't turn out well we can obviously revert this, but hopefully > this will make things smoother for those who are new to the PEP process. > ___ 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
Re: [Python-Dev] PEPs from non-core devs now need a sponsor
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://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] PEPs from non-core devs now need a sponsor
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 at times. I wish that weren’t the case, and it was certainly not the intention when the PEP process was originally designed, but Python is a large diverse community now, and a mature, slow moving language, so it’s rare that a great idea makes it through without contention. I think that the requirement to find a sponsor can help with that, regardless of whether the PEPable idea is ultimately accepted or rejected. Core devs generally have a pretty good sense of what it takes to get a PEP through the process, can provide encouragement when the millithreads get you down or overwhelmed, and can help short circuit the disappointment, time and emotional investment when the idea has a poor chance of being accepted. Many of our core devs have gone through it, with both outcomes, so their guidance can be very valuable. I like to think of the sponsor as a PEP mentor, although sponsors can of course have a range of involvement. Our core devs want you to succeed (or conversely save you from wasting your time), and they’ve been there, done that. Core dev sponsors can be a great resource for folks new to the process. Cheers, -Barry signature.asc Description: Message signed with OpenPGP ___ 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
Re: [Python-Dev] PEPs from non-core devs now need a sponsor
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. for someone using py, ideas sometimes come but since i've not yet submitted a pep, when i see a change in the flow, i ask: will it be easier or more difficult to submit peps now? i really got the impression that now chances are slimmer. great idea that core mentors now volunteer to guide peps, sorry for trouble. yours, Abdur-Rahmaan Janhangeer http://www.pythonmembers.club | https://github.com/Abdur-rahmaanJ Mauritius ___ 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
Re: [Python-Dev] PEPs from non-core devs now need a sponsor
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 a pep, i > guess the core devs wanted to make things easier but the sponsor thing etc > put me off. > for someone using py, ideas sometimes come but since i've not yet > submitted a pep, when i see a change in the flow, i ask: will it be easier > or more difficult to submit peps now? i really got the impression that now > chances are slimmer. > Before submitting a PEP one (including core-devs) usually starts a discussion on python-dev/ideas in order to start collecting feedback and, most importantly, to figure out whether the idea deserves a PEP or not (often times it doesn't). If the proposal is good it means somebody agreed with you: those persons are likely gonna be the ones who'll likely sponsor your PEP. If you can't find such a person immediately and the idea received positive feedback I imagine you'll just be asked to write a proto-PEP first, and if that is good enough somebody will eventually sponsor it and possibly even help you. If you can't find any person then it probably means it wasn't such a good idea, and that's also good because it will save you from the trouble of writing the PEP in the first place (meeting the PEP quality standards is not exactly a piece of cake). I doubt we'll end up in a situation where a good proposal won't happen just because nobody is willing to sponsor it. -- Giampaolo - http://grodola.blogspot.com ___ 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
