Conda Enhancement Proposals

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).

Accepted CEPS

CEP	Title
0000	CEP template
0001	CEP Purpose and Guidelines
0002	Add plugin architecture to conda
0003	Using the Mamba solver in conda
0004	Implement initial conda plugin mechanism
0005	Does not exist
0006	Add Channel Notices to conda
0007	Does not exist
0008	Conda Release Schedule
0009	Conda Deprecation Schedule
0010	Conda Version Support
0011	Define the menuinst standard
0012	Serving run_exports metadata in conda channels
0013	A new recipe format – part 1
0014	A new recipe format – part 2 - the allowed keys & values
0015	Hosting repodata.json and packages separately by adding a base_url property
0016	Sharded Repodata
0017	Optional python site-packages path in repodata
0018	Migration to the Zulip chat platform
0019	Computing the hash of the contents in a directory
0020	Support for abi3 Python packages
0021	Run-exports in sharded Repodata
0022	Frozen environments
0023	Text spec input files
0024	Specification of environment.yml input files
0025	Versioning of Existing conda Standards
0026	Identifying Packages and Channels in the conda Ecosystem
0027	Standardizing a publish attestation for the conda ecosystem
0028	Customizable system DLL linkage checks for Windows
0029	The MatchSpec query language
0030	Virtual packages
0031	Build provenance metadata
0032	Management and structure of conda environments
0033	Version literals and their ordering
0034	Contents of conda packages
0035	Distributable package artifacts file formats
0036	Package metadata files served by conda channels
0037	conda-lock.yml lockfiles
0038	Channel-wide metadata files served by conda channels
0039	A new recipe format (part 3): jinja functions in recipes
0040	A new recipe format (part 4): Rendered recipe YAML and serialization
0041	The staging output in v1 recipes / rattler-build
0042	Channel relations in repodata
0043	Conditional dependencies
0044	Optional dependency groups
0045	Simplified variant selection
0046	The __cuda_arch virtual package

References

These proposals are similar to conda-forge's CFEP, Python's PEP and IPython's IPEP processes etc.

Writing a new CEP

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.

CEPs which are in draft/proposed form should have the number XXXX in both their PR title, CEP title, and filename. A number will be assigned to the CEP upon acceptance, and all references to the CEP should be updated to reflect the CEP's number. To refer to the CEP before it has a number, use its PR number or its title.

Conda capitalization standards

1. Conda should be written in lowercase, whether in reference to the tool, ecosystem, packages, or organization.
2. References to the conda command should use code formatting (i.e. conda).
3. If the use of conda is not a command and if conda is at the beginning of a sentence, conda should be uppercase.

Examples

In sentences

Beginning a sentence:

• Conda is an open-source package and environment management system.
• conda install can 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 conda to update to that version.
• You can find conda packages within conda channels. The conda command can search these channels.

In titles and headers

Titles and headers should use the same capitalization and formatting standards as sentences.

In links

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.