Core Infrastructure Initiative best practices about nominally

[vaneseltine]

• The project website MUST succinctly describe what the software does (what problem does it solve?).
• The project website MUST provide information on how to: obtain, provide feedback (as bug reports or enhancements), and contribute to the software.
• The information on how to contribute MUST explain the contribution process (e.g., are pull requests used?) (URL required)
• The information on how to contribute SHOULD include the requirements for acceptable contributions (e.g., a reference to any required coding standard).
• The software produced by the project MUST be released as FLOSS.
• It is SUGGESTED that any required license(s) for the software produced by the project be approved by the Open Source Initiative (OSI).
• The project MUST post the license(s) of its results in a standard location in their source repository. (URL required)
• The project MUST provide basic documentation for the software produced by the project.
• The project MUST provide reference documentation that describes the external interface (both input and output) of the software produced by the project.
• The project sites (website, repository, and download URLs) MUST support HTTPS using TLS.
• The project MUST have one or more mechanisms for discussion (including proposed changes and issues) that are searchable, allow messages and topics to be addressed by URL, enable new people to participate in some of the discussions, and do not require client-side installation of proprietary software.
• The project SHOULD provide documentation in English and be able to accept bug reports and comments about code in English.