Open HarryHeights opened 5 years ago
When everything is in the README, it is simple to decide where to put information. When there is a separate contributors guide, I need to decide what goes where. Put differently, I'm not sure what should go in it besides the information already in the readme (or how much information should stay in the readme).
I would welcome a PR to add a contributors guide, even if it only has placeholders for me to fill in.
After reading this statement on your readme document, I saw the need for you to have a contributors guide document. First of all, the presence of that document sends out a message to prospective collaborators that you'd like their assistance on your project. Then secondly, it'll help them through the process of contributing to your project.