2020-12-15 Conda Community Meeting

Attendees

Name	Initials	Affiliation	Username

Michael Grant	mcg	Anaconda	mcg1969
Crystal Soja	CAS	Anaconda	@csoja
Filipe Fernandes	FF	conda-forge
Matthew Becker	MRB	conda-forge	@beckermr
Marcel Bargull	MB	Bioconda/conda-forge	@mbargull
Christopher "CJ" Wright	CJ	Lab49	@cj-wright
Connor Martin	CJM	Anaconda	@cjmartian
Cheng H. Lee	CHL	Anaconda	@chenghlee
Michael Sarahan	MCS	RStudio	@msarahan

(FF) 5K on conda messaging granted from NumFocus
- Cheng, Marcelo to work on it.

Anaconda: Organizational-level CLA
- No current updates.
- Existing CLA: consider updating to clarify a real name is required

Dropping Python 2 support in conda, conda-build in base environment
- https://github.com/conda/conda/issues/10180
- https://github.com/conda/conda-build/issues/4024
- Decision on Python 3.6 vs 3.7? (3.7: UTF-8 by default; data classes)
- (MG, CS): In favor of conda on 3.6, conda-build on 3.7
- (MB) concern raised about lag in conda development if significant 3.x refactoring is done
- (MB) concern about noarch <-> arch upgrade process, raise issue if a shadowed update is available
- (MB) miniconda 4.5.4 last Py3.6 installer
- (MS) separate CLI to make such decisions easier; longer term project.
- (CHL) staying with 3.6 in 2021 unless something else comes up.
Should we have a permanent resource (e.g., blog post) saying why users should upgrade? (Probably yes)
Who else should we invite to this meeting?
- Intel
- IBM (POWER, RedHat -> containers)
- Pangeo
- CZI
- HPC centers
- Tensorflow, Pytorch, etc.
- Others, as needed for specific topics