[python-committers] Re: Please fill in your details in the canonical list of Python core team membership
You're right - "python/voters" is a private repo and you need access to be able to update the file. You could ask for access from Brett (or Benjamin or Georg or Donald or Antoine or Victor). If you don't want to bother, feel free to send me your details privately and I'll update the file for you. Cheers, Brian On Fri, Jul 26, 2019 at 7:10 PM PJ Eby wrote: > I do not appear to have access to that repository, and so cannot edit the > file. If the "everyone" who is to fill in their details is "everyone on > the previously posted list" or "everyone on python-committers", then > apparently not everyone has access to the repo. :-) > > On Fri, Jul 26, 2019 at 7:45 PM Brett Cannon wrote: > >> Since the discussion of how to define the canonical list of Python core >> team membership finished ( >> https://mail.python.org/archives/list/python-committers@python.org/thread/MIS3UESO6UIIULBCCMAZI5WVYZJPDE7R/), >> I have gone ahead and created the official list. >> >> EVERYONE, please go to >> https://github.com/python/voters/blob/master/python-core.toml and fill >> in your information (remember you can make changes through GitHub's web >> UI). Please note that the repository is private and so only fellow core >> developers or people with admin privileges to the Python org on GitHub can >> see that file (and if you're curious, it should be in reverse chronological >> order of joining the team). And everyone has information to fill in except >> Paul G. and myself (since I added Paul's details when I on-boarded him and >> I obviously knew all of my details :) . >> >> It is important you fill in your details. PEP 13 says active core team >> members get to vote, have commit access, etc. The plan is to automate >> adding/removing privileges when we calculate who has been active and so >> this info will be needed to do that, else empty data will lead to you >> losing access. FYI the latest this updating of privileges will occur is >> probably the next steering council election which is slated for October >> when 3.8.0 goes out. >> >> Here's a quick primer to what all the fields mean in the TOML file: >> >> - name: self-explanatory ;) (luckily this has turned out to be unique for >> everyone) >> - other_names: if you happened to have committed under multiple names >> (I've filled this in for everyone the best I could, so people shouldn't >> need to change this) >> - voting_address: the email address you want voting ballots sent to (this >> repo is private so use whatever email address you want; currently filled in >> based on your email address in the last steering council election) >> - joined: when you joined the core team; I did the best I could based on >> the developer log, and otherwise calculated it based on your first >> merge/commit >> - github: your GitHub username >> - bpo: your bugs.python.org username >> - discourse: your discuss.python.org username >> >> I'll also mention I created >> https://github.com/python/voters/blob/master/former-committers.md to >> keep a record of who has had access to the CPython repo but are not in the >> Python core team roster. >> >> Finally, next steps. With this list done my next plan is to write up a >> script to use git changes to calculate who has been active. After that I'll >> write code to take the list of active members and generate the voter roll >> for steering council elections. From there I'll write some code to generate >> a new developer log for the devguide with all private info stripped out >> (e.g. voting email address). Finally, code will be written to help >> automatically add/remove privileges for (in)active team members. >> ___ >> python-committers mailing list -- python-committers@python.org >> To unsubscribe send an email to python-committers-le...@python.org >> https://mail.python.org/mailman3/lists/python-committers.python.org/ >> Message archived at >> https://mail.python.org/archives/list/python-committers@python.org/message/VH3HSJMQ6GB27AL6747OFPB5YKLVNVDV/ >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> > ___ > python-committers mailing list -- python-committers@python.org > To unsubscribe send an email to python-committers-le...@python.org > https://mail.python.org/mailman3/lists/python-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/python-committers@python.org/message/MBYR7BQDDSFTVJ6YVQAC34WJWVJAW3CT/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/7HTUAQ7BNV5N7DLIZO2ZT7V7ARWEJOK7/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Please fill in your details in the canonical list of Python core team membership
Hey Brett, Should the people with "Privileges relinquished..." in their notes (e.g. https://github.com/python/voters/blob/master/python-core.toml#L1230) be in this list or in https://github.com/python/voters/blob/master/former-committers.md ? Cheers, Brian On Fri, Jul 26, 2019 at 4:46 PM Brett Cannon wrote: > Since the discussion of how to define the canonical list of Python core > team membership finished ( > https://mail.python.org/archives/list/python-committers@python.org/thread/MIS3UESO6UIIULBCCMAZI5WVYZJPDE7R/), > I have gone ahead and created the official list. > > EVERYONE, please go to > https://github.com/python/voters/blob/master/python-core.toml and fill in > your information (remember you can make changes through GitHub's web UI). > Please note that the repository is private and so only fellow core > developers or people with admin privileges to the Python org on GitHub can > see that file (and if you're curious, it should be in reverse chronological > order of joining the team). And everyone has information to fill in except > Paul G. and myself (since I added Paul's details when I on-boarded him and > I obviously knew all of my details :) . > > It is important you fill in your details. PEP 13 says active core team > members get to vote, have commit access, etc. The plan is to automate > adding/removing privileges when we calculate who has been active and so > this info will be needed to do that, else empty data will lead to you > losing access. FYI the latest this updating of privileges will occur is > probably the next steering council election which is slated for October > when 3.8.0 goes out. > > Here's a quick primer to what all the fields mean in the TOML file: > > - name: self-explanatory ;) (luckily this has turned out to be unique for > everyone) > - other_names: if you happened to have committed under multiple names > (I've filled this in for everyone the best I could, so people shouldn't > need to change this) > - voting_address: the email address you want voting ballots sent to (this > repo is private so use whatever email address you want; currently filled in > based on your email address in the last steering council election) > - joined: when you joined the core team; I did the best I could based on > the developer log, and otherwise calculated it based on your first > merge/commit > - github: your GitHub username > - bpo: your bugs.python.org username > - discourse: your discuss.python.org username > > I'll also mention I created > https://github.com/python/voters/blob/master/former-committers.md to keep > a record of who has had access to the CPython repo but are not in the > Python core team roster. > > Finally, next steps. With this list done my next plan is to write up a > script to use git changes to calculate who has been active. After that I'll > write code to take the list of active members and generate the voter roll > for steering council elections. From there I'll write some code to generate > a new developer log for the devguide with all private info stripped out > (e.g. voting email address). Finally, code will be written to help > automatically add/remove privileges for (in)active team members. > ___ > python-committers mailing list -- python-committers@python.org > To unsubscribe send an email to python-committers-le...@python.org > https://mail.python.org/mailman3/lists/python-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/python-committers@python.org/message/VH3HSJMQ6GB27AL6747OFPB5YKLVNVDV/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/N2KIKDTMDT5FOIRX4TZ4AINWXXIRL5G6/ Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Transfer of power
On Thu, Jul 12, 2018 at 7:58 AM Guido van Rossum wrote: > Now that PEP 572 is done, I don't ever want to have to fight so hard for a > PEP and find that so many people despise my decisions. > > I would like to remove myself entirely from the decision process. I'll > still be there for a while as an ordinary core dev, and I'll still be > available to mentor people -- possibly more available. But I'm basically > giving myself a permanent vacation from being BDFL, and you all will be on > your own. > Hey Guido, Thank you so much for creating Python and nurturing it for the last 25+ years. I, and many others on the list, have built our careers around Python and we own you a huge amount of gratitude. So thank you very much and I hope that your retirement goes better than it does for most dictators ;-) Cheers, Brian > > After all that's eventually going to happen regardless -- there's still > that bus lurking around the corner, and I'm not getting younger... (I'll > spare you the list of medical issues.) > > I am not going to appoint a successor. > > So what are you all going to do? Create a democracy? Anarchy? A > dictatorship? A federation? > > I'm not worried about the day to day decisions in the issue tracker or on > GitHub. Very rarely I get asked for an opinion, and usually it's not > actually important. So this can just be dealt with as it has always been. > > The decisions that most matter are probably > - How are PEPs decided > - How are new core devs inducted > > We may be able to write up processes for these things as PEPs (maybe those > PEPs will form a kind of constitution). But here's the catch. I'm going to > try and let you all (the current committers) figure it out for yourselves. > > Note that there's still the CoC -- if you don't like that document your > only option might be to leave this group voluntarily. Perhaps there are > issues to decide like when should someone be kicked out (this could be > banning people from python-dev or python-ideas too, since those are also > covered by the CoC). > > Finally. A reminder that the archives of this list are public ( > https://mail.python.org/pipermail/python-committers/) although membership > is closed (limited to core devs). > > I'll still be here, but I'm trying to let you all figure something out for > yourselves. I'm tired, and need a very long break. > > -- > --Guido van Rossum (python.org/~guido) > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
