CFEP-01 CFEP Purpose and Guidelines and CFEP-00 CFEP Template#1
CFEP-01 CFEP Purpose and Guidelines and CFEP-00 CFEP Template#1pelson merged 2 commits intoconda-forge:masterfrom
Conversation
Conda-Forge Enhancement Proposal for CFEPs themselves as well as a template for future CFEPs.
cfep-01.md
Outdated
|
|
||
| All CFEPs will be resolved as either *Rejected*, *Accepted* or *Deferred* | ||
| depending on the consensus of the community. Once the community has reached a | ||
| consensus, the CFEP champion should update the Status of proposal and add a |
There was a problem hiding this comment.
The exactly mechanism on how a consensus is reached should be decided upon and included here.
|
Rendered versions of the README and CFEPs can be found in the jjhelmus/cfep01 branch |
|
|
||
| ## Resolution | ||
|
|
||
| All CFEPs will be resolved as either *Rejected*, *Accepted* or *Deferred* |
There was a problem hiding this comment.
A little nervous about the Deferred status. For instance, what limits how long something can be deferred? How do we ensure we actually reach a decision? Right now there are things that have effectively been deferred indefinitely. If we keep it, there need to be some limits on this so it actually gets accepted or rejected at some point. In some ways, I'd much rather see a proposal outright rejected if that is the case so that we can start making other plans.
Note that JEPs appear to exclude this status from the ones available too.
There was a problem hiding this comment.
I like @mwcraig wording from above
Deferred CFEPs can be re-submitted in a new pull request if the circumstances that justified deferring instead of accepting or rejecting have changed.
|
Thanks for putting this together @jjhelmus. This is very nicely done. Basically my comments fit along one line, which is inspired based on what @pelson had said in our meeting discussing governance and CFEPs. Namely that it should be ok to merge things in Draft mode and often. Only after that do we start digging into a discussion about the proposal and come to some decision. Other comments are directed at the decision process and making sure that it provides clear feedback and does happen. |
|
@conda-forge/core, please take a look at these documents that @jjhelmus has nicely put together for us and provide constructive feedback. These are laying the groundwork for how we make major decision on large changes going forward. So become familiar with it, ask questions about unclear portions, and make suggestions. We want to be sure we have firm footing going forward. |
README.md
Outdated
| @@ -1,3 +1,22 @@ | |||
| # Enhancement Proposals | |||
| conda-forge is a community led collection of recipes, build infrastructure | |||
|
Thanks for putting this together @jjhelmus! |
Conda-Forge Enhancement Proposal for CFEPs themselves as well as a template for
future CFEPs.