CoC: remove constraints on 'release history'

This commit is contained in:
tobtoht 2025-01-29 01:56:06 +01:00
parent 90359e31fd
commit 53cb44c7b7
No known key found for this signature in database
GPG Key ID: E45B10DD027D2472

View File

@ -138,7 +138,6 @@ C4 is meant to provide a reusable optimal collaboration model for open source so
- The user or Contributor SHOULD seek consensus on the accuracy of their observation, and the value of solving the problem.
- Users MUST NOT log feature requests, ideas, or suggestions unrelated to Monero code or Monero's dependency code or Monero's potential/future dependency code or research which successfully implements Monero.
- Users MUST NOT log any solutions to problems (verifiable or hypothetical) of which are not explicitly documented and/or not provable and/or cannot be reasonably proven.
- Thus, the release history of the project MUST be a list of meaningful issues logged and solved.
- To work on an issue, a Contributor MUST fork the project repository and then work on their forked repository.
- To submit a patch, a Contributor MUST create a Platform pull request back to the project.
- A Contributor MUST NOT commit changes directly to the project.