more/libCEED/CONTRIBUTING.md

4 <!---
5 Please use a pull request to the appropriate branch ('stable' for backward-compatible bug fixes for…
6 -->
7 …e your commits well-organized and [atomic](https://en.wikipedia.org/wiki/Atomic_commit#Atomic_comm…
8 Check that tests (including "examples") pass using `make prove-all`.
11 In typical development, every commit should compile, be covered by the test suite, and pass all tes…
12 …efficiency of reviewing and facilitates use of [`git bisect`](https://git-scm.com/docs/git-bisect).
15 It is useful to create a WIP (work in progress) pull request for any long-running development so th…
20 …-by: Helpful User <helpful@example.com>` or [`Co-authored-by: Snippet Mentor <code.by@comment.com>…
22 If your author information or email becomes inconsistent (look at `git shortlog -se`), please edit …
24 … and support it, their names are included in the automatically generated user-manual documentation.
45 … that a record of the contribution (including all personal information I submit with it, including…
50 …ntributors receive appropriate recognition through informal and academically-recognized credit sys…
58 …ublications about libCEED as a whole, including DOI-bearing archives, shall offer co-authorship to…
59 … libCEED contributions shall evaluate those listed in `AUTHORS` and offer co-authorship to those w…
61 …-authorship expectation for those publishing about use of libCEED (versus creation of new features…