Requesting New Sub-team/Project Team: Anaconda

[kenodegard]

Type of Team

Sub-team (Dynamic Charter)

Team Name

Anaconda

Team Handle

anaconda

Members

@jezdez
@chenghlee
@jjhelmus
@dholth
@travishathaway
@george-lorch
@ForgottenProgramme
@marcoesters
@schuylermartin45
@kenodegard

Charter

A dynamic charter since membership is based on Anaconda Inc. employment. Membership will be self-managed by Anaconda Inc. without requiring Steering Council approval for each member change.

Responsibilities

This team exists to facilitate communication and coordination between Anaconda Inc. and the broader conda community. Specifically, the team will:

1. Maintain GitHub project boards to track and publicly share Anaconda's conda-related work, e.g.:

• Quansight <> Anaconda Project Board
• Requesting New GitHub Project: Anaconda infrastructure#1134

3. Coordinate Anaconda's conda development efforts with community initiatives
4. Provide visibility into Anaconda's conda roadmap for the conda community
5. Participate in conda community discussions representing Anaconda's perspective

Scope

This is NOT a project team with commit access to any repositories. The scope is limited to communication and coordination activities that improve transparency between Anaconda Inc. and the community. The team will focus on making Anaconda's conda development plans visible to the community and finding opportunities for collaboration.

Additional Information

Zulip Thread: #general > Sub-teams for planning purposes

[jezdez]

For the record, this new sub-team will require a vote by the steering council pursuant to the voting item "Sub-team Formation".

It would be important to give the steering council more information about what the purpose of this team is.

One condition to participating in the subteam as mentioned above would be employment at Anaconda Inc (and subsidiaries), with a scope on GitHub project board maintenance (e.g. to coordinate work with community efforts).

But it would not be a project team, like @conda/conda-maintainers or @conda/builds-tools, since there is no need for commit access to specific code repositories, and it's not focused on a specific project either. It's more about communication of Anaconda's current conda-related work, publicly, to provide a roadmap of Anaconda's efforts to the rest of the conda community.

@kenodegard I think it would be good to update the scope of the team, or even switch to a static charter to spell this out a little more.

[kenodegard]

As I read the governance doc, a static charter would mean the sub-team is not self-governing and any new members of this team will require a vote by the steering council.

[jezdez]

@kenodegard yeah, that's the tricky part, self-governance seems useful for company-focused teams, you're right. I like the scope and responsibilities you listed above, that should clarify it that they are narrowly focused and not walk us back to catch-all teams like the old (and wrongly named) "conda-core" team.

[kenodegard]

Are we ready to request a vote from the Steering Council on this?

[jezdez]

Yeah, I was going to start the vote tomorrow