BIRDSOpenSource / BIRDSOpenSource/BIRDS4-FAB
add contributing guidelines to repo
- Dominant language
- C
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Simply create a document called CONTRIBUTING.md in the root of the repository, use it to describe the preferred issue reporting workflow, and
Make sure to emphasize the importance of submitting issues for anything that the user does not understand.
[Feel free to draw inspiration from here](https://github.com/microsoft/vscode/blob/cf4c4a0ece70d221d907a2bc0042cc164f73bb0c/CONTRIBUTING.md)
You can also **TAKE INSPIRATION** FROM THE FOLLOWING WRITEUP AND ADAPT ACCORDINGLY
Contributing
The main purpose of this repository is to continue evolving React core, making it faster and easier to use. Development of React happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving React.
[Contributing Guide](https://legacy.reactjs.org/docs/how-to-contribute.html)
Read our [contributing guide](https://legacy.reactjs.org/docs/how-to-contribute.html) to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to React.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the requested CONTRIBUTING.md location at the repository root and the linked VS Code and React contributing guides for structure and tone. Document the preferred issue-reporting workflow, including that users should submit issues when they do not understand something. Done means a clear CONTRIBUTING.md exists in the root and covers the requested guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100