Open
Description
Checklist
- I added a descriptive title
- I searched open reports and couldn't find a duplicate
Summary
In a recent conda community call and in Anaconda internal discussions, we were reminded that conda-build has had less focus from the conda maintainer team than conda itself.
My guess is that a lack of in-depth experience with conda package building made maintenance more difficult than conda. Plus, many of the use cases and scenarios encoded in conda-build are outside the scope of regular software development and are easier to code review and engage with when being a package builder.
As such, to improve the maintenance of conda-build, we should focus on:
- Simplifying the maintenance and contributing process further
- Adding experienced packagers to the maintenance team
- Tapping into the existing knowledge in the community of using conda-build
- Having at least one person of conda maintainer team skilled up by being mentored in the packaging practitioners
Linked Issues & PRs
### Short-term
- [ ] https://github.com/conda/conda-build/issues/4707
- [ ] https://github.com/conda/conda-build/issues/4698
- [ ] https://github.com/conda/conda-build/issues/4979
- [ ] https://github.com/conda/conda-build/issues/4980
- [ ] https://github.com/conda/conda-build/issues/4754
- [ ] https://github.com/conda/conda-build/issues/4975
- [ ] https://github.com/conda/conda-build/issues/4978
- [ ] https://github.com/conda/conda-build/issues/4640
- [ ] https://github.com/conda/conda-build/issues/4645
- [ ] https://github.com/conda/conda-build/issues/4755
- [x] Add end user documentation for recipe format v2
- [x] Add schema for recipe format v2
- [x] Create a linter for recipe format v2
- [ ] Sync with efforts around using conda-build/boa for WASM for emerging platform needs
### Mid-term
- [ ] https://github.com/conda/conda-build/issues/4932
- [ ] Get Anaconda build team to try out next-gen recipe format based on CEP (draft), to get experience and provide feedback to software team
- [ ] Support and interview conda-forge community while trialling next-gen recipe format, to learn about their experience
- [ ] Engage with boa maintainers to expand "build tools" team to also include boa and find common ground (e.g. port code improvements to conda-build, including code quality ;)
### Long-term
- [ ] Write evolution plan for conda-build users and its recipe format(s), and how it relates to other community initiatives like boa
- [ ] Execute migration plan together with community and commercial users