conda-forge core meeting 2023-06-28

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
Katherine Kinnaman	KK	kathatherine	Anaconda
Daniel Ching	DJC	carterbox	Argonne National Laboratory
Jaime Rodríguez-Guerra	JRG	jaimergp	Quansight/cf
John Kirkham	JK	jakirkham	NVIDIA/cf

12 people total

Standing items

• [x]

From previous meeting(s)

• (HV) Boost Unification (see below)
• (HV) Windows Fortran migration (see below)

Active votes

• New core member application
• (not yet made) new staged-recipes application
  • Check your inbox for both

Your __new__() agenda items

• (JRG): Upcoming GPU/long-job CI service. Question about mentioning partners/sponsors.
  • Quansight reached an agreement with a client to support this out of the goodness of their heart.
• (JRG): UI/UX updates on new website and dashboard.
  • Gabriela has been working on this proposal for the dashboard
  • Asmit has been working on this proposal for the frontpage
  • Intent to apply for a Sovereign Tech Fund challenge for documentation, revamping the (failed) GSoD application.
• (JK) GLIBC 2.28
  • https://almalinux.org/blog/impact-of-rhel-changes/
  • JK: CentOS 7 is EOL in 1 yr https://www.redhat.com/en/topics/linux/centos-linux-eol (June 30, 2024)
  • MRB: We just wait and see what Alma does?
  • IF: Maybe we can try Debian if needed.
• (JK) Windows + ARM
• (JRG) Update conda-forge teams and subteams
  • Specially important: code of conduct team PR
• (JRG) Definition of conda-forge (see PR)
• (HV) Boost unification
  • PR blocked on scope: unify & rename (as previously discussed) or also switch to -devel packages (which IMO opens a CFEP-20-sized can of worms)
  • Migrator PR +/- complete -- would like to do this before CPython 3.12 in the fall
• (HV) Windows Fortran migration
  • Open since 2 years; fortran-on-win-migratability will be important soon (scipy will need a new flang version to support windows builds for Python 3.12 at all; without migration we'd get run-dep conflicts with other libflang-dependents)
  • Migrator work that Isuru wanted has been done -- can we start?
  • Side benefit: Would enable openblas+openmp on windows
• (HV) PyPy 3.10 Migration?
  • Last PyPy release introduced PyPy 3.10 and dropped PyPy 3.8
  • Current round of NEP29 releases (numpy, scipy, etc.) already dropping 3.8
  • Possibly migrate PyPy 3.10 & drop PyPy 3.8? When?
• (JK) Drop CentOS 6 & use CentOS 7
  • https://github.com/conda-forge/conda-forge.github.io/issues/1436
• (WV) Sneak Peek of new resolver
  • Port of libsolv to Rust.
• (WV) Anybody wants to talk about pixi? https://github.com/prefix-dev/pixi
• (KK) Is the current functionality for anaconda.org's package instructions/metadata editing good enough?
  • Don't have a ton of background on this, but: https://github.com/conda/infrastructure/discussions/649
  • You can remove install instructions on .org now. Is that enough?
  • Certain packages are build on different feedstocks even though they have the same name
  • https://github.com/conda-forge/graalpy-feedstock/issues/4
  • Expand sorting functionality of packages - sort by architecture, etc.?
  • Somehow linking to recipes (feedstock link on page)
  • Matt+John send details on api call behavior we ran into recently

Pushed to next meeting

• (JK) Windows + ARM
• (JK) Drop CentOS 6 & use CentOS 7

CFEPs

• [ ]