Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Bringing Pinax Back to Life- FOSDEM

Bringing Pinax Back to Life- FOSDEM

KatherineMichel

January 18, 2021
Tweet

More Decks by KatherineMichel

Other Decks in Technology

Transcript

  1. 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.
  2. Re-Inventing the Wheel “Re-inventing the wheel makes a lot of

    sense if your goal is to understand wheels better.” -James Tauber
  3. 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
  4. Critical Problems • Tribal knowledge • Existing docs difficult to

    find, duplicated, inconsistent • Variation in configurations • Lack of engagement with individuals • Lack of engagement with the community • Tasks being done manually
  5. Solutions • Document tribal knowledge • Make one source of

    docs, easy to find, and use • Choose one configuration approach, across projects • Reduce the backlog of issues and PRs • Write more blog posts and publicize well • Automate more tasks
  6. Documentation • Highly valued • Often overlooked • And a

    means for establishing inclusive and accessible communities -From GitHub’s 2017 Open Source Survey
  7. Engagement with Individuals • Over 160 issues closed • Over

    100 PRs merged • Over 30 PRs closed • Countless questions answered in issues and Slack
  8. How It’s Going • Automation is still lacking • Global

    documentation is in need of improvement
  9. 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
  10. Additional Ideas • Automation: GitHub Actions/Apps, Probot • Workflow: protect

    branches, status checks, require review • Reduce scope: archive repos, mark repos as deprecated, disable issues • Bring on additional maintainers: selective permissions • Productivity: GitHub built in functionality (canned responses, notifications management, etc.)