├── emeritus.csv ├── meetings ├── agenda_template.md └── archive │ ├── 20210331_agenda_and_minutes.md │ ├── 20210623_agenda_and_minutes.md │ ├── 20210525_agenda_and_minutes.md │ ├── 20210721_agenda_and_minutes.md │ ├── 20210707_agenda_and_minutes.md │ ├── 20201215_agenda_and_minutes.md │ ├── 20210428_agenda_and_minutes.md │ ├── 20210126_agenda_and_minutes.md │ ├── 20210112_agenda_and_minutes.md │ ├── 20210317_agenda_and_minutes.md │ ├── 20210414_agenda_and_minutes.md │ ├── 20210303_agenda_and_minutes.md │ ├── 20210511_agenda_and_minutes.md │ ├── 20200824_agenda_and_minutes.md │ ├── 20201020_agenda_and_minutes.md │ ├── 20201102_agenda_and_minutes.md │ ├── 20200721_agenda_and_minutes.md │ ├── 20201117_agenda_and_minutes.md │ ├── 20201201_agenda_and_minutes.md │ ├── 20200908_agenda_and_minutes.md │ ├── 20200922_agenda_and_minutes.md │ └── 20201006_agenda_and_minutes.md ├── core.csv ├── LICENSE └── README.md /emeritus.csv: -------------------------------------------------------------------------------- 1 | github_username,email,name 2 | -------------------------------------------------------------------------------- /meetings/agenda_template.md: -------------------------------------------------------------------------------- 1 | # 2020-08-24 conda community meeting 2 | 3 | **** 4 | 5 | [Hangout link](https://meet.google.com/uje-pdns-hch) 6 | 7 | [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-08-25/09:00/b/Conda%20community%20meeting) 8 | 9 | [last weeks meeting]() None! 10 | 11 | ## Attendees 12 | 13 | * names 14 | 15 | ## Agenda 16 | 17 | * Welcome 18 | * Acceptance of previous week's agenda/minutes 19 | * New order of business 20 | 21 | 22 | ### Standing items 23 | - [ ] Item 24 | * [ ] SubItem 25 | ### New Agenda Items 26 | - [ ] Item 27 | * [ ] SubItem 28 | ### Active votes 29 | 30 | ### Subteam updates 31 | 32 | #### Open PRs 33 | 34 | ## Discussion 35 | 36 | ## Previous Action Items 37 | Copy previous action items from last meeting agenda. 38 | 39 | ### This meeting 40 | 41 | ### Last meeting 42 | 43 | ### 2 meetings ago 44 | 45 | ### 3 meetings ago 46 | 47 | ### Move to Issue Tracker 48 | 49 | -------------------------------------------------------------------------------- /core.csv: -------------------------------------------------------------------------------- 1 | github_username,email,name 2 | scopatz,scopatz@gmail.com,Anthony Scopatz 3 | xhochy,mail@uwekorn.com,Uwe Korn 4 | cj-wright,cjwright4242@gmail.com,Christopher J. 'CJ' Wright 5 | kkraus14,keith.j.kraus@gmail.com,Keith Kraus 6 | mariusvniekerk,marius.v.niekerk@gmail.com,Marius van Niekerk 7 | cjmartian,connormartin7@gmail.com,Connor Martin 8 | dharhas,dharhas@gmail.com, Dharhas Pothina 9 | goanpeca,goanpeca@gmail.com, Gonzalo Peña-Castellanos 10 | angloyna,angela.gloyna@gmail.com,Angela Gloyna 11 | teoliphant,teoliphant@gmail.com,Travis Oliphant 12 | chenghlee,clee@anaconda.com,Cheng H. Lee 13 | mcg1969,mgrant@anaconda.com,Michael Grant 14 | ocefpaf,ocefpaf@gmail.com,Filipe Fernandes 15 | ericdill,ericdill@pm.me,Eric Dill 16 | raydouglass,ray@raydouglass.com,Ray Douglass 17 | marcelotrevisani,marceloduartetrevisani@gmail.com, Marcelo Duarte Trevisani 18 | sodre,patrick@zero-ae.com,Patrick Sodré 19 | minrk,benjaminrk@gmail.com,Min Ragan-Kelley 20 | jjhelmus,jjhelmus@gmail.com,Jonathan Helmus 21 | prusse-martin,prusse.martin@gmail.com,Martin Prüsse 22 | msarahan,msarahan@gmail.com,Michael Sarahan 23 | csoja,csoja@anaconda.com,Crystal Soja 24 | awwad,sebastien.awwad@gmail.com,Sebastien Awwad 25 | myancy-anaconda,myancy@anaconda.com,Megan Yancy 26 | mbargull,marcel.bargull@udo.edu,Marcel Bargull 27 | jakirkham,jakirkham@gmail.com,John Kirkham 28 | beckermr,becker.mr@gmail.com,Matthew R. Becker 29 | -------------------------------------------------------------------------------- /meetings/archive/20210331_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-03-31 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-03-31/12:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | Username | 11 | | --------------- | -------- |------------ | ----------- | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | Filipe F. | FF | conda-forge | @ocefpaf | 14 | | John Lee | JL | Quansight | | 15 | | Travis Oliphant | TEO. | OpenTeams | @teoliphant | 16 | | Fabio Pliger | FP | Anaconda | @fpliger | 17 | | Sebastien Awwad | SA | Anaconda | @awwad | 18 | | Daniel Bast | DB | Anaconda | @dbast | 19 | 20 | 21 | ## Agenda 22 | 23 | * Welcome 24 | 25 | 26 | ### Announcements 27 | 28 | * (Anaconda) conda 4.10.0 now available on conda-canary channel; expected release to defaults on 2021-04-05. 29 | * Changelog: https://github.com/conda/conda/blob/4.10.0/CHANGELOG.md 30 | * (Anaconda) Expect Individual Edition 2021.04 release in next few weeks 31 | * Submitted letter of intent to CZI: sponsor mamba development 32 | 33 | 34 | ### Standing Items 35 | 36 | * Conda Community website mockups 37 | * Outreach to invite more organizations to join this meeting 38 | 39 | 40 | ### New Agenda Items 41 | 42 | * Update conda-package-handling: 43 | * Fix bug in static libarchive that broke some CI 44 | * (Anaconda) Planning on updating Linux compilers in defaults 45 | * Aiming for GCC 10.x on all architectures 46 | * Aiming to remove `conda`, `cos7` from platform triplet --- this has caused issues 47 | * Will work with conda-forge to coordinate our compiler stategies 48 | * Resurrecting community support for 32-bit ARM (berryconda) 49 | 50 | 51 | ### Outstanding Items From the Previous Meeting 52 | 53 | 54 | ### Active Votes 55 | 56 | 57 | ### Subteam Updates 58 | 59 | 60 | ### Open PRs 61 | 62 | 63 | ## Discussion 64 | 65 | 66 | ## Action items 67 | 68 | 69 | ## Last meeting points (2020-01-26) -------------------------------------------------------------------------------- /meetings/archive/20210623_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-06-23 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-06-09/12:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | GH Username | 11 | | ------------------ | -------- |-------------- | --------------- | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | Jaime Rodríguez-G. | JRG | Quansight | @jaimergp | 14 | | John Lee | JL | Quansight | @leej3 | 15 | | Filipe Fernandes | FF | conda-forge | @ocefpaf | 16 | | Sebastien Awwad | SA | Anaconda | @awwad | 17 | | | | | | 18 | 19 | 20 | 21 | ### Introductions 22 | 23 | * Jaime Rodríguez-G. (Quantsight) 24 | 25 | 26 | ### Announcements 27 | 28 | * conda 4.10.2 roadmap items complete; should be tagged today and package released towards end-of-the-week 29 | * Putting together [Packaging Con](https://packaging-con.org) (2-day virtual conference; beginning of November) 30 | 31 | 32 | ### Standing Items 33 | 34 | * Conda Community website mockups 35 | * Confirmed Anaconda owns the conda.org domain 36 | * https://github.com/conda-incubator/assets/issues/2#issuecomment-752871352 - at least get a GH page setup 37 | * Outreach to invite more organizations to join this meeting 38 | * Anaconda has invited Intel, IBM 39 | 40 | 41 | ### New Agenda Items 42 | 43 | * Robotics + conda packages 44 | * [RoboStack](https://github.com/RoboStack) 45 | * OSRF + Microsoft: ROS as conda packages for Windows 46 | * Plugins + conda packages 47 | * FreeCAD, QGIS: exploring plug-in manager based on libmamba 48 | * https://forum.freecadweb.org/viewtopic.php?style=3&f=42&t=58156&sid=d021658f134cfaf101896af54fb2c275 49 | * https://github.com/qgis/QGIS-Enhancement-Proposals/issues/179 50 | * Other tools may benefit; e.g., 51 | * ChimeraX; currently handle deps with custom wheels: https://cxtoolshed.rbvi.ucsf.edu/ 52 | * https://www.ccp4.ac.uk/ 53 | * https://www.phenix-online.org/ 54 | * Future of the conda community and these calls 55 | 56 | 57 | ### Outstanding Items From the Previous Meeting 58 | 59 | 60 | ### Active Votes 61 | 62 | 63 | ### Subteam Updates 64 | 65 | 66 | ### Open PRs 67 | 68 | 69 | ## Discussion 70 | 71 | 72 | ## Action items 73 | 74 | 75 | ## Last meeting points (2020-05-25) -------------------------------------------------------------------------------- /meetings/archive/20210525_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-05-25 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-05-25/12:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | GH Username | 11 | | ------------------ | -------- |-------------- | --------------- | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | matthew becker | MRB | conda-forge | @beckermr | 14 | | Sebastien Awwad | SA | Anaconda | @awwad | 15 | | Marcel Bargull | MB | Bioconda/cf | @mbargull | 16 | 17 | 18 | ### Introductions 19 | 20 | 21 | ### Announcements 22 | 23 | * [AnacondaCON 2021](https://anacondacon.io/): 9 Jun, all virtual. 24 | * conda 4.10.2 delayed by ~1 week 25 | 26 | 27 | ### Standing Items 28 | 29 | * Conda Community website mockups 30 | * Outreach to invite more organizations to join this meeting 31 | 32 | 33 | ### New Agenda Items 34 | 35 | * Planning conda-build release 36 | * All patches applied as binary; causes issues on Windows & how patch detection works (or doesn't) 37 | * https://github.com/conda/conda-build/issues/1973 38 | * https://github.com/conda/conda-build/pull/2035 39 | * Conda UTF-16 handling: 40 | * https://github.com/conda/conda/pull/9946 41 | * https://github.com/conda-forge/conda-feedstock/blob/master/recipe/gh9946_utf_16_replacement.patch 42 | * `sys.exit(...)` when invoking conda-build via API, rather than CLI. (Should raise Exceptions instead; developer quality-of-life improvement) 43 | 44 | * Update to spec (conda, conda-build) 45 | * Support for optional deps 46 | 47 | * Quetz: plans for authentication support 48 | * 5.0+ planning: authn schemes for package servers 49 | * Anaconda.org currently uses token-in-URL scheme 50 | * mamba: HTTP basic auth, anaconda.org token scheme 51 | * User requests for other schemes: 52 | * `~/.netrc` 53 | * RSA SecurID: https://github.com/conda/conda/pull/10667 54 | * (FP) Share APIs, not necessarily code, between mamba & conda for authn 55 | 56 | * (CJ) Version 4 symbol database released! 57 | 58 | * Packaging con --- more info next week 59 | 60 | 61 | ### Outstanding Items From the Previous Meeting 62 | 63 | 64 | ### Active Votes 65 | 66 | 67 | ### Subteam Updates 68 | 69 | 70 | ### Open PRs 71 | 72 | 73 | ## Discussion 74 | 75 | 76 | ## Action items 77 | 78 | 79 | ## Last meeting points (2020-05-11) -------------------------------------------------------------------------------- /meetings/archive/20210721_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-07-21 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-07-21/12:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | GH Username | 11 | | ------------------ | -------- |-------------- | --------------- | 12 | | Jannis Leidel | JL | Anaconda | @jezdez | 13 | | Matthew Becker | MRB | cf | @beckermr | 14 | | | | | | 15 | | Jaime RG | JRG | Quansight | @jaimergp | 16 | | Sebastien Awwad | SA | Anaconda | @awwad | 17 | | John Lee | JL | Quansight | @leej3 | 18 | | Marcel Bargull | MB | Bioconda/cf | @mbargull | 19 | | | | | | 20 | 21 | ### Introductions 22 | 23 | 24 | ### Announcements 25 | 26 | * 27 | 28 | 29 | ### Standing Items 30 | 31 | * Conda Community website mockups 32 | * JRG: Quansight Labs could not find a suitable applicant for the internship 33 | * JL: Anaconda might tackle this as part of their docs update. It would be in the open to welcome community contributions. 34 | * MRB: Previous plans included a GH Pages site at conda-incubator 35 | * Outreach to invite more organizations to join this meeting 36 | 37 | 38 | ### New Agenda Items 39 | 40 | * Place to store agenda: https://github.com/conda-incubator/governance/tree/master/meetings perhaps 41 | * Centralized help for the community? 42 | * Stale and lock bot going to start being used. Manay of these details could be migrated to a FAQ for the community. Via Github discussions? 43 | * Separating technical issues from user questions is important 44 | * Choosing the appropriate umbrella organization is required. maybe conda? 45 | * Jaime: dual strategy? Forum and more private chat app like slack 46 | * discord? 47 | * We need at least one way though... (for folks to reach the community group? mailing list?) 48 | * we have 6 people on this one: https://groups.google.com/g/conda 49 | * how is the community room on gitter being used? 50 | * Packaging con call for presentations is open: http://packaging-con.org/ 51 | * Adding a tab for open conda positions on our pending community website would be nice. 52 | 53 | ### Outstanding Items From the Previous Meeting 54 | 55 | 56 | ### Active Votes 57 | 58 | 59 | ### Subteam Updates 60 | 61 | 62 | ### Open PRs 63 | 64 | 65 | ## Discussion 66 | * Hiring a senior conda dev :D https://boards.greenhouse.io/anaconda/jobs/3222881 67 | 68 | ## Action items 69 | 70 | 71 | ## Last meeting points 72 | -------------------------------------------------------------------------------- /meetings/archive/20210707_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-07-07 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-07-07/12:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | GH Username | 11 | | ------------------ | -------- |-------------- | --------------- | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | Jannis Leidel | JL | Anaconda | @jezdez | 14 | | Marcel Bargull | MB | Bioconda/cf | @mbargull | 15 | | Filipe Fernandes | FF | conda-forge | @ocefpaf | 16 | | Sebastien Awwad | SA | Anaconda | @awwad | 17 | | Matt B | MRB | cf | @beckermr | 18 | | Jaime RG | JRG | Quansight | @jaimergp | 19 | | John Lee | JL | Quansight | @leej3 | 20 | | Julio Batista | JBS | | @jbsilva | 21 | 22 | 23 | ### Introductions 24 | 25 | * Julio Batista 26 | 27 | 28 | ### Announcements 29 | 30 | * conda 4.10.3 released; available on defaults and conda-forge 31 | * [Conda Enhancement Proposals](https://github.com/conda/ceps) relaunch 32 | * menuinst, pycosat repositories moving to conda org 33 | * Please feel free to ping Jannis or Cheng if another (ContinuumIO/Anaconda) repo needs to be moved 34 | 35 | 36 | ### Standing Items 37 | 38 | * Conda Community website mockups 39 | * Outreach to invite more organizations to join this meeting 40 | 41 | 42 | ### New Agenda Items 43 | 44 | * CEPs: 45 | * Should we apply [governance voting rules](https://github.com/conda-incubator/governance) from? 46 | * Clarify whether which CEPs apply to `conda` the application and which apply to `conda` the ecosystem 47 | * (TODO) CEP for artifact signature verification (SA, next two weeks) 48 | * RHEL 8 OpenSSL 49 | * defaults and conda-forge OpenSSL packages do include RHEL OpenSSL patches, which causes problems with system applications 50 | * E.g., https://github.com/conda/conda/issues/10241 51 | * Broader discussion --- how do we deal with: 52 | * compatiblity with (patched) system libraries; 53 | * system executables picking up conda libraries 54 | * (TODO) convo on if this is going to be fixed on RedHat side, etc. (CW? JL?) 55 | 56 | 57 | ### Outstanding Items From the Previous Meeting 58 | 59 | 60 | ### Active Votes 61 | 62 | 63 | ### Subteam Updates 64 | 65 | 66 | ### Open PRs 67 | 68 | 69 | ## Discussion 70 | 71 | 72 | ## Action items 73 | 74 | 75 | ## Last meeting points -------------------------------------------------------------------------------- /meetings/archive/20201215_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2020-12-15 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-12-01/09:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | ## Attendees 8 | 9 | | Name | Initials | Affiliation | Username | 10 | | ---- | -------- |------------ | -------- | 11 | | | | | | 12 | | Michael Grant | mcg | Anaconda | mcg1969 | 13 | | Crystal Soja | CAS | Anaconda | @csoja | 14 | | Filipe Fernandes | FF | conda-forge | | @ocefpaf | 15 | | Matthew Becker | MRB | conda-forge | @beckermr | 16 | | Marcel Bargull | MB | Bioconda/conda-forge | @mbargull | 17 | | Christopher "CJ" Wright | CJ | Lab49 | @cj-wright | 18 | | Connor Martin | CJM | Anaconda | @cjmartian | 19 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 20 | | Michael Sarahan | MCS | RStudio | @msarahan | 21 | 22 | 23 | ## Agenda 24 | 25 | * Welcome 26 | * Is there a meeting happening on the 29th? 27 | * Voice vote to cancel the 29th. 28 | * Host for next meeting? 29 | 30 | ### Announcements 31 | * (FF) 5K on conda messaging granted from NumFocus 32 | * Cheng, Marcelo to work on it. 33 | 34 | ### Standing Items 35 | * Anaconda: Organizational-level CLA 36 | * No current updates. 37 | * Existing CLA: consider updating to clarify a real name is required 38 | 39 | 40 | ### New Agenda Items 41 | 42 | * Dropping Python 2 support in conda, conda-build in base environment 43 | * https://github.com/conda/conda/issues/10180 44 | * https://github.com/conda/conda-build/issues/4024 45 | * Decision on Python 3.6 vs 3.7? (3.7: UTF-8 by default; data classes) 46 | * (MG, CS): In favor of conda on 3.6, conda-build on 3.7 47 | * (MB) concern raised about lag in conda development if significant 3.x refactoring is done 48 | * (MB) concern about noarch <-> arch upgrade process, raise issue if a shadowed update is available 49 | * (MB) miniconda 4.5.4 last Py3.6 installer 50 | * (MS) separate CLI to make such decisions easier; longer term project. 51 | * (CHL) staying with 3.6 in 2021 unless something else comes up. 52 | * Should we have a permanent resource (e.g., blog post) saying why users should upgrade? (Probably yes) 53 | * Who else should we invite to this meeting? 54 | * Intel 55 | * IBM (POWER, RedHat -> containers) 56 | * Pangeo 57 | * CZI 58 | * HPC centers 59 | * Tensorflow, Pytorch, etc. 60 | * Others, as needed for specific topics 61 | 62 | 63 | ### Outstanding Items From the Previous Meeting 64 | 65 | * N/A 66 | 67 | ### Active Votes 68 | 69 | 70 | ### Subteam Updates 71 | 72 | 73 | #### Open PRs 74 | 75 | * N/A 76 | 77 | ## Discussion 78 | 79 | 80 | ## Action items 81 | 82 | ## Last meeting points (2020-12-01) 83 | -------------------------------------------------------------------------------- /meetings/archive/20210428_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-04-28 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-04-28/12:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | GH Username | 11 | | ------------------ | -------- |-------------- | --------------- | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | Marcel Bargull | MB | Bioconda/cf | @mbargull | 14 | | Wolf Vollprecht | WV | QuantStack/cf | @wolfv | 15 | | Adrien Delsalle | AD | QuantStack | @adriendelsalle | 16 | | Matthew Becker | MRB | cf | @beckermr | 17 | | Marius van Niekerk | MvN | cf | @mariusvniekerk | 18 | | Sebastien Awwad | SA | Anaconda | @awwad | 19 | | John Lee | JL | Quansight | @leej3 | 20 | 21 | 22 | ### Introductions 23 | 24 | 25 | ### Announcements 26 | 27 | * (CJ) Citadel is hiring! (including a position on CJ's team, contact CJ for details) 28 | * Quantstack is hiring! 29 | * (CHL) Anaconda is hiring! 30 | * Quansight is hiring! 31 | 32 | 33 | ### Standing Items 34 | 35 | * Conda Community website mockups 36 | * Outreach to invite more organizations to join this meeting 37 | 38 | 39 | ### New Agenda Items 40 | 41 | * (CJ) NumFocus putting together working group to develop an "OSS for corporations" guide book. -- contact CJ if you want contribute. 42 | * [conda 5.0 planning](https://hackmd.io/fBdxnoMfTZu9_DKQW9myvA) 43 | * Planning release around Q3/Q4 2021 44 | * [WV / AD] TUF questions for conda-content-trust 45 | * Implementation based on TUF but does not directly implement spec (e.g., no `key_id`, distinct metadata protection, multi-channel) 46 | * Need to consider multiple repositories (channels) and mutiple authorities 47 | * Provide access to data for third-party developers to test against (SA) 48 | * Provide spec for repodata information 49 | * Shipped conda environments without needing conda's shell initialization functions? 50 | * Typically works, unless you need something in the activation scripts 51 | * Users can set `$PATH` as appropriate or use absolute paths 52 | * Refactor `conda-index` out of `conda-build` 53 | * Deprecate `conda-verify` -> merge into `conda-build` post-build checks 54 | * Scheduling: keep at every 2 weeks at current time, or switch? 55 | * Consensus is to keept meetings every two weeks until we hear otherwise. 56 | 57 | 58 | ### Outstanding Items From the Previous Meeting 59 | 60 | 61 | ### Active Votes 62 | 63 | 64 | ### Subteam Updates 65 | 66 | 67 | ### Open PRs 68 | 69 | 70 | ## Discussion 71 | 72 | 73 | ## Action items 74 | 75 | 76 | ## Last meeting points (2020-01-26) -------------------------------------------------------------------------------- /meetings/archive/20210126_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # DRAFT - 2021-01-26 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-01-26/09:00/b/Conda%20Community%20Meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | ## Attendees 8 | 9 | | Name | Initials | Affiliation | Username | 10 | | ---- | -------- |------------ | -------- | 11 | | CJ Wright | CJ | Lab49 | @cj-wright | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | Ralf Gommers | RG | Quansight | @rgommers | 14 | | Amy Williams | AW | Anaconda | @adwilliams81 | 15 | | Eric Dill | ED | DTN | @ericdill | 16 | | Michael Grant | MG | Anaconda | @mcg1969 | 17 | | | | | | 18 | 19 | 20 | ## Agenda 21 | 22 | * Welcome 23 | 24 | 25 | ### Announcements 26 | _None_ 27 | 28 | 29 | ### Standing Items 30 | * Anaconda: Organizational-level CLA 31 | * Anaconda legal team contacted; moving forward with Feb. delivery 32 | * Conda Community website mockups 33 | * https://github.com/conda-incubator/assets/issues/2 34 | * Blog post regarding why users should update to Python 3 35 | * Outreach to invite more organizations to join this meeting 36 | 37 | 38 | ### New Agenda Items 39 | * Revisit the meeting schedule. Should we change it to accomodate more people? 40 | * Maybe a new doodle? -> (CHL) Will put schedule a poll and announce via Slack, email 41 | * Ideally we should also ask conda-forge to be bi-weekly so we can use the same date and time allowing people attending both to reverse the slot for conda-community and conda-forge. 42 | * (CHL) Reach out to Intel, IBM to join community calls; (PW) Apple, Netflix; (RG) Pytorch 43 | 44 | * Python Symbol table of conda-forge packages 45 | * https://github.com/symbol-management/cf-symbol-table 46 | 47 | 48 | ### Outstanding Items From the Previous Meeting 49 | 50 | 51 | ### Active Votes 52 | 53 | 54 | ### Subteam Updates 55 | 56 | 57 | #### Open PRs 58 | 59 | * N/A 60 | 61 | ## Discussion 62 | 63 | ## Action items 64 | * Anaconda: update on organizational-level CLA 65 | 66 | ## Last meeting points (2020-1-11) 67 | * Conda Community website mockups 68 | * Dropping Python 2 support in conda, conda-build in base environment 69 | * https://github.com/conda/conda/issues/10180 70 | * https://github.com/conda/conda-build/issues/4024 71 | * Should we have a permanent resource (e.g., blog post) saying why users should upgrade? 72 | * Who else should we invite to this meeting? 73 | * Intel 74 | * IBM (POWER, RedHat -> containers) 75 | * Pangeo 76 | * CZI 77 | * [x] MRB: HPC centers 78 | * Tensorflow, PyTorch, etc. 79 | * Others, as needed for specific topics 80 | -------------------------------------------------------------------------------- /meetings/archive/20210112_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-01-12 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-12-01/09:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | ## Attendees 8 | 9 | | Name | Initials | Affiliation | Username | 10 | | ---- | -------- |------------ | -------- | 11 | | Marius van Niekerk | MvN | Flatiron Health | mariusvniekerk | 12 | |Isabela Presedo-Floyd | IRPF | Quansight Labs | isabela-pf | 13 | | Megan Yancy | MCY | Anaconda | myancy-anaconda | 14 | | Eric Dill | ED | DTN | ericdill | 15 | | Connor Martin | CJM | anaconda | cjmartian | 16 | | Matthew Becker | MRB | conda-forge | beckermr | 17 | | Uwe Korn | UK | conda-forge | xhochy | 18 | | Crystal Soja | CS | anaconda | csoja | 19 | | Michael Grant | MG | anaconda | mcg1969 | 20 | | Keith Kraus | KK | NVIDIA | kkraus14 | 21 | | Michael Sarahan | MCS | RStudio | msarahan | 22 | 23 | 24 | ## Agenda 25 | 26 | * Welcome 27 | * Host for next meeting? - MCY 28 | 29 | ### Announcements 30 | * 31 | 32 | ### Standing Items 33 | * Anaconda: Organizational-level CLA 34 | 35 | ### New Agenda Items 36 | * Conda community website mockups are up for feedback. 37 | * https://github.com/conda-incubator/assets/issues/2 38 | * Please provide feedback! 39 | * Question on Trademarks 40 | * Vote to come later 41 | 42 | ### Outstanding Items From the Previous Meeting 43 | 44 | * Blog post regarding why users should update to Python 3 45 | * Outreach to invite more organizations to join this meeting 46 | 47 | ### Active Votes 48 | 49 | 50 | ### Subteam Updates 51 | 52 | 53 | #### Open PRs 54 | 55 | * N/A 56 | 57 | ## Discussion 58 | 59 | ## Action items 60 | * Anaconda: update on organizational-level CLA 61 | ## Last meeting points (2020-12-15) 62 | 63 | * Dropping Python 2 support in conda, conda-build in base environment 64 | * https://github.com/conda/conda/issues/10180 65 | * https://github.com/conda/conda-build/issues/4024 66 | * Decision on Python 3.6 vs 3.7? (3.7: UTF-8 by default; data classes) 67 | * (MG, CS): In favor of conda on 3.6, conda-build on 3.7 68 | * (MB) concern raised about lag in conda development if significant 3.x refactoring is done 69 | * (MB) concern about noarch <-> arch upgrade process, raise issue if a shadowed update is available 70 | * (MB) miniconda 4.5.4 last Py3.6 installer 71 | * (MS) separate CLI to make such decisions easier; longer term project. 72 | * (CHL) staying with 3.6 in 2021 unless something else comes up. 73 | * Should we have a permanent resource (e.g., blog post) saying why users should upgrade? (Probably yes) 74 | * Who else should we invite to this meeting? 75 | * Intel 76 | * IBM (POWER, RedHat -> containers) 77 | * Pangeo 78 | * CZI 79 | * [x] MRB: HPC centers 80 | * Tensorflow, Pytorch, etc. 81 | * Others, as needed for specific topics 82 | -------------------------------------------------------------------------------- /meetings/archive/20210317_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-03-17 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-03-17/11:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | Username | 11 | | ------------ | -------- |------------ | ---------- | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | CJ Wright | CJ | Lab49 | @CJ-Wright | 14 | 15 | 16 | ## Agenda 17 | 18 | * Welcome 19 | 20 | 21 | ### Announcements 22 | 23 | * Apologies for the daylight savings scheduling oops. Will move 1 hour ahead for next meeting. 24 | * Berryconda (support for 32-bit ARMv7l) looking for a new maintainer: https://github.com/jjhelmus/berryconda/issues/83 25 | 26 | 27 | 28 | ### Standing Items 29 | 30 | * Conda Community website mockups 31 | * Outreach to invite more organizations to join this meeting 32 | 33 | 34 | ### New Agenda Items 35 | 36 | * Upcoming conda 4.10.0 release (planned around end of March, early April) 37 | * Formally dropping support for Python 2.7, Python < 3.6 (_in the base environment_) 38 | * https://github.com/conda/conda/issues/10180 39 | * conda-forge, defaults have not supported Py2.7 since 4.8.3 (Mar 2020), Py3.5 since 4.5.11 (Aug 2018) 40 | * This only impacts the base environment. Support for non-base Py2.7, < 3.6 envs will continue indefinitely. 41 | * Introducing support for artifact verification 42 | * First release: sign and verifies metadata in repodata.json 43 | * Currently only available as _pilot_ program to subset of Anaconda customers 44 | * Mid- to long-term goals include: 45 | * Making signed metadata on defaults 46 | * Allowing channels like conda-forge to sign packages & metadata 47 | * Soliciting community input on signature specifications, functional requirements, etc. 48 | * Link to Sebastian's talk: ... 49 | * Conda-content-trust: 50 | * Other fixes: https://github.com/conda/conda/milestone/47 51 | * New platforms being added to defaults (repo.anaconda.com) 52 | * linux-aarch64: targeting "server-class" ARM cores (e.g., Neoverse), but should (mostly) work with other 64-bit ARM CPUs (e.g., Raspi3/4) 53 | * linux-s390x: support for RHEL, Ubuntu, SLES on z14, z15 54 | * Anaconda Individual Edition installers available starting 2020.04 55 | * AST & symbol inspection: 56 | * https://cf-ast-symbol-table.web.cern.ch/api/v2/symbols/ 57 | * https://cf-ast-symbol-table.web.cern.ch/api/v2/symbol_table/ 58 | * https://github.com/symbol-management/api-match-audit 59 | * Chris Burr: used pwntools to pull out C symbols 60 | * Working on adding relative imports; will require data model change 61 | 62 | 63 | ### Outstanding Items From the Previous Meeting 64 | 65 | 66 | ### Active Votes 67 | 68 | 69 | ### Subteam Updates 70 | 71 | 72 | ### Open PRs 73 | 74 | 75 | ## Discussion 76 | 77 | 78 | ## Action items 79 | 80 | 81 | ## Last meeting points (2020-01-26) -------------------------------------------------------------------------------- /meetings/archive/20210414_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-04-14 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-04-14/12:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | Username | 11 | | ------------------ | -------- |------------ | --------------- | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | Marcel Bargull | MB | Bioconda/cf | @mbargull | 14 | | Matthew Becker | MRB | cf | @beckermr | 15 | | John Lee | JL | Quansight | @leej3 | 16 | | Marius van Niekerk | MvN | cf | @mariusvniekerk | 17 | | John Kirkham | JK | NVIDIA/cf | @jakirkham | 18 | | Keith Kraus | KK | NVIDIA/cf | @kkraus14 | 19 | 20 | ## Agenda 21 | 22 | * Welcome 23 | 24 | 25 | ### Announcements 26 | 27 | * (Anaconda) conda-package-handling 1.7.3 now available on defaults 28 | * (Anaconda) conda 4.10.1 now available on conda-canary channel; expected release to defaults on 2021-04-15. 29 | * Changelog: https://github.com/conda/conda/blob/4.10.1/CHANGELOG.md 30 | 31 | 32 | ### Standing Items 33 | 34 | * Conda Community website mockups 35 | * Outreach to invite more organizations to join this meeting 36 | 37 | 38 | ### New Agenda Items 39 | 40 | * (Anaconda) Bumping OS levels required for packages on defaults 41 | * Linux: CentOS 7 or newer; more specifically GNU libc >=2.17 42 | * OS X/macOS: 10.13 or newer 43 | * win-32 deprecated soon...ish. 44 | * Needed to support, e.g., MKL >=2020, PyTorch 1.8, etc. 45 | * Consider reserving `__` prefix for virutal packages. 46 | * Nvidia: virtual packages for drivers 47 | * Virtual packages as plugins, possibly defined in ``.condarc`? 48 | * https://github.com/conda/conda/issues/10131 49 | * Think through how to support CPU- or other hardware-specific features 50 | * Want to avoid subdir explosion 51 | * Virtual packages probably a cleaner approach 52 | * Library for detecting CPU features 53 | * https://github.com/workhorsy/py-cpuinfo 54 | * "source" subdir, caching sources 55 | * Need to preserve the source archives (e.g., bzip2, ICU) 56 | * bioconda has cache of tarballs via Galaxy project 57 | * updates conda-build to fallback 58 | * Ways to pass arguments to activation scripts 59 | * E.g., munge `*FLAGS` to set `-mcpu=`, `-march=`; `-std=cxxNN`; Windows SDK version 60 | * Should be exposed as machine- and human-readable metadata 61 | * Design doc for 5.0 (action item for CHL) 62 | * What we would like to see for next-gen conda metadata 63 | * What we would like to see for next-gen conda recipe 64 | 65 | 66 | ### Outstanding Items From the Previous Meeting 67 | 68 | 69 | ### Active Votes 70 | 71 | 72 | ### Subteam Updates 73 | 74 | 75 | ### Open PRs 76 | 77 | 78 | ## Discussion 79 | 80 | 81 | ## Action items 82 | 83 | * CHL: start design doc for 5.0 84 | 85 | 86 | ## Last meeting points (2020-01-26) -------------------------------------------------------------------------------- /meetings/archive/20210303_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-03-03 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-03-03/11:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | Username | 11 | | ------------ | -------- |------------ | ---------- | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | Filipe | FF | conda-forge | @ocefpaf | 14 | | | | | | 15 | 16 | 17 | ## Agenda 18 | 19 | * Welcome 20 | 21 | 22 | ### Announcements 23 | 24 | * Anaconda: Organizational-level CLA 25 | * Anaconda legal has clarified CLA language to cover both individuals and organizations. 26 | * Currently working with Anaconda IT to update links and PDF e-form. 27 | 28 | 29 | ### Standing Items 30 | 31 | * Conda Community website mockups 32 | * https://github.com/conda-incubator/assets/issues/2 33 | * Outreach to invite more organizations to join this meeting 34 | 35 | 36 | ### New Agenda Items 37 | 38 | * conda: working on new conda messaging feature 39 | * https://github.com/conda/conda/issues/10118 40 | * Allow packagers to include a file that will display a message before installating package into an environment. (Similar to what some maintainers do with pre-link scripts but without executable code) 41 | * Use cases: EULA, deprecation additional installation instructions, etc. 42 | * Funded by NumFOCUS small grant 43 | * Will sync with mamba team to make sure they support that feature 44 | * conda-forge: 45 | * Outreachy to update documentation on bot 46 | * Google season of docs (staged-recipes, recipes); would like someone from Anaconda to review 47 | * micromamba: 48 | * virtual packages (`nvidia-smi` rather loading the DSO) 49 | * config file loading 50 | * Bundling/vendoring of dependencies 51 | * Something to think about as we expand ecosystem (CRAN, NPM, etc.) 52 | * Learning from experiences of Linux distros unbundling packages in pip 53 | * https://github.com/pypa/pip/issues/9677 54 | * conda-forge: unpinned certifi, win-certstore 55 | * https://github.com/mamba-org/mamba/issues/589 56 | * Name squatting attacks against PyPI 57 | * Impacted CuPy 58 | * Will need to hold on to `conda`, `conda-build` names, even if we remove the associated packages 59 | * How do we protect conda ecosystem? (more unique identifiers; namespace separation) 60 | * Source trustworthiness 61 | * Watching for curl, wget, other network access 62 | * Does conda-build have the ability to just fetch sources? 63 | * (CHL) if not, would be a nice feature to have 64 | * (Allow us to perform actual build on isolated systems) 65 | 66 | 67 | ### Outstanding Items From the Previous Meeting 68 | 69 | 70 | ### Active Votes 71 | 72 | 73 | ### Subteam Updates 74 | 75 | 76 | ### Open PRs 77 | 78 | 79 | ## Discussion 80 | 81 | 82 | ## Action items 83 | 84 | * (CHL) Getting conda community 85 | 86 | 87 | ## Last meeting points (2020-01-26) 88 | 89 | * Updated meeting date & time -------------------------------------------------------------------------------- /meetings/archive/20210511_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2021-05-11 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2021-05-11/12:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | 8 | ## Attendees 9 | 10 | | Name | Initials | Affiliation | GH Username | 11 | | ------------------ | -------- |-------------- | --------------- | 12 | | Cheng H. Lee | CHL | Anaconda | @chenghlee | 13 | | Marcel Bargull | MB | Bioconda/cf | @mbargull | 14 | | CJ Wright | CJ | Citadel/cf | @CJ-Wright | 15 | | Sebastien Awwad | SA | Anaconda | @awwad | 16 | 17 | 18 | ### Introductions 19 | * Dan Meador (Anaconda) 20 | 21 | 22 | ### Announcements 23 | 24 | * Anaconda Individual Edition 2021.04 releasing this week. In addition to updates, adds linux-aarch64 (Neoverse N1/N2) and linux-s390x as supported platforms. 25 | * Anaconda (distro & platform) is hiring. 26 | * Citadel (HPC env and pkg management, contact CJ), is hiring. 27 | 28 | 29 | ### Standing Items 30 | 31 | * Conda Community website mockups 32 | * Outreach to invite more organizations to join this meeting 33 | 34 | 35 | ### New Agenda Items 36 | 37 | * Expect conda 4.10.2 release in the next week or two. 38 | * Roadmap: https://github.com/conda/conda/milestone/50 39 | * `conda env create` (snakemake, conda lock) vs `conda create` 40 | * `env` spec files seem preferred (channels, pip, etc.) 41 | * micromamba create reads yaml files 42 | * includes (undocumented) extension that allows platform-specific selection 43 | * (CHL) willing to pull that into conda itself; document in environment schema. 44 | * CentOS (8) EOL 45 | * Anaconda "defaults": supporting CentOS 7 (glibc 2.17) as default target until it hits EOL in 2024. If newer glibc needed to build something, will use older, supported versions of Ubuntu or Debian. 46 | * conda-forge discussion: https://github.com/conda-forge/conda-forge.github.io/issues/1432 47 | * yum requirements, CDTs -> but we can wait till 2024 48 | * consider other community-maintained alternatives like Rocky Linux 49 | * commercial interest in staying on RHEL (or other rpm-based distros) 50 | * adding `__glibc` run constrains 51 | * explicit in recipes; run_exports in compiler, sysroot packages; feature in conda build 52 | * need to consider what manylinux, other HPC centers, other communities (e.g., nix; R) plan to do 53 | * roll our own glibc? Need to consider patches, kernels, etc. 54 | * Thinking through how to handle compatibility with system packages (glibc, X11, etc.) 55 | * `yanked` vs `broken`: ways to remove or hide packages from the ecosystem 56 | * repodata timestamping (or other version management) for reproducibility --- bioconda 57 | 58 | 59 | ### Outstanding Items From the Previous Meeting 60 | 61 | 62 | ### Active Votes 63 | 64 | 65 | ### Subteam Updates 66 | 67 | 68 | ### Open PRs 69 | 70 | 71 | ## Discussion 72 | 73 | 74 | ## Action items 75 | 76 | 77 | ## Last meeting points (2020-05-11) -------------------------------------------------------------------------------- /meetings/archive/20200824_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2020-08-24 conda community meeting 2 | 3 | **** 4 | 5 | [Hangout link](https://meet.google.com/uje-pdns-hch) 6 | 7 | [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-08-25/09:00/b/Conda%20community%20meeting) 8 | 9 | [last weeks meeting]() None! 10 | 11 | ## Attendees 12 | 13 | * Matthew Becker 14 | * Marius van Niekerk 15 | * Cheng Lee 16 | * Hameer Abbasi 17 | * Angela Gloyna 18 | * Filipe Fernandes 19 | * Patrick Sodré 20 | * Raymond Douglass 21 | * Anthony Scopatz 22 | * Sebastien Awwad 23 | * Connor Martin 24 | * Jonathan Helmus 25 | * Gonzalo Peña-Castellanos 26 | 27 | ## Agenda 28 | 29 | * Welcome 30 | * Community meeting, not only core. 31 | * People are free to join/not. 32 | * Projects to invite/add to incubator 33 | * Discuss conda org transition 34 | * [Scopatz] Proposed Steps: 35 | * Figure out GitHub teams for core members 36 | * Move governance repo to conda org 37 | * Move smaller projects to community maintenance 38 | * constructor 39 | * conda-pack 40 | * conda-package-handling 41 | * schema 42 | * others? 43 | * Move conda & conda-build to community maintenance 44 | * Specification Subteam 45 | * Cheng Lee 46 | * Matthew Becker 47 | * Wolf (likely) 48 | * Numfocus fiscal sponsorship 49 | * website (and blog?) 50 | * do we want 51 | * this? (seems like yes) 52 | * how should we communicate to the community? (website duh) 53 | * twitter 54 | * use command line in conda to send out news 55 | * website 56 | * what should we communicate to the community? 57 | * join our slack 58 | * document long-term plans 59 | * outline governance doc 60 | * document how to get involved etc 61 | * publish meeting notes 62 | * list sponsors / contributors 63 | * list of repos 64 | * who to bug 65 | * some text on specs and how it guides the community 66 | 67 | 68 | 69 | ### Standing items 70 | None yet 71 | 72 | 73 | ### Your new agenda items 74 | - [ ] GitHub Teams 75 | * [ ] Public calendar 76 | * [ ] Establish a process for creating and doing admin tasks for repos on the `conda` org on GitHub 77 | * [ ] use a admin-requests repo to make tickets 78 | * [ ] LONG TERM: investigate moving repo management to terraform? Can use terraform cloud + security policies to tightly control application of how teams, repos etc can be made 79 | * [ ] need to talk to Anaconda IT to figure out permissions 80 | * Owners are not public 81 | * [ ] Changes made to Anaconda websites need to be locked down (CI jobs, etc). 82 | * [ ] Community permissions put up docs/pages to `conda.org`. 83 | * [ ] Website/email e-mail to be updated on GitHub org 84 | * [ ] Archive old projects to conda-attic? 85 | * [ ] change CLA bot to be only anaconda repos 86 | * [ ] Trademark and logo clearance from NumFocus 87 | * [ ] Move smaller projects to community maintenance 88 | * [ ] constructor 89 | * [ ] conda-pack 90 | * [ ] conda-package-handling 91 | * [ ] schema 92 | * [ ] conda 93 | * [ ] conda-build 94 | * [ ] build up website content 95 | * see above 96 | 97 | ### Stuff from last week that we didn't get to 98 | 99 | Who is taking these action items? 100 | 101 | * [ ] None yet 102 | 103 | ### Active votes 104 | 105 | ### Subteam updates 106 | 107 | #### Open PRs 108 | 109 | ## Discussion 110 | 111 | ## Check in on previous action items 112 | Copy previous action items from last meeting agenda. 113 | 114 | ### This meeting 115 | 116 | ### Last meeting 117 | 118 | ### 2 meetings ago 119 | 120 | ### 3 meetings ago 121 | 122 | ### Move to Issue Tracker 123 | 124 | -------------------------------------------------------------------------------- /meetings/archive/20201020_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2020-10-20 Conda Community Meeting 2 | 3 | **** 4 | 5 | [Meeting link](https://meet.google.com/owq-kbca-abk) 6 | 7 | [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-10-20/09:00/b/Conda%20community%20meeting) 8 | 9 | [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 10 | 11 | ## Attendees 12 | 13 | * **Name (Initials) (githubid)** 14 | * Matthew R Becker (MRB) (beckermr) 15 | * Megan C. Yancy (MCY) myancy-anaconda 16 | * Michael C. Grant (MCG) mcg1969 17 | * Paul Ivanov (PI) ivanov 18 | * Michael Sarahan (MCS) 19 | * Cheng Lee (CHL) (chenghlee) 20 | * Hameer Abbasi (HA) (hameerabbasi) 21 | * Amy Williams (AW) (@awilliams-anaconda) 22 | * Kale Franz (KF) @kalefranz 23 | * Sebastien Awwad (SA) (awwad) 24 | * Marcel Bargull (MB) mbargull 25 | * Crystal Soja (CAS) 26 | * Uwe Korn (UK) (xhochy) 27 | * Filipe Fernandes (FF) 28 | * Marcelo Duarte Trevisani (MDT) (marcelotrevisani) 29 | * Connor Martin (CJM) 30 | * Gonzalo Peña-Castellanos (GPC) 31 | * Eric Dill (EDD) gh: ericdill 32 | * Peter Wang (PZW) 33 | * Scopatz (SPZ) 34 | 35 | ## Agenda 36 | 37 | * Welcome 38 | 39 | ### Announcements 40 | * Meeting for 20201103: Move to 20201102 (Election day is 20201103) 41 | 42 | ### Standing Items 43 | 44 | * Website: Check the draft for [text on the website](https://docs.google.com/document/d/1gECzDW4QluEM2-00xrxoseKLD2MaD9k_xvcwj3cxtMg/edit#heading=h.j4l7zepliw4q 45 | ) so design process can continue with some actual content. 46 | * https://github.com/conda-incubator/assets/issues/2 47 | * Anaconda needs legal to sign-off on logo, etc. 48 | 49 | * Conda Community Triage / Conda Triage team so community members and contributors can start helping? 50 | * Conda Constructor 51 | * GPC - @goanpeca (1-2 hours per week?) 52 | * Conda 53 | * KF 54 | * GPC - @goanpeca (1-2 hours per week?) 55 | * CJM 56 | * Conda-build 57 | * KF 58 | * CJM 59 | * FF (ocefpaf) 60 | * MDT 61 | * Conda-Pack 62 | * MCG 63 | * Ensureconda 64 | * 65 | * setup-miniconda / setup-miniforge (github actions) 66 | * GPC - @goanpeca (1-2 hours per week?) 67 | * grayskull 68 | * MDT 69 | * conda-mirror? 70 | * conda-suggest? 71 | * conda-press? 72 | * conda-lock? 73 | * libronda 74 | * MCS 75 | * others from https://github.com/conda-incubator? 76 | 77 | 78 | * Discussion: 79 | KF is creating/updating process documentation of conda/conda-build 80 | Permissions are needed to let people update - need github ids 81 | members currently on call will be added for issue-management permissions to edit on repositories 82 | Triage during community call? (FF, MCG)- needs scheduling - some time in november? 83 | Kick-off meeting? 84 | 85 | * Organize list on this hackmd on 'short term'/'medium term'/'long term' actionable items? 86 | * Priority order: 87 | * Roadmap: https://github.com/conda/conda/milestone/38 88 | * CLA 89 | 90 | ### New Agenda Items 91 | * N/A 92 | 93 | ### Outstanding Items From the Previous Meeting 94 | * N/A 95 | 96 | 97 | ### Active Votes 98 | * N/A 99 | 100 | ### Subteam Updates 101 | * Specification Subteam 102 | 103 | #### Open PRs 104 | * N/A 105 | 106 | ## Discussion 107 | * 108 | 109 | ## Action items 110 | 111 | * Schedule community issue triage kick-off mtg -- ?? 112 | * Anaconda action item: get clarification about using "conda" trademark in community project names 113 | 114 | ## Previous Meetings 115 | 116 | 117 | ### Last Meeting 202001006 118 | 119 | #### Action Items 120 | 121 | 122 | #### Discussion 123 | * Specification Subteam 124 | * New format for recipes 125 | * slides: https://docs.google.com/presentation/d/19R-h7yeyMF2BnzLKu8UFVVF1npgSwhcvorqBKnxy6qE/edit?usp=sharing 126 | * Tool present for converting existing recipes 127 | * Goal: 128 | - Machine parsability (move information out of Jinja control structures, magic comments) 129 | - Cleaner model for multiple output recipes 130 | - https://github.com/mamba-org/conda-specs 131 | 132 | * Extension on Depfinder project 133 | * CW: 134 | * https://github.com/regro/libcfgraph/tree/master/import_maps 135 | * https://conda-forge.org/blog/posts/2020-10-02-versions/ 136 | 137 | 138 | ### Move to Issue Tracker 139 | 140 | 141 | ### Current Action Items 142 | -------------------------------------------------------------------------------- /meetings/archive/20201102_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2020-11-02 Conda Community Meeting 2 | 3 | **** 4 | 5 | [Meeting link](https://meet.google.com/owq-kbca-abk) 6 | 7 | [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-11-02/09:00/b/Conda%20community%20meeting) 8 | 9 | [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 10 | 11 | ## Attendees 12 | 13 | * **Name (Initials) (githubid)** 14 | * Megan Yancy MCY @myancy-anaconda 15 | * Amy Williams AW 16 | * Cheng Lee CHL 17 | * Filipe Fernandes FF @ocefpaf 18 | * Ray Donnelly RD @mingwandroid 19 | * Kale Franz KF @kalefranz 20 | * Bill Batey BB @lumbrefrio 21 | * Peter Wang PW @pzwang 22 | * Crystal Soja CAS 23 | * 24 | * Matt B. @beckermr 25 | 26 | 27 | ## Agenda 28 | 29 | * Welcome 30 | 31 | ### Announcements 32 | 33 | 34 | ### Standing Items 35 | 36 | * Schedule community issue triage kick-off mtg -- ?? 37 | Draft of triaging guidelines: https://gist.github.com/kalefranz/0c812846e5d755c29b067ba56b8a8ddf 38 | * KF will schedule 39 | 40 | * Anaconda: get clarification about using "conda" trademark in community project names 41 | * With Anaconda legal/marketing; hoping to get a blanket statement à la Arduino/Debian 42 | * Website: Check the draft for [text on the website](https://docs.google.com/document/d/1gECzDW4QluEM2-00xrxoseKLD2MaD9k_xvcwj3cxtMg/edit#heading=h.j4l7zepliw4q) so design process can continue with some actual content. 43 | * https://github.com/conda-incubator/assets/issues/2 44 | * Anaconda needs legal to sign-off on logo, etc. 45 | 46 | * Conda Community Triage / Conda Triage 47 | * Conda Constructor 48 | * Conda 49 | * @kalefranz: 50 | * Conda GitHub org cleanup: 51 | * Review a list of proposed repositories to remove from github.com/conda and move elsewhere. 52 | https://docs.google.com/spreadsheets/d/1QZGJ59GshRxyqLGhNohGn-zNjX2EU-Or9jh6x86fZes 53 | * Conda-build 54 | * Conda-Pack 55 | * Ensureconda 56 | * setup-miniconda / setup-miniforge (github actions) 57 | * grayskull 58 | * conda-mirror 59 | * conda-suggest 60 | * conda-press 61 | * conda-lock 62 | * libronda 63 | 64 | * Organize list on this hackmd on 'short term'/'medium term'/'long term' actionable items? 65 | * Priority order: 66 | * Roadmap: https://github.com/conda/conda/milestone/38 67 | * CLA 68 | * Look into modified CLA - organizations and other companies? 69 | 70 | ### New Agenda Items 71 | * N/A 72 | 73 | ### Outstanding Items From the Previous Meeting 74 | * N/A 75 | 76 | 77 | ### Active Votes 78 | * N/A 79 | 80 | ### Subteam Updates 81 | 82 | #### Open PRs 83 | * N/A 84 | 85 | ## Discussion 86 | * 87 | 88 | ## Action items 89 | 90 | * Anaconda: Organizational-level CLA 91 | 92 | ## Previous Meetings 93 | 94 | 95 | ### Last Meeting 202001020 96 | * Website: Check the draft for [text on the website](https://docs.google.com/document/d/1gECzDW4QluEM2-00xrxoseKLD2MaD9k_xvcwj3cxtMg/edit#heading=h.j4l7zepliw4q 97 | ) so design process can continue with some actual content. 98 | * https://github.com/conda-incubator/assets/issues/2 99 | * Anaconda needs legal to sign-off on logo, etc. 100 | 101 | * Conda Community Triage / Conda Triage team so community members and contributors can start helping? 102 | * Conda Constructor 103 | * GPC - @goanpeca (1-2 hours per week?) 104 | * Conda 105 | * KF 106 | * GPC - @goanpeca (1-2 hours per week?) 107 | * CJM 108 | * Conda-build 109 | * KF 110 | * CJM 111 | * FF (ocefpaf) 112 | * MDT 113 | * Conda-Pack 114 | * MCG 115 | * Ensureconda 116 | * 117 | * setup-miniconda / setup-miniforge (github actions) 118 | * GPC - @goanpeca (1-2 hours per week?) 119 | * grayskull 120 | * MDT 121 | * conda-mirror? 122 | * conda-suggest? 123 | * conda-press? 124 | * conda-lock? 125 | * libronda 126 | * MCS 127 | * others from https://github.com/conda-incubator? 128 | 129 | 130 | * Discussion: 131 | KF is creating/updating process documentation of conda/conda-build 132 | Permissions are needed to let people update - need github ids 133 | members currently on call will be added for issue-management permissions to edit on repositories 134 | Triage during community call? (FF, MCG)- needs scheduling - some time in november? 135 | Kick-off meeting? 136 | 137 | * Organize list on this hackmd on 'short term'/'medium term'/'long term' actionable items? 138 | * Priority order: 139 | * Roadmap: https://github.com/conda/conda/milestone/38 140 | * CLA 141 | 142 | #### Action Items 143 | * Schedule community issue triage kick-off mtg -- ?? 144 | * Anaconda action item: get clarification about using "conda" trademark in community project names 145 | 146 | #### Discussion 147 | 148 | 149 | ### Move to Issue Tracker 150 | 151 | 152 | ### Current Action Items 153 | -------------------------------------------------------------------------------- /meetings/archive/20200721_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # Conda-Tools Kick-off Agenda 2 | 3 | 1. Brief Intros 4 | who's here? 5 | - Amy Williams 6 | - Angela Gloyna 7 | - Anthony Scopatz 8 | - Cheng Lee 9 | - Connor Martin 10 | - Crystal Soja 11 | - Eric Dill 12 | - Filipe Fernandes 13 | - John Kirkham 14 | - Jonathan Helmus 15 | - Johan Mabille 16 | - Kai Tietz 17 | - Keith Kraus 18 | - Marcel Bargull 19 | - Marcelo Trevisani 20 | - Marius van Niekerk 21 | - Matthew Becker 22 | - Megan Yancy 23 | - Michael Sarahan 24 | - Patrick Sodré 25 | - Peter Wang 26 | - Ray Donnelly 27 | - Raymond Douglass 28 | - Sebastien Awwad 29 | - Sylvain Corlay 30 | - Tadeu Manoel 31 | - Travis Oliphant 32 | - Uwe Korn 33 | - Wolf Vollprecht 34 | - Yuvi Panda 35 | 3. Goals 36 | * NumFOCUS Sponsorship 37 | * Conda Specs 38 | * A place for tools to live 39 | * Support for tools 40 | * Open Roadmap 41 | * 42 | 4. Contributions 43 | 5. Agenda 44 | * Introductions 45 | * Goals - Set up new organization to 46 | * Discuss conda and ecosystem specifications 47 | * Put toolings in a common location 48 | * Provide governance 49 | * Name? 50 | * conda-tools org (https://github.com/conda-tools) : currently owned by conda-forge 51 | * conda org (https://github.com/conda) : owned by Anaconda, Inc 52 | * Preferred by Peter 53 | * Has existed for considerable time 54 | * Community would need to take admin control over the org 55 | * Move conda, conda-build, etc out? 56 | * Phased "transition" 57 | * 1. Move tools to conda organization (separate governance models for projects initially) 58 | * 2. Common governance model for tools, especially conda, eventually, hopefully, maybe... 59 | * What is the criteria for a project to be included in the conda organization 60 | * Balance easy to include in org with stability 61 | * Developing outside of the org allows easier freedom to explore 62 | * Incubator organization or "tag" 63 | * org seems better 64 | * incubator has not worked well in Jupyter, JEPs are needed for electing projects to the core org. 65 | * Incubation process rarely used 66 | * Projects tend to be developed "out in the world" and added directly to Jupyter without incubation 67 | * When a project is moved to "core", there is a maintainance burden. Incubating projects are more experimental 68 | * Moving to a incubating org allows projects to continue when developers leave companies. 69 | * Critia for inclusion should be minimal 70 | * Automated process 71 | * SnakePit (https://github.com/TheSnakePit): QuantStack lead (mamba, boa, quetz) 72 | * Other random name 73 | * Can the conda name be used? 74 | * Peter + Travis are okay with use and do not major concerns 75 | * Peter has concern about non-participants hijacking (strip mining) the community 76 | * How do we protect ourselves from these type of actions? 77 | * Form a consortium 78 | * mamba, boa and quetz do not use "conda" to avoid trademark infringement 79 | * Might change if there were rules for using the conda name 80 | * Papertrail giving conda-forge and other communities permission to use the conda "name" 81 | * bioconda related? 82 | * Specifications 83 | * Compatibility vs Maintainance 84 | * Would like to see a voting aspect to specification 85 | * Roadmap for specs 86 | * Support 87 | * In phase one, support would be provided by the projects themselves 88 | * 89 | 7. Governance 90 | * Proposal: Use conda-forge governance doc for this, modify for use case 91 | * core group is ~folks on this call 92 | * Commit rights should be maintained as projects move to new organizations 93 | * Initially individual projects would retain their own governance but be under the conda organization 94 | * Bootstrapping voting body 95 | * allow ppl to sign up, you have to vote to be in 96 | * README should include who runs them (Anaconda, QuantStack, individuals). Should include information on what level of support is provided and how to ask for it 97 | 9. What should we call ourselves? 98 | * Can we use the conda org? 99 | * Respecting the conda trademark 100 | * [scopatz] - I think uses such as in conda-forge or conda-lock fall under fair use as long as we don't then go and and try to trademark those conda-forge itself: https://en.wikipedia.org/wiki/Fair_use_(U.S._trademark_law) 101 | 102 | 103 | # Other notes / discussions 104 | * Where to have ongoing conversations? 105 | * New slack org? Slack channel on existing slack workspace? 106 | * maybe gitter? 107 | 108 | 109 | # Next Steps 110 | * How do we continue the conversions 111 | * https://github.com/conda-incubator (yay!) 112 | * Slack! 113 | * https://join.slack.com/t/conda-tools/shared_invite/zt-g0907dnm-FgXZrDkZ3WdcTNhg6d3ffQ 114 | * weekly or fortnightly call to keep things moving 115 | -------------------------------------------------------------------------------- /meetings/archive/20201117_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2020-11-17 Conda Community Meeting 2 | 3 | **** 4 | 5 | [Meeting link](https://meet.google.com/owq-kbca-abk) 6 | 7 | [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-11-17/09:00/b/Conda%20community%20meeting) 8 | 9 | [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 10 | 11 | ## Attendees 12 | 13 | | Name | Initials | Affiliation | Username | 14 | | ---- | -------- |------------ | -------- | 15 | | Megan Yancy | MCY | Anaconda | @myancy-anaconda | 16 | | Sebastien Awwad | SA | Anaconda distro team | @awwad | 17 | | Kale Franz | KF | Anaconda | @kalefranz | 18 | | Cheng Lee | CHL | Anaconda | @chenghlee | 19 | | Michael Grant | MG | Anaconda | mcg1969 | 20 | | CJ Wright | CJ | Lab49| @cj-wright| 21 | | Matthew Becker | | | beckermr | 22 | | Amy Williams | AW | Anaconda | awilliams-anaconda | 23 | | Filipe Fernandes | FF | | @ocefpaf | 24 | | Gonzalo Peña-Castellanos | GPC | Quansight | @goanpeca | 25 | | Crystal Soja | CAS | Anaconda | csoja | 26 | | Marcelo Duarte Trevisani | MDT | conda-forge | @marcelotrevisani | 27 | | Marcel Bargull | MB | conda-forge/Bioconda | @mbargull | 28 | | Michael Sarahan | MCS | | @msarahan | 29 | 30 | ## Agenda 31 | 32 | * Welcome 33 | 34 | ### Announcements 35 | 36 | 37 | ### Standing Items 38 | * N/A 39 | 40 | ### New Agenda Items 41 | * Rotating Meeting Facilitator 42 | * Call for volunteers 43 | * (@goanpeca) 44 | * Anaconda: Organizational-level CLA 45 | * No current updates 46 | * Overview of artifact verification / package signing for conda (adaptation of The Update Framework) -- SA 47 | * Slides here: https://docs.google.com/presentation/d/1YkY62Q8DVfCpeYq7_iI7d5aWeYQnj7ghtPWUDRHSSNE/edit?usp=sharing 48 | * conda-pack issue curation: labeling completed, contributors invited - MG 49 | * Call for volunteers 50 | * https://github.com/conda/conda-pack/issues 51 | 52 | ### Outstanding Items From the Previous Meeting 53 | * N/A 54 | 55 | 56 | ### Active Votes 57 | * Triaging and Issue Tracking meeting (KF): https://doodle.com/poll/cqpw3pkpew4tex5r 58 | * Please vote! 59 | 60 | ### Subteam Updates 61 | 62 | #### Open PRs 63 | * N/A 64 | 65 | ## Discussion 66 | * Ways to address diversity inclusiveness issues 67 | * new sub-team - charter for maintaining and advancing conda-forge as a diverse community, try to grow. Charter is dynamic. Looking for those who are not core contributors of conda-forge. 68 | * Would like input on document 69 | * https://github.com/conda-forge/conda-forge.github.io/pull/1187 70 | * Availability of artifact verification features to other pieces of software (than conda): 71 | * SA: @Wolf, Please be aware that at first, we're offering the trust and signing data to paid folks, because... lights on. But I don't see why support for consuming that data shouldn't be handled in any package manager frontend talking to the repository. There's a project with the majority of the low-level code and a set of algorithms. The process of integrating that into conda (or other managers) is a delicate thing, so I'm hoping that the guidelines are helpful enough... but this will improve after conda integration. 72 | * Wolf: sure. with quetz we're working hard to support mirroring of conda-channels (specifically conda-forge), and this trust & verification is pretty integral for that so ... we might have to implement this anyways, and then it would probably make sense to do it in the same fashion as upstream 73 | * SA: that'd be good, yeah. We can talk about the TUF work underlying it at the least 74 | 75 | ## Action items 76 | 77 | 78 | 79 | ## Previous Meetings 80 | 81 | 82 | ### Last Meeting 202001102 83 | 84 | * Schedule community issue triage kick-off mtg -- ?? 85 | Draft of triaging guidelines: https://gist.github.com/kalefranz/0c812846e5d755c29b067ba56b8a8ddf 86 | * KF will schedule 87 | * Update: Please give interest and availability for first meeting at https://doodle.com/poll/cqpw3pkpew4tex5r 88 | 89 | * Anaconda: get clarification about using "conda" trademark in community project names 90 | * With Anaconda legal/marketing; hoping to get a blanket statement à la Arduino/Debian 91 | * Website: Check the draft for [text on the website](https://docs.google.com/document/d/1gECzDW4QluEM2-00xrxoseKLD2MaD9k_xvcwj3cxtMg/edit#heading=h.j4l7zepliw4q) so design process can continue with some actual content. 92 | * https://github.com/conda-incubator/assets/issues/2 93 | * Anaconda needs legal to sign-off on logo, etc. 94 | 95 | * Conda Community Triage / Conda Triage 96 | * Conda Constructor 97 | * Conda 98 | * @kalefranz: 99 | * Conda GitHub org cleanup: 100 | * Review a list of proposed repositories to remove from github.com/conda and move elsewhere. 101 | https://docs.google.com/spreadsheets/d/1QZGJ59GshRxyqLGhNohGn-zNjX2EU-Or9jh6x86fZes 102 | * Update: Waiting on Anaconda IT department to create repositories under github.com/ContinuumIO 103 | * Conda-build 104 | * Conda-Pack 105 | * Ensureconda 106 | * setup-miniconda / setup-miniforge (github actions) 107 | * grayskull 108 | * conda-mirror 109 | * conda-suggest 110 | * conda-press 111 | * conda-lock 112 | * libronda 113 | 114 | * Organize list on this hackmd on 'short term'/'medium term'/'long term' actionable items? 115 | * Priority order: 116 | * Roadmap: https://github.com/conda/conda/milestone/38 117 | * CLA 118 | * Look into modified CLA - organizations and other companies? 119 | 120 | 121 | * Discussion: 122 | KF is creating/updating process documentation of conda/conda-build 123 | Permissions are needed to let people update - need github ids 124 | members currently on call will be added for issue-management permissions to edit on repositories 125 | Triage during community call? (FF, MCG)- needs scheduling - some time in november? 126 | Kick-off meeting? 127 | 128 | * Organize list on this hackmd on 'short term'/'medium term'/'long term' actionable items? 129 | * Priority order: 130 | * Roadmap: https://github.com/conda/conda/milestone/38 131 | * CLA 132 | 133 | #### Action Items 134 | * Anaconda: Organizational-level CLA 135 | 136 | #### Discussion 137 | 138 | 139 | ### Move to Issue Tracker 140 | 141 | 142 | ### Current Action Items -------------------------------------------------------------------------------- /meetings/archive/20201201_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2020-12-01 Conda Community Meeting 2 | 3 | * [Meeting link](https://meet.google.com/owq-kbca-abk) 4 | * [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-12-01/09:00/b/Conda%20community%20meeting) 5 | * [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 6 | 7 | ## Attendees 8 | 9 | | Name | Initials | Affiliation | Username | 10 | | ---- | -------- |------------ | -------- | 11 | | Gonzalo Peña-Castellanos | GPC | Quansight | @goanpeca | 12 | | Megan Yancy | MCY | Anaconda | @myancy-anaconda | 13 | | Marius van Niekerk | MvN | Flatiron Health | @mariusvniekerk | 14 | | Cheng Lee | CHL | Anaconda | @chenghlee | 15 | | Eric Dill | ED | DTN | @ericdill | 16 | | Crystal Soja | CAS | Anaconda | @csoja | 17 | | Christopher J "CJ" Wright | CJ | Lab49 | @cj-wright | 18 | | Keith Kraus | KK | NVIDIA | @kkraus14 | 19 | | Filipe Fernandes | FF | IOOS | ocefpaf | 20 | | Michael Grant | MG | Anaconda | mcg1969 | 21 | | Connor Martin | CJM | Anaconda |@cjmartian | 22 | | Marcel Bargull | MB | Bioconda / conda-forge | @mbargull | 23 | | Wolf Vollprecht | WV | QuantStack / mamba | @wolfv | 24 | | Matthew Becker | MRB | -- | @beckermr | 25 | | Marcelo Duarte Trevisani | MDT | conda-forge | @marcelotrevisani | 26 | | Michael Sarahan | MCS | RStudio | @msarahan | 27 | 28 | ## Agenda 29 | 30 | * Welcome 31 | 32 | ### Announcements 33 | 34 | 35 | ### Standing Items 36 | * Anaconda: Organizational-level CLA 37 | * No current updates. 38 | 39 | 40 | ### New Agenda Items 41 | 42 | * Rotating Meeting Facilitator 43 | * Call for volunteers 44 | * Who wants to go next? 45 | 46 | * Conda Triaging and Issue Tracking meeting took place. 47 | * Meeting: Kale, Marcel, Gonzalo, Cheng 48 | * Splitting responsibility by day: each person triages issues that come in that day 49 | * [conda-triage](https://conda.slack.com/archives/C01FMCT5W84) 50 | 51 | * Given that pip install conda still "works" but obviously installs something wildly out of date and non functional should we yank the releases on pypi ? (@marius) 52 | * Existing blog posts refer to conda being pip installable 53 | * Possible solutions: 54 | * could `pipx install conda` with a standalone binary? 55 | * `pip install conda` forcibly fails with a link to miniconda installer? 56 | * Remove the packages but reserve the package name? 57 | * _Very_ long term: cool but probably impractical due to major technical challenges 58 | * Short term fix: Anaconda will replace with newer stub package on PyPI. 59 | * Create a `conda-stub` repository that creates folder with an empty package. 60 | * Will not remove package (without annoucement) to avoid breaking existing users & workflows. 61 | * Issue: https://github.com/conda/conda/issues/10388 62 | 63 | * Where are the conda-standalone binaries these days? 64 | * Since all i know of is https://repo.anaconda.com/pkgs/misc/conda-execs 65 | * Short term I am unpacking the ones from https://anaconda.org/anaconda/conda-standalone (for use in ensureconda) 66 | * `conda install conda-standalone` -> installs into `$CONDA_PREFIX/standalone_conda` 67 | * https://repo.anaconda.com/pkgs/main/${subdir}/conda-standalone*.tar.bz2 68 | * Ray has pushed for updating these binaries for each conda release. 69 | * Anaconda needs to address internal CI issues around automating executable signing. (Currently use a manual process of downloading, re-signing, and re-uploading executables.) 70 | 71 | * [x] (MRB) package copying and package metadata on anaconda.org 72 | * We are having an issue in conda-forge where when we [copy](https://api.anaconda.org/docs#!/package/post_copy_package_owner_login_package_name_version_basename) packages from one user to another using the copy API endpoint, the metadata per package (doc_url, dev_url etc) displayed on anaconda.org is erased. We need this metadata for certain packages, especially cudatoolkit. 73 | * We need two fixes: 74 | * support for patch requests for the anaconda.org `/package/{owner_login}/{package_name}` API endpoint so that we can restore the metadata 75 | * fix the copy endpoint so it does not delete this metadata 76 | * These will let us fix the packages we have and make sure it doesn't happen for new packages. 77 | * issue: https://github.com/Anaconda-Platform/anaconda-client/issues/556 78 | 79 | * Audit (CJ) 80 | * Using depfinder to check: 81 | * Accurate 82 | * Under specified 83 | * Over specified 84 | * Under and over specified 85 | * Errored 86 | * Link to the information 87 | * https://github.com/conda-forge/by-the-numbers 88 | * https://github.com/conda-forge/by-the-numbers/blob/master/audit_accuracy.ipynb 89 | 90 | * Raises the question of how to handle optional dependencies and/or sub-packages? 91 | * Like RPM provides? 92 | 93 | * Additional test "keys" for conda-build (WV) 94 | * I wrote down some ideas here: https://github.com/mamba-org/boa/issues/93 95 | * Is conda-build interested in these tests? (CHL: yes; please open issue on conda-build GH) 96 | * Fits into concepts for conda-verify 97 | 98 | ### Outstanding Items From the Previous Meeting 99 | 100 | * N/A 101 | 102 | ### Active Votes 103 | 104 | 105 | ### Subteam Updates 106 | 107 | 108 | #### Open PRs 109 | 110 | * N/A 111 | 112 | ## Discussion 113 | 114 | 115 | ## Action items 116 | 117 | ## Last meeting points (2020-11-17) 118 | 119 | * Ways to address diversity inclusiveness issues 120 | * new sub-team - charter for maintaining and advancing conda-forge as a diverse community, try to grow. Charter is dynamic. Looking for those who are not core contributors of conda-forge. 121 | * Would like input on document 122 | * https://github.com/conda-forge/conda-forge.github.io/pull/1187 123 | * Availability of artifact verification features to other pieces of software (than conda): 124 | * SA: @Wolf, Please be aware that at first, we're offering the trust and signing data to paid folks, because... lights on. But I don't see why support for consuming that data shouldn't be handled in any package manager frontend talking to the repository. There's a project with the majority of the low-level code and a set of algorithms. The process of integrating that into conda (or other managers) is a delicate thing, so I'm hoping that the guidelines are helpful enough... but this will improve after conda integration. 125 | * Wolf: sure. with quetz we're working hard to support mirroring of conda-channels (specifically conda-forge), and this trust & verification is pretty integral for that so ... we might have to implement this anyways, and then it would probably make sense to do it in the same fashion as upstream 126 | * SA: that'd be good, yeah. We can talk about the TUF work underlying it at the least -------------------------------------------------------------------------------- /meetings/archive/20200908_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2020-09-08 Conda Community Meeting 2 | 3 | **** 4 | 5 | [Meeting link](https://meet.google.com/uje-pdns-hch) 6 | 7 | [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-09-08/09:00/b/Conda%20community%20meeting) 8 | 9 | [last weeks meeting]() None! 10 | 11 | ## Attendees 12 | 13 | * Matthew R Becker 14 | * Filipe Fernandes 15 | * Jonathan Helmus 16 | * Megan Yancy 17 | * Connor Martin 18 | * Uwe Korn 19 | * Angela Gloyna 20 | * Cheng Lee 21 | * Travis Oliphant 22 | * Devon Ryan 23 | * Marius van Niekerk 24 | * Hameer Abbasi 25 | * Gonzalo Peña-Castellanos 26 | * Marcelo Duarte Trevisani 27 | * Marcel Bargull 28 | * Michael Grant 29 | * Martin Prüsse 30 | * Crystal Soja 31 | * Peter Wang 32 | * Isabela Presedo-Floyd 33 | * Michael Sarahan 34 | 35 | 36 | ## Agenda 37 | 38 | * Welcome 39 | 40 | ### Announcements 41 | 42 | * Meeting Notes and Minutes location 43 | 44 | ### Standing Items 45 | * Archived records for minutes: https://github.com/conda-incubator/governance/tree/master/meetings 46 | * [x] Projects to invite/add to incubator 47 | * (FF) How are we going to move projects from incubator to main conda org? 48 | * Any core member can add 49 | * Holding off on directly asking mamba org (mamba, quetz, etc.) but they are welcome at any time 50 | * [ ] Website (and blog?) 51 | * needs name 52 | * conda.org is owned by Anaconda (Peter okay with using domain for this org.) 53 | * Do we need further help in designing website? 54 | * ask Quansight 55 | * Matthew R Becker can help as needed 56 | * chat w/ Isabela 57 | * Timeline: no rush 58 | * Website with links and calendar 59 | * communication: post in incubator 60 | 61 | * Blog would come later (no content yet) 62 | * GitHub organization 63 | * [ ] Public calendar 64 | * Turn a Google Calendar public for communication 65 | * Filipe Fernandes 66 | * https://calendar.google.com/calendar/embed?src=8h0v8cj3d0lhu0dfmmapoiq5ig%40group.calendar.google.com 67 | * [ ] Establish a process for creating and doing admin tasks for repos on the `conda` org on GitHub 68 | * [ ] use a admin-requests repo to make tickets 69 | * [ ] LONG TERM: investigate moving repo management to terraform? Can use terraform cloud + security policies to tightly control application of how teams, repos etc can be made 70 | * Do we have anything ready to migrate? 71 | * Governance 72 | * [ ] need to talk to Anaconda IT to figure out permissions 73 | * Owners are not public 74 | * Anaconda is still going to operate conda GitHub org. 75 | * [ ] Changes made to Anaconda websites need to be locked down (CI jobs, etc). 76 | * Anaconda 77 | * [ ] Community permissions put up docs/pages to [conda.org](conda.org). 78 | * No repos yet 79 | * [ ] Website/email e-mail to be updated on [GitHub.org](github.org) 80 | * (CHL) Need to figure out who will take ownership of email, etc. 81 | * [ ] Archive old projects to conda-attic? 82 | * Determine as we bring more projects onboard 83 | * [ ] change CLA bot to be only anaconda repos 84 | * yes, unsure of current status (in flight) 85 | * As long as there is an admin, we can deploy 86 | * [ ] Trademark and logo use clearance 87 | * Still needs to be discussed, will push to next meeting 88 | * Will probably need to have clarification before website deployment 89 | * [ ] Move smaller projects to community maintenance 90 | * [ ] constructor *not ready to move yet 91 | * [ ] conda-pack 92 | * [ ] conda-package-handling 93 | * [ ] schema 94 | * Cheng Lee looking into getting access 95 | * Probably first Anaconda-owned project that we will shift to community maintenance 96 | * [ ] conda *not ready to move yet 97 | * [ ] conda-build *not ready to move yet 98 | 99 | ### New Agenda Items 100 | 101 | * [x] Anaconda: What are the plans for use of the conda organization? 102 | * discussed above 103 | 104 | ### Outstanding Items From the Previous Meeting 105 | 106 | ### Active Votes 107 | 108 | ### Subteam Updates 109 | * Specification Subteam 110 | * Contents of `info/` directory 111 | * `repodata.json` 112 | * `current_repodata.json` 113 | * `channeldata.json` 114 | 115 | #### Open PRs 116 | 117 | ## Discussion 118 | * What are the milestones that Anaconda is looking to move to a community governance model? 119 | * What can be community-governed? 120 | * Breaking conda-build into smaller parts? Implement as separate projects and adapting them to conda? 121 | * How will the community contribute in the governance model? 122 | * (ED) Are there definite milestones before Anaconda will shfit to community governance? 123 | * Transparency of decisions? 124 | * (TO) Need to make clear what are community objetives, what are strictly corporate objectives, and what are a mix of both. 125 | * Anaconda has always been an avid supporter of the conda community and been a great steward of many conda tools to this point. There is a need now for more clarity of which parts of the conda ecosystem can become community governed (community-driven). There are now advocates for conda-build, conda-pack, conda-constructor, and even conda itself to become community-driven. 126 | * Some comments from Travis about how Anaconda employee contributors mostly wear a community hat when they contribute to the conda community and so it can be hard for both sides to understand when that might not be the case. This can lead to situations where a company like Anaconda that is very supportive of the community can be at the same time "hard to work with" from the community perspective unless there is clarity about which hat people are wearing when they contribute. It's also why community-governance can become an important issue so that people can trust the project evolves according to the community as a whole and not just particular stake-holders. 127 | * Even if Anaconda decides that one or more of the conda tools must remain as Anaconda-governed for the time being, it would really help to have transparency and communication from Anaconda-as-a-business of project goals, roadmaps, and priorities and have them separated from individual Anaconda employee desires and goals as community members. Travis suspects that most changes are actually driven by Anaconda employees as community members and not because of Anaconda-as-a-business directed work (but it would be great to be able to know this). 128 | 129 | ## Previous Action Items 130 | 131 | ### This Meeting 132 | 133 | ### Last Meeting 20200824 134 | * plans for use of the conda organization 135 | * [ ] Figure out GitHub teams for core members 136 | * [ ] Move governance repo to conda org 137 | * [ ] Move smaller projects to community maintenance 138 | * [ ] constructor 139 | * [ ] conda-pack 140 | * [ ] conda-package-handling 141 | * [ ] schema 142 | * [ ] others? 143 | * [ ] Move conda & conda-build to community maintenance 144 | * [ ] What should we communicate to the community? 145 | * join our slack 146 | * document long-term plans 147 | * outline governance doc 148 | * document how to get involved etc 149 | * publish meeting notes 150 | * list sponsors / contributors 151 | * list of repos 152 | * who to bug 153 | * some text on specs and how it guides the community 154 | * [ ] Move smaller projects to community maintenance 155 | * [ ] constructor 156 | * [ ] conda-pack 157 | * [ ] conda-package-handling 158 | * [ ] schema 159 | * [ ] conda 160 | * [ ] conda-build 161 | * [ ] build up website content 162 | * [ ] Numfocus fiscal sponsorship 163 | 164 | ### Move to Issue Tracker 165 | ### Action Items 166 | * Moving smaller projects to community maintenance 167 | * [ ] schema 168 | * Cheng Lee 169 | * Anaconda Roadmap 170 | * Github organization 171 | * Website 172 | -------------------------------------------------------------------------------- /meetings/archive/20200922_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2020-09-22 Conda Community Meeting 2 | 3 | **** 4 | 5 | [Meeting link](https://meet.google.com/owq-kbca-abk) 6 | 7 | [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-09-22/09:00/b/Conda%20community%20meeting) 8 | 9 | [last weeks meeting]() None! 10 | 11 | ## Attendees 12 | 13 | * **Name (Initials)** 14 | * Megan Yancy (MCY) 15 | * Jonathan Helmus (JJH) 16 | * Matt B. (MRB) 17 | * Filipe (FF) 18 | * Isabela Presedo-Floyd (IRPF) 19 | * Hameer Abbasi (HA) 20 | * Marius van Niekerk (MvN) 21 | * Michael Grant (MG) 22 | * Michael Sarahan (MCS) 23 | * Martin Prüsse (MP) 24 | * Gonzalo Peña-Castellanos (GPC) 25 | * Peter Wang (PW) 26 | * Marcel Bargull (MB) 27 | * Anthony Scopatz (AS) 28 | * Connor Martin (CJM) 29 | * Stan Seibert (SRS) 30 | * Uwe Korn (UK) 31 | * Amy Williams 32 | * Angela Gloyna 33 | * Cheng Lee 34 | * Christopher 'CJ' Wright (CJW) 35 | * Crystal Soja 36 | * Keith Kraus 37 | * Peter Wang 38 | * 39 | 40 | ## Agenda 41 | 42 | * Welcome 43 | 44 | ### Announcements 45 | 46 | ### Standing Items 47 | * Discussion: Community Needs 48 | 49 | ### New Agenda Items 50 | * Discussion: Community needs 51 | 52 | ### Outstanding Items From the Previous Meeting 53 | 54 | ### Active Votes 55 | * N/A 56 | 57 | ### Subteam Updates 58 | * Specification Subteam 59 | 60 | #### Open PRs 61 | * N/A 62 | 63 | ## Discussion 64 | 65 | Timebox: 45 minutes 66 | Continued our discussion from last time regarding what the community feels they are not getting (discussion notes below, Last Meeting 20200908/Discussion): 67 | * What responsibilities does the community want to have? 68 | * 69 | * What does the community feel like they are missing? 70 | 71 | * What parts do people feel hung up on? And are there other software models we can use so that those who want to drive/own it, can do so? Part of the approach might be to create separate efforts for those portions, that can move forward unencumbered. (MCS) 72 | * PRs and reviews 73 | * More people to review PRs? 74 | * Require more people who understand the code, but that's challenging at the moment. (large, intertwined code base that's not really approachable.) 75 | * Knowledge transfer (How can we help/train more people?) 76 | * Pair Programming to understand the code? 77 | * Recurrent Online sprints? 78 | * Live coding & pair programming? 79 | * Improving documentation 80 | * Deep dive into architecture? 81 | * Youtube? 82 | * https://www.anaconda.com/blog/understanding-and-improving-condas-performance 83 | * https://www.anaconda.com/blog/how-we-made-conda-faster-4-7 84 | * Michael Grant 85 | * CLA is potentially a barrier 86 | * Just having one is a barrier (not the actual content) 87 | * Some people do have objections at the level of the principle of it. 88 | * CLA always takes rounds with CEOs and then a lawyer call. They are quickly approved but until the call happens, months can pass. 89 | * Running test suite in local machine is also difficult (AS) 90 | * Potentially provide some easier way to build a testing docker container? 91 | * Lacking clear standards for what "compatability" means (AS) 92 | * Ways to identify issues that may be easier/low hanging fruit for the community tackle (GPC) 93 | * good first issue tag, https://github.com/conda/conda/issues?q=is%3Aopen+is%3Aissue+label%3Agood_first_issue 94 | * Comunication with PRs, especially when multiple PRs address the same issue 95 | * Better communication of bandwidth 96 | * Acknowldegement of receiving PRs 97 | * PR Review team? 98 | * What team to ask? - Update template? 99 | * Anaconda 100 | * Community 101 | * Better expectation communication 102 | * Open and public roadmap 103 | * How do PRs fit into the roadmap? 104 | * https://docs.github.com/en/enterprise/2.20/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization 105 | * What is the path to introduce big changes? 106 | 107 | * Are there specific subprojects we can pull from the existing larger repositories that can be built off to facilitate community iteration and improvement? 108 | * 109 | * Can we define initiatives that the community can collaboratively drive forward? 110 | * 111 | * Can we nominate key community contributors who have enough experience with a project's codebase to be promoted to merge privileges? 112 | * 113 | 114 | ## Action items 115 | 116 | * Take a look at the issue tracker and PR Tracker to gather some general view of outstading items 117 | * Have a Conda Community Triage / Conda Triage team so community members and contributors can start helping? 118 | * Have some sort of label to indicate issues that definitely should be closed? 119 | * Organize list on this hackmd on 'short term'/'medium term'/'long term' actionable items? 120 | * Check the draft for [text on the website](https://docs.google.com/document/d/1gECzDW4QluEM2-00xrxoseKLD2MaD9k_xvcwj3cxtMg/edit#heading=h.j4l7zepliw4q 121 | ) so design process can continue with some actual content. 122 | 123 | * Look at current PRs, identify ones that we can look closer at 124 | * Triage issues and PRs for next live review session 125 | * Permissions on labels- volunteers, please add name to list - will be available on slack 126 | * Email and Slack with email link to meeting notes 127 | * Roadmap 128 | 129 | ## Previous Meetings 130 | 131 | 132 | ### Last Meeting 20200908 133 | 134 | #### Action Items 135 | * Moving smaller projects to community maintenance 136 | * [ ] schema 137 | * Cheng Lee 138 | * Anaconda Roadmap 139 | * Github organization 140 | * Website 141 | * Text for website: https://docs.google.com/document/d/1gECzDW4QluEM2-00xrxoseKLD2MaD9k_xvcwj3cxtMg/edit 142 | 143 | 144 | #### Discussion 145 | * What are the milestones that Anaconda is looking to move to a community governance model? 146 | * What can be community-governed? 147 | * Breaking conda-build into smaller parts? Implement as separate projects and adapting them to conda? 148 | * How will the community contribute in the governance model? 149 | * (ED) Are there definite milestones before Anaconda will shfit to community governance? 150 | * Transparency of decisions? 151 | * (TO) Need to make clear what are community objetives, what are strictly corporate objectives, and what are a mix of both. 152 | * Anaconda has always been an avid supporter of the conda community and been a great steward of many conda tools to this point. There is a need now for more clarity of which parts of the conda ecosystem can become community governed (community-driven). There are now advocates for conda-build, conda-pack, conda-constructor, and even conda itself to become community-driven. 153 | * Some comments from Travis about how Anaconda employee contributors mostly wear a community hat when they contribute to the conda community and so it can be hard for both sides to understand when that might not be the case. This can lead to situations where a company like Anaconda that is very supportive of the community can be at the same time "hard to work with" from the community perspective unless there is clarity about which hat people are wearing when they contribute. It's also why community-governance can become an important issue so that people can trust the project evolves according to the community as a whole and not just particular stake-holders. 154 | * Even if Anaconda decides that one or more of the conda tools must remain as Anaconda-governed for the time being, it would really help to have transparency and communication from Anaconda-as-a-business of project goals, roadmaps, and priorities and have them separated from individual Anaconda employee desires and goals as community members. Travis suspects that most changes are actually driven by Anaconda employees as community members and not because of Anaconda-as-a-business directed work (but it would be great to be able to know this). 155 | 156 | ### Move to Issue Tracker 157 | 158 | 159 | ### Current Action Items 160 | 161 | 162 | 163 | 164 | -------------------------------------------------------------------------------- /meetings/archive/20201006_agenda_and_minutes.md: -------------------------------------------------------------------------------- 1 | # 2020-10-06 Conda Community Meeting 2 | 3 | **** 4 | 5 | [Meeting link](https://meet.google.com/owq-kbca-abk) 6 | 7 | [What time is the meeting in my time zone](https://arewemeetingyet.com/Chicago/2020-10-06/09:00/b/Conda%20community%20meeting) 8 | 9 | [Last Meeting's Agenda and Minutes](https://github.com/conda-incubator/governance/tree/master/meetings) 10 | 11 | ## Attendees 12 | 13 | * **Name (Initials)** 14 | * Megan Yancy (MCY) 15 | * Connor Martin (CJM) 16 | * Amy Williams (ADW) 17 | * Michael Grant (MCG) 18 | * Jonathan Helmus (JJH) 19 | * Michael Sarahan (MCS) 20 | * Matthew R Becker (MRB) 21 | * Crystal Soja (CAS) 22 | * Marcel Bargull (MB) 23 | * Gonzalo Peña-Castellanos (GPC) 24 | * Anthony Scopatz (AS) 25 | * Peter Wang (PZW) 26 | * Paul Ivanov (PI) 27 | * Kale Franz (KJF) 28 | * Cheng Lee (CHL) 29 | * Ray Douglass (RRD) 30 | * Sebastien Awwad (SA) 31 | * Eric Dill (ED) 32 | * Wolf Vollprecht 33 | * Sylvain Corlay 34 | * Filipe Pires Alvarenga Fernandes (FF) 35 | * Christopher Wright (CW) 36 | * Marius van Niekerk 37 | 38 | ## Agenda 39 | 40 | * Welcome 41 | 42 | ### Announcements 43 | 44 | ### Standing Items 45 | 46 | ### New Agenda Items 47 | * N/A 48 | 49 | ### Outstanding Items From the Previous Meeting 50 | * * Website:Check the draft for [text on the website](https://docs.google.com/document/d/1gECzDW4QluEM2-00xrxoseKLD2MaD9k_xvcwj3cxtMg/edit#heading=h.j4l7zepliw4q 51 | ) so design process can continue with some actual content. 52 | * https://github.com/conda-incubator/assets/issues/2 53 | * Anaconda needs legal to sign-off on logo, etc. 54 | * Isabela will do draft design, but intent is to make site community-managed (a la conda-forge). 55 | * MG: Likes "good first issue" on landing page 56 | 57 | * Take a look at the issue tracker and PR Tracker to gather some general view of outstanding items 58 | * Have a Conda Community Triage / Conda Triage team so community members and contributors can start helping? 59 | * Discusssion: What does this look like? 60 | * MG: Conda Constructor- Every issue is tagged 61 | * CAS: document for how to tag issues for conda project in flight. 62 | * Look at current PRs, identify ones that we can look closer at 63 | * Triage issues and PRs for next live review session 64 | * Permissions on labels- volunteers, please add name to list - will be available on slack 65 | * CHL will start a slack channel 66 | * Email and Slack with email link to meeting notes 67 | * Roadmap 68 | * Focus here first 69 | * 5.0.0 roadmap: https://github.com/conda/conda/milestone/38 70 | * 5.0.0 suggestion issue: https://github.com/conda/conda/issues/10265 71 | * Organize list on this hackmd on 'short term'/'medium term'/'long term' actionable items? 72 | * Priority order: 73 | * Roadmap 74 | * CLA 75 | * ED: Should we support Windows ARM64 (e.g., surface)? 76 | * Python ARM64 Windows: https://bugs.python.org/issue33125 77 | Closing this as the work we need for support is now added. Whether we start releasing binaries from python.org is a discussion to have on python-dev and with the broader community. 78 | Right now, I don't think the ecosystem is ready to add support (mainly because there is no CI system that can build/test easily). And most of our tooling isn't up to the task either. Until that can be improved, it's not fair to expect third party packagers to provide wheels or support the platform. 79 | 80 | ### Active Votes 81 | * N/A 82 | 83 | ### Subteam Updates 84 | * Specification Subteam 85 | * New format for recipes 86 | * slides: https://docs.google.com/presentation/d/19R-h7yeyMF2BnzLKu8UFVVF1npgSwhcvorqBKnxy6qE/edit?usp=sharing 87 | * Tool present for converting existing recipes 88 | * Goal: 89 | - Machine parsability (move information out of Jinja control structures, magic comments) 90 | - Cleaner model for multiple output recipes 91 | - https://github.com/mamba-org/conda-specs 92 | 93 | #### Open PRs 94 | * N/A 95 | 96 | ## Discussion 97 | 98 | * See: Subteam Updates/Specification Subteam 99 | * Extension on Depfinder project 100 | * CW: 101 | * https://github.com/regro/libcfgraph/tree/master/import_maps 102 | * https://conda-forge.org/blog/posts/2020-10-02-versions/ 103 | 104 | ## Action items 105 | 106 | * 107 | 108 | 109 | ## Previous Meetings 110 | 111 | 112 | ### Last Meeting 20200922 113 | 114 | #### Action Items 115 | 116 | * Take a look at the issue tracker and PR Tracker to gather some general view of outstading items 117 | * Have a Conda Community Triage / Conda Triage team so community members and contributors can start helping? 118 | * Have some sort of label to indicate issues that definitely should be closed? 119 | * Organize list on this hackmd on 'short term'/'medium term'/'long term' actionable items? 120 | * Check the draft for [text on the website](https://docs.google.com/document/d/1gECzDW4QluEM2-00xrxoseKLD2MaD9k_xvcwj3cxtMg/edit#heading=h.j4l7zepliw4q 121 | ) so design process can continue with some actual content. 122 | 123 | * Look at current PRs, identify ones that we can look closer at 124 | * Triage issues and PRs for next live review session 125 | * Permissions on labels- volunteers, please add name to list - will be available on slack 126 | * Email and Slack with email link to meeting notes 127 | * Roadmap 128 | 129 | 130 | #### Discussion 131 | * What responsibilities does the community want to have? 132 | * 133 | * What does the community feel like they are missing? 134 | 135 | * What parts do people feel hung up on? And are there other software models we can use so that those who want to drive/own it, can do so? Part of the approach might be to create separate efforts for those portions, that can move forward unencumbered. (MCS) 136 | * PRs and reviews 137 | * More people to review PRs? 138 | * Require more people who understand the code, but that's challenging at the moment. (large, intertwined code base that's not really approachable.) 139 | * Knowledge transfer (How can we help/train more people?) 140 | * Pair Programming to understand the code? 141 | * Recurrent Online sprints? 142 | * Live coding & pair programming? 143 | * Improving documentation 144 | * Deep dive into architecture? 145 | * Youtube? 146 | * https://www.anaconda.com/blog/understanding-and-improving-condas-performance 147 | * https://www.anaconda.com/blog/how-we-made-conda-faster-4-7 148 | * Michael Grant 149 | * CLA is potentially a barrier 150 | * Just having one is a barrier (not the actual content) 151 | * Some people do have objections at the level of the principle of it. 152 | * CLA always takes rounds with CEOs and then a lawyer call. They are quickly approved but until the call happens, months can pass. 153 | * Running test suite in local machine is also difficult (AS) 154 | * Potentially provide some easier way to build a testing docker container? 155 | * Lacking clear standards for what "compatability" means (AS) 156 | * Ways to identify issues that may be easier/low hanging fruit for the community tackle (GPC) 157 | * good first issue tag, https://github.com/conda/conda/issues?q=is%3Aopen+is%3Aissue+label%3Agood_first_issue 158 | * Comunication with PRs, especially when multiple PRs address the same issue 159 | * Better communication of bandwidth 160 | * Acknowldegement of receiving PRs 161 | * PR Review team? 162 | * What team to ask? - Update template? 163 | * Anaconda 164 | * Community 165 | * Better expectation communication 166 | * Open and public roadmap 167 | * How do PRs fit into the roadmap? 168 | * https://docs.github.com/en/enterprise/2.20/user/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#permission-levels-for-repositories-owned-by-an-organization 169 | * What is the path to introduce big changes? 170 | 171 | * Are there specific subprojects we can pull from the existing larger repositories that can be built off to facilitate community iteration and improvement? 172 | * 173 | * Can we define initiatives that the community can collaboratively drive forward? 174 | * 175 | * Can we nominate key community contributors who have enough experience with a project's codebase to be promoted to merge privileges? 176 | * 177 | ### Move to Issue Tracker 178 | 179 | 180 | ### Current Action Items -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Attribution 4.0 International 2 | 3 | ======================================================================= 4 | 5 | Creative Commons Corporation ("Creative Commons") is not a law firm and 6 | does not provide legal services or legal advice. Distribution of 7 | Creative Commons public licenses does not create a lawyer-client or 8 | other relationship. Creative Commons makes its licenses and related 9 | information available on an "as-is" basis. Creative Commons gives no 10 | warranties regarding its licenses, any material licensed under their 11 | terms and conditions, or any related information. Creative Commons 12 | disclaims all liability for damages resulting from their use to the 13 | fullest extent possible. 14 | 15 | Using Creative Commons Public Licenses 16 | 17 | Creative Commons public licenses provide a standard set of terms and 18 | conditions that creators and other rights holders may use to share 19 | original works of authorship and other material subject to copyright 20 | and certain other rights specified in the public license below. The 21 | following considerations are for informational purposes only, are not 22 | exhaustive, and do not form part of our licenses. 23 | 24 | Considerations for licensors: Our public licenses are 25 | intended for use by those authorized to give the public 26 | permission to use material in ways otherwise restricted by 27 | copyright and certain other rights. Our licenses are 28 | irrevocable. Licensors should read and understand the terms 29 | and conditions of the license they choose before applying it. 30 | Licensors should also secure all rights necessary before 31 | applying our licenses so that the public can reuse the 32 | material as expected. Licensors should clearly mark any 33 | material not subject to the license. This includes other CC- 34 | licensed material, or material used under an exception or 35 | limitation to copyright. More considerations for licensors: 36 | wiki.creativecommons.org/Considerations_for_licensors 37 | 38 | Considerations for the public: By using one of our public 39 | licenses, a licensor grants the public permission to use the 40 | licensed material under specified terms and conditions. If 41 | the licensor's permission is not necessary for any reason--for 42 | example, because of any applicable exception or limitation to 43 | copyright--then that use is not regulated by the license. Our 44 | licenses grant only permissions under copyright and certain 45 | other rights that a licensor has authority to grant. Use of 46 | the licensed material may still be restricted for other 47 | reasons, including because others have copyright or other 48 | rights in the material. A licensor may make special requests, 49 | such as asking that all changes be marked or described. 50 | Although not required by our licenses, you are encouraged to 51 | respect those requests where reasonable. More considerations 52 | for the public: 53 | wiki.creativecommons.org/Considerations_for_licensees 54 | 55 | ======================================================================= 56 | 57 | Creative Commons Attribution 4.0 International Public License 58 | 59 | By exercising the Licensed Rights (defined below), You accept and agree 60 | to be bound by the terms and conditions of this Creative Commons 61 | Attribution 4.0 International Public License ("Public License"). To the 62 | extent this Public License may be interpreted as a contract, You are 63 | granted the Licensed Rights in consideration of Your acceptance of 64 | these terms and conditions, and the Licensor grants You such rights in 65 | consideration of benefits the Licensor receives from making the 66 | Licensed Material available under these terms and conditions. 67 | 68 | 69 | Section 1 -- Definitions. 70 | 71 | a. Adapted Material means material subject to Copyright and Similar 72 | Rights that is derived from or based upon the Licensed Material 73 | and in which the Licensed Material is translated, altered, 74 | arranged, transformed, or otherwise modified in a manner requiring 75 | permission under the Copyright and Similar Rights held by the 76 | Licensor. For purposes of this Public License, where the Licensed 77 | Material is a musical work, performance, or sound recording, 78 | Adapted Material is always produced where the Licensed Material is 79 | synched in timed relation with a moving image. 80 | 81 | b. Adapter's License means the license You apply to Your Copyright 82 | and Similar Rights in Your contributions to Adapted Material in 83 | accordance with the terms and conditions of this Public License. 84 | 85 | c. Copyright and Similar Rights means copyright and/or similar rights 86 | closely related to copyright including, without limitation, 87 | performance, broadcast, sound recording, and Sui Generis Database 88 | Rights, without regard to how the rights are labeled or 89 | categorized. For purposes of this Public License, the rights 90 | specified in Section 2(b)(1)-(2) are not Copyright and Similar 91 | Rights. 92 | 93 | d. Effective Technological Measures means those measures that, in the 94 | absence of proper authority, may not be circumvented under laws 95 | fulfilling obligations under Article 11 of the WIPO Copyright 96 | Treaty adopted on December 20, 1996, and/or similar international 97 | agreements. 98 | 99 | e. Exceptions and Limitations means fair use, fair dealing, and/or 100 | any other exception or limitation to Copyright and Similar Rights 101 | that applies to Your use of the Licensed Material. 102 | 103 | f. Licensed Material means the artistic or literary work, database, 104 | or other material to which the Licensor applied this Public 105 | License. 106 | 107 | g. Licensed Rights means the rights granted to You subject to the 108 | terms and conditions of this Public License, which are limited to 109 | all Copyright and Similar Rights that apply to Your use of the 110 | Licensed Material and that the Licensor has authority to license. 111 | 112 | h. Licensor means the individual(s) or entity(ies) granting rights 113 | under this Public License. 114 | 115 | i. Share means to provide material to the public by any means or 116 | process that requires permission under the Licensed Rights, such 117 | as reproduction, public display, public performance, distribution, 118 | dissemination, communication, or importation, and to make material 119 | available to the public including in ways that members of the 120 | public may access the material from a place and at a time 121 | individually chosen by them. 122 | 123 | j. Sui Generis Database Rights means rights other than copyright 124 | resulting from Directive 96/9/EC of the European Parliament and of 125 | the Council of 11 March 1996 on the legal protection of databases, 126 | as amended and/or succeeded, as well as other essentially 127 | equivalent rights anywhere in the world. 128 | 129 | k. You means the individual or entity exercising the Licensed Rights 130 | under this Public License. Your has a corresponding meaning. 131 | 132 | 133 | Section 2 -- Scope. 134 | 135 | a. License grant. 136 | 137 | 1. Subject to the terms and conditions of this Public License, 138 | the Licensor hereby grants You a worldwide, royalty-free, 139 | non-sublicensable, non-exclusive, irrevocable license to 140 | exercise the Licensed Rights in the Licensed Material to: 141 | 142 | a. reproduce and Share the Licensed Material, in whole or 143 | in part; and 144 | 145 | b. produce, reproduce, and Share Adapted Material. 146 | 147 | 2. Exceptions and Limitations. For the avoidance of doubt, where 148 | Exceptions and Limitations apply to Your use, this Public 149 | License does not apply, and You do not need to comply with 150 | its terms and conditions. 151 | 152 | 3. Term. The term of this Public License is specified in Section 153 | 6(a). 154 | 155 | 4. Media and formats; technical modifications allowed. The 156 | Licensor authorizes You to exercise the Licensed Rights in 157 | all media and formats whether now known or hereafter created, 158 | and to make technical modifications necessary to do so. The 159 | Licensor waives and/or agrees not to assert any right or 160 | authority to forbid You from making technical modifications 161 | necessary to exercise the Licensed Rights, including 162 | technical modifications necessary to circumvent Effective 163 | Technological Measures. For purposes of this Public License, 164 | simply making modifications authorized by this Section 2(a) 165 | (4) never produces Adapted Material. 166 | 167 | 5. Downstream recipients. 168 | 169 | a. Offer from the Licensor -- Licensed Material. Every 170 | recipient of the Licensed Material automatically 171 | receives an offer from the Licensor to exercise the 172 | Licensed Rights under the terms and conditions of this 173 | Public License. 174 | 175 | b. No downstream restrictions. You may not offer or impose 176 | any additional or different terms or conditions on, or 177 | apply any Effective Technological Measures to, the 178 | Licensed Material if doing so restricts exercise of the 179 | Licensed Rights by any recipient of the Licensed 180 | Material. 181 | 182 | 6. No endorsement. Nothing in this Public License constitutes or 183 | may be construed as permission to assert or imply that You 184 | are, or that Your use of the Licensed Material is, connected 185 | with, or sponsored, endorsed, or granted official status by, 186 | the Licensor or others designated to receive attribution as 187 | provided in Section 3(a)(1)(A)(i). 188 | 189 | b. Other rights. 190 | 191 | 1. Moral rights, such as the right of integrity, are not 192 | licensed under this Public License, nor are publicity, 193 | privacy, and/or other similar personality rights; however, to 194 | the extent possible, the Licensor waives and/or agrees not to 195 | assert any such rights held by the Licensor to the limited 196 | extent necessary to allow You to exercise the Licensed 197 | Rights, but not otherwise. 198 | 199 | 2. Patent and trademark rights are not licensed under this 200 | Public License. 201 | 202 | 3. To the extent possible, the Licensor waives any right to 203 | collect royalties from You for the exercise of the Licensed 204 | Rights, whether directly or through a collecting society 205 | under any voluntary or waivable statutory or compulsory 206 | licensing scheme. In all other cases the Licensor expressly 207 | reserves any right to collect such royalties. 208 | 209 | 210 | Section 3 -- License Conditions. 211 | 212 | Your exercise of the Licensed Rights is expressly made subject to the 213 | following conditions. 214 | 215 | a. Attribution. 216 | 217 | 1. If You Share the Licensed Material (including in modified 218 | form), You must: 219 | 220 | a. retain the following if it is supplied by the Licensor 221 | with the Licensed Material: 222 | 223 | i. identification of the creator(s) of the Licensed 224 | Material and any others designated to receive 225 | attribution, in any reasonable manner requested by 226 | the Licensor (including by pseudonym if 227 | designated); 228 | 229 | ii. a copyright notice; 230 | 231 | iii. a notice that refers to this Public License; 232 | 233 | iv. a notice that refers to the disclaimer of 234 | warranties; 235 | 236 | v. a URI or hyperlink to the Licensed Material to the 237 | extent reasonably practicable; 238 | 239 | b. indicate if You modified the Licensed Material and 240 | retain an indication of any previous modifications; and 241 | 242 | c. indicate the Licensed Material is licensed under this 243 | Public License, and include the text of, or the URI or 244 | hyperlink to, this Public License. 245 | 246 | 2. You may satisfy the conditions in Section 3(a)(1) in any 247 | reasonable manner based on the medium, means, and context in 248 | which You Share the Licensed Material. For example, it may be 249 | reasonable to satisfy the conditions by providing a URI or 250 | hyperlink to a resource that includes the required 251 | information. 252 | 253 | 3. If requested by the Licensor, You must remove any of the 254 | information required by Section 3(a)(1)(A) to the extent 255 | reasonably practicable. 256 | 257 | 4. If You Share Adapted Material You produce, the Adapter's 258 | License You apply must not prevent recipients of the Adapted 259 | Material from complying with this Public License. 260 | 261 | 262 | Section 4 -- Sui Generis Database Rights. 263 | 264 | Where the Licensed Rights include Sui Generis Database Rights that 265 | apply to Your use of the Licensed Material: 266 | 267 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right 268 | to extract, reuse, reproduce, and Share all or a substantial 269 | portion of the contents of the database; 270 | 271 | b. if You include all or a substantial portion of the database 272 | contents in a database in which You have Sui Generis Database 273 | Rights, then the database in which You have Sui Generis Database 274 | Rights (but not its individual contents) is Adapted Material; and 275 | 276 | c. You must comply with the conditions in Section 3(a) if You Share 277 | all or a substantial portion of the contents of the database. 278 | 279 | For the avoidance of doubt, this Section 4 supplements and does not 280 | replace Your obligations under this Public License where the Licensed 281 | Rights include other Copyright and Similar Rights. 282 | 283 | 284 | Section 5 -- Disclaimer of Warranties and Limitation of Liability. 285 | 286 | a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE 287 | EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS 288 | AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF 289 | ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, 290 | IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, 291 | WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR 292 | PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, 293 | ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT 294 | KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT 295 | ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. 296 | 297 | b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE 298 | TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, 299 | NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, 300 | INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, 301 | COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR 302 | USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN 303 | ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR 304 | DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR 305 | IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. 306 | 307 | c. The disclaimer of warranties and limitation of liability provided 308 | above shall be interpreted in a manner that, to the extent 309 | possible, most closely approximates an absolute disclaimer and 310 | waiver of all liability. 311 | 312 | 313 | Section 6 -- Term and Termination. 314 | 315 | a. This Public License applies for the term of the Copyright and 316 | Similar Rights licensed here. However, if You fail to comply with 317 | this Public License, then Your rights under this Public License 318 | terminate automatically. 319 | 320 | b. Where Your right to use the Licensed Material has terminated under 321 | Section 6(a), it reinstates: 322 | 323 | 1. automatically as of the date the violation is cured, provided 324 | it is cured within 30 days of Your discovery of the 325 | violation; or 326 | 327 | 2. upon express reinstatement by the Licensor. 328 | 329 | For the avoidance of doubt, this Section 6(b) does not affect any 330 | right the Licensor may have to seek remedies for Your violations 331 | of this Public License. 332 | 333 | c. For the avoidance of doubt, the Licensor may also offer the 334 | Licensed Material under separate terms or conditions or stop 335 | distributing the Licensed Material at any time; however, doing so 336 | will not terminate this Public License. 337 | 338 | d. Sections 1, 5, 6, 7, and 8 survive termination of this Public 339 | License. 340 | 341 | 342 | Section 7 -- Other Terms and Conditions. 343 | 344 | a. The Licensor shall not be bound by any additional or different 345 | terms or conditions communicated by You unless expressly agreed. 346 | 347 | b. Any arrangements, understandings, or agreements regarding the 348 | Licensed Material not stated herein are separate from and 349 | independent of the terms and conditions of this Public License. 350 | 351 | 352 | Section 8 -- Interpretation. 353 | 354 | a. For the avoidance of doubt, this Public License does not, and 355 | shall not be interpreted to, reduce, limit, restrict, or impose 356 | conditions on any use of the Licensed Material that could lawfully 357 | be made without permission under this Public License. 358 | 359 | b. To the extent possible, if any provision of this Public License is 360 | deemed unenforceable, it shall be automatically reformed to the 361 | minimum extent necessary to make it enforceable. If the provision 362 | cannot be reformed, it shall be severed from this Public License 363 | without affecting the enforceability of the remaining terms and 364 | conditions. 365 | 366 | c. No term or condition of this Public License will be waived and no 367 | failure to comply consented to unless expressly agreed to by the 368 | Licensor. 369 | 370 | d. Nothing in this Public License constitutes or may be interpreted 371 | as a limitation upon, or waiver of, any privileges and immunities 372 | that apply to the Licensor or You, including from the legal 373 | processes of any jurisdiction or authority. 374 | 375 | 376 | ======================================================================= 377 | 378 | Creative Commons is not a party to its public 379 | licenses. Notwithstanding, Creative Commons may elect to apply one of 380 | its public licenses to material it publishes and in those instances 381 | will be considered the “Licensor.” The text of the Creative Commons 382 | public licenses is dedicated to the public domain under the CC0 Public 383 | Domain Dedication. Except for the limited purpose of indicating that 384 | material is shared under a Creative Commons public license or as 385 | otherwise permitted by the Creative Commons policies published at 386 | creativecommons.org/policies, Creative Commons does not authorize the 387 | use of the trademark "Creative Commons" or any other trademark or logo 388 | of Creative Commons without its prior written consent including, 389 | without limitation, in connection with any unauthorized modifications 390 | to any of its public licenses or any other arrangements, 391 | understandings, or agreements concerning use of licensed material. For 392 | the avoidance of doubt, this paragraph does not form part of the 393 | public licenses. 394 | 395 | Creative Commons may be contacted at creativecommons.org. 396 | 397 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Conda & Conda-Incubator Governance 2 | 3 | This document outlines the policies and procedures that manage the conda community. This document recognizes that, while packaging and package tooling is deeply important to all of us, participation in the organization is voluntary. Individual members of the core team, any sub-team, and external contributors choose to participate and may choose to leave at any time for any reason or for no reason. 4 | 5 | Larger organizations, such as for-profit businesses, that contribute code and support to the conda organization are welcome to (but not required to) maintain creative control of their contributions as long as such contributions adhere to the rules in this document. Such organizations are also welcome to cede creative & maintenance control of any specific project to the community as well. 6 | 7 | We deeply appreciate all good faith contributions. 8 | 9 | 10 | ## Code of Conduct 11 | 12 | The conda organization adheres to the [NumFOCUS Code of Conduct](https://www.numfocus.org/code-of-conduct). 13 | 14 | 15 | ## Naming & Manifest 16 | 17 | This document defines the conda organization as the body responsible for governing the tools, specifications, and libraries within the conda ecosystem, broadly speaking. This encompasses specific GitHub organizations, such as `conda` and `conda-incubator`. Authors of particular software projects, such as `conda` or `mamba`, are free to choose if and when their projects are included as part of the conda organization. 18 | 19 | This organization does not hold as part of its role the creation of any packages. The act of packaging itself has other organizations dedicated to their creation, such as Anaconda, conda-forge, & bioconda. 20 | 21 | 22 | ## Terminology 23 | 24 | 1. *Conda* or *The conda organization* : The conda organization defined here, including `conda` and `conda-incubator`. 25 | 2. *The conda project* : The actual conda software itself, as distinct from the conda organization. 26 | 3. *The conda ecosystem* : The broadest set of tools, packages, and people that use any conda related tooling. The conda organization is a subset of *the conda ecosystem*. Members of the ecosystem should not feel compelled or obligated to participate in the conda organization, though positive engagement is welcome. 27 | 28 | 29 | ## Teams & Roles 30 | 31 | Here are defined the primary teams participating in the conda organization's activities. 32 | 33 | * **core:** The core team is the governing body over the entire conda organization. Members of the core team have full voting rights within the organization. Members of core are the face of the organization, and are responsible for officially interfacing with external communities, organizations, non-profits, and companies. The core team may create new sub-teams, as appropriate. Each member of core is entitled to one vote on all elected matters. 34 | * **maintainers:** A maintainer is an individual or group responsible for the management of a software project consisting of one or more repositories and any software releases. Maintainers have the ability to merge pull requests into the repositories of the software project they maintain and produce releases of that software project. 35 | * **external contributors:** This group encompasses all others who are not on core or maintainers. This includes first-time contributors, collaborators, and original authors. They have no special rights within the conda organization itself. 36 | * **emeritus-core:** Core members that are inactive (commits, GitHub comments/issues/reviews, dev meetings, and voting on polls) in the past six months will be asked if they want to become emeritus-core developers. One week after asking, if the inactive core member has not responded, they will be automatically moved to emeritus status. Any core member can also request to become emeritus if they wish to do so (e.g. taking a sabbatical or long vacation). Emeritus core members can still vote and be brought back to active core anytime, the only difference is that emeritus-core votes will not count towards the total core members when computing the necessary votes a poll needs to meet quorum. The `core.csv` list should be updated when change in the status of a member occurs. 37 | 38 | 39 | ## Sub-Teams 40 | 41 | The core team may elect to create new sub-teams for managing the daily business of the organization. While sub-teams may have non-core members, every sub-team must have at least one core team member at all times. If a sub-team fails to have a core team member for more than 1 week, that team is considered to be dissolved. A new sub-team would need to be established by the core in order to reinstate the activity. 42 | 43 | Sub-teams have a charter that is either *dynamic* or *static*. 44 | 45 | * A **dynamic** charter means that the sub-team is self-organizing, with respect to its own internal policies, procedures, and membership. A sub-team may choose to modify its membership independent of the core team. For example, a Google Summer of Code team could be a good candidate for a dynamic charter. Alternatively, maintenance teams also have a dynamic charter, except for voting on commit rights and membership, as detailed below. 46 | * A **static** charter means that all membership decisions and non-trivial policies changes must be approved by the core team. For example, a finance team may require a static charter. 47 | 48 | All sub-teams must adhere to the governance, policies, and procedures of the conda organization at all times. 49 | 50 | 51 | ## Community, Federated, & Attic Maintenance 52 | 53 | The conda organization acknowledges that project contributions may come from a variety of sources. To this end we define two maintenance categories for our projects. 54 | 55 | * A **Community** maintained project is one where the development, ownership, and maintenance are controlled by the conda organization at large. Contributors keep the copyright for code they wrote and submit for inclusion to the respective project under the terms of license of that project. 56 | * A **Federated** project is maintained by a sub-team of *the conda organization*. Such projects maintain control of distribution and licensing via the project's sub-team. Federated projects are not controlled by the community at large. Still, as part of the conda organization, federated projects agree to the terms of this governance document, including but not limited to the Code of Conduct. 57 | * An **Attic** project is one which is unmaintained or clearly superseded by another project. No support is provided or anticipated for these projects. 58 | 59 | All projects must prominently list their maintenance status in their README and provide clear instructions on where people can seek help for the project. The possible maintenance statuses are one of `federated` or `community` or `attic`. 60 | 61 | All conda projects must use an [OSI approved software license](https://opensource.org/). We recommend and encourage the use of [BSD-family licenses](https://opensource.org/licenses/BSD-3-Clause). We recommend that specifications and documentation use [Creative Commons licenses](https://creativecommons.org/). 62 | 63 | Project maintenance teams (defined below) decide among themselves whether or not to move their projects in and out of `attic` status. Core must be notified before this change and will mark `attic` projects as archived. 64 | 65 | 66 | ### The Rationale for Federated Projects 67 | 68 | Federated projects enable conda ecosystem projects to exist under the same umbrella organization, while maintaining community standards. They acknowledge the time and investment the developers and authors have put into their creations and that in certain cases they wish to maintain creative control. A federated system also allows for a phased transition plan for projects to become increasingly community maintained over time. 69 | 70 | Federated projects cannot expect that the community will maintain or support the project as long as the project remains federated. If/when a federated project transitions to the community maintenance model, this project will be maintained and supported by the community. 71 | 72 | Federated projects are under no obligation to have a transition plan or any intention of becoming a community maintained project. However, this is strongly encouraged and community maintained projects are seen as the ideal. Federated projects are seen as the reality. 73 | 74 | 75 | ## Incubation 76 | 77 | All projects start their journeys in an experimental or unstable state. To this end, we delineate stable projects as living in the `conda` GitHub organization. Therefore, projects new to the conda organization & governance must begin their inclusion here in the `conda-incubator` organization. The barrier to entry for a project to be added to the incubator should be very low. A vote from core is required to move a project from incubation to the main GitHub organization. 78 | 79 | The member of core sponsoring the incubation is responsible for ensuring that basic legal requirements have been met that allow for the incubation. For example, trademark usage and license terms must been checked prior to incubation. 80 | 81 | 82 | ## Maintenance Teams 83 | 84 | A maintenance team is a sub-team with a dynamic charter, except for a few caveats as detailed here. They exist to maintain a specific project (or possibly set of projects). Each project in `conda` or `conda-incubator` should belong to exactly one maintenance team. This team is granted write access to the repos associated with the project. 85 | 86 | The initial maintenance team for projects in the `conda` organization are specified in the vote to move a project from the incubator to the main `conda` organization. As this vote has a 60% threshold and sub-team formation is only a 50% threshold, the vote for adding a project to the main `conda` organization can serve both purposes. Maintenance teams for incubating projects do not need a vote for their creation. Instead they are created when the project is moved into `conda-incubator`. 87 | 88 | For federated and incubating projects, the maintenance team decides among themselves on how to add and/or remove members from the maintenance team. Further, maintenance teams for incubating projects are exempted from the requirement to have at least one core member. For a community maintained project, a petition for commits right is made to the current members of the maintenance team for that project. If this petition passes according to the voting rules for "Nominate new member of a maintenance team" below, the petitioner is granted write access and added to the team. 89 | 90 | Members of **core** are excluded from these votes and retain commits rights to all community projects as stated above. They can add or remove themselves from maintenance teams as they see fit in order to indicate which projects they are involved with, have a say in voting for write access petitions, etc. Members of core may not add themselves to a maintenance team in order to vote on a petition for commit access if they were not already on that team when the petition was made. 91 | 92 | 93 | ## Voting 94 | 95 | This section presents descriptions and criteria for voting items in the conda organization. The core team is the only team with voting rights. Members of core may also call a vote on any topic. The restrictions on calling a vote are as follows: 96 | 97 | * There must only be one vote active on a particular item at any time. 98 | * The act of calling for a vote must not itself violate the code of conduct. For example, Sam repeatedly called for votes immediately after a previous vote failed to achieve Sam's result. Sam is attempting to bully other members of core into agreeing, and is thus violating the code of conduct. 99 | * Voting yes moves the proposal forward; 100 | Voting no is the only way to express opposition to the proposal; 101 | There is always an option to abstain from voting; 102 | Not voting is discouraged, but non-votes do not count as "no", "yes", or "abstain". 103 | * Core members must explicitly abstain from a vote via making a comment on the PR/issue or selecting the "abstain" option. Simply not voting at all doesn't count as an abstention. 104 | * Abstentions count towards the quorum but are excluded when computing if a vote passes. 105 | 106 | Voting items are labeled as either **standard** or **sensitive**. Standard items are ones where public record and discourse is preferable. Sensitive voting items are ones where the results of the vote should remain private to the voters after the vote has occurred. Sensitive votes should take place on a secure anonymous voting platform in order to retain election integrity and anonymity. (We may use `Polys `_ and `the Helios voting system `_, but are open to any secure, anonymous system.) The email capability of your chosen voting platform should be used for sending voting invitations and reminders, and you should use the email list from `core.csv` as the authoritative list of emails to use. 107 | 108 | The default voting period is 1 week (7 days). This may be modified at the time when a vote is called, but may never be less than one week modulo exceptions for some time-sensitive votes below. 109 | 110 | Additional requirements may apply in case low turnouts have to be handled, see "Quorum" below. 111 | 112 | To call for a standard vote, here is a template Issue/PR comment: 113 | 114 | 115 | @conda/core 116 | This PR falls under the {policy} policy, please vote and/or comment on this PR. 117 | This PR needs {policy_percent} of core to vote yea to pass. 118 | To vote please leave Approve (yea) or Request Changes (nay) reviews. 119 | If you would like changes to the current language please leave a comment or push to this branch. 120 | This vote will end on {date}. 121 | 122 | A ``vote`` label must be applied to the PR or issue. 123 | 124 | ---- 125 | 126 | **Posting results:** To maintain the historical record, the outcome of any standard vote which invoked the timeout rules below should be recorded in the "vote-results" folder of our documentation. 127 | 128 | Each "timed out" vote should be its own file. The filename should reflect the topic and the date that the vote opened. The file should contain at least: 129 | 130 | * vote description 131 | * vote policy 132 | * vote totals 133 | * Poll open and close dates 134 | * documentation of the vote reminders as detailed below 135 | 136 | Non-timed-out vote results should be documented in github PR/issue upon which the voting happened. A ``vote`` label must be applied to the PR or issue. 137 | 138 | ---- 139 | 140 | **Quorum:** All percentages below express *both* required participation, as a fraction of the active core team, as well as the fraction of that fraction who vote affirmatively (i.e. vote `yes`) on the issue. For example, in a vote requiring 50%, with 18 active core members, at least 9 must vote; if 9 vote, there must 5 affirmative votes. If 13 members vote, 7 must be affirmative. 141 | 142 | Because everyone is busy and it is difficult sometimes to get quorum, votes not achieving quorum will eventually time out on their set end date. When this happens, the current participation level is taken for what it is, and the percentage of affirmative votes is calculated from whatever the vote total is at that time. In order for a timeout to occur, the vote must have: 143 | 144 | * been open for at least 2 weeks 145 | * been presented and discussed at a Core team meeting 146 | * been advertised on at least 3 separate occasions on the core chat channel (beginning of voting period, middle, and one day prior to proposed timeout) 147 | * been sent to core members via email. Email reminders must have been sent similarly to the core chat channel: at least 3 times, occurring as beginning of voting period, middle, and one day prior to proposed timeout. 148 | 149 | Extending the above example, if 9 people are required for a quorum, but only 7 have voted, those 7 votes can form the basis of a completed vote after the above conditions are met. 4 votes within those 7 would be needed to pass the vote. 150 | 151 | To post a timeout reminder, here is a template comment: 152 | 153 | @conda/core 154 | This vote falls under the {policy} policy, please vote and/or comment on this PR. 155 | This vote needs {policy_percent} of core to vote yea to pass. 156 | This vote presently has {current_voters}, and needs {policy_percent * core - current_voters} more for quorum. 157 | It is proposed that this vote will time out and be evaluated with the current votes in {days}, on {date}. 158 | To vote please leave Approve (yea) or Request Changes (nay) reviews. 159 | 160 | To declare a standard vote "timed out," the person making such a declaration must post a pull-request adding a vote record to the `vote-results` folder. The declaration PR should be merged by the first core member who is available to verify that the requirements for the timeout have been met, based on their own personal records. 161 | 162 | ---- 163 | 164 | **Voting Total Examples** 165 | 166 | Assume the core team has 10 active members, 2 emeritus members, and the vote threshold is 50%. 167 | 168 | 1. Among core there are 3 "yes", 2 "no", and 1 "abstain" votes. No emeritus votes were recorded. This vote has reached quorum (3 + 2 + 1 = 6 which is at least 50% of 10). It also passes since it recorded 3 "yes" votes and 2 "no" votes giving 3/5 (60%) which is at least 50% of 5. 169 | 170 | 2. Among core there are 4 "yes", 2 "no", and no abstentions. One emeritus core member voted "no". This vote has reached quorum (4 + 2 = 6 which is at least 50% of 10). It has also passed since it recorded 4 "yes" votes and 3 "no" votes giving 4/7 which is at least 50% of 6. 171 | 172 | 3. Among core there are 3 "yes" votes, "1" no vote and no abstentions. No emeritus members voted. Further the timeout rules above **were** invoked. This vote has thus reached quorum and it has passed since 3/4 (75%) is at least 50%. 173 | 174 | 4. Among core there are 3 "yes" votes, "1" no vote and no abstentions. No emeritus members voted. Further the timeout rules above **were not** invoked. This vote has not reached quorum and should be extended or redone. 175 | 176 | ---- 177 | 178 | **Enhancement Proposal Approval:** When ready, the proposer may call for a vote on an existing conda enhancement proposal (EP). This requires a super-majority (60%) to pass so that the decision to accept the EP is unequivocal and we have ensured that consensus has been reached. 179 | 180 | * Standard 181 | * 60% Majority to pass 182 | 183 | ---- 184 | 185 | **Nominate new member of core:** The proposer must provide a sufficient justification as to why the nominee should be welcomed into core. Prior service to the community, including but not limited to: working on conda organization projects, writing conda specifications, and helping to bridge disparate communities are an important part of the nomination process. 186 | 187 | * Sensitive 188 | * 2/3rds Majority to pass 189 | 190 | ---- 191 | 192 | **Nominate new member of a maintenance team:** The proposer must provide a sufficient justification as to why the nominee should be welcomed into the maintenance team. Prior work on the project is an essential part of the nomination process. The voting body for these votes are the current members of the maintenance team at the time the nomination is made. 193 | 194 | * Sensitive 195 | * 50% Majority or at least 3 yes votes, whichever is smaller, to pass 196 | 197 | ---- 198 | 199 | **Sub-team Formation:** Proposers must specify the name, role & responsibility, members, and charter (dynamic or static) of any new sub-teams. 200 | 201 | * Standard 202 | * 50% Majority to pass 203 | 204 | ---- 205 | 206 | **Sub-team Dissolution:** Proposers must specify the name and justification for why a sub-team should be dissolved. 207 | 208 | * Standard 209 | * 50% Majority to pass 210 | 211 | ---- 212 | 213 | **Add Project/Repo to Incubator:** Any single member of core may add a project to the incubator, given the knowledge and consent of the author. The low barrier to entry here is because we want to encourage innovation, experimentation, and growth. Members of core are encouraged to use common sense when adding new projects to the `conda-incubator` organization. 214 | 215 | * Standard 216 | * 1 member of core willing to add the repository, no vote required 217 | 218 | ---- 219 | 220 | **Remove Project/Repo from Incubator:** While we do not anticipate this ever being necessary, if the situation arises where a project needs to be removed from the incubator, two potential options are available, depending on the copyright & maintenance of the project. 221 | 222 | In the first, easy case, the incubated project has been wholly developed and maintained by the authors. Here, the project should be allowed to leave incubation if the developers of that project decide and consent to leave. No vote from core is required. A willing core member may be needed to transfer the repository, though. 223 | 224 | In the second case, the incubated project has been communally developed by other members of the conda organization AND/OR the copyright of the project has been transferred to the conda organization, NumFOCUS, or a similar entity that is larger than the developers/copyright holders at the time initial incubation. In this case, core must decide whether or not to allow the project to leave. A simple vote is required. 225 | 226 | * Standard 227 | * 50% Majority to pass 228 | 229 | ---- 230 | 231 | **Incorporate a Software Project into the main `conda` Organization:** At some point, many projects will want to be included in the main `conda` GitHub (or otherwise) organization. Moving a project into this organization can be done with a super-majority vote from core. There are no strict criteria for when a project is ready, stable, or viable for this step. Rather, members of core are entrusted to use their objective best judgment and common sense when making this determination. Adherence to conda specifications is a particularly important aspect of the decision to include a project in the main conda organization. The membership of the initial maintenance team should be included in the vote information. There is not requirement for a project to incubate before a vote of this nature can be called. This kind of vote applies only to software projects. Specifications are covered separately. 232 | 233 | * Standard 234 | * 60% Majority to pass 235 | 236 | ---- 237 | 238 | **Graduate a Specification Project from Incubation to Main:** The purpose of specifications is to be fully endorsed by the main conda organization. Graduating a specification can be done with a super-super-majority vote from core. The purpose of this is to ensure that the overwhelming majority of the conda ecosystem agrees with the goals & aims of the specification, even if no software implements it at the time of the vote. Specifications are highly encouraged to be written and developed in `conda-incubator` so they can accrue comments and changes. New versions of a specification (beyond simple typographical and grammatical fixes) are considered new specifications for purposes of voting here. 239 | 240 | In spite of the high threshold for approval here, we highly encourage the writing of specification documents. 241 | 242 | * Standard 243 | * 70% Majority to pass 244 | 245 | ---- 246 | 247 | **Lock an Issue, Pull Request, Thread:** Occasionally, discussions become toxic and antithetical to the goal of fostering the conda community. Members of core have the right to lock the thread in an "ask for forgiveness and not for permission" way so bad situations are handled quickly. The lock must be justified in the thread itself with a text explaining the reasons for locking and how the participants can contest it. 248 | 249 | * Standard 250 | * No need for voting to lock a thread 251 | 252 | ---- 253 | 254 | **Block a Contributor:** In extreme cases, such as repeated harassment, it may become necessary to block a user completely from participating in all conda organization activities. This should not be done lightly, but it may be necessary to do so expediently. Shorter voting periods (at minimum 24 hrs) are allowed here. The proposer of the block must provide ample justification as to why this is needed. 255 | 256 | * Sensitive 257 | * 60% Majority to pass 258 | 259 | ---- 260 | 261 | **Remove member of core:** The proposer must provide an overwhelming justification as to why the member core should be removed. 262 | 263 | * Sensitive 264 | * 75% Majority to pass 265 | 266 | ---- 267 | 268 | **Spending of funds:** Proposers must specify the purpose, time limit, and source of funds that are to be spent. Purpose and time limit should be general enough in order to prevent excessive voting. For example, recurrent items (such as CI) should not need to be voted on each and every month. Instead, they should exist for a defined period of time (e.g. until the current migration ends, or for the next year). For such recurring expenses, the person coordinating spending the funds can choose to cancel the spending if it is deemed no longer necessary or cost-effective without calling another vote, although they should make reasonable efforts to notify the rest of core before doing so. 269 | 270 | Prior to their submission, grant proposals must be supplied to the core members and a vote called under the `Spending of funds` policy. If the vote does not pass the proposal is not to be submitted in its current form and an additional round of voting is required on any subsequent draft. If the vote passes and the funds are awarded, further voting to spend the funds is not required. 271 | 272 | * Standard 273 | * 50% Majority to pass 274 | 275 | ---- 276 | 277 | **Modifying the governance document:** The voting should happen in the PR in question and there must be a call to `@conda/core`. The voting period must be open for at least one core member meeting cycle to allow for clarification questions and discussions. 278 | 279 | * Standard 280 | * 75% Majority to pass 281 | 282 | ---- 283 | 284 | All other voting items are considered to be standard and require a 50% majority to pass. 285 | 286 | 287 | ## Ratification of this Document 288 | 289 | In order initiate the conda organization described here, anyone is able to participate and become a member of the starting core team (or emeritus team). In order to be founding core team member, an individual must perform the following actions: 290 | 291 | 1. Each individual has to participate in the vote to ratify this governance document, 292 | 2. Each individual has to personally add their own name - and only their own name - to the core.csv or emeritus.csv file. 293 | 294 | These criteria are intended to be inclusive while having founding core members demonstrate a real interest in participating. 295 | 296 | Interested individuals should use their own judgment and discretion when determining if they should be a founding core member. Being a founding core member implies the intention to participate in this organization through voting, governance discussions, core meetings, etc. If you are not in a current position to have this level of engagement but anticipate this level of engagement at a future date, consider signing on with initial emeritus status. 297 | 298 | There is no obligation or need to become a core member, if this is not relevant to you. This organization will be making a number of sub-teams, which we welcome and invite the broader conda ecosystem to participate in, when it is of interest. 299 | 300 | We encourage everyone to find their niche in this organization, and welcome participation at any and all levels. 301 | 302 | The vote for ratification of this governance document is public and requires a 75% majority of those participating in the vote to pass. 303 | 304 | **Timeline:** 305 | 306 | 1. A draft version of this document will be proposed for general review and comment (RFC). This RFC period must last at least 7 days before a vote can be called. 307 | 2. A vote on the reviewed document is called and will be open for exactly 7 days. 308 | * If the vote fails, return to step 1. 309 | * If the vote passes, continue to step 2. 310 | 3. Individuals who participated in the vote are able to add themselves to the core.csv or emeritus.csv file. After doing so, they are considered members of the core team. 311 | 312 | If for some reason someone is unable to make the timeline when the vote is called, that person can always be added to the core team later via the normal process. 313 | 314 | 315 | ## Current Members of Core 316 | 317 | In alphabetical order, 318 | 319 | {{ core_members }} 320 | 321 | 322 | ## Emeritus members 323 | 324 | In alphabetical order, 325 | 326 | {{ emeritus_members }} 327 | 328 | 329 | ## Document History 330 | 331 | This document was initially written by Anthony Scopatz, CJ Wright, Matthew R. Becker, Uwe Korn, and Eric Dill. 332 | 333 | This document is released under the CC-BY 4.0 license. --------------------------------------------------------------------------------