conda-forge core meeting 2022-08-10

Add new agenda items under the Your __new__() agenda items heading

last weeks meeting What time is the meeting in my time zone Meeting info:

  • To join the video meeting, click this link:

  • Otherwise, to join by phone, dial +1 347-384-8597 and enter this PIN: 828 997 153#

  • To view more phone numbers, click this link:




GitHub ID


Matthew Becker




Jaime Rodríguez-G




Keith Kraus



Voltron Data

Dave Clements




Mike McCarty




Marcelo Trevisani




Katherine Kinnaman




John Kirkham




Wolf Vollprecht




Eric Dill



cf / voltrondata

Matti Picus




18 people total.

Standing items

  • [x] intros for new folks on the call

  • [x] open votes

From previous meeting(s)

Your new() agenda items

  • [x] (KJK) Update arrow pinning from 4.x - 7.x to 6.x - 9.x


      • No objections

  • [x] (JK) conda-forge & NVIDIA licensing

    • nvidia looking to change their licensing with us

    • cuda-compat would be interesting

  • [ ] (JRG) Usage of build strings in conda-forge – potentially disrupting changes in conda?

    • Our CF issue:

    • PR:

    • tangent (Axel): build strings getting semantically overloaded, c.f.

    • (From WV in chat):

      • this might be the problematic line 🙂


    • Isuru suggests a “resolved at build-time” build-string constraints with aliased package names outputs for each “feature”

    • Jaime: some examples in conda-forge meta.yaml

  • [x] (DPC) Outreachy

    • Should we participate in the Dec-Mar cohort?

    • Communities need to apply in early / mid September

    • Projects are submitted after that.

    • Will bring up again on next call.

  • [x] (MRB) drop pypy3.7

    • MP is in favor of whatever is easiest for conda-forge

    • conclusion to drop pyp37 and miniforge installer for pypy

    • need to make an announcement

  • [x] (Axel) abseil update - start migration?

    • - please review or chime in

  • [x] (Axel) vc142 update - PR ready

    • - make announcement (“we’ll drop in 2 weeks”), wait for reaction

  • [x] (KK) Security doc for conda-forge builds

    • Doc issue:

  • [x] (Axel) OpenSSL 3 migraion

    • (JRG) stalled PR at, upstream issue at

  • [x] (Axel) Question: Status CUDA support (problems with CUDA<11.2 in tf/pytorch)

    • No current change planned, but individual feedstocks can drop older CUDA

Active votes

  • cfep-21 license packages for static/header libraries

    • Opened July 25, 2022 ends August 2, 2022


  • cfep-12 Removing packages that violate the terms of the source package

    • Stalled since May 26, 2020

    • Active debate about moving to “broken” vs deleting from conda-forge channel

    • Active vote, ends on 2020-03-11

    • What were the results of the vote?

    • Did we hear back from NumFOCUS? they did the legal seminar which is recorded



  • [ ] (MvN) vs2022 compiler support

    • Initial stab at some pieces

    • This is a new VC version

      • Uses existing UCRT

    • Would need to use the windows-2022 github actions image

    • TODO: follow on to change the name of the runtime to vc_runtime

    • TODO: will need patches for msys epoch for UCRT

    • (CHL) For reference: msys2 environments - pick your own compiler + libstdc++ + Windows runtime adventure


    • (RG) “we need some version of mingw-w64 for SciPy 1.9.0 too, MSVC + gfortran will no longer work. we use an Rtools toolchain in CI now”

  • [ ] (CHL) How does conda-forge use channeldata.json?

    • Only known use by c-f: counting # of package namespaces for “By the numbers” on the webpage; other uses deprecated

    • TODO: CEP to deprecate & remove --use-channeldata from conda-build

    • TODO: CEP to add run exports to repodata.json


  • TODO: Articulate suggested mechanism for “so you’re thinking about taking a contract to work on conda-forge”. tl;dr is you should work on a design doc with the impacted parties (or working groups, or interested folks) on the conda-forge side. Once you have agreement on the scope, delivery timeline, and anything that’s needed from the conda-forge volunteer side, go ahead and sign that contract with your payer. if you don’t do this first, you may encounter some difficulties finishing delivery of your contractual agreement with your payer.


  • review Qt PR after logs are uploaded

  • Add cupython and cuquantum to don’t mirror list (MRB done)

  • re: std=c++14, Wait for Kai to comment and merge the PR

  • CJ and Jaime coordinate to Let Maxiconda know that we can’t use their logo 2021-12-01

  • WV: Set up meet-and-greet call with homebrew team?

  • MRB: (repodata patches) make a cron job that runs and posts an issue + commit if it is non-empty


  • Self-hosting CI TODOs:

    • Change URL from Proposals:



    • Set up monitoring

      • Quantstack is setting up grafana for the mirror



  • [x] (WV): TensorFlow-GPU ready to go, just need to decide if GPU should get prio over CPU?!

    • GPU gets prio


  • [ ] (IF/MRB/MV) intel oneAPI

    • todo

      • [ ] (Nikolay) licensing for opencl_rt

      • [ ] (Nikolay) intelmpi ABI compat w/ mpich

      • [ ] (MRB/IF) figure out how exactly to package C/C++ compilers

      • [ ] (MRB/IF) think about fortran ABI

      • [x] (MRB) make conda-forge compilers room (add people including keith)

  • [ ] (MB) asking core members to move to “emeritus” status

    • [ ] TODO: Eric to set up quarterly check-in for all core members to see if they’re interested in remaining “active” or if they want to move to emeritus

      • Remove emeritus folks from having access to various credentials (api tokens, twitter password, etc.)? This would require a change to the governance doc.


  • TODO: Think about bringing in JOSS to provide context around how we might best write papers


  • TODO: Check on Forrest Watters permissions for core

2020-10-28 2020-10-21

  • [ ] (Marius?) Python 2.7 migration

    • ( ) [ ] make a hint

    • ( ) [ ] make an announcement

    • ( ) [ ] make the hint a lint


  • [ ] Make sure to add the NVBug info to the cudatoolkit package that conda-forge makes (if we make one)


  • [ ] (ED) Update governance docs with similar voting model as what got put into conda-tools (+3 with no -1 is a pass)

  • [ ] (SC) Write jinja template to turn institutional partners yaml into a website

  • [ ] (SC) Document what needs to be done to create an OVH account and get access

2020-08-26 Docker hub

  • [ ] (JK) Check in on Azure build workers to see if they have the docker hub limitation.

  • [ ] (JK) work with dockerhub to see if we can get OSS status

    • [ ] Check in again at some point. We haven’t heard back as of 2020-09-23


  • [ ] Shout-out on twitter at some point. “Thanks forOVHCloud for providing a VM”, etc. (maybe after we ship qt on windows with it?)

  • [ ] Figure out how to communicate breaking changes to users. Likely should open up an issue immediately for futher discussion. Ping @kkraus, plus capture notes from further up in these meeting notes

  • [ ] John K. will update the cuda toolkit feedstock on the git repo to note the NVBug link to the internal NVIDIA issue tracker

  • [ ] Jonathan will update docs to note that some non-exhaustive list of packages (like cuda-toolkit, MKL, etc.)

  • [ ] Jonathan will review this PR

  • [ ] (Kale) schedule conda working group

  • [ ] cfep-10 next steps: CJ to call a vote for feedback

  • [ ] cfep-06 next steps: Ask staged recipes team to champion this CFEP and move it forward

  • [ ] jakirkham & CJ-wright to sync on adding CUDA to the migration bot

  • [ ] (Eric) Scheduling Anaconda <-> conda-forge sync on requirements gathering

    • Will try and get this scheduled in the next month.

  • [ ] (Anthony) Reach out to NumFocus to figure out legal ramifications of not including licenses in files.

  • [ ] (Eric) check internally for funding levels for hotels & flying folks from the community in?

  • [ ] (Eric) Figure out finances of conda-forge to support themselves?

  • [ ] (jjhelmus) Open up CFEP for which python’s we’re going to support

  • [ ] (jakirkham) write a blog post on CUDA stuff we discussed today

  • [ ] (jakirkham) update docs on how to add CUDA support to feedstocks

  • [ ] (jakirkham) will open an issue on conda-smithy to investigate Drone issues. (ping the aarch team)


  • [ ] (ED) Who we are page? Some combination of a FAQ and a who is everyone. FAQ things like:

    • who’s the POC for CF <> Anaconda, CF <> NumFocus, CF <> Azure

    • who’s the POC for the various subteams?

    • Informal information: roles, day jobs, bios, the whole nine yards, why you’re here, etc.

    • Public or internal? I don’t really care either way. Anyone feel strongly one way or the other?

    • opt-in to public bios

    • software carpentry has a large number of instructors and has

    • some concern about “yet another place to keep stuff up to date”

  • [ ] (ED) document strategies for reproducible environments using conda-forge

  • [ ] (UK) Static libraries stuff

    • [ ] Add linting hints to builds to find them

    • [x] Recommend how to package them -> CFEP-18

    • [x] We should write docs saying we don’t provide support and this is a bad idea. -> CFEP-18