Mariatta's Python Language Summit 2018 Presentation

Presented at Python Language Summit 2018. Since we were out of time, I only managed to present only the first (and most important) topic.

Related LWN article: https://lwn.net/Articles/754779/

Transcript

1. @mariatta Python Language Summit 2018
 
 @mariatta
2. Let’s Use GitHub Issues! @mariatta Python Language Summit 2018
 
 @mariatta
3. Rationale ✤ We’re already using GitHub issues for other Core Python projects: ✤ Dev guide, core workflow, all the bots, PEPs, peformance, docsbuild scripts, Cpython reps Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
4. Rationale ✤ Other popular open source projects are using GitHub issues ✤ People are likely to already have a GitHub account ✤ The b.p.o is just so hard to use!!! Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
5. B.p.o maintenance ✤ In mercurial ✤ Few people maintains it ✤ Do current maintainers even want to continue maintaining it? ✤ How to contribute? Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
6. B.p.o annoyances ✤ I can never search for anything ✤ The “nosy” list ✤ Email address is exposed ✤ Contributors need two accounts: b.p.o & GitHub Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
7. Why GitHub is better ✤ APIs and automations ✤ Email notifications contain metadata (https:// help.github.com/articles/about-email-notifications/) ✤ Issue template ✤ Emoji and markdown Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
8. Migrating to GitHub Issues ✤ Migrate the CLA host (something new, or DocuSign) ✤ Freeze the b.p.o (make it readonly, but not shutdown) ✤ New issues to be created in GitHub Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
9. Migrating to GitHub Issues ✤ Old and languishing issues should just be closed / ignored ✤ Button to copy over issue and comments from b.p.o to GitHub Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
10. Comments so far? Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
11. Blurb on the Web ✤ `blurb add` but on the web ✤ Login with GitHub ✤ Let’s you add news entry to your own PRs ✤ Core devs can add news entry to any PRs ✤ Need web host (costs money) Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
12. Automerge PRs (on master) ✤ https://github.com/python/core-workflow/issues/29 ✤ Let the bot automatically merge PRs with passing CIs and approved core dev review ✤ Label the PR with: “automerge” ✤ Real question: how to come up with commit message? Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
13. Automerge PRs (on master) ✤ Make miss-islington work on PRs on master too? ✤ Reminding people that status checks is now done. ✤ But this might be too noisy on master Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta
14. Misc/ACKs as status checks ✤ https://github.com/python/core-workflow/issues/7 ✤ We still want to come up with better way to handle Misc/ACKs, or auto-generate it. ✤ At the very least, bedevere can check if contributor’s name is listed in Misc/ACKs. Python Language Summit 2018
 Let’s Use GitHub Issues!
 @mariatta