1# Contributing to www 2 3First and foremost, thank you! We appreciate that you want to contribute to 4**www**, your time is valuable, and your contributions mean a lot to us. 5 6## Important! 7 8By contributing to this project, you: 9 10* Agree that you have authored 100% of the content 11* Agree that you have the necessary rights to the content 12* Agree that you have received the necessary permissions from your employer to make the contributions (if applicable) 13* Agree that the content you contribute may be provided under the Project license(s) 14 15## Getting started 16 17**What does "contributing" mean?** 18 19Creating an issue is the simplest form of contributing to a project. But there 20are many ways to contribute, including the following: 21 22- Updating or correcting documentation 23- Feature requests 24- Bug reports 25 26**Showing support for www** 27 28Please keep in mind that open source software is built by people like you, who 29spend their free time creating things the rest the community can use. 30 31Don't have time to contribute? No worries, here are some other ways to show your 32support for **www**: 33 34- star :star: the [project](https://github.com/nbari/www) 35- tweet your support for **www** 36 37## Issues 38 39### Before creating an issue 40 41Please try to determine if the issue is caused by an underlying library, and if 42so, create the issue there. Sometimes this is difficult to know. We only ask 43that you attempt to give a reasonable attempt to find out. Oftentimes the readme 44will have advice about where to go to create issues. 45 46Try to follow these guidelines 47 48- **Investigate the issue** 49- **Check the readme** - oftentimes you will find notes about creating issues, and where to go depending on the type of issue. 50- Create the issue in the appropriate repository. 51 52### Creating an issue 53 54Please be as descriptive as possible when creating an issue. Give us the information we need to successfully answer your question or address your issue by answering the following in your issue: 55 56- **version**: please note the version of **www** are you using 57- **extensions, plugins, helpers, etc** (if applicable): please list any extensions you're using 58- **error messages**: please paste any error messages into the issue, or a [gist](https://gist.github.com/) 59 60### Closing issues 61 62The original poster or the maintainer's of **www** may close an issue at 63any time. Typically, but not exclusively, issues are closed when: 64 65- The issue is resolved 66- The project's maintainers have determined the issue is out of scope 67- An issue is clearly a duplicate of another issue, in which case the duplicate issue will be linked. 68- A discussion has clearly run its course 69 70 71## Pull Request Process 72 73- Make sure the destination branch is **develop**, We are using git-flow. 74 75 76[so]: http://stackoverflow.com/questions/tagged/www 77