mirror of
https://github.com/monero-project/monero.git
synced 2025-12-10 07:22:34 +01:00
CoC: remove constraints on 'release history'
This commit is contained in:
@@ -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.
|
- 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 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.
|
- 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 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.
|
- 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.
|
- A Contributor MUST NOT commit changes directly to the project.
|
||||||
|
|||||||
Reference in New Issue
Block a user