2020-04-29 conda-forge core meeting

Attendees

  • Marius van Niekerk

  • Filipe Fernandes

  • Kai Tietz

  • Uwe Korn

  • Cheng Lee

  • Isuru Fernando

  • Amy Williams

  • Josh Adelman

  • Jonathan Helmus

  • Ray Donnelly

  • CJ Wright

  • Matthew Becker

  • Michael Sarahan

  • Eric Dill

  • Marcel Bargull

  • Wolf Vollprecht

  • Ray Douglass

  • Kale Franz

  • Lori Burns

  • Peter Wang

  • Anthony Scopatz

  • Keith Kraus

  • John Kirkham

Agenda

Your agenda items

  • (all) intros for new people on the line?

  • (UK) Self-sufficient MinGW-based toolchain / packages: m2w64 stack update https://github.com/conda-forge/conda-forge.github.io/issues/1044

    • R heavily depends on gcc, so on windows we have been using MinGW. Maybe we could switch to clang?

    • Need to use msys2 to install packages from CRAN in an R-conda environment.

    • R packages use autotools, so need a posix environment that supports fork. Could use cross-compile

    • Need to separate m2 and m2w64. m2 are for building stuff and mw264 are for linking stuff. definiteyl need m2 ones to have bash / archivers / linkers. question is what are we going to do with m2w64. The binutils package is really old. Those gcc packges can’t directly link to packages built with MSVC. MinGW is not linking to ucrt but this is configurable.

    • What defaults should we have in conda-forge? ucrt or mscrt

    • Is it a goal to interop with CRAN packages? They’ve moved on to msys2 - getting c/c++ directly from msys2 packages. Still stuck with an older compiler (pkg / version?) Doesn’t want to change it because it’s tested so well.

    • Building with existing gcc 5.4 should be okay with gcc 8, last breakage in 4.4?/8?. Would be good to update to newer version.

    • gfortran ABI breakage between 5 and 8

    • CRAN libraries which use fortran, compatibility with current conda-forge packages built with gfortran

    • Test:

      • Use R from conda-forge, install package from CRAN

      • Ideally something that uses modern C++

      • r-cpp, data.tables, something that wraps Fortran(?)

    • clang version of MinGW, existing llvm can target MinGW or MSVC

    • Move remainder of conversation to github issue (https://github.com/conda-forge/conda-forge.github.io/issues/1044).

  • (JJH) Update from Peter on Anaconda, Inc’s repository

    • Making a change to the terms of service for repo.anaconda.com

    • Wholescale mirroring or heavy usage for commercial purposes will be prohibited

    • Open source usage is fine

    • Does conda-forge want to do the same thing for our packages?

    • Share blog post with:

      • Filipe, Kirkham, Keith, Scopatz

  • (Matt) CFEP-13 rollout - see notes below

    • random notes from other items

      • spruce up the blog!

      • doc fixes on cf-mark-broken

      • mark broken vs. hotfix : should document and make hotfixing easier

        • need to diff the diff

  • (Scopatz) DynamoDB Billing

    • conda-forge AWS account has ~$2200 in charges, alerts have been setup

    • NumFocus credit card?

    • Next steps:

      • Make issue, vote

    • Stop putting expenses on personal credit cards, ask core before spending monies

Meeting ended before we could discuss:

  • (CJ) adding a standing budget item to the agenda

  • (ED) Enforce 2FA? bot / donations discussion in core gitter

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

    • 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?

Active votes

Subteam updates

Bot

Stuff from last week that we didnt get to

  • [CJ/Matt] R 4.0.0 migration is underway-ish

    • see status here: https://github.com/conda-forge/conda-forge.github.io/issues/1025

    • need to wait on the R stuff due to gfortran tests

  • [CJ] Better understanding/handling of run_exports

    • Particularly applicable to issues involving boost and header only deps https://github.com/regro/cf-scripts/issues/960

ARM

POWER

CUDA

Docs

staged-recipes

website

security+systems

  • [Matt] Ready to roll out CFEP-13 - The plan is to

    1. make an announcement that this is happening

    2. provision feedstock tokens for every feedstock

    3. add the STAGING_BINSTAR_TOKEN to every feedstock

    4. add conda_forge_output_validation: true to the conda-forge.yml for every feedstock

    5. wait a while and then turn off the current binstar tokens

    6. run an admin migration to cleanup residual tokens in the CI services and conda-forge.yml files.

    As people rerender feedstocks, they will automatically be moved to the new system. Then eventually rerenders will be required when we deactivate the old tokens.

    We plan to add a few things to help users.

    1. We are moving the cf-mark-broken repo to an admin-requests repo and will be adding the feature for people to request that the feedstock tokens be reset.

    2. The validation/copy service will be changed to start making comments on PRs if it finds errors Still working out the details here.

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

  • 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

    • 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?

Discussion

Check in on previous action items

Copy previous action items from last meeting agenda.

Last meeting

  • [ ] (ED) schedule mirroring conversation

  • [ ] (Kale) schedule

  • [ ] (CJ) Merge all the pinnings PRs

  • [ ] (CJ) Institutional Partners page in docs

    • [ ] TODO: Submit skeleton for PR into conda-forge.github.io repo

2 meetings ago

  • [x] (Matt Becker) Update the docs with our current thinking / principles.

3 meetings ago

Move to Issue Tracker

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

  • Remove conda forge readthedocs.

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