"Keynote: Changelong"
summary
Argues that big non-code changes — the change long of processes, governance, docs and tooling — require the same proposals, reviews and records as code. Gives specifics: Python kept 2.x and 3.x for 14 years, accepted pattern matching after ~20 years of debate, migrated source to Git/GitHub starting 2017 and only recently moved a 15-year issue tracker, archived a 1999 mailing list in favor of Discourse, and still uses reStructuredText since 2002 while only 128 people currently vote in steering elections.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:29What is changelog
- 2:32Why changelogs matter
- 3:58Deprecations and changes
- 7:39Human changes are hard
- 10:13Pushback against change
- 15:38Cost of resisting change
- 16:00Python’s evolution
- 25:03Non-code changes as code
- 26:10Change processes
- 29:03Wishlist for Python
- 32:39Call to action
related talks
01h 10mKeynote 2: Robust Python and Why It Matters
35mInterview
42mKeynote - Steering Council Panel
01h 00mKEYNOTE / Python Steering Council
54mCore Python Devs on how COVID has changed core Python development
41mHow to Grow an Open Source Project: A Case Study of Python
01h 01mKeynote 2: The State of Python in 2024
44mKeynote
