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