Add development agreements documentation #7821
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As demonstrated in #7799, there is currently a lack of clarity regarding our processes and the agreements we have made. To address this and ensure the transfer of knowledge to future team members, I have created the
agreements.rst
file. This file will serve as a central repository for listing all our agreements.I propose a single rule for this document: any changes must receive approval through pull requests from all current developers. This ensures collective agreement and maintains the integrity of our processes.
To initiate the
agreements.rst
with relevant content, I have included our consensus on the branching model, as discussed in the following issues:The importance of having such a document, particularly in a distributed team with considerable turnover, cannot be overstated. Documenting agreements: