Skip to main content

2020-06-22 conda-forge core meeting

Attendees​

  • Eric D
  • Filipe
  • Uwe
  • Jonathan Helmus
  • Kirkham
  • Matt B.
  • Anthony Scopatz
  • Lori
  • Cheng Lee
  • Ray Douglass
  • Keith Kraus
  • Sylvain
  • Mike Sarahan
  • Wolf
  • Isuru

Agenda​

Your agenda items​

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

  • (FF) NumFOCUS updates on GH 2FA, Google Drive, and AWS

    • GitHub 2FA issue has been resolved (only needed for core members)
    • Donors names and addresses are in NumFocus Google Drive
    • Need to respond to NumFocus on possible AWS usage, deadline has passed. The purpose here was to get credits for CF to use on AWS
      • Can send a note to Leah
      • maybe get credits for AWS workspaces for windows machines? This would help with debugging windows stuff. Also have aarch64 machines. Edit the following doc if you've got ideas for how do to stuff with AWS. Next week Filipe will send an email to Leah / NumFocus
      • https://hackmd.io/bXUZ8a08SBeTs4t9fVXR4A?edit

  • (FF) Scipy BoF, sprint, and members attendance/presentations.

    • CJ/Marius will be handling packaging BoF.
    • Anyone to handle sprints?
    • Anyone submitting talks / tutorials?
      • John to give talk on GPU packaging
      • wolf giving talk on scikit-geometry

  • (CJ) standing budget item

    • Waiting on follow up on existing AWS charges

  • (CJ/Anthony/MRB) making a conda-tools org for tooling (conda-smithy, conda, mamba, grayskull, boa, etc.)

    • Bit of an existential threat of forking the community of conda package users. Would be good to try and avoid that.
    • Centralize tools under one github org
      • conda-forge org?
        • benefit: already a NumFocus project. Get a lot of admin overhead for free (governance model, community participation, etc.)
      • conda-tools or new other org?
        • putting tooling org under conda-forge raises questions with some enterprise users and some other users. Separate org may be easier
        • Form new org, apply as new NumFocus project. Accomplishes same goal of bringing together single set of community led tools and projects for this ecosystem.
        • Proposal: If we form new org just copy the conda-forge governance model
        • This could also be a good place to have the specification discussions that we've been talking about for a while (conda, conda-build meta.yaml, etc.)
    • (WV) Having specs in a centralized community-owned place would be great - makes planning for the future feasible.
    • (FF) How do we avoid stifling innovation?
      • pypa sort of has a "Graduate into top level org" policy.
      • need to be a welcoming org. More along the lines of pyvis
    • (SC) What is considered "core" to jupyter is not the implementations, but the protocols / file formats / etc. If you write a tool in Jupyter that supports these then you have immediate access to a wide variety of tooling
      • What is the analog of this for the conda ecosystem? package specs (meta.yaml), package formats, etc.?
    • Need to be careful about naming. Don't want to become another "python packaging authority"

  • (WV) Quick announce of micromamba (https://gist.github.com/wolfv/fe1ea521979973ab1d016d95a589dcde)

  • (WV) Update on standardization of next gen package format from last meeting?

  • (MRB/Isuru) cos7 and CDTs plans

    • merge this PR: https://github.com/conda/conda-build/pull/3969
    • move all cos6/cos7 CDT packages from defaults to conda-forge
    • update builds with no_hoist and run constrained on the sysroot packages
    • migrate all of them to new sysroot and add dep on sysroot package
    • remove shims in compilers

  • (FF) Should we do Outreachy as part of an effort to support diversity in tech? Advantages are low cost and high impact. Dissdvantages are the time effort from the mentors.

  • (UK) CFEP-18: Packaging static libraries

  • (IF) cf-mark-broken: Marking not broken packages as broken

  • (KK) CUDA 11 support

Active votes​

Subteam updates​

Bot​

  • (CJ) Status of openjdk, r-java stalled out
Stuff from last week that we didnt get to​

ARM​

POWER​

CUDA​

Docs​

staged-recipes​

website​

security+systems​

  • still need to finish CFEP-13

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

    • 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-18 Packaging static libraries

Discussion​

Check in on previous action items​

Copy previous action items from last meeting agenda.

Last meeting​

  • (CJ) Form finance subteam
  • document how users are supposed to interpret broken label
  • update how we, as core, are supposed to mark packages as broken
  • (ED) document strategies for reproducible environments using conda-forge
  • (UK) Static libraries stuff
    • Add linting hints to builds to find them
    • Recommend how to package them -> CFEP-18
    • We should write docs saying we don't provide support and this is a bad idea. -> CFEP-18

2 meetings ago​

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

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)