diff --git a/CONTRIBUTING_8md_source.html b/CONTRIBUTING_8md_source.html index 65bcbca97..ab2a40f4b 100644 --- a/CONTRIBUTING_8md_source.html +++ b/CONTRIBUTING_8md_source.html @@ -5,7 +5,7 @@ -EnTT: docs/CONTRIBUTING.md Source File +EnTT: docs/md/CONTRIBUTING.md Source File @@ -22,7 +22,7 @@
EnTT -  2.7.3 +  3.0.0
@@ -60,10 +60,10 @@ $(function() {
-
docs/CONTRIBUTING.md
+
docs/md/CONTRIBUTING.md
-
1 # Contributing
2 
3 First of all, thank you very much for taking the time to contribute to the
4 `EnTT` framework.<br/>
5 How to do it mostly depends on the type of contribution:
6 
7 * If you have a question, **please** ensure there isn't already an answer for
8  you by searching on GitHub under
9  [issues](https://github.com/skypjack/entt/issues). Do not forget to search
10  also through the closed ones. If you are unable to find a proper answer, feel
11  free to [open a new issue](https://github.com/skypjack/entt/issues/new).
12  Usually, questions are marked as such and closed in a few days.
13 
14 * If you want to fix a typo in the inline documentation or in the README file,
15  if you want to add some new sections or if you want to help me with the
16  language by reviewing what I wrote so far (I'm not a native speaker after
17  all), **please** open a new
18  [pull request](https://github.com/skypjack/entt/pulls) with your changes.
19 
20 * If you found a bug, **please** ensure there isn't already an answer for you by
21  searching on GitHub under [issues](https://github.com/skypjack/entt/issues).
22  If you are unable to find an open issue addressing the problem, feel free to
23  [open a new one](https://github.com/skypjack/entt/issues/new). **Please**, do
24  not forget to carefully describe how to reproduce the problem, then add all
25  the informaion about the system on which you are experiencing it and point out
26  the version of `EnTT` you are using (tag or commit).
27 
28 * If you found a bug and you wrote a patch to fix it, open a new
29  [pull request](https://github.com/skypjack/entt/pulls) with your code.
30  **Please**, add some tests to avoid regressions in future if possible, it
31  would be really appreciated. Note that the `EnTT` framework has a
32  [coverage at 100%](https://coveralls.io/github/skypjack/entt?branch=master)
33  (at least it was at 100% at the time I wrote this file) and this is the reason
34  for which you can be confident with using it in a production environment.
35 
36 * If you want to propose a new feature and you know how to code it, **please**
37  do not issue directly a pull request. Before to do it,
38  [create a new issue](https://github.com/skypjack/entt/issues/new) to discuss
39  your proposal. Other users could be interested in your idea and the discussion
40  that will follow can refine it and therefore give us a better solution.
41 
42 * If you want to request a new feature, I'm available for hiring. Take a look at
43  [my profile](https://github.com/skypjack) and feel free to write me.
+
1 # Contributing
2 
3 First of all, thank you very much for taking the time to contribute to the
4 `EnTT` framework.<br/>
5 How to do it mostly depends on the type of contribution:
6 
7 * If you have a question, **please** ensure there isn't already an answer for
8  you by searching on GitHub under
9  [issues](https://github.com/skypjack/entt/issues). Do not forget to search
10  also through the closed ones. If you are unable to find a proper answer, feel
11  free to [open a new issue](https://github.com/skypjack/entt/issues/new).
12  Usually, questions are marked as such and closed in a few days.
13 
14 * If you want to fix a typo in the inline documentation or in the README file,
15  if you want to add some new sections or if you want to help me with the
16  language by reviewing what I wrote so far (I'm not a native speaker after
17  all), **please** open a new
18  [pull request](https://github.com/skypjack/entt/pulls) with your changes.
19 
20 * If you found a bug, **please** ensure there isn't already an answer for you by
21  searching on GitHub under [issues](https://github.com/skypjack/entt/issues).
22  If you are unable to find an open issue addressing the problem, feel free to
23  [open a new one](https://github.com/skypjack/entt/issues/new). **Please**, do
24  not forget to carefully describe how to reproduce the problem, then add all
25  the information about the system on which you are experiencing it and point
26  out the version of `EnTT` you are using (tag or commit).
27 
28 * If you found a bug and you wrote a patch to fix it, open a new
29  [pull request](https://github.com/skypjack/entt/pulls) with your code.
30  **Please**, add some tests to avoid regressions in future if possible, it
31  would be really appreciated. Note that the `EnTT` framework has a
32  [coverage at 100%](https://coveralls.io/github/skypjack/entt?branch=master)
33  (at least it was at 100% at the time I wrote this file) and this is the reason
34  for which you can be confident with using it in a production environment.
35 
36 * If you want to propose a new feature and you know how to code it, **please**
37  do not issue directly a pull request. Before to do it,
38  [create a new issue](https://github.com/skypjack/entt/issues/new) to discuss
39  your proposal. Other users could be interested in your idea and the discussion
40  that will follow can refine it and therefore give us a better solution.
41 
42 * If you want to request a new feature, I'm available for hiring. Take a look at
43  [my profile](https://github.com/skypjack) and feel free to write me.