Skip to content

Latest commit

 

History

History
32 lines (22 loc) · 1.63 KB

File metadata and controls

32 lines (22 loc) · 1.63 KB

We gladly accept community contributions to make the project better. These typically take the form of improvements to either the text, code or both.

License

In our commitment to open-science and open-source, the teaching materials for our mini-course are licensed under the CC-BY-SA license, while thc ode is licensed under the copyleft AGPL3-0 license. All community contributions to the project will fall under the same licenses. We ask that any contributions be your own words and code, and not verbatum copy-and-paste from a LLM.

Sign Your Work

The sign-off is a simple line at the end of the message for a commit. All commits in your pull request need to be signed. Your signature certifies that you wrote the patch or otherwise have the right to contribute the material (see Developer Certificate of Origin):

This is my commit message

Signed-off-by: David Rach <flowcore@som.umaryland.edu>

Git has a -s command line option to append this automatically to your commit message:

$ git commit -s -m "This is my commit message"

Pull Request

  1. Open an issue, mention what you want to do. That way we can avoid misplaced effort of multiple people tackling the same issue separately.
  2. Fork our repository.
  3. Create your own branch.
  4. Make your edits, keeping commit changes restricted to individual files.
  5. Sign all your commits.
  6. When ready, open a pull request from your branch to main.
  7. We will reply with comments, update with any edits.
  8. After review, we will merge or suggest additional changes.