-
-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #265 from VeldaKiara/main
September and October SC updates
- Loading branch information
Showing
3 changed files
with
388 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,163 @@ | ||
|
|
||
| # Steering Council Updates for September 2024 | ||
|
|
||
| ## 2024-09-04 | ||
|
|
||
| Developer in Residence Update: | ||
|
|
||
| - Release of [Python 3.13rc2](https://www.python.org/downloads/release/python-3130rc2/) with resolved blockers | ||
| - PyREPL fixes nearing completion | ||
| - Security releases pending due to ongoing fixes | ||
|
|
||
| Code Review on PRs: | ||
|
|
||
| - Discussion on implementing mandatory core developers PR code reviews (starting with new features only) | ||
|
|
||
| Funding for Developers in Residence: | ||
|
|
||
| - Ongoing discussions about retaining current developers | ||
| - Budget planning for 2024 and 2025 | ||
| - Funding for developers in residence appears secure for the near future | ||
|
|
||
| Core Developer Sprint in 2025: | ||
|
|
||
| - Venue selection dependent on sponsorship | ||
| - Considering reaching out to potential sponsors for additional costs outside of venue | ||
|
|
||
| Grants Discussion: | ||
|
|
||
| - Proposal to sponsor a developer for specific work | ||
| - Emphasis on clear communication and defining grant parameters | ||
| - Concerns about transparency and community perception if we started a grants program. | ||
|
|
||
| Community and Governance: | ||
|
|
||
| - Discussions on separating technical and community direction roles | ||
| - Need for clarification on Python Software Foundation and core developer responsibilities | ||
| - Consideration of updating [PEP 13](https://peps.python.org/pep-0013/) to reflect evolving governance structure (this must come from the community, not the Steering Council) | ||
|
|
||
| Diversity and Inclusion: | ||
|
|
||
| - Acknowledgment of frustrations regarding the pace of Diversity, Equity and Inclusion (DEI) initiatives | ||
| - Need to balance technical contributions with community dynamics | ||
|
|
||
| Next Steps: | ||
|
|
||
| - Continue discussions on grant processes and parameters | ||
| - Follow up on potential sponsorships for core developer sprint | ||
|
|
||
| ## 2024-09-11 | ||
|
|
||
| Meeting with Guido and Steering Council (office hours!) | ||
|
|
||
| Guido's Focus: | ||
|
|
||
| - Guido has been working extensively on [asyncio](https://docs.python.org/3/library/asyncio.html) | ||
| - His priority remains Python contributions | ||
|
|
||
| A core dev ban Incident: | ||
|
|
||
| - The developer received a 3-month ban, which was unexpected by some | ||
| - The ban was not solely based on a single discussion but considered other factors. | ||
| - Concerns raised about how this affects the reputation of core developers, and the impact on the inclusion and outreach efforts. | ||
| - The Steering Council is following procedures recommended by the Code of Conduct Working Group | ||
|
|
||
| Diversity in Hiring: | ||
|
|
||
| - Feedback received on a desire to see balanced hiring practices | ||
| - Considering a grants program as an alternative to direct hiring for specific CPython maintenance needs | ||
| - Discussing the legal requirements and ethical considerations around targeted hiring practices | ||
|
|
||
| Discourse Moderation: | ||
|
|
||
| - Issues with automatic moderation on Discourse have been identified | ||
| - There's a need to improve communication about moderation actions | ||
| - The Steering Council is considering ways to improve the situation and clarify areas of responsibility | ||
|
|
||
| Governance and Responsibilities: | ||
|
|
||
| - Discussions about re-examining areas of authority and responsibility within the Python community | ||
| - Considering separating Code of Conduct responsibilities from the Steering Council. Community must drive this change | ||
| - Exploring ways to improve the feedback mechanism for moderators | ||
|
|
||
| Voting Procedures: | ||
|
|
||
| - Considering changes to the voting system, potentially moving to [STAR voting](https://discuss.python.org/t/adopting-star-voting/63637) | ||
| - Discussing the process for changing [PEP 13](https://peps.python.org/pep-0013/) and the required support from core developers | ||
|
|
||
| Next Steps based on this discussion: | ||
|
|
||
| - Propose a plan to improve voting organization | ||
| - Consider changes to [PEP 13](https://peps.python.org/pep-0013/) | ||
| - Clarify which matters require voting and how to conduct votes effectively | ||
|
|
||
| Meeting among the Steering Council Members | ||
|
|
||
| Code of Conduct (CoC) Issues: | ||
|
|
||
| - Questions raised about the ban of a core dev and the responsibility for this action | ||
| - Concerns about harassment related to the CoC decisions | ||
|
|
||
| PEP-related Discussions: | ||
|
|
||
| - Steering Council to consider [PEP 2](https://peps.python.org/pep-0002/) and inclusion matters, with a focus on PyPI integration | ||
| - Ongoing discussions about adding to the PyPI library and involving more people in the process | ||
| - No updates on [PEP 667](https://peps.python.org/pep-0667/) at this time | ||
|
|
||
| Community Engagement: | ||
|
|
||
| - Suggestions for moderating panel discussions to maintain focus among core developers | ||
| - Discussions on requiring code review during sprints | ||
|
|
||
| Mentoring and Resources: | ||
|
|
||
| - Acknowledgment of the need to develop mentoring resources | ||
| - Plans to determine how to implement mentoring effectively | ||
|
|
||
| PyPI Policy: | ||
|
|
||
| - Ongoing discussions about PyPI policies | ||
|
|
||
| PyREPL: | ||
|
|
||
| - Request for an informational PEP for PyREPL | ||
|
|
||
| ## 2024-09-18 | ||
|
|
||
| Core Developer Promotion: | ||
|
|
||
| - The Steering Council unanimously accepts the community vote to promote Kirill Podoprigora to Core Developer | ||
| - Steering Council to follow up on the promotion process | ||
|
|
||
| Core Developer Sprint 2025: | ||
|
|
||
| - Considering Arm's proposal to host in Cambridge, UK | ||
| - Pablo to discuss expectations and needs with Diego | ||
| - Visa considerations to be clarified with Arm and PSF | ||
| - Six months advance notice required for invitees | ||
|
|
||
| Python 3.13 Release: | ||
|
|
||
| - Proceeding with 3.13.0 release as planned, no RC3 | ||
| - Two potential blockers under consideration | ||
| - The exec+compile double traceback issue not considered a blocker | ||
|
|
||
| PyPI and Packaging Discussions: | ||
|
|
||
| - Ongoing conversations about decision-making processes for PyPI and packaging | ||
| - Consideration of creating a working group for cross-cutting concerns | ||
|
|
||
| Community Concerns: | ||
|
|
||
| - Discussions around recent community concerns and responses | ||
| - Acknowledgment of community division and the need for careful communication | ||
| - Consideration of proposing changes to PEP-13 to clarify Steering Council roles | ||
|
|
||
| Upcoming Sprint: | ||
|
|
||
| - Plans for in-person discussions at the Bellevue sprint | ||
| - Suggestion to have separate rooms for sensitive topics to accommodate all participants | ||
|
|
||
| ## 2024-09-23 | ||
|
|
||
| Steering Council met informally at the Core Dev Sprint in Bellevue, WA (USA) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,223 @@ | ||
| # Steering Council Updates for October 2024 | ||
|
|
||
| ## 2024-10-02 | ||
|
|
||
| Release Management: | ||
|
|
||
| - Preparations for next week's release underway | ||
| - [Python 3.13 RC3](https://www.python.org/downloads/release/python-3130rc3/) released with Windows installer updates and the [Incremental GC rolled back](https://discuss.python.org/t/incremental-gc-and-pushing-back-the-3-13-0-release/65285) | ||
| - Some concerns about [RC3](https://www.python.org/downloads/release/python-3130rc3/), mostly cosmetic issues to be addressed in 3.13.1 | ||
| - Performance discussions: mixed reports on speed compared to 3.12 | ||
|
|
||
| Core Developer Updates: | ||
|
|
||
| - Someone nominated for triaging, open vote on Discourse | ||
| - Increase in core developer numbers noted | ||
|
|
||
| Process Improvements: | ||
|
|
||
| - Discussion on requiring reviews for features in 3.13 and 3.14 | ||
| - Acknowledgment of trust issues within the community | ||
| - Considering changes to discussion processes and decision-making | ||
| - Concerns about workload and response times for working groups | ||
|
|
||
| Community Engagement: | ||
|
|
||
| - Łukasz invited for Python 3.13 celebrations | ||
| - Upcoming Discord event with Pablo and Łukasz | ||
|
|
||
| PyREPL and Windows Issues: | ||
|
|
||
| - Functionality issues noted for Windows and shell support | ||
| - Discussions on function key behavior and documentation | ||
|
|
||
| Future Planning: | ||
|
|
||
| - New [PEP 2026](https://peps.python.org/pep-2026/) for calendar version to be reviewed next week | ||
| - PEP 667 [re-review](https://github.com/python/peps/pull/3845) closed | ||
| - Mentorship survey responses to be checked | ||
|
|
||
| Core Developer Sprints: | ||
|
|
||
| - Discussions about 2025 sprint location (Cambridge UK proposal) | ||
| - Considerations for accessibility and travel logistics | ||
| - Suggestion to create a document outlining sprint hosting requirements and costs | ||
|
|
||
| Miscellaneous: | ||
|
|
||
| - Office hours with another developer in residence scheduled for next week | ||
| - [PEP 2026](https://peps.python.org/pep-2026/) to be discussed next week | ||
| - Łukasz's requirement review process discussed | ||
|
|
||
| ## 2024-10-09 | ||
|
|
||
| Developer in Residence Discussion: | ||
|
|
||
| - Addressed concerns about a core developer's behavior and communication | ||
| - Discussed workload distribution and priorities | ||
| - Mentioned potential improvements for buildbots and test result tracking | ||
| - Explored ideas for better utilization of developer in residence role | ||
|
|
||
| Community Communication: | ||
|
|
||
| - Acknowledged concerns about transparency and fear within the community | ||
| - Discussed need for clearer communication about processes and decisions | ||
| - Considered ways to address misconceptions about Steering Council responsibilities | ||
|
|
||
| Core Developer Promotion: | ||
|
|
||
| - The Steering Council unanimously accepts the community vote to promote Matt Page to Core Developer | ||
|
|
||
| Election Process: | ||
|
|
||
| - Discussed implementation of STAR voting for upcoming term | ||
| - Noted need for Python Software Foundation to have 4 weeks to implement new voting tools | ||
| - Considered conducting mock elections to test new system | ||
|
|
||
| Python 3.13 Release: | ||
|
|
||
| - Announced release of [Python 3.13](https://docs.python.org/3/whatsnew/3.13.html) | ||
|
|
||
| Core Developer Sprints: | ||
|
|
||
| - Discussed potential Arm-hosted sprint in Cambridge UK | ||
| - Considered logistics, including hotel bookings and travel arrangements | ||
| - Explored sponsorship possibilities, including potential separate corporate sponsorship for 2026 | ||
|
|
||
| Financial Considerations: | ||
|
|
||
| - Discussed need for responsible budgeting aligned with non-profit status | ||
| - Mentioned adherence to US State Department guidelines for per diem and expenses | ||
| - Emphasized importance of Python Software Foundation involvement in financial decisions | ||
|
|
||
| Procedural Matters: | ||
|
|
||
| - Considered need for Call for Proposals (CFP) for future sprints | ||
| - Discussed community satisfaction and transparency in decision-making | ||
|
|
||
| ## 2024-10-16 | ||
|
|
||
| Developer in Residence Discussion: | ||
|
|
||
| - Concerns raised about collaboration and communication within the active [asyncio](https://docs.python.org/3/library/asyncio.html) developers | ||
| - Discussed the need for multiple experts in [asyncio](https://docs.python.org/3/library/asyncio.html) due to its complexity | ||
| - Emphasized the importance of aligning grant work with larger project goals | ||
|
|
||
| Core Developer Management: | ||
|
|
||
| - Discussed process for removing commit bits from inactive core devs | ||
| - Agreed to defer this discussion to the next Steering Council to avoid confusion with upcoming elections | ||
|
|
||
| Core Developer Sprint: | ||
|
|
||
| - Proceeding with Arm's offer to host in Cambridge UK | ||
| - Exploring additional sponsorship opportunities | ||
| - Clarified need to set expectations with sponsors regarding exclusivity | ||
|
|
||
| PEP 2026 (Calendar Versioning): | ||
|
|
||
| - Mixed opinions among SC members, ranging from slightly positive to slightly negative | ||
| - Noted lack of community consensus on the proposal | ||
| - Decided to defer decision to the next Steering Council | ||
|
|
||
| Election Process: | ||
|
|
||
| - Discussed need for clear timeline for upcoming Steering Council elections | ||
| - Considered using Notion Calendar for scheduling office hours. Decided to defer decision to the next Steering Council | ||
|
|
||
| PEP Delegation: | ||
|
|
||
| - Discussed process for delegating PEPs to working groups (e.g., C API working group) | ||
| - Considered whether to fully delegate decisions or just seek recommendations | ||
|
|
||
| Community Engagement: | ||
|
|
||
| - Discussed need for clearer communication about Steering Council's focus in coming months | ||
| - Considered public announcement about deferring certain PEPs to next Steering Council. Decided to respond to all PEPs that will be deferred | ||
|
|
||
| ## 2024-10-23 | ||
|
|
||
| Core Developer Sprint: | ||
|
|
||
| - Discussion about possible locations and timing for next year | ||
| - Need to open a poll for dates | ||
| - Location has good facilities including breakout rooms and cafeteria | ||
| - Host site has experience with similar events like Linux mini conference | ||
|
|
||
| Administrative Updates: | ||
|
|
||
| - Standing delegation docs PR needs review | ||
| - Need to formalize mentorship resources and working group | ||
| - Discussion about type annotations standardization | ||
| - Need to document code of conduct violation handling process | ||
|
|
||
| Core Developer Promotion Process: | ||
|
|
||
| - Need for more transparent criteria and process | ||
| - Concerns about pushing mentors too hard on promotions | ||
| - Need to balance mentor discretion with transparency | ||
|
|
||
| PEP Decisions: | ||
|
|
||
| - Decision to defer PEPs [2026](https://peps.python.org/pep-2026/) and [661](https://peps.python.org/pep-0661/) to next steering council | ||
| - Discussion about handling [PEP 761](https://peps.python.org/pep-0761/) | ||
| - Need for clarity on PEP decision timing relative to steering council election | ||
|
|
||
| Technical Discussions on JIT | ||
|
|
||
| - Concerns raised about debugging and profiling capabilities | ||
| - Discussion about JIT implementation impacts | ||
| - Need for balance between performance improvements and debugging capabilities | ||
| - Suggestion for informational PEP to lay out debugging/profiling issues | ||
|
|
||
| ## 2024-10-30 | ||
|
|
||
| Developer in Residence Update: | ||
|
|
||
| - Required reviews for PRs are now implemented, though not disruptive as no PRs are currently automatically marked as features | ||
| - Small disruption occurred due to changing required checks on main, requiring some PRs to update their branches | ||
| - "Do not merge" check was renamed for clarity | ||
| - ARM runners are being added for GitHub for Linux and Windows: | ||
| - Windows runner temporarily on hold due to compiler issues | ||
| - Using paid runners with ARM sponsorship arrangement | ||
| - Cost expected to be lower than MacOS runners ($500/week) | ||
| - ARM will reimburse costs through GitHub sponsorship | ||
|
|
||
| - New episode of the [core.py podcast](https://www.youtube.com/playlist?list=PLShJCpYUN3C3XrdguJiAZrQEnQGH-Sq26) released | ||
| - Work ongoing on asyncio debugging changes | ||
| - Making changes so borrowed reference to task isn't needed on every generator | ||
| - [_asynciomodule.c](https://github.com/python/cpython/blob/main/Modules/_asynciomodule.c) now holds list of pointers to root tasks for each interpreter | ||
|
|
||
| - Increased moderation challenges on Python Discourse forums recently | ||
| - Dealing with controversial discussions about moderation | ||
| - Some users potentially trying to provoke bans | ||
|
|
||
| - Another core developer was accepted into the Python Software Foundation Code of Conduct Working Group | ||
|
|
||
| Meeting among the Steering Council Members | ||
|
|
||
| - Discussion on [PEP 744 (JIT PEP)](https://peps.python.org/pep-0744/): | ||
| - Potential change from informational to standards track PEP | ||
| - Need to set clearer expectations and requirements | ||
| - Concerns about debugging/profiling support | ||
|
|
||
| - Issues with CPython development complexity: | ||
| - Performance-focused work making contribution harder | ||
| - Challenge for community contributors to keep up | ||
|
|
||
| - Discussion of full-time developer impact: | ||
| - Faster CPython team and Meta employees' (free-threading work) pace of changes | ||
| - Balance between progress and community involvement | ||
| - Review process challenges | ||
| - Discussing if we could require non-affiliated or cross-discipline core dev reviews for a broader perspective on changes | ||
| - Timing and responsiveness concerns | ||
| - Community involvement challenges: | ||
| - Review workload distribution | ||
| - Election planning: | ||
| - Timeline discussion | ||
| - Encouraging nominations | ||
| - Approved August monthly notes for publishing | ||
| - Concerns about maintaining community accessibility | ||
| - Documentation challenges | ||
| - Onboarding new contributors | ||
| - Balance between corporate and community contributions |