Hugo van Kemenade @hugovk@mastodon.social
Public

🔒 news:

We're going to start disabling the commit bit (aka write access) to the repo for inactive core team members.

discuss.python.org/t/regularly

I proposed this after a security discussion at last year's :

pyfound.blogspot.com/2024/06/p

Disabling the commit bit has no impact on core team status, nor Steering Council voting status, and you can easily ask for it back again.

Regularly disabling unused commit access to the cpython repo

Howdy committers - The Python Steering Council (PSC) has had an open issue based on discussions last year to improve our project’s security posture. We’re going to move forward with disabling GitHub commit privileges for inactive core team members. This has no impact on “core team” or “Python Steering Council (PSC) voting” status. It is merely a good security practice to not leave unused credentials laying around. Seth (Security Developer-in-Residence) lays out the rationale here. How do we...

discuss.python.org · Discussions on Python.org

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/hugovk/statuses/115603641868052557 on your instance and quote it. (Note that quoting is not supported in Mastodon.)