Opportunities to contribute ‣ ‣ Community Kick the tires, does it ‣ Translate the project evangelism, speak, work? into a different teach, and spread your language ‣ love for the project Answer the question: “what features would ‣ ‣ Give feedback on Submit new questions you love to see?” proposed bug fixes to the project’s Q&A and features, propose ‣ forums, or take a stab Flesh out new ones at an answer documentation, note where documentation ‣ ‣ Recruit new Host a genius bar at is lacking developers the next local meetup
Successful open source projects operate with rough consensus among (all) stakeholders !
Best Practice #2: Minimize information imbalance !
Open source is about growing a community
Work outside the firewall !
‣ Procedurally ( ) (One issue tracker, one way to provide feedback or discuss features; minimize and memorialize meatspace discussions)
‣ Day-to-day( ) (The project’s status, how to submit an issue/feature request or contribute a fix/enhancement) ( ・ ・ ) ‣ Long-term( ) (Project mission statement, philosophy, and goal, features and requirements list, project roadmap)( ・ )
Best Practice #3: Optimize for developers !
You can have open source without executive oversight !
You can have open source without policy guidance !
You can’t have open source without developers !
You can’t have open source without code !
Best Practice #4: Start small, go through the motions !
You wouldn’t run a marathon without training !
Organizations have muscle memory !
Open source is scary (they will say “no” at first)
( NO ) !
1. Start by experimenting with “open source” in private
(Best lunch places near your office, the office’s favorite chocolate chip cookie recipe) ( ) 2. Get everyone involved
(legal, procurement, ethics, etc.)
3. Ship 0.1, not 1.0 1.0 0.1
(and manage expectation)( )
Best Practice #5: Open source problems, not solutions !
Developers want to contribute to a cause not provide free labor
“Yes we can”, not “yes we did” !
If you’re happy with your ship, you’ve shipped too late !
Secrets of successful open source projects Internal collaboration External engagement 1. The technology is the easy part 6. Expand your definition of stakeholders 2. Start small, go through the motions 7. Be the hub, encourage spokes 3. Minimize information imbalance 8. Minimize friction 4. Embrace the constraints of open source 9. Decentralize governance 5. Open source problems, not solutions 10. Encourage contributors
How to f ! oster an open source culture inside Government @benbalter firstname.lastname@example.org government.github.com github.co.jp email@example.com