PharoDAYS 2015: How to contribute (to Pharo) by Marcus Denker
0 likes292 views
The document provides guidance on how to contribute to the Pharo open source project. It outlines that contributors can help by reporting bugs and adding details to existing issues, summarizing discussions, finding duplicate issues, asking others to take action, testing fixes, reviewing code fixes, fixing issues themselves, and working with others on issues. The life cycle of an issue is described from being opened to being integrated into Pharo if the fix is approved. Statistics are given that while there are currently over 600 open issues, over 11,000 have been closed in the past year, with over 5 being closed per day on average. Contributing helps improve Pharo's stability and users' productivity over time.
PharoDAYS 2015: How to contribute (to Pharo) by Marcus Denker
- 1. How to Contribute to Pharo
- 2. What?
- 3. Bug Reports
- 4. Cleanups
- 5. Features
- 6. Issue Tracker • https://pharo.fogbugz.com • Need an account (not perfect, we know)
- 7. Life of an Issue • Open a new one • “Work needed” • Fixed (review needed) • Fixed (checked by the monkey) • Fixed (to be integrated) • Fixed (integrated) ==> CLOSE
- 8. You can Help! • report problems • add “how to reproduce” to existing • read and summarize discussions • Find duplicates • ask others to take action
- 9. You can Help 2 • Test fixes: Does it fix the bug? • Review fixes: Does the code look ok? • Fix issues yourself. • You can even team up with someone!
- 10. A lot of work... • The issue tracker needs eyeballs every day • We have 675 open issue • But we CLOSED 11878 • 1983 in 1 year >5 PER DAY!
- 11. But it pays off.. • Pharo got much more stable over the years • People are more productive • Feedback loop: acceleration of improvement
- 13. DEMO: Fixing an Issue