This repo was created based on recent discussions around the log4j 0day and what it means for maintainers, consumers of FOSS, and for the open source community at large.
FOSS is not perfect. There are many problems with it, just as with every area of human endeavor.
Before we can solve those problems, we need to determine what they are, seek consensus on their accuracy, and prove the value of solving them. In this process, we may draw the attention of those who can develop solutions.
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
- The user or Contributor SHOULD search for an issue that describes the problem they face or observe.
- If none is found, the user or Contributor SHOULD write the issue by describing the problem they face or observe.
- The user or Contributor SHOULD seek consensus on the accuracy of their observation, and the value of solving the problem.
- Users SHALL NOT log feature requests, ideas, suggestions, or any solutions to problems that are not explicitly documented and provable.