upstream/opnsense-core
1
0
Fork 0
mirror of https://github.com/opnsense/core.git synced 2026-02-18 18:18:13 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

CONTRIBUTING: minor tweaks

Browse source
This commit is contained in:
Franco Fichtner 2016-04-28 08:53:39 +02:00
parent aa21adfe18
commit 160c1245cf
1 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
CONTRIBUTING.md
View file

@ -14,13 +14,13 @@ as there may be workarounds or ideas available.
When creating bug reports, please make sure you provide the following:
* Current OPNsense version where the bug first appeared
* The last OPNsense version where the bug did not appear
* The current OPNsense version where the bug first appeared
* The last OPNsense version where the bug did not exist
* The exact URL of the GUI page involved (if any)
* A list of steps to replicate the bug
All issues reported will have to be triaged and prioritised. As we
are a small time we may not always have the time to implement and help,
are a small team we may not always have the time to implement and help,
but reporting an issue may help others to fill in.
Feature requests that are in line with project goals will eventually
@ -28,8 +28,8 @@ be added to our roadmap:
https://opnsense.org/about/road-map/
Feature requests beyond the scope of OPNsense may still be doable using
the plugin framework:
Feature requests beyond the scope of OPNsense may still be provided
using the plugin framework:
https://github.com/opnsense/plugins
@ -40,9 +40,9 @@ And above all: stay kind and open. :)
Pull requests
-------------
When creating pull request, please heed these points:
When creating pull request, please heed the following:
* Base your code on the latest master branch to avoid manual merges.
* Code review may ensue in order to help shape your proposal.
* Pull request must adhere to 2-Clause BSD licensing.
* Explain the problem and your proposed solution.
* Base your code on the latest master branch to avoid manual merges
* Code review may ensue in order to help shape your proposal
* Pull request must adhere to 2-Clause BSD licensing
* Explain the problem and your proposed solution