- Each use case is described by a Markdown file in the
use-cases/cases/directory, one file per use-case.- Choose a simple descriptive filename, avoid spaces, and mind that filenames are case-sensitive.
- All documents should be plain text following Markdown syntax and always use the UTF-8 character encoding. Use the
.mdextension. - We recommend you use this template as a basis for your use case document, but feel free to add things or deviate from it if it's not sufficient for your needs. Do make sure to check out the template for an idea of the information we request.
- You can use any text editor you like, or edit online through the interface offered by Github.
- Link to your document from the
use-cases/README.md, where you have room for a simple title and optionally a short description. You can just copy and adapt one of the existing entries. - Submit your contributions by pushing directly to this repository if you as a Pull Requests. This automatically opens up a thread for discussion and peer review of your contributions and will notify all group members. A coordinator can finally approve and merge your contributions.
- Trivial contributions (spelling corrections etc) can be contributed directly if you have push access to the repository.
- If you prefer to push directly to the repository and skip the review/discussion stage offered by the Pull Request, then that is fine too at this point in time.
See the generic contributing guidelines for further instructions.