Django , for example, has a special landing page to welcome new contributors. These labels make it easy for someone new to your project to quickly scan your issues and get started. You will never interact with most people who land on your project.
- Behind the Net: 101 Incredible Hockey Stories!
- A Splendid Ecstasy: The Trials, Thrills And Joys Of Authorship?
- Spatial Microsimulation for Rural Policy Analysis (Advances in Spatial Science).
- User community.
- A Gringocua Travels Puerto Rico Guayanilla (Pueblos of Puerto Rico Book 31).
- How Possession Can Help You Lose Weight: A Spoof Diet Plan.
- Elizabeth Clansham.
Even a few kind words can keep someone from leaving your project in frustration. We want to start off by saying thank you for using Rubinius. This project is a labor of love, and we appreciate all of the users that catch bugs, make performance improvements, and help with documentation.
Every contribution is meaningful, so thank you for participating. That being said, here are a few guidelines that we ask you to follow so we can successfully address your issue.
People are excited to contribute to projects when they feel a sense of ownership. See if you can find ways to share ownership with your community as much as possible. Here are some ideas:. Give every contributor commit access. If your project is on GitHub, move your project from your personal account to an Organization and add at least one backup admin. Organizations make it easier to work on projects with external collaborators. The reality is that most projects only have one or two maintainers who do most of the work.
Open community approach - Wikiversity
The bigger your project, and the bigger your community, the easier it is to find help. While you may not always find someone to answer the call, putting a signal out there increases the chances that other people will pitch in. And the earlier you start, the sooner people can help. In the early stages of your project, making major decisions is easy. When you want to do something, you just do it. As your project becomes more popular, more people will take interest in the decisions you make. When your community is grappling with a difficult issue, tempers may rise.
People may become angry or frustrated and take it out on one another, or on you. Your job as a maintainer is to keep these situations from escalating. Even if you have a strong opinion on the topic, try to take the position of a moderator or facilitator, rather than jumping into the fight and pushing your views.
If someone is being unkind or monopolizing the conversation, act immediately to keep discussions civil and productive. Other people are looking to you for guidance.
Community & Collaboration
Set a good example. You can still express disappointment, unhappiness, or concern, but do so calmly. The internet thanks you. If people are overly focused on debating the merit of a particular feature, it may help to revisit your README and talk about the higher vision of your project. Some projects use a voting process to make major decisions. Voting can become political, where community members feel pressured to do each other favors or vote a certain way. Sometimes, voting is a necessary tiebreaker. Under a consensus seeking process, community members discuss major concerns until they feel they have been adequately heard.
When only minor concerns remain, the community moves forward. Instead, it prioritizes listening and discussion. Making other people feel heard, and committing to resolving their concerns, goes a long way to diffuse sensitive situations. Then, follow up on your words with actions. Make sure that everybody feels heard and that all information has been made public before moving toward a resolution. Discussion is important, but there is a difference between productive and unproductive conversations.
Encourage discussion so long as it is actively moving towards resolution. Allowing these conversations to continue is not only bad for the issue at hand, but bad for the health of your community. It sends a message that these types of conversations are permitted or even encouraged, and it can discourage people from raising or resolving future issues.
Context is important. Consider who is involved in the discussion and how they represent the rest of the community. Is everybody in the community upset about, or even engaged with, this issue? Or is a lone troublemaker? If the issue does not represent the broader needs of your community, you may just need to acknowledge the concerns of a few people. If this is a recurring issue without a clear resolution, point them to previous discussions on the topic and close the thread.
With a good attitude and clear communication, most difficult situations are resolvable. However, even in a productive conversation, there can simply be a difference in opinion on how to proceed. In these cases, identify an individual or group of people that can serve as a tiebreaker. A tiebreaker could be the primary maintainer of the project, or it could be a small group of people who make a decision based on voting. Your tiebreaker should be a last resort. Divisive issues are an opportunity for your community to grow and learn.
Embrace these opportunities and use a collaborative process to move to a resolution wherever possible.
- Building Welcoming Communities?
- Reggie The Hedgehog!
- In The News.
- Bridges Grading & Hauling, Inc; 03-1874/ 08/02/04?
- CONTACT FORM;
- Registration now open!.
- Table of Contents.
Healthy, thriving communities fuel the thousands of hours poured into open source every week. Many contributors point to other people as the reason for working - or not working - on open source. Making your life easier as an open source maintainer, from documenting processes to leveraging your community.
Growing your community
Facilitate healthy and constructive community behavior by adopting and enforcing a code of conduct. Start with your documentation: Make it easy for someone to use your project. Good first issues : To help new contributors get started, consider explicitly labeling issues that are simple enough for beginners to tackle. GitHub will then surface these issues in various places on the platform, increasing useful contributions, and reducing friction from users tackling issues that are too hard for their level.
When someone new lands on your project, thank them for their interest! It only takes one negative experience to make someone not want to come back. Be responsive. Many contributors start with a bug report or small fix. There are many ways to contribute to a project. Let people help how they want to help. Document everything When you start a new project, it may feel natural to keep your work private. Be responsive As you promote your project , people will have feedback for you. Give your community a place to congregate There are two reasons to give your community a place to congregate.
Home Search Documents. Open Community Contracts. Search for contracts. Master Spreadsheet Download. Our Posting Policy. Further details regarding our posting policy and the criteria we apply in selecting contracts to publish on the site are available at the below button.