conda-forge is a community-led collection of recipes, build infrastructure and packages for the conda package manager. As the conda-forge community grows, changes will be needed to adapt how the project operates both from a technical standpoint as well as to address social topics such as governance and expected conduct.
To address these changes in an open manner, all major changes to the project should be submitted as conda-forge enhancement proposals (CFEP). These CFEPs are similar to Python's PEP and IPython's IPEP processes.
Community members are encouraged to author a CFEP to suggest changes before any code is written to allow for the community to discuss the proposed changes. The formal process by which CFEPs should be authored and how they are reviewed and resolved is specified in CFEP-01. A template for new CFEPs is given in CFEP-00.
| CFEP | Title |
|---|---|
| CFEP-01 | CFEP Purpose and Guidelines |
| CFEP-02 | Upgrade default macOS Travis image to xcode6.4 |
| CFEP-03 | Providing manually uploaded builds on the conda-forge anaconda channel |
| CFEP-05 | Providing pre-release builds on the conda-forge anaconda channel |
| CFEP-07 | Migration strategy to Anaconda compilers |
| CFEP-09 | Pinning Proposal System for Automatic Rebuilds |
| CFEP-11 | Automated Closing of Excessively Old PRs on Staged Recipes |
| CFEP-13 | Securing conda-forge Uploads to anaconda.org |
| CFEP-14 | Security and Systems Subteam |
| CFEP-15 | Deprecate Python 2.7 and vs2008 |
| CFEP-16 | Setting license and license_family field |
| CFEP-18 | Packaging static libraries |
| CFEP-23 | Migration to the Zulip chat platform |
| CFEP-24 | More Secure Package Name Approval Process |
| CFEP-25 | Globally Pinned Minimum Python Version for noarch: python Packages |
| CFEP-26 | Guidelines for (Re)Naming Packages |
| CFEP-27 | A more unixy layout for cpython on windows |