2019-02-20 conda-forge meeting

Pinned Items


New items

  • Elections

    • Staged

      • mjscosta

        • “I can review C++ and Python, and Python + extensions recipes.”

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

    • Two kinds of migration

      • No breakage (everything is pinned properly so everything can live side by side)

      • Breakage (current pins are incorrect, need second channel or hotfix repodata)

  • Plans for AnacondaCon

  • Migrations

    • gfortran

      • Need to build a migrator for new osx gfortran

    • Power and Arm

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

      • Fixed some bugs, graph is fuller now

    • Openssl

      • https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/191

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

      • https://github.com/regro/cf-scripts/issues/409

      • https://www.openssl.org/blog/blog/2018/11/28/version/

      • Channel priority doesn’t stop default’s python being installed with the newest openssl

      • rebuild against openssl as soon as possible

        • Anaconda to take this on for their next sprint (starting Monday, Feb 11).

      • Pending new pinning

    • Readline

      • ABI change

      • Needs migrator

  • Meta Channel

    • https://github.com/regro/conda-metachannel

      • Blocking parts

      • Still need a domain / subdomain so that we can add some TLS

    • probably not ready yet for use internally in

    • Want benchmarks

  • Conda-forge on Open Source Directions

  • Azure status

    • Linux and OSX ready to go

    • Need to fix windows (vc9 and cmake)

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

    • Postpone to next meeting

  • ESIP update

    • choose a date and place for the sprint

    • decide how much we will use for CIs vs Sprint/Travel (1000USD/4000USD?)

  • Nvidia relationship

    • Anaconda met with Rapids (NVIDIA) team

    • Reach out to NVIDIA to attend meetings

    • Add NVIDIA person to core?

    • Add to governance discussing donations and governance.

    • More followup with NVIDIA needed

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

    • Maybe form a working group?

  • Perl ecosystem?

    • noarch

    • base stack

    • Many perl packages on bioconda (600+)

    • Perl ABI?

      • https://abi-laboratory.pro/?view=timeline&l=perl

    • move forward with plan to incorporate perl into CF