Skip to content

Latest commit

 

History

History
67 lines (47 loc) · 2.45 KB

README.md

File metadata and controls

67 lines (47 loc) · 2.45 KB
Raw

Ovio - Idea Box

You recently visited ovio.org and have ideas or feedback for Ovio? You're in the right place!

Contributing to Ovio

We are building Ovio for you, the organizations and volunteers using technology for good. We welcome all your feedback and ideas to keep improving your experience!

Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.

Following these guidelines helps to communicate and respect the time of everyone involved.

Using the issue tracker

The issue tracker is the preferred channel for bug reports and features requests, but please respect the following restrictions:

  • Please do not use the issue tracker for personal support requests.

  • Please do not derail or troll issues. Keep the discussion on topic and respect the opinions of others.

  • Please do tag your issues and let us know if this is a bug or a feature request.

Bug reports

A bug is a demonstrable problem that is caused by the code in the repository. Good bug reports are extremely helpful - thank you!

Guidelines for bug reports:

Use the GitHub issue search — check if the issue has already been reported.

A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome? All these details will help people to fix any potential bugs.

Example:

Short and descriptive example bug report title

A summary of the issue and the browser/OS environment in which it occurs. If suitable, include the steps required to reproduce the bug.

  1. This is the first step
  2. This is the second step
  3. Further steps, etc.

Any other information you want to share that is relevant to the issue being reported. This might include the lines of code that you have identified as causing the bug, and potential solutions (and your opinions on their merits).

Feature requests

Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.