@@ -13,12 +13,12 @@ Add new agenda items under the `Your __new__() agenda items` heading
13
13
14
14
| Name | Initials | GitHub ID | Affiliation |
15
15
| ----------------------- | -------- | --------------- | --------------------------- |
16
- | | | | |
17
- | | | | |
18
- | | | | |
19
- | | | | |
20
- | | | | |
21
- | | | | |
16
+ | Jaime Rodríguez-Guerra | JRG | jaimergp | Quansight/cf |
17
+ | Cheng H. Lee | CHL | chenghlee | conda-forge/Anaconda |
18
+ | John Kirkham | JK | jakirkham | conda-forge/NVIDIA |
19
+ | Marcel Bargull | MB | mbargull | Bioconda/cf |
20
+ | Filipe Fernandes | FF | ocefpaf | conda-forge |
21
+ | Jannis Leidel | JL | jezdez | Anaconda/conda-forge |
22
22
| | | | |
23
23
| | | | |
24
24
| | | | |
@@ -37,13 +37,87 @@ X people total
37
37
38
38
- [ ]
39
39
40
- ### Your __ new__ () agenda items
41
-
42
- - [ ]
40
+ ### Your ` __new__() ` agenda items
41
+
42
+ - [X] (JK) Windows ARM64
43
+ - (SD) Working on new Windows ARM hardware
44
+ - like Surface Pro X
45
+ - CPython building on Windows ARM (tier 3)
46
+ - Currently GHA doesn't have native Windows ARM support
47
+ - How to enable developers?
48
+ - Interested in enabling conda-forge to build packages
49
+ - Easy to give resources to one org (conda-forge fits the bill)
50
+ - What would be needed?
51
+ - Dev time (Finn dev w/Steve would be contributing)
52
+ - Hardware?
53
+ - Easiest path: https://azure.microsoft.com/en-us/products/dev-box/
54
+ - Could also ship physical machines
55
+ - Can cross-compile (have cross-compilers)
56
+ - (MRB) Does LIEF work on Windows ARM?
57
+ - (SD) Ordinary PE with another instruction set
58
+ - (JRG/MRB) Migrator? Doable
59
+ - (JRG) Constructor stack? NSIS, pyinstaller (conda-standalone)
60
+ - SD: x86 installers should work
61
+ - JRG: We need changes in constructor to support "cross-installers", but not too complicated (export CONDA_SUBDIR?)
62
+ - ED: what's needed?
63
+ - 1 or more "core sponsor(s)" of the work that can ensure things aren't block
64
+ on the CF side
65
+ - someone that provides hardware
66
+ - someone that has the time to hack on this problem
67
+ - someone at Anaconda that can help push changes into the
68
+ various tools that need to be updated to support the new platform
69
+ -
70
+ - Thoughts? :)
71
+ - (JL) Introducing new platform is non-trivial
72
+ - Want to make sure this is somehow funded
73
+ - Maybe NF as a conduit (SDG or ...?) for Conda / cf
74
+ - (MRB) How did we do this in the past (aarch64, pp64le, OSX arm)?
75
+ - (IF) Linux aarch64 was Jonathan Helmus ( https://github.com/jjhelmus ) starting with Rasberry Pi and going from there
76
+ - (IF) Can bootstrap
77
+ - (JL)
78
+ - (IF) Keeping things green (once a package works we'd like it to keep working)
79
+ - (IF) A few more Azure jobs? Particularly if Windows ARM supports multiple version
80
+ - (MRB) Cross-compiling is probably most efficient approach (like what MacOS ARM uses)
81
+ - (MRB) ~~ Let's create a~~ tracking issue
82
+ - https://github.com/conda-forge/conda-forge.github.io/issues/1940
83
+ -
84
+ - (CHL) Tracking ecosystem support as [ conda/conda #11472 ] ( https://github.com/conda/conda/issues/11472 )
85
+ - PR [ conda/conda #11778 ] ( https://github.com/conda/conda/pull/11778 ) : add ` win-arm64 ` as platform in ` conda `
86
+ - PR [ conda/conda-build #4579 ] ( https://github.com/conda/conda-build/pull/4579 ) : add ` win-arm64 ` as platform in ` conda-build `
87
+ - [ ContinuumIO/anaconda-issues #12957 ] ( https://github.com/ContinuumIO/anaconda-issues/issues/12957 ) : add ` win-arm64 ` as platform in anaconda.org
88
+ - [X] (JK) New CTK packages / CUDA 12
89
+ - Most packages up (few remaining / some follow up items)
90
+ - ` cuda-version `
91
+ - https://github.com/conda-forge/cudatoolkit-feedstock/pull/89
92
+ - https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/435
93
+ - Opening CUDA 12 migrator
94
+ - Package layout changes:
95
+ - Document?
96
+ - Message?
97
+ - Incremental rollout?
98
+ - (Longer-term) CUDA 11 backport?
99
+ - New style packages on older CUDA versions
100
+ - What version to start with (` nvidia ` channel has ` 11.4 ` )?
101
+ - ` cudatoolkit ` becomes metapackage?
102
+ - Potential to drop some CUDA specific things
103
+ - Docker images
104
+ - conda-forge-ci-setup simplification
105
+ - [x] (HV) Bump to GCC 12 / LLVM 15 (should not be controversial, just needs a merge)
106
+ - https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/4215
107
+ - [ ] (HV) RHEL 8-compatible sysroot (most likely AlmaLinux, matching [ manylinux_2_28] ( https://github.com/pypa/manylinux/issues/1282 ) )
108
+ - sync requirements / naming with Anaconda (once aligned, I'll try to start raising PRs)
109
+ - (CHL) Anaconda naming convention is ` sysroot_${subdir}=${glibc_version} ` (so probably ` sysroot_linux-64=2.28 ` )
110
+ - use cdt_name = "conda_2_28"
111
+ - pull CDTs out of alma8
112
+ - see Matthew's initial [ TODO list] ( https://github.com/conda-forge/conda-forge.github.io/issues/1432#issuecomment-1512315951 ) .
113
+ - [ ] (HV) Boost harmonization
114
+ - Can we agree on the plan in https://github.com/conda-forge/boost-cpp-feedstock/issues/137 ?
115
+ - If so, I can start raising PRs
116
+ - agreed to plan with name libboost-python for anaconda py-boost and conda-forge boost
43
117
44
118
### Pushed to next meeting
45
119
46
- - [ ]
120
+ - [ ] (WV) rattler-build - new conda package build tool: https://github.com/prefix-dev/rattler-build
47
121
48
122
### CFEPs
49
123
0 commit comments