2026-01-21 Conda Ecosystem Meeting
Zoom link · What time is the meeting in my time zone: 5pm, 2pm
Various parts of the conda ecosystem gather on a regular basis. This meeting brings together all of these sub-communities for a community wide call.
Attendees
- JRG: Jaime Rodríguez-Guerra (@jaimergp), Quansight, conda-forge/core
- ME: Marco Esters (@marcoesters), Anaconda
- DW: Dawn Wages (@dawnwages), Anaconda
- TH: Travis Hathaway (@travishathaway), Anaconda
- DY: Dan Yeaw (@danyeaw), Anaconda
- JL: Jannis Leidel (@jezdez), Anaconda, conda-forge/core
- DH: Daniel Holth (@ dholth), Anaconda
- WV: Wolf Vollprecht, (@wolfv), Prefix.dev, conda-forge/core
- IF: Isuruf Fernando (@isuruf), OpenTeams, conda-forge/core
Announcements
- JRG: conda-rattler-solver 0.0.4 is out with pretty decent compatibility with conda's UX expectations.
New agenda items
- (JRG) Review request for https://github.com/conda/governance/pull/334
- (DH) CEP to adopt Python API conventions, amend deprecation policy in conda.
- https://github.com/conda/ceps/pull/143
- JRG: Start RFC period for two weeks, tag steering-council. Two weeks later, start vote.
- (DW) Conda communications governance - DW and Daina Bouqin
- Open an issue with membership request on conda/governance, tag @conda/communications
- DW will help with first round of documenting best practices to support the growing team
- (WV) FOSDEM Plans.
- CEP hackathon on Friday!
- JRG: Create channel on Zulip.
- (WV) rattler-build refactor underway with the new cache output implementation
- https://github.com/wolfv/rattler-build-parser-tests our test suite
- JRG: Yay! cached multi-outputs!
- WV: Idea to use PKL to replace Jinja config language.
- (WV) sigstore progress: we have an endpoint to retrieve bundles and are working on a CEP to specify that (e.g.
*.conda.sigs)- New Rust implementation passes the sigstore compliance test suite passing!
- https://github.com/conda/ceps/pull/142
- IF: What happens when the logs expire in GHA?
- WV: Sigstore logs are kept in transparency logs permanently, but the actual build logs will indeed expire. Would need to think about ways of storing those somewhere else.
- Example preview: https://prefix.dev/channels/sigstore-example/packages/signed-package
- (TH) Idea for a new blog post series: You can do that with conda? Highlights some of the lesser known use cases for conda and helps promote our packaging ecosystem (first post here: https://github.com/conda/conda-dot-org/pull/309).
Deferred to next meeting
- (HV) Package rename CFEP; what are next steps? We should wrap this up
- (HV) Use our own QEMU instead of Fedora's: discuss approach & next steps
- (HV) [tentative, pending attendance of Isuru and OpenKylin folks] Choice of RISC-V CPU architecture baseline
- (HV) Move to macOS >=11.0; libcxx v22 will require >=11.0, leaving us little leeway.
- https://github.com/conda-forge/conda-forge.github.io/issues/2467
- https://github.com/conda-forge/conda-forge.github.io/pull/2721
- Potential alternative: since the split of
libcxx-develfromlibcxx(andclangxx_<target> vNdepending on the matching libc++ headers, i.e.libcxx-devel vN), we would theoretically be able to publish libcxx v22 without raising the deployment target; as long as our default compiler version on osx is <22, the run-export of the C++ compiler would still produce builds compatible with libcxx 21 at runtime.