Power of Communities
0 likes304 views
The document discusses best practices for participating in and contributing to open source software communities. It recommends communicating transparently without private emails, asking and reporting issues politely by providing necessary details to reproduce problems, writing short emails that stay on topic, and contributing fixes and improvements rather than just requesting changes from others. Participating can be rewarding and communities rely on involvement from both individuals and companies to continuously improve software.
1 of 28
Download to read offline
More Related Content
Similar to Power of Communities (20)
Ad
More from ESUG (20)
Ad
Recently uploaded (20)
Power of Communities
- 2. Expectations Patterns and anti patterns
- 3. What can we expect?
- 4. A lot!
- 6. Sharing is positive energy
- 8. When is the last time you freely learn something for free?
- 10. Communication is key Be transparent No private emails
- 11. Really alone?
- 12. More
- 13. A lot more
- 14. Feature X does not work You turn around during weeks You ramble... But may be this is just that feature X is not the way you think it is
- 15. Solution: Communicate Ask/report nicely May be this is real problem? May be you were wrong? But ask/report and you will know
- 16. Mails
- 17. Mailing-lists auto saturate Too many mails kills communication
- 19. Don’t break a thread! One thread one topic
- 20. Is that mail any “useful”? fun is allowed :)
- 21. Try to answer to the point and not aside :)
- 22. There is no such a thing as “I want that”, “the maintainer of that package should do that”
- 23. Report a bug which system which version can we reproduce it get a unit test
- 24. Companies!? If you rely on a software system how do you expect it to magically get better?
- 25. Wishful thinking or acting Participate to bounty Participate by giving some of your time
- 26. Most of the fixes are trivial 85% of bugs are trivial Focus on them!
- 27. Don’t keep your fixes on your harddisc!
- 28. Join this is fun!