Confirmed users
14,525
edits
User:Ashughes/Iris Community Engagement Plan: Difference between revisions
Jump to navigation
Jump to search
User:Ashughes/Iris Community Engagement Plan (view source)
Revision as of 08:23, 16 May 2019
, 16 May 2019→Phase 3: Profit
| Line 50: | Line 50: | ||
= Phase 3: Profit = | = Phase 3: Profit = | ||
= Other Considerations = | |||
* Select a communication platform (Slack, Discourse, Github, etc) | |||
* Where possible, use bots for leaderboards, to welcome newcomers, to help people find tasks, and to enable people to engage | |||
* Ensure you have a code of conduct, create a safe space for people to work how they want to work and to make mistakes | |||
* Help your helpers: get them access to core Engineering resources, invite them to chats/calls to further their understanding and engagement, point them towards programs to collaborate with individuals. The more community members turn into experts, and the more experts turn into professionals on your platform, the better it is for everyone. | |||
* Create contests to spur rapid development of a specific deliverable | |||
* Blog about your project and community, encourage those in your community to do the same, and amplify those posts. | |||
* Periodically feature a member of the community | |||
* Send swag, stickers, etc of your community to your community | |||
* Think about how you're helping to build careers | |||
* Periodically reflect on the state of your community, identify areas for improvement and commit to solving one problem. | |||
* Set Goals and Measure Results. How will you benefit from this collection of potential advisors, critics, contributors, and customers? What are your critical metrics, and how can you measure them? Identify your main goal: Is it software downloads? Getting developers to contribute to your project? Adding names to your developer mailing list? For example, consider using the “Unique clones” number included in the Traffic Statistics section of the GitHub repo reports as it'll give you a good idea of your daily download activity. Also log all of the GitHub repository statistics on a regular basis: Stars, Forks, Issues, Pull Requests as these statistics give you usage “signals.” | |||
* Estimate future marketing activities and product evolution and put a straw-man plan in place, this will give you a way to measure progress against any plan. | |||
* Consider the tech you're using and how you can utilize external communities centred around that tech to bolster your project (eg. Hackernews) | |||
* Excellent documentation is the first step in making your software easy-to-use, make sure you have readmes, the API, and supporting technical documentation in place. | |||
* Code of conduct: In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. | |||
* Make it easy for developers to ask and answer questions. (IRC is one of the primary channels we use. There is usually one of our developers “lurking” around there somewhere.) | |||
* Identify issues for first-timers | |||
* Documentation edits are a great way to gain experience in an open source project. | |||
* Getting the opinions of your users reveals whether your code is meeting its big-picture goals. | |||
* In addition to user interviews, attend conferences and meetups to build awareness and find the right audience. Even when you aren’t presenting, attending these events and speaking to developers directly is a great way to get feedback. Face-to-face interactions often help us build a better understanding of the problems and challenges that developers face. | |||
* Listen to feedback | |||