Skip to main content

conda-forge core meeting 2022-04-06

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
Eric DillEDericdillVoltron Data
Katherine KinnamanKKkathatherineAnaconda
Travis HathawayTHtravishathawayAnaconda
Cheng H. LeeCHLchenghleeAnaconda
Keith KrausKJKkkraus14Voltron Data
Matthew BeckerMRB.beckermrcf
John KirkhamJKjakirkhamcf/NVIDIA
Dave ClementsDPCtnabtafAnaconda
Mike McCartyMMmmccartyNVIDIA
Jannis LeidelJLjezdezcf/Anaconda

24 people total.

Standing items

  • intros for new folks on the call

    • Alex Dibbley - works on cuda installer. pushes builds to
    • Travis Hathaway - Anaconda, works on conda distribution
    • Kai Tietz - works on distro team from Anaconda. packaging building
    • Jon Velando - IC, humble feedstock maintainer
  • (FF) budget

    • current approvals?
    • Whenever updated numbers land, please screenshare and show the budget.
      • Link is in Keybase (numfocus_spreadsheets.txt)
    • something something open collective. numfocus sent out an email for onboarding
  • open votes

  • 2022 Outreachy / GSoC

    • Community accepted
    • Project proposals due Tuesday/Wednesday March 22 (Americas) / March 23 (Europe)
      • In addition to project propsal also need contribution tasks
      • And Channels for potential interns to communicate with us.
    • Two projects
      • Grayskull and Friends, Jannis, and Marcelo (pyproject.toml support)
      • Doc, Matt and Katherine
    • questions:
    • todos:
      • Have people got time to support Grayskull work? (JL, DPC will follow up)
    • KK - do we have a code of conduct?
    • MRB and KK will have their own meeting around proposals

From previous meeting(s)

Your new() agenda items

  • (MRB) numfocus TOS draft
    • if you're on core, draft of TOS has been sent to email list.
    • Pam has some questions that we (core) needs to respond to.
    • Need to be sensitive on pushing too much onto the community
    • TODO: Everyone on core needs to read, comment or otherwise be OK with the email from Pam
    • TODO: Get Feedback from core team by next core meeting
  • (MRB) what is the status of moving to .conda on sha256?
    • (CHL) .conda format support added to .org server; in beta/testing using main/defaults
    • (CHL) Scheduled: verifying .conda is supported by CDN sync process
    • (CHL) Scheduled: anaconda-client release with .conda upload support
    • MRB - what about sha256 for packages in repodata? only thing we can get is md5.
      • CHL - have a ticket, not sure it has been scheduled.
      • MRB - api doesn't give back sha256.
      • MRB TODO Send endpoints to Cheng (done)
  • (WV) New CZI proposal
  • (WV) bloomberg
  • (JK/AD) CUDA Conda packages next steps
    • Want to check that run_exports
    • Also want to check sysroot handling
    • Include nvbug link
  • (KT/CHL) Deprecating noarch: python builds from defaults
    • conflates platform- vs. interpreter-independence
    • punted discussion of noarch but specific python version builds to the next conda community meeting

Pushed to next meeting

  • TODO: Feedback on TOS from core team by next core meeting
  • (KT/CHL) Deprecating noarch: python builds from defaults
  • (JL / WV) Update on conda-forge as OCI.
    • MRB - this is an update to conda
    • MRB - we should start uploading some packages to get a sense of how this works
  • (ED / JV) Getting involved in supply chain stuff for conda-forge

Active votes


  • 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



  • 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