Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Requesting New Sub-team/Project Team: Quansight #225

Open
kenodegard opened this issue Mar 26, 2025 · 6 comments
Open

Requesting New Sub-team/Project Team: Quansight #225

kenodegard opened this issue Mar 26, 2025 · 6 comments

Comments

@kenodegard
Copy link
Contributor

kenodegard commented Mar 26, 2025

Type of Team

Sub-team (Dynamic Charter)

Team Name

Quansight

Team Handle

quansight

Members

@jaimergp
@trallard
@soapy1
@peytondmurray

Charter

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

Note

This mirrors the request for the Anaconda Inc. sub-team (#222).

Warning

A GitHub team with this name already exists with the members listed above, this request is to make it an officially sanctified sub-team.

Responsibilities

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

  1. Maintain GitHub project boards to track and publicly share Quansight's conda-related work, e.g., Quansight <> Anaconda Project Board
  2. Coordinate Quansight's conda development efforts with community initiatives
  3. Provide visibility into Quansight's conda roadmap for the conda community
  4. Participate in conda community discussions representing Quansight'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 Quansight and the community. The team will focus on making Quansight's conda development plans visible to the community and finding opportunities for collaboration.

Additional Information

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

@jaimergp
Copy link
Contributor

Thank you! I agree and consent to being added.

@peytondmurray
Copy link

Thanks for this! I consent to be added.

@trallard
Copy link
Member

Thanks! I also consent.

@soapy1
Copy link

soapy1 commented Mar 26, 2025

Thank you! I consent to be added.

@jaimergp
Copy link
Contributor

I think we are all set here @kenodegard

@kenodegard
Copy link
Contributor Author

In that case it looks like it is time to request a vote from the steering council

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants