Skip to content

Commit 4d2c99b

Browse files
emilyemorehouseemilyemorehouse
authored
Merge pull request #265 from VeldaKiara/main
September and October SC updates
2 parents 72d977e + f18425a commit 4d2c99b

File tree

3 files changed

+388
-0
lines changed

3 files changed

+388
-0
lines changed

‎README.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,8 @@ for filename in filenames:
8787
- [2024-04,05,06](updates/2024-04,05,06-steering-council-update.md)
8888
- [2024-07](updates/2024-07-steering-council-update.md)
8989
- [2024-08](updates/2024-08-steering-council-update.md)
90+
- [2024-09](updates/2024-09-steering-council-update.md)
91+
- [2024-10](updates/2024-10-steering-council-update.md)
9092
<!-- [[[end]]] -->
9193

9294
## Process

‎updates/2024-09-steering-council-update.md‎

Lines changed: 163 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,163 @@
1+
2+
# Steering Council Updates for September 2024
3+
4+
## 2024-09-04
5+
6+
Developer in Residence Update:
7+
8+
- Release of [Python 3.13rc2](https://www.python.org/downloads/release/python-3130rc2/) with resolved blockers
9+
- PyREPL fixes nearing completion
10+
- Security releases pending due to ongoing fixes
11+
12+
Code Review on PRs:
13+
14+
- Discussion on implementing mandatory core developers PR code reviews (starting with new features only)
15+
16+
Funding for Developers in Residence:
17+
18+
- Ongoing discussions about retaining current developers
19+
- Budget planning for 2024 and 2025
20+
- Funding for developers in residence appears secure for the near future
21+
22+
Core Developer Sprint in 2025:
23+
24+
- Venue selection dependent on sponsorship
25+
- Considering reaching out to potential sponsors for additional costs outside of venue
26+
27+
Grants Discussion:
28+
29+
- Proposal to sponsor a developer for specific work
30+
- Emphasis on clear communication and defining grant parameters
31+
- Concerns about transparency and community perception if we started a grants program.
32+
33+
Community and Governance:
34+
35+
- Discussions on separating technical and community direction roles
36+
- Need for clarification on Python Software Foundation and core developer responsibilities
37+
- 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)
38+
39+
Diversity and Inclusion:
40+
41+
- Acknowledgment of frustrations regarding the pace of Diversity, Equity and Inclusion (DEI) initiatives
42+
- Need to balance technical contributions with community dynamics
43+
44+
Next Steps:
45+
46+
- Continue discussions on grant processes and parameters
47+
- Follow up on potential sponsorships for core developer sprint
48+
49+
## 2024-09-11
50+
51+
Meeting with Guido and Steering Council (office hours!)
52+
53+
Guido's Focus:
54+
55+
- Guido has been working extensively on [asyncio](https://docs.python.org/3/library/asyncio.html)
56+
- His priority remains Python contributions
57+
58+
A core dev ban Incident:
59+
60+
- The developer received a 3-month ban, which was unexpected by some
61+
- The ban was not solely based on a single discussion but considered other factors.
62+
- Concerns raised about how this affects the reputation of core developers, and the impact on the inclusion and outreach efforts.
63+
- The Steering Council is following procedures recommended by the Code of Conduct Working Group
64+
65+
Diversity in Hiring:
66+
67+
- Feedback received on a desire to see balanced hiring practices
68+
- Considering a grants program as an alternative to direct hiring for specific CPython maintenance needs
69+
- Discussing the legal requirements and ethical considerations around targeted hiring practices
70+
71+
Discourse Moderation:
72+
73+
- Issues with automatic moderation on Discourse have been identified
74+
- There's a need to improve communication about moderation actions
75+
- The Steering Council is considering ways to improve the situation and clarify areas of responsibility
76+
77+
Governance and Responsibilities:
78+
79+
- Discussions about re-examining areas of authority and responsibility within the Python community
80+
- Considering separating Code of Conduct responsibilities from the Steering Council. Community must drive this change
81+
- Exploring ways to improve the feedback mechanism for moderators
82+
83+
Voting Procedures:
84+
85+
- Considering changes to the voting system, potentially moving to [STAR voting](https://discuss.python.org/t/adopting-star-voting/63637)
86+
- Discussing the process for changing [PEP 13](https://peps.python.org/pep-0013/) and the required support from core developers
87+
88+
Next Steps based on this discussion:
89+
90+
- Propose a plan to improve voting organization
91+
- Consider changes to [PEP 13](https://peps.python.org/pep-0013/)
92+
- Clarify which matters require voting and how to conduct votes effectively
93+
94+
Meeting among the Steering Council Members
95+
96+
Code of Conduct (CoC) Issues:
97+
98+
- Questions raised about the ban of a core dev and the responsibility for this action
99+
- Concerns about harassment related to the CoC decisions
100+
101+
PEP-related Discussions:
102+
103+
- Steering Council to consider [PEP 2](https://peps.python.org/pep-0002/) and inclusion matters, with a focus on PyPI integration
104+
- Ongoing discussions about adding to the PyPI library and involving more people in the process
105+
- No updates on [PEP 667](https://peps.python.org/pep-0667/) at this time
106+
107+
Community Engagement:
108+
109+
- Suggestions for moderating panel discussions to maintain focus among core developers
110+
- Discussions on requiring code review during sprints
111+
112+
Mentoring and Resources:
113+
114+
- Acknowledgment of the need to develop mentoring resources
115+
- Plans to determine how to implement mentoring effectively
116+
117+
PyPI Policy:
118+
119+
- Ongoing discussions about PyPI policies
120+
121+
PyREPL:
122+
123+
- Request for an informational PEP for PyREPL
124+
125+
## 2024-09-18
126+
127+
Core Developer Promotion:
128+
129+
- The Steering Council unanimously accepts the community vote to promote Kirill Podoprigora to Core Developer
130+
- Steering Council to follow up on the promotion process
131+
132+
Core Developer Sprint 2025:
133+
134+
- Considering Arm's proposal to host in Cambridge, UK
135+
- Pablo to discuss expectations and needs with Diego
136+
- Visa considerations to be clarified with Arm and PSF
137+
- Six months advance notice required for invitees
138+
139+
Python 3.13 Release:
140+
141+
- Proceeding with 3.13.0 release as planned, no RC3
142+
- Two potential blockers under consideration
143+
- The exec+compile double traceback issue not considered a blocker
144+
145+
PyPI and Packaging Discussions:
146+
147+
- Ongoing conversations about decision-making processes for PyPI and packaging
148+
- Consideration of creating a working group for cross-cutting concerns
149+
150+
Community Concerns:
151+
152+
- Discussions around recent community concerns and responses
153+
- Acknowledgment of community division and the need for careful communication
154+
- Consideration of proposing changes to PEP-13 to clarify Steering Council roles
155+
156+
Upcoming Sprint:
157+
158+
- Plans for in-person discussions at the Bellevue sprint
159+
- Suggestion to have separate rooms for sensitive topics to accommodate all participants
160+
161+
## 2024-09-23
162+
163+
Steering Council met informally at the Core Dev Sprint in Bellevue, WA (USA)

‎updates/2024-10-steering-council-update.md‎

Lines changed: 223 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,223 @@
1+
# Steering Council Updates for October 2024
2+
3+
## 2024-10-02
4+
5+
Release Management:
6+
7+
- Preparations for next week's release underway
8+
- [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)
9+
- Some concerns about [RC3](https://www.python.org/downloads/release/python-3130rc3/), mostly cosmetic issues to be addressed in 3.13.1
10+
- Performance discussions: mixed reports on speed compared to 3.12
11+
12+
Core Developer Updates:
13+
14+
- Someone nominated for triaging, open vote on Discourse
15+
- Increase in core developer numbers noted
16+
17+
Process Improvements:
18+
19+
- Discussion on requiring reviews for features in 3.13 and 3.14
20+
- Acknowledgment of trust issues within the community
21+
- Considering changes to discussion processes and decision-making
22+
- Concerns about workload and response times for working groups
23+
24+
Community Engagement:
25+
26+
- Łukasz invited for Python 3.13 celebrations
27+
- Upcoming Discord event with Pablo and Łukasz
28+
29+
PyREPL and Windows Issues:
30+
31+
- Functionality issues noted for Windows and shell support
32+
- Discussions on function key behavior and documentation
33+
34+
Future Planning:
35+
36+
- New [PEP 2026](https://peps.python.org/pep-2026/) for calendar version to be reviewed next week
37+
- PEP 667 [re-review](https://github.com/python/peps/pull/3845) closed
38+
- Mentorship survey responses to be checked
39+
40+
Core Developer Sprints:
41+
42+
- Discussions about 2025 sprint location (Cambridge UK proposal)
43+
- Considerations for accessibility and travel logistics
44+
- Suggestion to create a document outlining sprint hosting requirements and costs
45+
46+
Miscellaneous:
47+
48+
- Office hours with another developer in residence scheduled for next week
49+
- [PEP 2026](https://peps.python.org/pep-2026/) to be discussed next week
50+
- Łukasz's requirement review process discussed
51+
52+
## 2024-10-09
53+
54+
Developer in Residence Discussion:
55+
56+
- Addressed concerns about a core developer's behavior and communication
57+
- Discussed workload distribution and priorities
58+
- Mentioned potential improvements for buildbots and test result tracking
59+
- Explored ideas for better utilization of developer in residence role
60+
61+
Community Communication:
62+
63+
- Acknowledged concerns about transparency and fear within the community
64+
- Discussed need for clearer communication about processes and decisions
65+
- Considered ways to address misconceptions about Steering Council responsibilities
66+
67+
Core Developer Promotion:
68+
69+
- The Steering Council unanimously accepts the community vote to promote Matt Page to Core Developer
70+
71+
Election Process:
72+
73+
- Discussed implementation of STAR voting for upcoming term
74+
- Noted need for Python Software Foundation to have 4 weeks to implement new voting tools
75+
- Considered conducting mock elections to test new system
76+
77+
Python 3.13 Release:
78+
79+
- Announced release of [Python 3.13](https://docs.python.org/3/whatsnew/3.13.html)
80+
81+
Core Developer Sprints:
82+
83+
- Discussed potential Arm-hosted sprint in Cambridge UK
84+
- Considered logistics, including hotel bookings and travel arrangements
85+
- Explored sponsorship possibilities, including potential separate corporate sponsorship for 2026
86+
87+
Financial Considerations:
88+
89+
- Discussed need for responsible budgeting aligned with non-profit status
90+
- Mentioned adherence to US State Department guidelines for per diem and expenses
91+
- Emphasized importance of Python Software Foundation involvement in financial decisions
92+
93+
Procedural Matters:
94+
95+
- Considered need for Call for Proposals (CFP) for future sprints
96+
- Discussed community satisfaction and transparency in decision-making
97+
98+
## 2024-10-16
99+
100+
Developer in Residence Discussion:
101+
102+
- Concerns raised about collaboration and communication within the active [asyncio](https://docs.python.org/3/library/asyncio.html) developers
103+
- Discussed the need for multiple experts in [asyncio](https://docs.python.org/3/library/asyncio.html) due to its complexity
104+
- Emphasized the importance of aligning grant work with larger project goals
105+
106+
Core Developer Management:
107+
108+
- Discussed process for removing commit bits from inactive core devs
109+
- Agreed to defer this discussion to the next Steering Council to avoid confusion with upcoming elections
110+
111+
Core Developer Sprint:
112+
113+
- Proceeding with Arm's offer to host in Cambridge UK
114+
- Exploring additional sponsorship opportunities
115+
- Clarified need to set expectations with sponsors regarding exclusivity
116+
117+
PEP 2026 (Calendar Versioning):
118+
119+
- Mixed opinions among SC members, ranging from slightly positive to slightly negative
120+
- Noted lack of community consensus on the proposal
121+
- Decided to defer decision to the next Steering Council
122+
123+
Election Process:
124+
125+
- Discussed need for clear timeline for upcoming Steering Council elections
126+
- Considered using Notion Calendar for scheduling office hours. Decided to defer decision to the next Steering Council
127+
128+
PEP Delegation:
129+
130+
- Discussed process for delegating PEPs to working groups (e.g., C API working group)
131+
- Considered whether to fully delegate decisions or just seek recommendations
132+
133+
Community Engagement:
134+
135+
- Discussed need for clearer communication about Steering Council's focus in coming months
136+
- Considered public announcement about deferring certain PEPs to next Steering Council. Decided to respond to all PEPs that will be deferred
137+
138+
## 2024-10-23
139+
140+
Core Developer Sprint:
141+
142+
- Discussion about possible locations and timing for next year
143+
- Need to open a poll for dates
144+
- Location has good facilities including breakout rooms and cafeteria
145+
- Host site has experience with similar events like Linux mini conference
146+
147+
Administrative Updates:
148+
149+
- Standing delegation docs PR needs review
150+
- Need to formalize mentorship resources and working group
151+
- Discussion about type annotations standardization
152+
- Need to document code of conduct violation handling process
153+
154+
Core Developer Promotion Process:
155+
156+
- Need for more transparent criteria and process
157+
- Concerns about pushing mentors too hard on promotions
158+
- Need to balance mentor discretion with transparency
159+
160+
PEP Decisions:
161+
162+
- Decision to defer PEPs [2026](https://peps.python.org/pep-2026/) and [661](https://peps.python.org/pep-0661/) to next steering council
163+
- Discussion about handling [PEP 761](https://peps.python.org/pep-0761/)
164+
- Need for clarity on PEP decision timing relative to steering council election
165+
166+
Technical Discussions on JIT
167+
168+
- Concerns raised about debugging and profiling capabilities
169+
- Discussion about JIT implementation impacts
170+
- Need for balance between performance improvements and debugging capabilities
171+
- Suggestion for informational PEP to lay out debugging/profiling issues
172+
173+
## 2024-10-30
174+
175+
Developer in Residence Update:
176+
177+
- Required reviews for PRs are now implemented, though not disruptive as no PRs are currently automatically marked as features
178+
- Small disruption occurred due to changing required checks on main, requiring some PRs to update their branches
179+
- "Do not merge" check was renamed for clarity
180+
- ARM runners are being added for GitHub for Linux and Windows:
181+
- Windows runner temporarily on hold due to compiler issues
182+
- Using paid runners with ARM sponsorship arrangement
183+
- Cost expected to be lower than MacOS runners ($500/week)
184+
- ARM will reimburse costs through GitHub sponsorship
185+
186+
- New episode of the [core.py podcast](https://www.youtube.com/playlist?list=PLShJCpYUN3C3XrdguJiAZrQEnQGH-Sq26) released
187+
- Work ongoing on asyncio debugging changes
188+
- Making changes so borrowed reference to task isn't needed on every generator
189+
- [_asynciomodule.c](https://github.com/python/cpython/blob/main/Modules/_asynciomodule.c) now holds list of pointers to root tasks for each interpreter
190+
191+
- Increased moderation challenges on Python Discourse forums recently
192+
- Dealing with controversial discussions about moderation
193+
- Some users potentially trying to provoke bans
194+
195+
- Another core developer was accepted into the Python Software Foundation Code of Conduct Working Group
196+
197+
Meeting among the Steering Council Members
198+
199+
- Discussion on [PEP 744 (JIT PEP)](https://peps.python.org/pep-0744/):
200+
- Potential change from informational to standards track PEP
201+
- Need to set clearer expectations and requirements
202+
- Concerns about debugging/profiling support
203+
204+
- Issues with CPython development complexity:
205+
- Performance-focused work making contribution harder
206+
- Challenge for community contributors to keep up
207+
208+
- Discussion of full-time developer impact:
209+
- Faster CPython team and Meta employees' (free-threading work) pace of changes
210+
- Balance between progress and community involvement
211+
- Review process challenges
212+
- Discussing if we could require non-affiliated or cross-discipline core dev reviews for a broader perspective on changes
213+
- Timing and responsiveness concerns
214+
- Community involvement challenges:
215+
- Review workload distribution
216+
- Election planning:
217+
- Timeline discussion
218+
- Encouraging nominations
219+
- Approved August monthly notes for publishing
220+
- Concerns about maintaining community accessibility
221+
- Documentation challenges
222+
- Onboarding new contributors
223+
- Balance between corporate and community contributions

0 commit comments

Comments
 (0)