Closed beckermr closed 6 months ago
xref https://github.com/conda-forge/cfep/issues/8 for prior discussions
Also see CFEP-08 for a prior proposal. This proposal is largely similar, but specifies voting rules, exempts upstream maintainers to help avoid maintenance issues, allows core maintainers on a feedstock to add folks by unanimous consent, and doesn't specify how we declare the TB2C list except that it is done via consensus and/or a vote.
The goal relative to CFEP-08 is to be less prescriptive in which feedstocks make the list and to spread the maintenance out to trusted community members who may not be on the core team.
Do you have a shortlist of packages you are considering? Is "python" (which version) included in these? I would like to run through one to see what dependencies would be affected by one of your "too big to fail" packages.
I feel like many things are "optional" and we have included many "batteries" with our packages which may make this a difficult endeavor.
I do not yet have a list. I want to generate a similar list and see how many maintainers we have who do not satisfy the criterion in the CFEP. We may be in the position of codifying a policy that we de facto already have.
I'm closing this for now since I don't think i'll have time to put energy into it on second thought.
I'm closing this for now since I don't think i'll have time to put energy into it on second thought.
This is an effort that will take some dedication, coordination, and kind helpful comments from all of us. Also, maybe we should write a NF small grant, or some other sort of funding, to help whoever leads this.
Thanks @beckermr for starting it. Let's use this as a base for the next step b/c there are already many good ideas and points here.
This PR has the "too big to be compromised" proposal from our discussion.