2021-08-04 Conda Community Meeting
Attendees
Name | Initials | Affiliation | GH Username |
---|
Jaime RG | JRG | Quansight | @jaimergp |
Cheng H. Lee | CHL | Anaconda | @chenghlee |
Marcel Bargull | MB | Bioconda/cf | @mbargull |
John lee | JL | Quansight | @leej3 |
Sebastien Awwad | SA | Anaconda | @awwad |
Filipe Fernandes | FF | conda-forge | @ocefpaf |
matthew becker | MRB | conda-forge | @beckermr |
Michael Sarahan | MCS | conda-forge | @msarahan |
| | | |
| | | |
Introductions
Announcements
Standing Items
- Conda Community website mockups
- Outreach to invite more organizations to join this meeting
New Agenda Items
- Twitter account claim ongoing
- Conda security issues
- Conda CI issues found and CI Docker images now built in-place
- GitHub repo improvements incoming:
- CEP 2 - Plugin architecture for Conda merged (https://github.com/conda/ceps/pull/1)
- CEP <--> Conda community governance?
- (MRB) asking people to go emeritus
- we have quite a few folks who have not been attending meetings
- our governance allows for us to ask them to go emeritus after 6 months and if they do not respond in a week, we can move them
- this is never permanent (people can move themselves back at any time)
- this only serves to lower voting quorum thresholds so that the governance can function
- this will be the first time we are using this policy and so I suggest the following
- we send people a very polite note pointing out the policy
- we give them a grace period of 2 months to attend a meeting (roughly 4-5 chances) or be active in some way
- if we hear nothing, we move them to emeritus
Outstanding Items From the Previous Meeting
Active Votes
Subteam Updates
Open PRs
Discussion
Action items
- conda security issue reporting:
- Check membership of conda-security@anaconda.com
- Determine who should be in the list of folks notified in the case of security issues for conda (this group? fewer?)
- Create a mailing list for that group.
- Update readmes in conda repos and Anaconda issues repo to point to the mailing list for security issues.
- Update issue templates in the conda and Anaconda issues repos to emphasize using the mailing list for security issues instead of posting there.
- Post a policy on keeping this mailing list up to date.
- Consider forwarding conda-security@anaconda.com to the new list.
- Update any documentation pointing to conda-security@anaconda.com to point to the new list.
Last meeting points