On 2018-10-03 17:56, Wes Turner wrote:
The phrase "core developers and the BDFL"
is where some sort of alternate quorum/majority policy would need to be
specified if this is a contentious issue in practice?
The whole point of the process described in PEP 8000 is to make this
more precise. The
re: Updating the BDFL-Delegate policy (in PEP 1)
On Wednesday, October 3, 2018, Wes Turner wrote:
>
>
> On Saturday, September 22, 2018, Wes Turner wrote:
>
>> [...]
>>
>> https://devguide.python.org/#contributing
>>
>> https://devguide.python.org/experts/
>> - is there a different BDFL-delegat
On Saturday, September 22, 2018, Wes Turner wrote:
> Here are links to the Apache governance docs:
>
> https://www.apache.org/foundation/governance/#technical
>
> https://www.apache.org/foundation/governance/pmcs.html
>
> Which are the PSF docs for these exact same processes for open source
> gov
>> And now you made it sound even worse by insinuating that I don’t know the
>> language and maybe I’m not a part of the community.
>
> Anders, I'm sorry you feel that everyone is piling onto you.
Well a bit, but mostly I was just pointing out that the text I replied to
wasn’t thought out an
On 09/22/2018 05:52 AM, Anders Hovmöller wrote:
And now you made it sound even worse [...]
Their use of the word "you" is "everybody who wants to write a PEP", not
you "Anders Hovmöller" specifically. (Isn't English a wonderful
language? *sigh* )
--
~Ethan~
__
On Sat, Sep 22, 2018 at 8:52 AM Anders Hovmöller
wrote:
> >>> I think that entire paragraph made it sound even worse than what I
> wrote originally. It reads to an outsider as “if you don’t know what’s
> wrong I’m not going to tell you”.
> >
> > More like, if you're not sufficiently familiar with
On Sat, Sep 22, 2018 at 5:53 AM Anders Hovmöller
wrote:
>
>
> >>>
> >>> I think that entire paragraph made it sound even worse than what I
> wrote originally. It reads to an outsider as “if you don’t know what’s
> wrong I’m not going to tell you”.
> >
> > More like, if you're not sufficiently fam
>>>
>>> I think that entire paragraph made it sound even worse than what I wrote
>>> originally. It reads to an outsider as “if you don’t know what’s wrong I’m
>>> not going to tell you”.
>
> More like, if you're not sufficiently familiar with the community or
> the language,
And now you mad
Sorry, hit send too soon...
On Sat, 22 Sep 2018 at 13:24, Paul Moore wrote:
>
>
> On Sat, 22 Sep 2018 at 10:56, Anders Hovmöller wrote:
> >
> >
> >
> > > If one doesn't know who the senior developers are yet, she should think
> > > twice about whether she's ready to PEP anything. That's not a l
On Sat, 22 Sep 2018 at 10:56, Anders Hovmöller wrote:
>
>
>
> > If one doesn't know who the senior developers are yet, she should think
> > twice about whether she's ready to PEP anything. That's not a litmus
> > test; some PEPs have eventually succeeded though the proponent was new
> > to the pr
Here are links to the Apache governance docs:
https://www.apache.org/foundation/governance/#technical
https://www.apache.org/foundation/governance/pmcs.html
Which are the PSF docs for these exact same processes for open source
governance? (In re: to transitioning from BDFL is not dead, but)
htt
On Saturday, September 22, 2018, Wes Turner wrote:
>
> It seems like everything's fine, but I would have no idea, BTW
>
Would project boards be helpful for coordinating proposal status
information, or extra process for something that's already working just
fine?
https://github.com/python/peps/p
> If one doesn't know who the senior developers are yet, she should think
> twice about whether she's ready to PEP anything. That's not a litmus
> test; some PEPs have eventually succeeded though the proponent was new
> to the project development process.[2] But it's a lot less painful if
> you
Process suggestions that could minimize non-BDFL's BDFL legwork:
* https://github.com/python/peps
* https://github.com/pypa/interoperability-peps
* Use GitHub reactions for voting on BDFL delegates, PEP final approval,
and PEP sub issues?
* Specify a voting deadline?
* How to make a quorum ca
Executive summary: Writing a PEP is an inherently uncertain process.
Achieving "community consensus" is the goal of the process, not a
precondition.
Anders Hovmöller writes:
> In general pep1 is frustratingly vague. Terms like “community
> consensus” without defining community or what number
15 matches
Mail list logo
