2019-10-30 conda-forge core meeting


Attendees

  • Eric D.

  • Marcel

  • Filipe

  • Jonathan

  • Sophia C.

  • John K.

  • Dougal

  • Marius

  • Mike S.

  • CJ

  • Lori

Agenda

Your agenda items

  • (Eric) What’s everyone going to be for Halloween?

    • Game of Thornes end episode writter (Filipe)

  • (Eric) Scheduling a time that’s more convienent for folks in other time zones. Quick vote and I’ll schedule it

    • 10:00 UTC (6:00 EDT)

    • 12:00 UTC (8:00 EDT)

    • 17:00 UTC (13:00 EDT) (current meeting time)

    • We don’t need to reschedule to accomodate. Filipe wanted to accomodate some others in other time zones but they’ve sort of disappeared

  • (Filipe) Discussion NumFOCUS PEX cards. Do we need it? Should we order one?

    • Opinion: we should avoid these and just do better planning. Worst case

    • What about recurring costs? For recurring costs, NumFocus can pay these for us so we should plan ahead and get them to do that.

    • Conclusion: Better planning.

  • (Filipe) Updated on the new SGD submission.

    • Small Grants Development (SGD)

    • to foster some work on conda-skeleton and regenerating recipes. This is to do what bioconda folks are already doing. This will help us be better about dependency tracking and metadata updates

    • Filipe is planning on paying someone to do this work (Marcelo Trevisani)

  • (Filipe) Strategies to catch up with Qt releases.

    • (Isuru) Qt 5.12 is an LTS release with EOL in Dec 2021. This is what is packaged in conda-forge.

    • (Isuru) Qt 5.13 is a regular release with EOL in one year usually. (June 2020)

    • We should be building Qt more regularly. How do we achieve this? Provisioning Windows Azure VMs seems like the best path forward.

      • We’d need to make an Azure org (or whatever their term is) and then distribute credentials

      • We should consider talking to Microsoft about help doing this on Azure.

      • Marius will run point on these conversations this week at NumFocus Summit and PyData.

      • Get updates from Marius at next dev meeting.

  • (CJ) Any NumFOCUS summit things: (from NumFOCUS) We ask that our more senior projects come prepared to briefly share any recent project news or experiences that would be of value for others to learn about. Things like:

    • Funding successes or failures

    • Major governance changes and their impact

    • Initiatives taken to increase diversity and inclusion in your project and their results

    • Any experiences that other projects could learn from

    • (Eric) Send out email to conda-forge group asking for feedback on these points.

  • (CJ) pydata nyc lightning talk for CF, Tom asked for a short something

    • Anthony said he’d take this

  • (John) Aligning on GPU packages between CF and defaults

    • NCCL

      • (pronounced: Nickel)

      • Defaults is still on 1

        • Will likely update when one of our deps needs it.

      • Many things don’t work without 2 (or even newer)

      • Now in CF at version 2.4

    • CuPy

      • Recently added to conda-forge

      • PfN (Preferred Networks) taking over maintenance of the feedstock

      • Defaults is still on 6.0.0 (latest is 6.5.0)

        • Building is really hard on windows and this is what the hold-up is on the Anaconda side.

    • xgboost

      • Currently CPU only in conda-forge

      • Would like to add GPU builds to conda-forge

        • https://github.com/conda-forge/xgboost-feedstock/issues/26

      • Selection between CPU/GPU can be simplified

        • https://github.com/conda-forge/xgboost-feedstock/issues/23

        • https://github.com/conda-forge/xgboost-feedstock/pull/35

    • ppc64le and aarch64

      • Currently no aarch64 cudatoolkit packages

      • ppc64le cudatoolkit packages out-of-date (currently at 9.0)

        • Anaconda would have much more success getting newer packages out if the recipe was updated – the holdup is finding where all the shared libraries moved to.

      • NVIDIA Docker images exist for ppc64le

      • NVIDIA Docker images in the works for aarch64

  • (Marius) Kubernetes build update

    • Can build cupy on a transient kubernetes gpu cluster.

    • Preliminary results feel positive.

    • maybe we have blog post #2 right here?

    • All of this work is happening on GKE. Would be good to try and get this ported over to Azure, maybe.

  • (CJ) Should conda-forge ship ARM / aarch64 conda-forge miniconda installers?

    • Anaconda builds ppc packages and provides anaconda / miniconda installer

    • Should conda-forge build these?

      • There’s no one on this conda-forge call that actually wants to own the maintenance burden of this.

  • (Filipe) Python 3.8 made it to defaults

    • (Mike): “sort of” made it to defaults. We only have py3.8 available right now.

Subteam updates

Bot

  • (CJ) ROS (robot operating system) integrated with auto tick bot (mostly, they didn’t jinja2 their urls causing problems)

  • (CJ) The bot now handles multi-output recipes properly, should make migrations go better

  • (CJ) CircleCI run URLs are now in bot commits, and comments making debug easier

ARM

Docs

staged-recipes

website

CI infrastructure

Compiler upgrade

CFEP updates

How do we start getting traction on these?

cfep-03 Manual upload of builds

cfep-04 X11 and CDT policy

cfep-05 dev/rc builds

  • (Eric) I think there’s been some discussion on cfep-05 recently. Maybe @cj can give us an update

  • (CJ) I think the main stall here is if we can get .../label/rc/matplotlib to be a valid anaconda.org path

  • (CJ, John K.) also are dev labels provided on a per package or per feedstock level (should we have a .../rc/gdal and .../rc/libgdal)

    • (Eric) We should implement this in whatever way is as simple as possible for the conda-forge tooling ecosystem. If there is enough of sentiment that they want

cfep-06 Staged-recipes review lifecycle

cfep-08 Too Big To Fail

cfep-10 Feedstock statuses, unmaintained

Discussion

Check in on previous action items

Copy previous action items from last meeting agenda.

Last meeting

  • [ ] (Filipe) CFEP-03: Review, fix any text and merge it in.

    • Minor updates that are needed. This will likely get done in December.

  • [ ] (CJ) CFEP-08: Merge in with deferred status

    • Will check in next meeting.

2 meetings ago

3 meetings ago

  • [ ] (Eric) Email out to see if we can get more engagement on regular dev meetings.

  • [x] (Sophia) Set up meeting to talk about Condafile stuff.

    • Will punt on this until she’s working on this actively again

  • [x] (Filipe) Ping Bjorn to try and get Debian community more involved with conda-forge

    • Going to drop this from our tracker

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

4 meetings ago

  • [x] (Filipe) Progress on setting up a self-hosted blog

    • Medium seems to be generally downvoted

    • Host your own blog seems to be generally positive

    • Can we mimic what Dask does for their dev blog? https://github.com/dask/dask-blog

    • Moved to github issue https://github.com/conda-forge/conda-forge.github.io/issues/916

  • [x] (Needs Owner) Searching on our website is a little difficult

  • [x] (Filipe, Anthony) Improve docs on releasing conda-smithy. Currently says “use rever”. Would be good to fill out more info there for those of us that are unfamiliar with rever.