Withdraw `conda/conda`-specific CEPs (2-10)
- Dominant language
- No language data
- Stars
- 34
- Forks
- 41
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 1
Description
Our CEP process has matured in efficiency, popularity and scope. In hindsight, CEPs 2 to 11 should have not been ecosystem wide decisions (governed by @conda/conda-maintainers), but `conda/conda` specific ones (governed by @conda/conda-maintainers). I propose we withdraw those CEPs and instead adopt them as CCEPs (conda/conda enhancement proposals, or conda client enhancement proposals, whatever).
Contributor guide
No contributing guide indexed for this repository
Research direction
Review CEPs 2–11 and the proposal process described in the repository. Confirm which proposals are conda-specific, then withdraw them from ecosystem-wide governance and adopt them as CCEPs; done means the affected CEPs and their status clearly reflect that change.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100