Request for incubation: `conda-recipe-manager`

[schuylermartin45]

Hello everyone, I would like to move the conda-recipe-manager project to conda-incubator.

We hope that this move will allow others to easily contribute to our recipe automation efforts. To start, our primary focus is on the conversion of our existing recipe format to the new "v1" format proposed in CEP-13 & CEP-14

I am currently working through migrating this work from another Anaconda project, percy. As of writing this proposal, the conversion is not complete BUT most of the applicable code and configuration files have been copied-over.

I would like to migrate the repository at: https://github.com/anaconda/conda-recipe-manager I would like the existing build-team to manage this project.

I am submitting this issue for the historical record. Any feedback is welcome and appreciated! Thanks!

(The text of this issue was heavily based on the precedent set by Issue https://github.com/conda-incubator/governance/issues/108)

[schuylermartin45]

@chenghlee and @jezdez for visibility ^

[jezdez]

I'm happy to sponsor this, and I'll need to do the repo transfer since GitHub only allows org owners to migrate whole repos. I'll ask for permission from the existing build tools team on Element to approve this.

[jezdez]

https://matrix.to/#/!zjZSkaZgcvxBwdCKne:matrix.org/$2_FaMoMRCcZ5_rnmDtdahjWrc4wpx34dhjQpI4ML52o

[beckermr]

How does this relate to souschef from @marcelotrevisani?

[beckermr]

Not blocking incubation, just wondering.

[wolfv]

Very excited about the potential recipe translation enabled by this 👍

[schuylermartin45]

@beckermr I don't want to speak for @marcelotrevisani but I believe Marcel and I briefly spoke over a community call about a month back, where I presented a slide deck on the project. As far as I understand it/have been able to find in the community, this new parser is the most advanced recipe editing tool currently available.

Of course I'm biased as the author, but I don't think most of the existing efforts convert the recipe into a parse-tree and/or have the ability to manipulate JINJA and selector syntax. I built this originally for Anaconda's needs but my team and I noticed an opportunity to use this to speed up the adoption of the v1/rattler-build format and took it.

I also believe on the call that we all expect that multiple tools may be required to update all 20,000+ conda-forge recipes and 2,600+ Anaconda recipes. So I wouldn't take this as a complete replacement for souschef, as much as another tool in our toolbox.

Let me know if you have any additional questions!

[beckermr]

Ahhh cool. You should checkout what I wrote for the conda-forge bot:

• https://github.com/regro/cf-scripts/blob/master/conda_forge_tick/recipe_parser/_parser.py
• https://github.com/regro/cf-scripts/blob/master/tests/test_recipe_parser.py

and its tests.

[beckermr]

There may bits of code to handle more jinja2 syntax in particular.

This parser can parse almost everything in conda-forge.

[schuylermartin45]

@jezdez @chenghlee I haven't seen any opposition, do we feel confident about moving this project into the incubator?

[jezdez]

@schuylermartin45 Indeed, I'll recreate the build tools team in the conda-incubator (since it currently only exists in the conda org) and then start the transition of the repo.

[jezdez]

@conda-incubator/builds-tools Hey all, heads-up that I've just created the "build tools" here in the conda-incubator organization as well.

The team in the conda organization had been created following the discussion in https://github.com/conda/conda-build/issues/4698.

The reason to add the team here as well is so we can add the new conda-recipe-manager project to the incubator under that guidance of the "build tools" team.

[jezdez]

And transferred! https://github.com/conda-incubator/conda-recipe-manager