2018-11-27 conda-forge meeting¶
Pinned Items
Zoom instructions: +How to connect to zoom
New items
CloudFlare Migration
Sophia will add a diagram of the system
To go live tomorrow, Wed Nov 28, morning (~9 AM central). Anaconda will monitor it actively.
MichaelS/Sophia will announce this start time on gitter along with the diagram and a rehash of the reasoning and changes proposed.
NumFOCUS Small Grant Proposal accept and we just got 3000USD for the “conda-forge sprint at SciPy 2019”
ESIP second change for a small grant 6-10k
https://www.esipfed.org/esip-lab/funding-opportunities/f2018rfp
GSoC 2019
https://developers.google.com/open-source/gsoc/timeline
Journal article
https://github.com/conda-forge/conda-forge-paper
Put together sections see who is interested in writing
Previous items
Compiler rebuild status
python done for both compiler stacks
Qt: try to build on Azure?
(DISCUSSED/Postponed) New approach to reducing CI load https://github.com/conda-forge/conda-forge.github.io/issues/647
Might be possible to not be totally insecure with work. But nobody is volunteering to do that work right now. :)
Pushing PR builds to a staging channel might be a nice UX improvement so you can test anyway.
Copying packages to gcc7 label https://github.com/conda-forge/conda-smithy/issues/892
MPI metapackage
Just wait for new conda 4.6 with strict channel priority, and then add main label to those builds
(DISCUSSED/Postponed)Mergify = auto-merge version bump PRs when CIs pass?
https://github.com/conda-forge/conda-forge-maintenance/issues/49
Worry about bot not detecting dependency changes
Definitely opt-in only at first
One possibility: only after an approved review (so you can say “merge assuming CIs pass”)
Add overlinking error flag by default?