Skip to content

Latest commit

 

History

History
45 lines (36 loc) · 4.53 KB

2023-07-steering-council-update.md

File metadata and controls

45 lines (36 loc) · 4.53 KB
Raw

2023-07-03

  • The Steering Council checked in on ongoing conduct issues and the steps to handle them.
  • The SC discussed an email that suggested an update to PEP 12 (Sample reStructuredText PEP Template) to formalize including acceptance and rejection rationale to PEPs once they have a decision. The SC thinks this is a good idea and will work on drafting this change.
  • The SC discussed dropping the python-committers mailing list. An email will be sent to gauge interest and usage of the mailing list.

2023-07-10

  • The Steering Council met with Łukasz, the Developer-in-Residence, and discussed:
    • The Deputy Developer-in-Residence job, which has been posted and started receiving applications.
    • The 3.12 final beta release, which has a few important bug fix PRs that are open.
    • EuroPython, which is happening next week. Łukasz will be giving a talk and running a panel along with sprints
  • The SC continued to discuss support for core developer mentorship with Deb. The distinction between supporting mentorship for new core developers and improving the process of becoming a core developer was raised – we are specifically looking for how to support existing core developers in mentoring contributors. The SC decided to pause the discussion to solidify what we are looking for in this arrangement.
  • The SC discussed PEP 703 (Making the Global Interpreter Lock Optional in CPython).
    • The poll results are in and indicate that 87% of respondents think we should be actively looking to make Python free-threaded and 63% want to accept and support the maintenance cost of PEP 703.
    • Proceeding with caution, the SC decided to formalize a statement on our intention to accept the PEP, along with requirements and expectations for doing so.
  • The SC discussed two C API changes in 3.12 that did not follow PEP 387 (Backwards Compatibility Policy) to decide how they should be handled, namely:
    • Type Object’s tp_dict can now be NULL. This has limited impact and is likely acceptable.
    • PyLongObject implementation and ob_digits. The SC decided to roll back changes only in 3.12, not main (3.13) for now. Overall, this change is okay.
  • The SC checked in on requiring PR reviews; a poll has been opened.

2023-07-17

  • The Steering Council checked in on ongoing conduct issues and the steps to handle them.
  • The SC received feedback from the community on the lack of use for the python-committers email list and decided to close it.
  • The SC continued to discuss PEP 703 (Making the Global Interpreter Lock Optional in CPython), with a focus on establishing a hard list of requirements for acceptance to be included in a forthcoming pre-announcement.

2023-07-24

  • The Steering Council met with Łukasz, the Developer-in-Residence, and discussed:
    • How EuroPython went (both the conference and the sprints).
    • dtrace and how to test the probes so they keep functioning.
    • Miss Islington needs porting to GitHub Actions before we can switch over to requiring 2FA.
    • The SC asked the DiR to evaluate how we could require code reviews for feature PRs.
  • The SC discussed support for core developer mentorship, namely the budget around a proposal to do an inventory of the current mentorship program.
  • The SC gave our approval to the Security Developer-in-Residence for their CNA proposal.
  • The SC discussed updating non-borrowing C APIs to match borrowing ones.
  • The SC continued to discuss PEP 703 (Making the Global Interpreter Lock Optional in CPython).

2023-07-31