diff --git a/community/minutes/2024-11-13.md b/community/minutes/2024-11-13.md deleted file mode 100644 index 0428af7f49..0000000000 --- a/community/minutes/2024-11-13.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -tags: [meeting-notes] -title: '2024-11-13' ---- -# conda-forge core meeting 2024-11-13 - -Add new agenda items under the `Your __new__() agenda items` heading - -- [Zoom link](https://zoom.us/j/9138593505?pwd=SWh3dE1IK05LV01Qa0FJZ1ZpMzJLZz09) -- [What time is the meeting in my time zone](https://dateful.com/convert/utc?t=5pm) -- [Previous meetings](https://conda-forge.org/community/minutes/) - -## Attendees - -| Name | Initials | GitHub ID | Affiliation | -| ----------------------- | -------- | --------------- | --------------------------- | -| | | | | -| | | | | -| | | | | -| | | | | -| | | | | -| | | | | -| | | | | -| | | | | -| | | | | - -X people total - -### Standing items - -- [ ] DJC conda-forge default build containers should always have the latest glibc/sysroot package that we publish - - https://github.com/conda-forge/conda-forge-pinning-feedstock/issues/6283#issuecomment-2453101928 - - defaulting to the latest os makes os_version irrelevant for most users because glibc backward compatability - - glibc constraint still set by sysroot package at build time; this package can lag behind syroot in container -### From previous meeting(s) - -- [ ] - -### Active votes - -- [ ] - -### Your __new__() agenda items - -- [ ] - -### Pushed to next meeting - -- [ ] - -### CFEPs - -- [ ]