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)
question: “what features would you love to see?” ‣ Flesh out documentation, note where documentation is lacking ‣ Community evangelism, speak, teach, and spread your love for the project ‣ Submit new questions to the project’s Q&A forums, or take a stab at an answer ‣ Host a genius bar at the next local meetup ‣ Translate the project into a different language ‣ Give feedback on proposed bug fixes and features, propose new ones ‣ Recruit new developers Opportunities to contribute
this thing written in? ‣ Do I need a lawyer to know if I can use it? ‣ How do I bootstrap my local development environment ‣ How do I submit an improvement? How long will it take to merge?
to run the project locally in the README) ‣ Daily (Provide constructive and supportive feedback, express gratitude when merging or commenting) ‣ Going Forward (Automate testing with continuous integration, minimize friction through shared tooling)
the easy part 2. Start small, go through the motions 3. Minimize information imbalance 4. Embrace the constraints of open source 5. Open source problems, not solutions 6. Expand your definition of stakeholders 7. Be the hub, encourage spokes 8. Minimize friction 9. Decentralize governance 10. Encourage contributors Internal collaboration External engagement