PEP 790 schedules Python 3.15.0 final for 2026-10-09. The full What's New is long by design, so this post is the shorter upgrade list I would check first: explicit lazy imports, UTF-8 as the default encoding, unpacking in comprehensions, the new profiling package with Tachyon, and frozendict. Each section stays short -- what changed, why it shows up in day-to-day work, and a small example where one helps. Lazy imports get a concrete beat from years of chasing import cost in the Open World Holidays Framework. Everything else worth planning around still lives in the official What's New and Porting guides.

Communities get the Slack they tolerate. Large communities drown less often in obvious scam posts or clear code of conduct violations than in everyday attention tax. Wrong channel posts, top-level replies that should have been threads, and the `Also send to #channel` checkbox quietly multiply unread counts for people who never asked for the ping. This post is a practitioner etiquette essay from Slack-lived experience: pick the right room, consolidate before you hit Enter, trim link previews, prefer reactions over thanks-noise, and remember that deleted messages still leave footprints. It ends with a short checklist you can pin.

A reflective note for contributors and mentees on three hats in open source -- maintainer, mentor, and manager -- learned in that order, with sponsorship as an optional bridge when someone is ready and the program is not. It sketches a soft maturity ladder from Foundations through Hire-ready, and when personal funding keeps a track record growing between cycles. It includes a sponsorship path after a GSoC rejection so the work does not pause for a calendar, and another where a consistent public track record leads through sponsorship to an internship and a permanent role. Organization stipends can become GitHub Sponsors support when orgs pass them through. The numbers are a funnel: hundreds of contributors, dozens of mentees and sponsored people, and a rare hire.

The 2026 PSF Board election fills four seats under Approval Voting through September 15. This post walks every nominee A-Z with links to nomination statements, AMAs, and PSF blog interviews, plus a short evaluative paragraph on each. I have no personal affiliation with any candidate. Facts and links are a best-effort snapshot from those public sources and may be incomplete or wrong. Read the primary materials before you vote, and contact me if something needs a correction.

Parts 1 and 2 covered preparation, contribution, and communication. This part is about the proposal itself -- the document mentors use to judge whether you can finish the work. It starts with strategy for your three slots, including why one or two strong proposals beat three thin ones. From there it covers structure: background, motivation, technical approach, timeline, deliverables, risks, collaboration, and responsible AI use while writing. The goal is a proposal that shows readiness, not just enthusiasm.