Skip to main content

2026-05-20 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​

  1. TH: Travis Hathaway (@travishathaway), Anaconda
  2. BZ: Bas Zalmstra (@baszalmstra), CF/C, C/SC, Prefix.dev
  3. JRG Jaime Rodríguez-Guerra (@jaimergp), CF/C, C/SC, Quansight
  4. WV: Wolf Vollprecht (@wolfv), CF/C, C/SC, Prefix.dev
  5. MvN: Marius van Niekerk (@mariusvniekerk), CF/C, C/SC
  6. IF: Isuru Fernando (@isuruf), CF/C, OpenTeams
  7. CHL: Cheng H. Lee (@chenghlee), CF/C, C/SC, Anaconda
  8. PZ: Pavel Zwerschke (@pavelzw), C/SC, QuantCo

Announcements​

From previous meetings​

  • TH: Ideas for better tracking staged-recipe reviews
    • staged-recipe review dashboard - idea on conda-forge zulip
    • Would it help to create a special dashboard for us to track recipe reviews?
      • Score board to encourage reviewers
      • Clear goals for new reviewers to achieve
      • Seeing which pull requests have been waiting the longest
      • Organizing pull requests by responsible team

New agenda items​

  • IF: CFEP: Unixy layout for python on windows

    • Optional: A CEP that adds python_scripts_path similar to python_site_packages_path to conda clients so noarch: python packages can create Windows entry points in %PREFIX%/bin rather than %PREFIX%/Scripts/?
      • Choices for python_scripts_path would be limited because the paths have to be in PATH and conda's set of paths is bin, Scripts, Library/bin, Library/mingw-w64/bin, Library/usr/bin.

  • WV: Repodata v3 preview rollout

    • rattler-build DONE
    • prefix.dev DONE
    • Pixi underway

  • WV: RISCV status?

    • https://github.com/conda-forge/ctng-compiler-activation-feedstock/pull/189
    • WV: Migration?
      • MvN/IF: Eventually
      • IF: First we need activation finished. Bootstrapping a platform often challenging for many communities.
      • IF: When do we move to next arch? Recommends waiting for other communities to do so like Rocky or Fedora.
      • WV/JRG: Both recall that OpenKylin preferred starting with rva23 directly.

  • WV: Verification of sigstore attestations in conda packages, CEP: https://github.com/conda/ceps/pull/168

Deferred to next meeting​

  • CHL: (About hardcoded activation paths in conda). Did we write CEPs for all the other magic strings inside conda?. Thing about making these sort of issues into CEPs is that it would force what are essentially conda-forge's and Anaconda's conventions on all channels, which is something we as an ecosystem could do, but we should be deliberate about it. (Might not make that big a difference practically speaking, since such conventions are already hard-coded into conda & friends in various ways.)