Bringing Pinax Back to Life- PyCon US Maintainers Summit

Transcript

1. Bringing Pinax Back to Life By Katherine “Kati” Michel
2. About Me 2
3. In Summary Without a long term strategy, Pinax became difficult to maintain. I’ll tell you the problems and possible solutions, so we can learn from it.
5. Time Machine: 2008
6. How It Began Personal Sites Inspiring Reusable Features
7. Fast Forward: 2017 Photo by Adam Gregory of https://atomimages509.wixsite.com/atom
8. How It Was Going “Pinax is every idea I’ve ever had.”
9. How It Was Going 80 Projects and Apps account blog static stripe waitinglist zero company documents team-wiki wiki forums socialauth Pinax Themes Popular Pinax Apps Pinax Starter Projects django-user-accounts pinax-stripe pinax-announcements pinax-badges pinax-blog pinax-calendars pinax-cohorts pinax-comments pinax-documents pinax-eventlog pinax-events pinax-forums pinax-images pinax-invitations pinax-likes pinax-messages pinax-news pinax-notifications pinax-points pinax-ratings pinax-referrals pinax-submissions pinax-teams pinax-testimonials pinax-types pinax-waitinglist pinax-webanalytics pinax-wiki pinax-templates pinax-theme-bootstrap
10. How It Was Going GitHub Organization, Global Docs, and Slack
11. How It Was Going Sustainability lacking
12. Simplified, Self-Service, Self-Sustaining
13. Problem: Tribal knowledge Solution: Document the tribal knowledge
14. Documentation • Highly valued • Often overlooked • And a means for establishing inclusive and accessible communities -From GitHub’s 2017 Open Source Survey
15. Pinax Documentation
16. Problem: Existing docs difficult to find, duplicated, and inconsistent Solution: One source of docs, easy to find, use
17. One Source of Docs
18. Problem: Variations in configurations Solution: Choose one configuration approach and implement across projects
19. One Configuration Approach
20. Problem: Lack of engagement with individuals Solution: Reduce backlog of issues and PRs and catch up with engagement
21. Engagement with Individuals • Over 160 issues closed • Over 100 PRs merged • Over 30 PRs closed • Countless questions answered in issues and Slack
22. Problem: Lack of engagement with the community Solution: Write more blog posts and publicize well
23. Engagement with Community
24. Problem: Tasks being done manually Solution: Automate tasks
25. How It’s Going: July 2020 Release • 28 apps included • Support for Python 2.7 dropped • A huge milestone for me personally and professionally
26. How It’s Going: 21.05 Release • Time to update Python/Django test matrix • Implement automation that didn’t make it into the last release (run tox from GA, auto-publish to PyPI) • Global documentation should be improved
27. Biggest Lesson Learned: Release Succeeded Due to My Communication and Teaching Skills • Blog posts attracted contributors • Release documentation enabled them to help, to mutual benefit
28. Additional Ideas • Bring on additional maintainers: selective permissions • Workflow: protect branches, status checks, require review • Automation: GitHub Actions/Apps, Probot • Reduce scope: archive repos, mark repos as deprecated, disable issues • Productivity: GitHub built in functionality (canned responses, notifications management, etc.)
29. Challenge and Opportunity
30. Thank You! Twitter: KatiMichel GitHub: KatherineMichel Email: kthrnmichel@gmail.com