Skip to main content

conda-forge core meeting 2021-11-17

last weeks meeting What time is the meeting in my time zone Meeting info:

Attendees​

  • Eric D
  • Matthew Becker
  • Keith Kraus
  • Cheng Lee
  • Wolf V
  • Filipe
  • Isuru
  • Marcel
  • Adrien Delsalle - working with Wolf on mamba
  • John K
  • Ryan May
  • Ken Odegard
  • Lori Burns
  • CJ Wright

Agenda​

Standing items​

  • intros for new folks on the call

  • (FF) budget

    • current approvals?
    • Whenever updated numbers land, please screenshare and show the budget.
      • Link is in Keybase (numfocus_spreadsheets.txt)

  • open votes

    • none

  • 2022 Outreachy / GSoC

    • Ask each week: Any interested parties in owning this?
    • Discussion 2021-11-03
      • If we want to do outreachy again we need a champion - Filipe can't do it next year. Same with GSoC.
      • GSoC is free to us
      • Outreachy costs us $$ ($6500). $6k for student, $500 for admin
      • Some interest from Jannis - he and Filipe will chat about possibly handing off

From previous meeting(s)​

  • (CHL): Any updates/improvements needed for anaconda.org? (Context: needed to plan internal development work for 21Q4, 22Q1)

    • Support for .conda packages

    • (IF): ability to modify the instructions -- change the "To install this package with conda run one of the following: ..." messages; e.g., squash (default) comments about broken labels.

    • (IF): repodata patches for labels

    • (MRB): faster CDN sync

    • (MRB): support for package signing

    • (CHL): THE MD5 THE!

Your new() agenda items​

  • (WV via ED): Packagingcon recap

    • Interesting talks:
      • lxroot for sandboxing; may be useful for mamba to isolate recipe
      • OCI image registries - would like to support in mamba
      • PubGrub: dart resolver implemented in Rust
        • interested in error messages specifically to see if we can improve error messages in current solver
      • mike sarahan did some rust code in conda (ronda / libronda or something?)
      • homebrew / homebrew linux packaging stack - proposing to homebrew "homebrew meets CF" - maybe they could help us with self-hosted runner questions?
    • MB - major intent was to bring people together from all the different spaces. quite a lot of time we heard from speakers or in the chat was "oh you're doing the same thing" or "oh we should collaborate"
    • TODO: Set up meet-and-greet call with homebrew team?
    • what's the cadence? Idea was to make it again next year but in person. has $50k in the bank (- 30% that numfocus takes). Probably need to start organizing it now.

  • (WV): Announcement about repodata signing in https://adelsalle.medium.com/5ce65a27d7d5

    • Should new core members get a YubiKey? ;)
    • basic plan:
      • anaconda.org needs to get rid of MD5 sums
      • we can have a conda-forge key to sign metadata and repodata to support mirroring
      • isuru: we can't have second class maintainers
      • cheng: need to check potential legal ramifications of signing

  • (WV): cudatoolkit run-depend on __cuda?

    • Can use CONDA_OVERRIDE_CUDA to force install on systems without __cuda available

  • (MRB): should we redo the repodata patches at least once a week?

    • I think we have some that continue to apply to new artifacts because of ongoing bugs/changes/issues
      • non-backwards compatible operators in conda-build?
      • mpi changes?
      • todo:
        • make a cron job that runs show_diff.py and posts an issue + commit if it is non-empty

  • (WV): Can we get Qt over the finish line?! 🙏

  • (CHL,KO): Updates from Anaconda

  • TODO: Skip mid-december meeting. One more core call at start of december.

Pushed to next meeting​

Active votes​

CFEPs​

  • cfep-12 Removing packages that violate the terms of the source package
    • Stalled since May 26, 2020
    • 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? they did the legal seminar which is recorded

TODOs​

2021-11-03

  • Self-hosting CI TODOs:
    • Change URL from drone.conda-forge.org. Proposals:
      • woodpecker.conda-forge.org
      • ci.conda-forge.org
    • Set up monitoring
      • Quantstack is setting up grafana for the mirror

2021-10-18

2021-09-22

  • (WV): TensorFlow-GPU ready to go, just need to decide if GPU should get prio over CPU?!

    • GPU gets prio

  • (MRB) master to main move (https://github.com/conda-forge/conda-forge.github.io/issues/1162)

    • everything done except feedstocks, releases, conda-smithy, and our github actions
      • releases is broken, opened an issue with github
    • some options for feedstocks
      • make sure to change the upload on branch key
    • (MRB) make an announcement on how to update local clones (moved to the issue above)
    • (MRB) make sure to update upload_on_branch (moved to the issue above)

2020-11-18

  • (IF/MRB/MV) intel oneAPI
    • todo
      • (Nikolay) licensing for opencl_rt
      • (Nikolay) intelmpi ABI compat w/ mpich
      • (MRB/IF) figure out how exactly to package C/C++ compilers
      • (MRB/IF) think about fortran ABI
      • (MRB) make conda-forge compilers room (add people including keith)
  • (MB) asking core members to move to "emeritus" status
    • TODO: Eric to set up quarterly check-in for all core members to see if they're interested in remaining "active" or if they want to move to emeritus
      • Remove emeritus folks from having access to various credentials (api tokens, twitter password, etc.)? This would require a change to the governance doc.

2020-11-11

  • TODO: Think about bringing in JOSS to provide context around how we might best write papers

2020-11-03

  • TODO: Check on Forrest Watters permissions for core
  • (FF) Outreachy would cost 6500 USD.
    • Next steps: write abstract and vote on spending of funds.

2020-10-28 2020-10-21

  • (Marius?) Python 2.7 migration
    • ( ) [ ] make a hint
    • ( ) [ ] make an announcement
    • ( ) [ ] make the hint a lint

2020-10-07

  • Make sure to add the NVBug info to the cudatoolkit package that conda-forge makes (if we make one)

2020-09-09

2020-08-26 Docker hub

  • (JK) Check in on Azure build workers to see if they have the docker hub limitation.
  • (JK) work with dockerhub to see if we can get OSS status
    • Check in again at some point. We haven't heard back as of 2020-09-23

OVH

  • Shout-out on twitter at some point. "Thanks forOVHCloud for providing a VM", etc. (maybe after we ship qt on windows with it?)

  • Figure out how to communicate breaking changes to users. Likely should open up an issue immediately for futher discussion. Ping @kkraus, plus capture notes from further up in these meeting notes

  • John K. will update the cuda toolkit feedstock on the git repo to note the NVBug link to the internal NVIDIA issue tracker

  • Jonathan will update docs to note that some non-exhaustive list of packages (like cuda-toolkit, MKL, etc.)

  • Jonathan will review this PR

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

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

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