GitHub already made this easier, but I feel like they just aren't pushing it in front of everyone early enough. They added support for the CONTRIBUTING/CONTRIBUTING.md file[1], but it is only displayed when opening up an issue or pull request. I think all they would really need to do is advertise projects which have a properly set up file while browsing, similar to how README files are already displayed. If a person wants to contribute, telling them how to contribute only after opening up an issue/PR is a bit late, no?
It seems like contriubtion guidelines aren't necessarily what the author is pushing. AFIK, this wouldn't help new developers get up to speed with the code base.
Comments
GitHub already made this easier, but I feel like they just aren't pushing it in front of everyone early enough. They added support for the CONTRIBUTING/CONTRIBUTING.md file[1], but it is only displayed when opening up an issue or pull request. I think all they would really need to do is advertise projects which have a properly set up file while browsing, similar to how README files are already displayed. If a person wants to contribute, telling them how to contribute only after opening up an issue/PR is a bit late, no?
[1] https://github.com/blog/1184-contributing-guidelines
It seems like contriubtion guidelines aren't necessarily what the author is pushing. AFIK, this wouldn't help new developers get up to speed with the code base.
Well it would if owners set up their readme / contrib pages with a good overview of
- "getting started as a developer"
- "this is how this works"
- "new developers should start reading here, browse here, and ignore this until later"
style info. I think this is what the AP was bringing up. And it is what was being discussed in the blog post. Lowering the barrier to entry.