---
# System prepended metadata

title: 2025-04-09 Conda Community Meeting
tags: [meeting-notes]

---

---
tags: [meeting-notes]
---
# 2025-04-09 Conda Community Meeting

[Zoom link](https://zoom.us/j/9138593505?pwd=SWh3dE1IK05LV01Qa0FJZ1ZpMzJLZz09) · [What time is the meeting in my time zone](https://dateful.com/convert/utc?t=5pm)

Various parts of the conda community gather on a regular basis. This meeting brings together all of these sub-communities for a community wide call.

## Attendees

| Name                   | Initials | Affiliation  | GH Username      |
| ---------------------- | -------- | ------------ | ---------------- |
| Jaime Rodríguez-Guerra | JRG      | Quansight/sc | jaimergp         |
| John Kirkham           | JK       | NVIDIA/cf    | jakirkham        |
| Matthew R Becker       | MRB      | conda-forge  | beckermr         |
| Tania Allard           | TA       | Quansight    | trallard          |
|                        |          |              |                  |
|                        |          |              |                  |
|                        |          |              |                  |
|                        |          |              |                  |
|                        |          |              |                  |
|                        |          |              |                  |

4 people in total

## Introductions

- [ ]

## Announcements

- [ ] (JL: most Anaconda staff are at a company meeting during the meeting this week and won't be able to attend)
- [ ] JRG: CEP vote for `environment.yml` until Apr 21: https://github.com/conda/ceps/pull/81

## New Agenda Items

- [ ] (JK) Sub-team structure
    - https://github.com/conda/governance/issues/222
    - https://github.com/conda/governance/issues/225
    - https://github.com/conda/governance/issues/226
    - MRB: The original intent of the subteams section in the governance was _not_ to tie every Github team to a governance-defined subteam.
    - JRG: Add note about that in the governance?
    - MRB: If the intent is just to provision access to project boards, suggest to create per-project-board / per-contract teams without going through a vote.
    - TA: Add badges / repo tags to each repo to list them as community or federated.
