conda-forge core meeting 2023-11-01
Add new agenda items under the Your __new__() agenda items
heading
Attendees
Name | Initials | GitHub ID | Affiliation |
---|---|---|---|
Marius van Niekerk | MvN | mariusvniekerk | Voltron Data/c-f |
Cheng H. Lee | CHL | chenghlee | Anaconda/c-f |
Dave Clements | DPC | tnabtaf | Anaconda |
Marcel Bargull | MB | mbargull | Bioconda/cf |
Jaime Rodríguez-Guerra | JRG | jaimergp | Quansight/cf |
Wolf Vollprecht | WV | wolfv | prefix.dev. |
Filipe Fernandes | FF | ocefpaf | conda-forge |
Daniel Ching | DJC | carterbox | Argonne National Lab |
Matthew R Becker | MRB | beckermr | cf |
Mark A Anderson | MAA | markan | anaconda |
John Kirkham | JK | jakirkham | NVIDIA/cf |
14 people total
Standing items
- [ ]
From previous meeting(s)
- (HV) archspec-enabled
- Since last time conda has started depending on archspec package.
- Progressing...
- Will revisit in a meeting or two
- (JK) m2 recipes
- Postpone
- (JK) Windows ARM
- Isuru syncing with MSFT
Active votes
- [ ]
Your __new__()
agenda items
- (JK) We/NVIDIA are hiring.
- (HV) next steps for MacOS 10.13
- jinja for
stdlib("c")
was merged into conda-build (not yet released) - what's the next step? admin migration to add
{{ stdlib("c") }}
wherever there's a{{ compiler("c") }}
? - MRB recommends agains an admin migration as too intrusive. Be better to have a mini-migrator that rolls it out to new feed stocks.
- JRG: 4.3k recipes with
compiler('c')
(gh search) - MRB will comment about places where (linux) sysroot is set in our infra in the issue.
- WV will open an issue or a CFEP for this discussion.
- This issue came up because there is a part of the build that is hidden, it is not exposed anywhere
- jinja for
- (HV) Tracking issue for CUDA 12 on win?
- https://github.com/conda-forge/cuda-nvcc-feedstock got windows support today
- Something like [https://github.com/conda-forge/staged-recipes/issues/21382] for windows?
- JK: No issue yet. Would be good to confirm that it works before we start rolling it out everywhere
- (WV) First CEP for recipe spec accepted 🎉 ... now unto the next
- https://github.com/conda-incubator/ceps/blob/main/cep-13.md (accepted)
- https://github.com/conda-incubator/ceps/pull/56 (the next one!)
- Pure YAML.
- There is another CEP for key/values.
- Drastic changes to multiple outputs.
- Large changes to the test section.
- List of tests, composed of test elements.
- JRG: only ~100 recipes use
for
loops [search] - (MRB) Be careful when just abandoning keys in current spec. They were put there for a reason. Try to understand those reasons, even if we don't keep them.
- (MB) Intent to archive
ruamel_yaml
feedstock- https://github.com/conda-forge/ruamel_yaml-feedstock/issues/107
- conda now dependent on upstream version.
- (DPC) Anything to highlight in the November conda newsletter?
- (DPC) Is it time to get off twitter?
- FF: We should mmove period.
- BlueSky account is secured.
- Not clear which Mastodon server we should use
- It's a slow move. We should have both for some time.
- Point Twitter to new one
- Dave and Filipe will coordinate across conda-forge and conda.
- FF: We should mmove period.
Pushed to next meeting
- (HV) archspec-enabled
- (JK) m2 recipes
- (JK) Windows ARM
CFEPs
- [ ]