Skip to main content

conda-forge core meeting 2022-07-27

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:


NameInitialsGitHub IDAffiliation
Marcelo TrevisaniMDTmarcelotrevisanconda-forge
Katherine KinnamanKKkathatherineAnaconda
Jason McAllisterJMSolid-Snake-JayAnaconda
Matthew BeckerMRBbeckermrcf
Dave ClementsDPCtnabtafAnaconda
Jaime Rodríguez-GuerraJRGjaimergpQuansight/cf
Daniel ChingDJCcarterboxArgonne
Jan JanssenJJjan-janssenLos Alamos
Wolf VollprechtWVwolfvQuantStack
Matti PicusMPmattipQuansight/PyPy
John KirkhamJKjakirkhamNVIDIA/cf

XX people total.

Standing items

  • intros for new folks on the call

  • open votes

From previous meeting(s)

Your new() agenda items

  • (JK) R-base compilers

  • (JRG): Review guidelines PR is welcoming comments

    • This is FYI - folks should look at this PR
  • (JRG): Status of GPU CI server

    • Changing datacenters; updates will be provided as soon as we know more.
  • (Axel): Static abseil builds as escape hatch for those not on C++17

    • JRG: Leave one - two weeks for folks to comment.
    • Axel: Especially if you disagree with the rename "abseil-cpp" → "libabseil" due to this
  • (Axel): Status of "special ops" CI queue initiative

    • MRB: Waiting on ToS writing with NumFOCUS
  • (Axel): Move to vc142 on windows

    • (MP) numpy has open issue to move away from static lib. It is not clear how NumPy can work around this without shipping a dynamic library in the binary package.
  • (MP): (if there is time) Update on the PyPy 3.8/3.9 migration:

    • Scipy was just merged, matplotlib is waiting for pyqt, jupyter_core is waiting for pywin32. It would be nice if there was a way around those dependencies
      • It should be possible to manually push a migration PR to matplotlib and jupyter_core, hopefully the bot will pick up the new packages
    • A recent update to the pypy-feedstock (misnamed pypy3.6-feedstock) but aarch64 and ppc64 builds take too long to run on CI. Isuruf gave me access to vms to produce builds, but they have run out of disk space. Can they get restarted somehow?
  • (JK) Looking into HPy builds of Python

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



  • (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
      • (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)


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
    • Recommend how to package them -> CFEP-18
    • We should write docs saying we don't provide support and this is a bad idea. -> CFEP-18