2019-09-18 conda-forge core meeting¶
Pre-arranged stuff to talk about. Email core team on Monday of the week of the dev meeting to ask for things to talk about.
(CJ) CFEP5. Updated the proposal to reflect the desire for a
Filipe: Update the issue with discussion during call when finished with conference.
CJ: Hot potato! you own this cfep now
(CJ) updates to the bot database structure
(CJ) piggy back migrations proposal
e.g., Converting python package installs from
python setup.py installto
pip install <more stuff>
(CJ) cfep9 update
(Filipe, Dougal) How can we get users to engage us and open issues?
(Marius, Isuru) Azure migration update?
Do we want to roll out https://github.com/conda-forge/conda-smithy/issues/1131 to all feedstocks?
Update to clang 8.0.1 and gfortran 7.3.0 on OSX
No rebuild necessary. (Rebuild for gfortran 7.3.0 is already done. We build with 7.3.0 and 4.8.5)
This should be pain free except for some packages that do -Wall -Werror.
We get better compilers.
We don’t have to rely on defaults as we build these in conda-forge CI.
We get a linker that supports .tbds . (new linker might work with older compiler, but not sure about packages compiled with -flto)
Make missing license_file an error¶
We merged https://github.com/conda-forge/conda-smithy/pull/1102 in the feedstock
(Isuru) - It’s illegal to not package the license file in most licenses, so we should strictly enforce this.
1268 feedstocks with no license files (some may not require a license file)
(Isuru) - PR to conda-smithy was to enforce this for GPL, BSD, MIT, Apache only
(Scopatz) Reach out to NumFocus to figure out legal ramifications of not including licenses in files.
(John K.) Three hard problems regarding licensing
not all packages even include a license file
people in the community are resistant to packaging license files
we already have packges in our ecosystem that do not have
Your agenda items¶
(Eric) Scheduling Anaconda <> conda-forge sync on anaconda.org requirements gathering
(Sophia) New conda environments. What do you like? What do you hate? What are we still missing? Workflows, Condafile, CLI
(Filipe) A closer collaboration with other packaging communities would be awesome. I guess that we don’t have a good means for that kind of communication at the moment. Gitter is high volume, our mailing list never cought on, and an email thread may get stale quickly or we may drop people accidentally. TL;DR maybe we should invite them to our meeting call. Filipe to ping Bjorn – maybe we can get both Bjorn and debian on a dev meeting
(Eric) Email out to see if we can get more engagement on regular dev meetings.
Notes from todays dev meeting
Check in on previous action items¶
Copy previous action items from last meeting agenda.
[ ] (Filipe) Progress on setting up a self-hosted blog
Medium seems to be generally downvoted
Host your own blog seems to be generally positive
Can we mimic what Dask does for their dev blog? https://github.com/dask/dask-blog
[ ] (Needs Owner) Searching on our website is a little difficult
[ ] (Filipe, Anthony) Improve docs on releasing conda-smithy. Currently says “use rever”. Would be good to fill out more info there for those of us that are unfamiliar with rever.
[x] (Filipe, Anthony) conda-smithy release.
2 meetings ago¶
[ ] John K: Create, or link, google doc with survey questions
[x] Anthony and Filipe: conda smithy release for linux-armv7l
3 meetings ago¶
Unresolved action items in this heading will be moved to issues on conda-forge.github.io
[x] Mike S.: pypy Next steps: Say yes / no to the spec, point out potential pitfalls, give it back to (Matti?) and say here’s the work that needs to be done.
(Eric) Opened up issue: https://github.com/conda-forge/conda-forge.github.io/issues/867
[x] Marius: Open issue on conda-forge.github.io noting work done on the kubernetes cluster. Did some kubernetes work at scipy.
(Eric) Opened up issue: https://github.com/conda-forge/conda-forge.github.io/issues/868
[x] Marius: reach out to internal IT to clean up some Zoom hiccups. Still in progress 2019-09-04
New Action items¶
Copy new action items to next meetings agenda so we can check in. Make sure each action item is assigned to someone or it will likely not get done.
[ ] (Eric) Email out to see if we can get more engagement on regular dev meetings.
[ ] (Sophia) Set up meeting to talk about Condafile stuff.
[ ] (CJ) write blog post on bot work and compiler migration
[ ] (Filipe) Ping Bjorn to try and get Debian community more involved with conda-forge
[ ] (Eric) Scheduling Anaconda <> conda-forge sync on anaconda.org requirements gathering
[ ] (Anthony) Reach out to NumFocus to figure out legal ramifications of not including licenses in files.