| Date | Status | Decided By | Description |
|---|---|---|---|
| 10/12/2023 | Accepted | - Nick Bauters | Initial version |
This document provides guidelines for contributing to the project and describes where everything is documented. This document should always be read before querying the project owner for questions and contribution requests.
If you want to contribute to this project, you can contact the project owner via GitHub. Before contacting, make sure to at least read this document thoroughly.
- Read the README file.
- Read the Contributing guidelines
- Read the Cooperative rulesets
- Read the Architectural decisions
- Query the project owner
- Wait for response
- The project owner will investigate your query
- The project owner will respond to the query
- When positive 10. You will receive links to the project 11. A branch will be created for an update to the contribution guidelines and readme file.
- Declares to have read all the required documentation and agrees to these documents.
- Declares to follow all set rules and guidelines.
A contributor will automatically stop being a contributer when:
- The project is finished
- The contributor is no longer contributing to the project for over 6 months
- The contributer whishes to stop contributing and has communicated this to the project owner
| Name | Role | Started | Stopped |
|---|---|---|---|
| Nick Bauters | Project Owner | 10/12/2023 | not applicable |
Cooperative rulesets are basic documents that describe how to work together on this project. These documents are archived in markdown and can be found in the Cooperative documentation folder.
These documents are ordered in specific cases and contain the context of the case, the general aproach to the case. And addition information.
Currently, the following cases are available:
- C001-git: How to work with Git in this project.
- C002-gitHub: How GitHub is used and implemented in this project.
- C003-issues: How feature requests and bugs are used and implemented in this project.
- C004-development-installation: How to install the project for development purposes.
Architectural decisions are decisions that are made during the development of the project. These decisions start as investigations and are documented in the Architectural decisions folder.
The investigative nature of these documents, means that they are not always correct and or implemented. You should always read the entire document and pay extra attention to the decision outcome.
Currently, the following decisions are available:
Not applicable
No adjustments made to the decision log.