I'm sorry, I seem to have accidentally licked a cookie [1] here. I'm still
keen to see this happen and to be a part of it, and have been trying to be
find the spoons to take the lead on organizing, but it's been a few weeks
now and that hasn't happened yet [2].
Does anyone else want to take the le
> Hmm, I don't think it is should be our (CPython) responsibility to keep
> track and maintain the list of the core devs of alternate Python
> implementations. Don't they have their own community / website? They have
> their own repo, bug tracker, governance model, and everything, right?
>
Core de
On 8/1/2018 8:32 PM, Mariatta Wijaya wrote:
I think it would also be a good idea to include core developers
of other Python implementations in such a document, in
separate sections, e.g. for Jython, IronPython, PyPy,
Stackless, etc
Hmm, I don't think it is should be our (CPython
On Wed, Aug 1, 2018 at 8:29 PM Mariatta Wijaya
wrote:
[..]
> Please don't misunderstand my wanting to set up a deadlines and process as
> wanting to rush things.
Absolutely, I understand, I didn't want to imply that "[name] is
rushing the process". Sorry if I sounded this way. I do have an
impre
>
> I think it would also be a good idea to include core developers
> of other Python implementations in such a document, in
> separate sections, e.g. for Jython, IronPython, PyPy,
> Stackless, etc
Hmm, I don't think it is should be our (CPython) responsibility to keep
track and maintain the list
>
> IIRC we always promoted core devs by popular vote, so I don't think
> this would be a problem. Do we have any candidates that are currently
> waiting for us deciding on a governance model?
If this new governance model will include core devs being able to vote on
PEPs, then I will have differ
On Wed, Aug 1, 2018 at 6:44 PM Mariatta Wijaya
wrote:
>
>
> Thank you for the responses and concerns.
>
> I do want to keep this discussion open and ongoing, and I still think that we
> do need a set deadline on things.
I talked to a few core developers recently (at EuroPython and over
messenger
Thank you for the responses and concerns.
I do want to keep this discussion open and ongoing, and I still think that
we do need a set deadline on things.
Currently any undecided PEP is stalled, and no one can pronounce on them.
And we probably won't/can't promote any new core devs until we have ne
On Wed, Aug 1, 2018 at 5:26 PM Nathaniel Smith wrote:
[..]
> Now we have to figure that out: the legitimacy of any new governance
> system is ultimately going to have to rest on the consensus of the
> core devs. The only way I know to get that is by taking the time to
> work through the difficult
Hello,
I may be missing something, but I fail to view the "tests" log in this
failed CI build:
https://python.visualstudio.com/cpython/_build/results?buildId=20701&view=logs
Regards
Antoine.
___
python-committers mailing list
python-committers@python
On Wed, Aug 1, 2018 at 3:44 PM M.-A. Lemburg wrote:
> On 01.08.2018 23:28, Mariatta Wijaya wrote:
> > See also an open issue to revamp the Developer log:
> > https://github.com/python/devguide/issues/390
> >
> > Someone has also said that they're working on tracking down the dormant
> > core devs,
On 01.08.2018 23:28, Mariatta Wijaya wrote:
> See also an open issue to revamp the Developer log:
> https://github.com/python/devguide/issues/390
>
> Someone has also said that they're working on tracking down the dormant
> core devs, but now I can't find that email.
I think the log is fine at it
Le 01/08/2018 à 23:31, Jack Diederich a écrit :
> https://hg.python.org/committers.txt
Probably outdated, for example Pablo Salingo Salgado doesn't seem there.
Regards
Antoine.
>
> On Wed, Aug 1, 2018 at 5:28 PM, Mariatta Wijaya
> mailto:mariatta.wij...@gmail.com>> wrote:
>
> See also a
https://hg.python.org/committers.txt
On Wed, Aug 1, 2018 at 5:28 PM, Mariatta Wijaya
wrote:
> See also an open issue to revamp the Developer log:
> https://github.com/python/devguide/issues/390
>
> Someone has also said that they're working on tracking down the dormant
> core devs, but now I can
I think Nathaniel and Marc-André are speaking wisely here.
Sorry, I've not much to add ;-)
Regards
Antoine.
Le 01/08/2018 à 23:22, Nathaniel Smith a écrit :
> On Wed, Aug 1, 2018 at 12:41 PM, Mariatta Wijaya
> wrote:
>> Since this is like a CFP I figured we should clarify what's expected the
See also an open issue to revamp the Developer log:
https://github.com/python/devguide/issues/390
Someone has also said that they're working on tracking down the dormant
core devs, but now I can't find that email.
Mariatta
On Wed, Aug 1, 2018 at 2:15 PM M.-A. Lemburg wrote:
> It's become fair
On Wed, Aug 1, 2018 at 12:41 PM, Mariatta Wijaya
wrote:
> Since this is like a CFP I figured we should clarify what's expected the
> proposal, and I also wanted to be more detailed in the timeline.
>
> Oct 1 00:00:00 UTC: Deadline of coming up with proposals of governance
> model.
>
> To be includ
It's become fairly obvious that we are missing a list of core
developers on some site. One we can use as reference and one
which core devs can also show to other to prove they are
core developers.
I guess the natural place for such a list is the dev guide,
but we could also use a page on www.pytho
Thanks for your action plan, Mariatta, but I'm -1 on having
strict timelines for these processes.
We need to gradually approach a new model as we've done in the
past decades and not push for any possibly borked model right from
the start. The processes for this need to stay flexible, easy
to adapt
Thanks! AoE timezone works for me.
In that case, let's use AoE instead of UTC.
Mariatta
On Wed, Aug 1, 2018 at 1:36 PM Thomas Wouters wrote:
>
>
> On Wed, Aug 1, 2018 at 12:42 PM Mariatta Wijaya
> wrote:
>
>> 2. Are people ok UTC timezone?
>>
>
> FYI, for the PSF elections and similar deadlin
On Wed, Aug 1, 2018 at 12:42 PM Mariatta Wijaya
wrote:
> 2. Are people ok UTC timezone?
>
FYI, for the PSF elections and similar deadlines, we use the AoE timezone:
https://www.timeanddate.com/time/zones/aoe -- it makes it harder for people
to miss the deadline for timezone reasons.
--
Thomas
Since this is like a CFP I figured we should clarify what's expected the
proposal, and I also wanted to be more detailed in the timeline.
*Oct 1 00:00:00 UTC:* Deadline of coming up with proposals of governance
model.
To be included in the proposal:
- explanation and reasoning of the governance m
22 matches
Mail list logo
