I don't think the actual problem lays with people that are "scared" to contribute. I never spoke to a person that was afraid to do a PR, but I have spoken to people that are demanding but refusing to contribute in any way.
I think by creating a code of conduct (a standardized one), people can point these (unaware) demanding users to that page to create awareness.
I am not talking about people asking questions, I am talking about people "demanding" features (as a good example, strong naming). I recently saw this:
A rando commenter on GitHub decided to tell me to "Strong name ReactiveUI or take it off NuGet". Seriously considering the latter right now.
โ Paul Betts (@paulcbetts) August 5, 2015
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
I think that is part of what's wrong with the OSS world. Because of approaches by people this way, OSS authors build a level of frustration. This, in the end, might lead to a rude-looking response to newcomers, scaring them off.
The combination of a code of conduct and firsttimersonly can be a double-edged sword. It creates awareness for OSS users how much work is involved in getting a library up and running and supporting that. It should never be taking for granted. Once this awareness is created, they might think: "hey, this is a cool library. Let's contribute, but I have no idea how to start." Then any OSS library can point to the firsttimersonly guide and indeed have a few issues.
Note that the default responses are:
- We need this feature finished by monday
- I am too busy
- I also have a family, want to spend time with them
If we can create awareness of their (unintended) behavior, we might get them to contribute and help out a bit as well. And note there are a lot of ways people can contribute:
- Write docs
- Write examples
- Write blog posts
- Pull requests
- etc
I think 1 / 2 / 3 could also be included in the firsttimersonly. People forget that even writing docs is a great way to learn a system and contribute to OSS.