Skip to content

Commit 78e147a

Browse files
Update src/orga/minutes/2023-08-09.md
1 parent e1e327f commit 78e147a

File tree

1 file changed

+36
-7
lines changed

1 file changed

+36
-7
lines changed

src/orga/minutes/2023-08-09.md

Lines changed: 36 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,11 @@ Add new agenda items under the `Your __new__() agenda items` heading
1313

1414
| Name | Initials | GitHub ID | Affiliation |
1515
| ----------------------- | -------- | --------------- | --------------------------- |
16-
| | | | |
17-
| | | | |
18-
| | | | |
19-
| | | | |
20-
| | | | |
16+
| Matthew R Becker | MRB | beckermr | cf |
17+
| Katherine Kinnaman | KK | kathatherine | Anaconda |
18+
| Chris Ostrouchov | CO | costrouc | Quansight |
19+
| Cheng H. Lee | CHL | chenghlee | Anaconda/cf |
20+
| John Kirkham | JK | jakirkham | NVIDIA/cf |
2121
| | | | |
2222
| | | | |
2323
| | | | |
@@ -39,11 +39,40 @@ X people total
3939

4040
### Your __new__() agenda items
4141

42-
- [ ]
42+
- [x] (JK) GLIBC 2.28
43+
- ARM / Power
44+
- NVIDA CUDA static libraries cudart using 2.17 symbols only
45+
- (MRB) Should we mark existing glibc 2.28 sysroots as broken? Will submit PR and see what happens.
46+
- SUSE as an option potentially? Will wait and see; still unclear where everything stands
47+
- [x] (JK) Adding `conda-libmamba-solver` to Miniforge
48+
- https://github.com/conda-forge/miniforge/issues/284
49+
- Jaime (absent): I won't be able to attend today but I am very interested in solving the question above. Miniconda already ships conda-libmamba-solver, and by the September release it will be the default solver (i.e. a `conda` dependency). So it will end up in Miniforge at some point when we update to 23.9 or above. The question is: shall we ...
50+
- a) ship `mamba` in Miniforge too
51+
- a2) the above, and deprecate Mambaforge
52+
- and add links that redirect "mambaforge" -> "miniforge"
53+
- use copies to ensure old installs work (if no redirect option)
54+
- b) let `mamba` in Mambaforge only, and keep both installers separate, with the only difference being the presence of the `mamba` Python package (but note that libmamba and libmambapy are there)
55+
- Discussion: generally have miniconda/miniforge (include conda-libmamba-solver)
56+
- Are we dumping the pypy installers? keep (Up to Matti and others to decide)
57+
- Handling PyPy as separate item (so keeping PyPy installers for now)
58+
- List of artifacts
59+
- https://github.com/conda-forge/miniforge/releases/tag/23.1.0-4
60+
- Consensus is a2
61+
- [x] (JK) TexLive?
62+
- https://github.com/conda-forge/texlive-core-feedstock/issues/84
63+
- We'll need to discover and solve dependency issues before we deprecate (if we choose to do so).
64+
- We don't want to maintain a full (La)TeX distribution. Maybe add a caveat that this is for small bits of TeX, not a "full" distribution. (Reset expectations)
65+
- Plan to add README (maybe also `description` in `meta.yaml`) to reset expectations about this package
66+
- Point out release and migrator merged recently
67+
- [x] (JRG) `osx-arm64` native runners. Possibility to ask for sponsorship to MacStadium ([they do it for Homebrew](https://www.macstadium.com/customers/homebrew)) or Scaleway ([they have an OSS program](https://www.scaleway.com/en/about-us/open-source-program/)).
68+
- JRG: Sorry I will be absent but this was discussed briefly in the core chat and in case anyone missed it, posting it here for visibility.
69+
- JRG: Scaleway offers "up to" 2400€/year for OSS projects. M1 runners cost 0.11€/h, so we can afford around 2.5 runners.
70+
- Asked Amit about cirun support for scaleway
4371

4472
### Pushed to next meeting
4573

46-
- [ ]
74+
- [ ] (JK) Windows ARM
75+
- [ ] (CHL) How long should we keep `osx-64` support?
4776

4877
### CFEPs
4978

0 commit comments

Comments
 (0)