Small fix to contribution section
This commit is contained in:
parent
265f96309b
commit
779938e54d
|
@ -59,5 +59,5 @@ You are very welcome to contribute. If you have a new feature in mind, you can a
|
|||
* Try to keep the API as minimal as possible. That means if a feature or fix can be implemented without affecting the existing API but requires more development time, then we will opt to sacrifice development time.
|
||||
* Solutions need to be POSIX compliant. The thread-pool is advertised as such so it makes sense that it actually is.
|
||||
* For coding style simply try to stick to the conventions you find in the existing codebase.
|
||||
* Tests: A new fix (and sometimes a feature) should be covered by tests. If the existing tests are not sufficient, we expect an according test to follow with the pull request.
|
||||
* Tests: A new fix or feature should be covered by tests. If the existing tests are not sufficient, we expect an according test to follow with the pull request.
|
||||
* Documentation: for a new feature please add documentation. For an API change the documentation has to be thorough and super easy to understand.
|
||||
|
|
Loading…
Reference in New Issue