Skip to main content

2020-11-11 conda-forge core meeting

Zoom link What time is the meeting in my time zone last weeks meeting


  • Matthew R Becker
  • Cheng H Lee
  • Keith Kraus
  • Filipe Fernandes
  • Jaime Rodriguez-Guerra


Standing items

From previous meeting(s)

Your new() agenda items

  • (JRG) [email protected] is interested in helping out with a "conda-forge paper" for JOSS

    • Would be useful for scientists to get citations
    • Two approaches
      • Everyone on core is an author
      • Only people that need
    • Generating something to cite
      • Zenodo? Rolling Zenodo DOIs don't accumulate citations (we need to confirm that.)
      • JRG: As per the FAQ How does DOI versioning work?, they provide two types of DOIs: version-specific and project-specific. Each project gets at least two: a general one, and then one more for the current version. They are separate DOIs (so different citation "wallets"), but we could ask people to cite the project DOI, and the version specific ones will contain the increasingly growing list of contributors (maybe splitted by time?). For example:
        • Project DOI -> points to
          • Author is "The Conda Forge Community".
          • Content of the release: the documentation at that point, or a statement of the mission.
        • Versions: one per year (or other period of time).
          • Each release includes authors that contributed at least one package to conda-forge (new feedstock, new merged PR?). Sorted by amount of contributions. Opt-in via PR label (staged-recipes + PR).
          • Content: whatever is easier to automate. Possibly a list of the newly feedstocks, merged PRs in that timeframe.
      • JRG (cont.): Authors that want credit in their CV can include the Project DOI and the versions that include their contributions, if needed.
    • How do we slice and dice credit? Write a paper and publish it for that specific tool?
    • TODO: Think about bringing in JOSS to provide context around how we might best write papers
    • MRB: I think the community itself should be the sole author.
  • CZI proposal results and next steps

    • We got a boilerplate no "good proposal but we got too many" from CZI.
  • (CHL) to-dos for osx-arm64 rollout

    • Action item for Anaconda: fix CDN to push osx-arm64 packages
    • Anaconda may add signing to conda-build at some point in expectation that apple will require real certs and not simply an ad-hoc signature

Pushed to next meeting

  • (MB) asking core members to move to "emeritus" status
  • (CJ) We seem to have some artifacts that have more files than expected
    • 4 pkgs ship requests (other than requests itself) see below
    • What should we do about these?
      • Old pkgs
      • Newer/latest pkgs

Active votes

Subteam updates









CI infrastructure

Compiler upgrade

CFEP updates

Open PRs

  • cfep-04 X11 and CDT policy

    • INACTIVE - Merge in with some inactive-esque status?
    • Needs new champion. Thanks for your work on this pkgw! Has unaddressed comments from pkgw as from Jan 10, 2020
  • cfep-06 Staged-recipes review lifecycle

    • INACTIVE - Merge in with some inactive-esque status?
    • Lingering comment from @saraedum. @jakirkham, can you reply? Has unadressed comment from @saraedum from Jan 8, 2020
    • (MRB) The stalebot has solved the worst of the issues here. I think we could defer this one permanently.
  • cfep-10 Feedstock statuses, unmaintained

    • INACTIVE - Merge in with some inactive-esque status?
    • Needs another review. Has unaddressed updates from pkgw as of Jan 11, 2020
  • 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?
  • cfep-17 Handling pin backports and dependency rebuilds

    • Stalled debate about implementation details between Isuru, CJ and Matt
    • UPDATE 2020-07-22: We in principle have agreement to render the extra pinnings needed directly in the feedstock on a temporary basis (i.e., until the migration has ended).
  • cfep-20


Check in on previous action items

Copy previous action items from last meeting agenda.

This meeting


  • (MRB) proposed policy on when core pushes to the feedstocks they don't maintain * [x] (MRB) put in docs PR * [ ] (MRB) make PR on bot to mention the policy
  • TODO: Check on Forrest Watters permissions for core
  • (FF) Outreachy would cost 6500 USD.
    • Next steps: write abstract and vote on spending of funds.

Last meeting


2 meetings ago


  • (Marius?) Python 2.7 migration
    • ( ) [ ] make a hint
    • ( ) [ ] make an announcement
    • ( ) [ ] make the hint a lint

Move to Issue Tracker


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



  • (MRB)
    • do libgfortran name change
    • add target platform to hashes
    • do gfortran migration with bot
    • bump pinnings


  • Get a call set up with Jon Mease about the kaleido staged recipes PR
    • Emailed on 2020-09-16
  • (FF) Open up a PR on the python feedstock for python 3.9 and see what fails


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
  • (MRB) start pushing images to quay (


  • (???) build webpage to credit them (and others)

  • If we're adding a logo, will want to make sure that we have permission to use it.

  • 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