Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (11)
Ähnlich wie Staking Your Claim In Open Source
Ähnlich wie Staking Your Claim In Open Source (20)
Mehr von evanphx
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Staking Your Claim In Open Source
- 1. Staking Your Claim in OSS How To Succeed at Open Source Development Wednesday, October 13, 2010
- 2. Rubinius Evan Phoenix Engine Yard Wednesday, October 13, 2010
- 3. 4 Laws/Guidelines Wednesday, October 13, 2010
- 4. 1 Contributors are a privilege Wednesday, October 13, 2010
- 5. 2 “No” is an acceptable answer Wednesday, October 13, 2010
- 6. 3 Responsibility is power Wednesday, October 13, 2010
- 7. 4 Communicate. A lot. Wednesday, October 13, 2010
- 8. Be nice. Wednesday, October 13, 2010
- 9. They’re doing you a favor. Wednesday, October 13, 2010
- 10. Keep your cool Wednesday, October 13, 2010
- 11. Case Study 1: The unwanted feature Wednesday, October 13, 2010
- 12. Contributor: “I added the ability to avoid flushing the toilet!” Wednesday, October 13, 2010
- 13. Wednesday, October 13, 2010
- 14. What you might think: “What an idiot.” Wednesday, October 13, 2010
- 15. Deep Breath. Chillax. Apply the laws. Wednesday, October 13, 2010
- 16. What you say: “Great! But we’re not ready to integrate that.” Wednesday, October 13, 2010
- 17. Talk about: • Why they want it. • Why you don’t. Wednesday, October 13, 2010
- 18. Forking for all the right reasons Wednesday, October 13, 2010
- 19. Fork for love, not for hate Wednesday, October 13, 2010
- 20. Bad Reason: “The other devs are assholes.” Wednesday, October 13, 2010
- 21. Good Reason: “I want to experiment with something new.” Wednesday, October 13, 2010
- 22. Fork in public Wednesday, October 13, 2010
- 23. Be the forks friend Wednesday, October 13, 2010
- 24. Process Wednesday, October 13, 2010
- 25. Too much process = contributor pain Wednesday, October 13, 2010
- 26. Too little process = project pain Wednesday, October 13, 2010
- 27. Avoid complicated setup/workflow Wednesday, October 13, 2010
- 28. Premature process is the root of all frustration Wednesday, October 13, 2010
- 29. Case Study 2: Controlling the Chaos Wednesday, October 13, 2010
- 30. Contributor: “Here are 10 new patches!” Wednesday, October 13, 2010
- 31. Wednesday, October 13, 2010
- 32. Committer: “These patches overlap with stuff we already wrote,” Wednesday, October 13, 2010
- 33. Committer: “And they introduce 5 new dependencies...” Wednesday, October 13, 2010
- 34. Committer: “And they’re in a completely different style.” Wednesday, October 13, 2010
- 35. Wednesday, October 13, 2010
- 36. Remember the laws. Wednesday, October 13, 2010
- 37. Use this as a teachable moment Wednesday, October 13, 2010
- 38. Committer: “Thanks for all the hard work, we need to discuss this first.” Wednesday, October 13, 2010
- 39. Discuss • How to keep patches up to date • Architecture integration • Adhering to style guide Wednesday, October 13, 2010
- 40. Revise Process • How and when to submit patches • Document architecture and style guide Wednesday, October 13, 2010
- 41. Worst Case Wednesday, October 13, 2010
- 42. Contributor: “I’m not willing to change for you.” Wednesday, October 13, 2010
- 43. Committer: “Sorry to hear that, have a good life.” Wednesday, October 13, 2010
- 44. Best Case Wednesday, October 13, 2010
- 45. Common Case Wednesday, October 13, 2010
- 46. Contributor: “No problem, I’ll get right on that.” Wednesday, October 13, 2010
- 47. Enthusiasm is Transformative Wednesday, October 13, 2010
- 48. Easy Wins Wednesday, October 13, 2010
- 49. “How can I help?” Wednesday, October 13, 2010
- 50. Simple goals, easy tasks Wednesday, October 13, 2010
- 51. Run this command, fix what is broken. Wednesday, October 13, 2010
- 52. Rubinius & RubySpec Wednesday, October 13, 2010
- 53. 90%+ committers Wednesday, October 13, 2010
- 54. Dirkjan Bussink Wednesday, October 13, 2010
- 55. Wednesday, October 13, 2010
- 56. commit 5386d9299360b5f1ede14392b97da6dc7163ed00 Author: Dirkjan Bussink <d.bussink@gmail.com> Date: Tue Jan 8 20:29:01 2008 +0100 Added Process::POSIX safety checks kernel/core/process.rb | 87 +++++++++++++++++++++++++++++++++++------------ 1 files changed, 65 insertions(+), 22 deletions(-) Wednesday, October 13, 2010
- 57. 446 commits Wednesday, October 13, 2010
- 58. Easy wins are a gateway drug. Wednesday, October 13, 2010
- 59. No Core Team Wednesday, October 13, 2010
- 60. Trust is transformative Wednesday, October 13, 2010
- 61. Rubinius Wednesday, October 13, 2010
- 62. One Patch == Commit Privileges Wednesday, October 13, 2010
- 63. Responsibility > Privilege Wednesday, October 13, 2010
- 64. Skeptic: “There will be chaos.” Wednesday, October 13, 2010
- 65. > 10 reverts Wednesday, October 13, 2010
- 66. Why? Wednesday, October 13, 2010
- 68. But... Wednesday, October 13, 2010
- 69. Conflicts with “No” Wednesday, October 13, 2010
- 70. Communicate about features Wednesday, October 13, 2010
- 71. Advocate forks/ branches for new features Wednesday, October 13, 2010
- 72. As a contributor... Wednesday, October 13, 2010
- 73. Remember these laws. Wednesday, October 13, 2010
- 74. Don’t take it personally. Wednesday, October 13, 2010
- 75. OSS is a social contract Wednesday, October 13, 2010
- 76. Contributors want to succeed Wednesday, October 13, 2010
- 77. Contributors want to respect Wednesday, October 13, 2010
- 78. Give respect, get respect. Wednesday, October 13, 2010
- 79. We all just want to be loved. Wednesday, October 13, 2010