conda-forge core meeting 2023-09-06

Add new agenda items under the Your __new__() agenda items heading

• Zoom link
• What time is the meeting in my time zone
• Last week's meeting

Attendees

Name	Initials	GitHub ID	Affiliation
Dave Clements	DPC	tnabtaf	Anaconda
Cheng H. Lee	CHL	chenghlee	Anaconda/c-f
Marcel Bargull	MB	mbargull	Bioconda/cf
Filipe Fernandes	FF	ocefpaf	conda-forge
Jaime Rodríguez-Guerra	JRG	jaimergp	Quansight/cf
Matthew R Becker	MEB	beckermr	cf

11 people total

Standing items

• [ ]

From previous meeting(s)

• (JK) NumPy 2.0 planning
  • https://github.com/conda-forge/conda-forge.github.io/issues/1997
  • https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/issues/516
• (JK) Start using conda's libmamba solver
  • https://github.com/conda-forge/conda-forge-ci-setup-feedstock/pull/259
  • https://github.com/conda-forge/docker-images/pull/240
  • JRG:
    • Working on full support for this in conda-smithy. Merged the mambabuild parts already, will proceed with the "install" parts next.
• (HV) -dev vs. -devel
  • came up in boost unification, current PR uses the latter based on Isuru's rationale
  • matches Anaconda naming & CDTs, does not match recent CUDA feedstocks, tangentially related to distro discussion (RHEL vs. Debian). We should try to choose one.
  • JRG: Our own data:
    • -dev suffix: 33 packages
    • -devel suffix: 10 packages

Active votes

• [x]

Your __new__() agenda items

• (HV) MacOS 10.13, redux
  • Cannot use recipe_append.yaml as discussed last call, doesn't work for outputs
  • Since then: new feedstock for "sysroot" on osx & plan to handle this through new jinja function {{ stdlib('c') }} together with cbc-keys for sysroot_impl+version (would also help linux side)
  • This will probably take a while (conda-build, boa, rattler-build, etc., much less rolling out to all feedstocks), and we need an intermediate fix due to already-pressing issues.
• (HV) Branch deletion policy?
  • I'd suggest to delete dead branches on feedstocks (e.g. long-EOL maintenance branches), and keep history as a git tag on the feedstock. Thoughts?
• (DPC) From the open source director at Posit
  • We are starting to see more requests to add R packages to conda. e.g. https://github.com/tidymodels/tidyclust/issues/167
  • We’re not quite sure how to do this though, and if there’s any sort of social norms around adding your own packages to conda to navigate. Is there guidance you could offer? We’d like to be helpful if we could!
  • Docs: "Contributing Packages"
  • Check all submissions in staged-recipes: https://github.com/conda-forge/staged-recipes/pulls?q=is%3Aopen+is%3Apr+label%3AR
• (CHL) Annoucement: expect a conda release end of September

Pushed to next meeting

• [ ]

CFEPs

• [ ]