Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Maintaining quality in open source

64 views

Published on

Open source software is unique in the fact that the community can help build and maintain the software project. Because of this, processes must exist to ensure that quality is held to a high standard no matter who contributes. This presentation outlines strategies to effectively engage with the community while ensuring product quality. Some strategies include collaboration guidelines, build scripts, and pull request review processes.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Maintaining quality in open source

  1. 1. Maintaining quality in open source
  2. 2. Quality Engineer @ GitHub /meaghan-lewis meaghan@github.com @iammeaghanlewis
  3. 3. 3 CLIENT APPS
  4. 4. 4
  5. 5. 5
  6. 6. 6
  7. 7. 7
  8. 8. What distinguishes open source projects?
  9. 9. COMMUNITY 9
  10. 10. 1WHY INVOLVEMENT MATTERS
  11. 11. Contributions are key ● Engagement is good ● More eyes on the application ● More ideas for features and enhancements
  12. 12. CONTRIBUTIONS MAKE OR BREAK A PROJECT
  13. 13. ENCOURAGE THE COMMUNITY
  14. 14. Make it easy ● Helpful README ● Have contribution guidelines ● Maintain build & test scripts ● Have templates
  15. 15. Readme
  16. 16. Contributing
  17. 17. Scripts
  18. 18. Run tests in CI automatically
  19. 19. Issue template
  20. 20. Pull request template
  21. 21. COMMUNITY INTERACTIONS
  22. 22. Types of collaboration Issues Pull Requests Support
  23. 23. Issues ● Label issues accordingly ● Triage regularly ● Work with community members
  24. 24. Label issues accordingly
  25. 25. Triage
  26. 26. Work with collaborators
  27. 27. Pull requests ● Have test process & plan ● Test changes ● Give feedback
  28. 28. Define testing process
  29. 29. Manual test scenarios
  30. 30. Confirm PR tested
  31. 31. Support ● Make notices publicly available ● Pre-canned responses ● Have SLA for response
  32. 32. Halp
  33. 33. Canned Replies
  34. 34. Takeaways 1Make information accessible Have processes to support contributors Be responsive and helpful 2 3
  35. 35. Thanks! Any questions? /meaghan-lewis meaghan@github.com @iammeaghanlewis

×