2019-05-29 conda-forge meeting

Pinned Items

New items

  • We need to share two passwords: @condaforge twitter account and the staged-recipes GH account that register the feedstocks. Is everybody OK with keybase?

    • Just move the passwords to keybase

  • NumFOCUS summit will be in late Oct/early Nov it would be nice to have a strong conda-forge representation there.

  • We have 1 small grant development from NumFOCUS (3k) with the goal of a SciPy sprint. I’m writing a new one (this round is 5k) for a better recipe regeneration in conda-skeleton. If anyone is interested please let me know. (I’ll share a Google docs soon.)

    • Is this specific to the pypi generation? Yes!

    • This might be a helpful starting point https://github.com/ericdill/conda-skeletor (This is a real dumb name, so please don’t keep the legacy of this name haha)

  • We have a NumFOCUS team Google drive folder for conda-forge. Who has access to it? Should we make it available to all conda-forge core members?

    • Scopatz to check during the call

  • SciPy 2019

    • BoF and Sprint submitted! We need to know who wants to go, present, use FA, etc.

    • Coordinate more SciPy activities: lightning talks, lunch/dinner?

    • ~~TODO: Open an issue on github conda-forge.github.io to keep track of who is going to Scipy 2019~~

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

  • Discuss a strategy to manage qt patches (23!) and new version builds in the CIs.

  • ESIP update:

    • balance: 3827.78 USD

    • use part of the money to pay for Azure dedicated machines: Windows and Linux to build Qt.

    • Use money to fund travel to SciPy this year?

  • http://conda-forge.org does not auto-upgrade to https

  • CFEP9 conda-smithy

    • PR is now doing the right thing but requires some minor changes to conda-build to make it less gross

    • Works for VC14→ 14.1 and VS2015→ VS2017 as a test case.

  • Emiritus Change model

    • TODO: Governance model similar to sklearn for moving users to non-voting

Old items

  • “Dogfood” strict, which may be default in the next conda, in our CIs?

    • https://github.com/conda-forge/conda-forge-ci-setup-feedstock/pull/50

    • https://github.com/conda-forge/staged-recipes/pull/8009

    • Currently we have a problem with vc on Windows. If we activate strict only the vc present in conda-forge, which is vc 14, will be used but we are building without strict and depending on vc 14.1 from defaults. That means we would need to remove conda-forge vc packages and probably do some rebuilds. (Tried to rebuild qt with strict and hit a wall there even when removing our vc, which means more things must be rebuild first, maybe a migrator would be the best course of action here.)

  • Discuss the use of Drone (native ARM) in conda-forge.

    • https://github.com/conda-forge/conda-smithy/pull/1069

  • Make conda-forge enhancements proposal a “first class citizen” and it a voting process for approving them in our governance docs. (scopatz volunteered to add it to the docs.)

  • Elections/Governance Upcoming helper for staged-recipes - jan jansen (TODO)

    • Staged-recipes team in Governance doc (Review and merge)

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

    • Add formal budget team to Governance doc.

    • Make the spreadsheets available to all (NumFOCUS team drive folder).

    • Perform switch after blas migration is more finished (ocefpaf: check the blas migration status.)

      • Need to either copy over new compiler activation scripts package to cf

      • Or delete ours entirely

      • TODO: Verify that smithy and pinnings are fine for the compilers

  • Azure status

    • Need to fix windows (vc9/14 and cmake)

    • Credentials issues (need pipelines account to access Azure, will move to GH auth soon)

    • How to handle bespoke build agents (for builds taking longer than 6 hours (qt, compilers, etc.)

    • How to restart an Azure job?

  • NVIDIA

    • Louder communication path for large ecosystem shifts (compiler migrations)

      • Banner on AnacondaCloud, status updates on channel

      • Print something while using conda install

      • More frequent updates

    • AnacondaCloud can fall over (mirroring conda)

    • Try to track down hard linked drivers in GPU packages.

    • Progress on colo talks for bins of gpus at Anaconda (Waiting on Mike W. on this.)

  • Migrations

    • Blas

      • Underway

    • Libprotobuf

      • Underway

    • gfortran (wait for cfep-09)

      • Need to build a migrator for new osx gfortran

      • https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/174 maybe?

    • Power and Arm

      • Ongoing https://conda-forge.org/status/

      • More leafs to target?

    • Openssl

      • Underway

    • Readline (wait for cfep-09)

      • ABI change

      • Needs migrator

    • @Christopher W : Add link to migration (conda-forge status?) docs for conda-forge.github.io (ocefpaf: I’ll add the status link to the docs)

  • Nvidia relationship

    • Building GPU packages using conda-forge packages, upload to their own channel after building with cudatoolkit on their own Jenkins system.

    • GPU compiler shim package: https://github.com/conda-forge/staged-recipes/pull/8229

    • Maybe form a working group?

  • Perl ecosystem? (ocefpaf:Ask bBjorn G.)

    • move forward with plan to incorporate perl into CF

      • Do we have an issue or something for this?

  • R 3.6 migration? (ocefpaf: Ask bBjorn G.)

    • https://github.com/conda-forge/r-base-feedstock/pull/82