Please fill in your details in the canonical list of Python core team membership
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/MI...), 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.
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 <brett@python.org> 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/MI...), 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-leave@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/V... Code of Conduct: https://www.python.org/psf/codeofconduct/
Brian Quinlan wrote:
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 ?
They should be in python-core.toml. Relinquishment basically means "I don't want to have commit rights anymore", not "I don't want to be considered to have ever been a core dev" (which is what python-core.toml represents).
-Brett
Cheers, Brian On Fri, Jul 26, 2019 at 4:46 PM Brett Cannon brett@python.org 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/MI...), 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-leave@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/V... Code of Conduct: https://www.python.org/psf/codeofconduct/
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 <brett@python.org> 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/MI...), 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-leave@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/V... Code of Conduct: https://www.python.org/psf/codeofconduct/
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 <pje@telecommunity.com> 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 <brett@python.org> 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/MI...), 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-leave@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/V... 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-leave@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/M... Code of Conduct: https://www.python.org/psf/codeofconduct/
The "everyone" is "everyone with GitHub access" really (there are people on python-committers who are not considered core developers, for instance, so this list isn't used as an indicator of anything). Basically if you're aren't contributing anymore than it isn't as critical to update your info since it's all about permissions to systems that eventually only active team members will have elevated privileges for. But as Brian said, you can ask someone to add your info for you if you want. (And I don't expect us to bother purging python-committers so there's no worry there.)
And I actually can't grant access to repositories; that a PSF infrastructure request to add someone to Python core team on GitHub under the Python org (which I can handle making the request, I just don't click the button that grants privileges).
participants (3)
-
Brett Cannon -
Brian Quinlan -
PJ Eby