Skip to main content

2020-02-19 conda-forge core meeting



Your agenda items

  • (ED) Recurring Anaconda update on what's going on on our side.

    • CF summit this year: Scipy?
      • Anaconda can help cover travel costs
      • scheduling challenges to work through.
      • overlapping tutorials or overlapping sprints?
      • maybe one day at the start and a half day at the end?
      • Second day of sprints not too many people show up anyway.
      • proposal: full-day meeting second tutorial day, half day meeting second day of sprints.
    • conda / conda-build update, if any *
  • (ED) Thread about .conda package format on twitter

  • Miniforge installers for platforms where Anaconda, Inc provides Miniconda

    • As CF core we had voted to NOT to x64. They're doing nice work, so it's not like we're mad at them. The biggest question is that it seems like there are parts of the CF ecosystem that are operating outside of the decisions we make as core.
      • We had proposed using conda-pack for standalone CI usage. Host the conda-pack'd conda-forge x86 "miniconda" on azure / s3 somewhere.
    • Eric TODO: Work with Scopatz to get the right people in the room to talk through these concerns.
  • TODO: Track votes

    • Eric to sync with Marius on some github strategies for tracking who participates in the voting

Subteam updates


  • (Eric) Do we need further discussion of Automerging?
    • Tradeoff discussion from last meeting was "increase risk of bad packages and increasing throughput"
    • (CJ) Discussion of what we can do to minimize risk of bad packages, what is the spectrum of risk tolerance among us (eg. if we had X capability I would feel comfortable with automerge)
      • Attempt at using pip check, issues with that approach
      • Advanced conda skeleton?
  • (AS) dynamodb +
    • terraform in shared, encrypted git repo on
    • pieces of bot moving to dynamodb
    • pieces of other bits of infrastructure can move to keybase w/ terraform as well (herkou, keys in repos, etc)







CI infrastructure

Compiler upgrade

CFEP updates

Open PRs

  • cfep-04 X11 and CDT policy

    • 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

    • Lingering comment from @saraedum. @jakirkham, can you reply? Has unadressed comment from @saraedum from Jan 8, 2020
  • cfep-10 Feedstock statuses, unmaintained

    • Needs another review. Has unaddressed updates from pkgw as of Jan 11, 2020


Check in on previous action items

Copy previous action items from last meeting agenda.

Last meeting

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

2 meetings ago

  • Open up a CFEP about what to do about Python 2.7.
  • (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.
  • (Eric) Change meeting cadence
    • We're not going to change the meeting cadence. Too much momentum for us on this every-other-wednesday schedule.

3 meetings ago

  • cfep-11 next steps: Merge PR and ping staged-recipes team they can implement if they want?
  • 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

Move to Issue Tracker

  • (Eric) Scheduling Anaconda <-> conda-forge sync on 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.