Conda is an Open Source project with a diverse and wide-ranging ecosystem.
To better allow community members to provide feedback and proposals for conda's implementation, all major changes should be submitted as Conda Enhancement Proposals (CEP).
These proposals are similar to conda-forge's CFEP, Python's PEP and IPython's IPEP processes etc.
Community members are encouraged to author a CEP to suggest changes before any code is written to allow for the community to discuss the proposed changes.
The formal process by which CEPs should be authored and how they are reviewed and resolved is specified in CEP 1.
A template for new CEPs is given in CEP 0.
- Conda should be written in lowercase, whether in reference to the tool, ecosystem, packages, or organization.
- References to the conda command should use code formatting (i.e.
conda). - If the use of conda is not a command and if conda is at the beginning of a sentence, conda should be uppercase.
Beginning a sentence:
- Conda is an open-source package and environment management system.
conda installcan be used to install packages.
Conda in the middle of a sentence:
- If a newer version of conda is available, you can use
conda update condato update to that version. - You can find conda packages within conda channels. The
condacommand can search these channels.
Titles and headers should use the same capitalization and formmating standards as sentences.
Links should use the same capitalization conventions as sentences. Because the conda docs currently use re-structured text (RST) as a markup language, and RST does not support nested inline markup, documentation writers should avoid using code backtick formatting inside links.