2020-07-15 conda-forge core meeting



Standing items

  • [x] (CJ) budget, also finance subteam creation

    • https://github.com/conda-forge/conda-forge.github.io/pull/1093

  • [x] intros for new folks on the call

Stuff from last week that we didn’t get to

  • [x] (ED) Did we need to do anything as a result of this discussion from last week?

    • [x] (IF) strict channel priority

      • Needed for PyPy

      • Needed for Cos7

      • Remove packages that we don’t fully support. For eg: there are 3 builds of scipy on windows.

      • Older versions of tensorflow?

        • https://github.com/conda-forge/conda-forge.github.io/issues/1102

  • [ ] (ED) Did we need to do anything as a result of this discussion from last week?

    • [x] Discussion of “hard to build packages”

      • rstudio (redist may be somewhat sketchy?)

      • tensorflow

      • qt

      • scipy on Windows

      • Should we publish a list and ask for help on those?

  • [x] (UK) Make a NEWS about CFEP-18, add to docs

  • [x] (UK) “GPL-free” variants

    • Some packages like Python, sqlite have a dependency on libreadline which is GPL licensed. There might be arguments that this doesn’t trickle up the stack but Corporate Compliance/IT have a different stance on that.

    • Similar issues with other packages where the GPL-dependency is quite often an optional one.

    • We probably want to have that functionality enabled by default but provide an alternative variant without GPL dependencies.

  • How to communicate breaking changes to users?

    1. Make a list of packages that are fundamental to the ecosystem, like too big to fail

    2. What kinds of communication do we need for different kinds of changes?

      • communicate breaking changes at the individual repo level

      • communicate CFEP changes

      • communicate known breaking changes to large parts of the ecosystem

      • (discussion) everyone that lives on conda-forge is basically living on master. Could add epoch labels? Snapshot repodata.json labels. @Isuru / @kirkham move to github issue?

  • [ ] (CL) msys2 packages

    • Anaconda deciding on update plans for “defaults” channel

    • No immediate action needed at this time

Your new agenda items

  • [ ] (CJ) rebuild migraiton automerges default

    • Currently either automerge is on or off, but it would be good to allow ppl to choose to automerge only for rebuilds and not version updates

    • These automerges may be safer than version automerges, since the deps

    • don’t change and the build is more likely to fail if the package would be broken.

    • https://github.com/regro/cf-scripts/pull/1063

  • [ ] (CJ) s390x support

    • https://github.com/conda-forge/conda-smithy/issues/1359

  • [ ] (FF) new conda-build release that fixes the Windows prefix issue https://github.com/conda/conda-build/issues/3909#issuecomment-626586540

  • [x] (FF) CZI proposal https://docs.google.com/document/d/1dEXQsrXM5kBW6ARLpsVGRQltVxQVbVkjmXbBh8LnHac

Active votes

Subteam updates









  • [ ] still need to finish CFEP-13 (can move ahead now that latest smithy is out)

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


Check in on previous action items

Copy previous action items from last meeting agenda.

This meeting

  • [ ] 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

  • [ ] (Eric) TODO: Make strict an option in conda_forge.yaml and turn it on by default. Open issue in conda-smithy

  • [ ]

Last meeting

2 meetings ago

  • [ ] Eric to add a new page to our docs around how to engage with conda-forge and affiliated in a commercial relationship.

  • [ ] Eric will get the NVBug link from Keith and archive it in the conda-forge google drive.

  • [ ] 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

3 meetings ago

Move to Issue Tracker

  • [ ] (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 anaconda.org 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)

    • https://github.com/conda-forge/conda-forge.github.io/issues/954

  • [ ] (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 https://carpentries.org/instructors

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

  • [ ] (CJ) Form finance subteam

  • [ ] (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