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: prefix.dev #226

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

Requesting New Sub-team/Project Team: prefix.dev #226

kenodegard opened this issue Mar 27, 2025 · 6 comments

Comments

@kenodegard
Copy link
Contributor

kenodegard commented Mar 27, 2025

Type of Team

Sub-team (Dynamic Charter)

Team Name

prefix.dev

Team Handle

prefix.dev

Members

@wolfv
@baszalmstra
@ruben-arts
@nichmor
@Hofer-Julian
@tdejager

Charter

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

Note

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

Responsibilities

This team exists to facilitate communication and coordination between prefix.dev and the broader conda community. Specifically, the team has the option to:

  1. Maintain GitHub project boards to track and publicly share prefix.dev's open source efforts within the conda community
  2. Coordinate prefix.dev's development efforts with community initiatives
  3. Provide visibility into prefix.dev's roadmap for the conda community
  4. Participate in conda community discussions representing prefix.dev'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 prefix.dev and the conda community. The team will focus on making prefix.dev's development plans visible to the community and finding opportunities for collaboration.

Additional Information

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

@baszalmstra
Copy link
Contributor

Thanks! I consent to being added.

@Hofer-Julian
Copy link

I consent to being added!

@wolfv
Copy link
Contributor

wolfv commented Mar 28, 2025

me too.

@tdejager
Copy link

Me too!

1 similar comment
@nichmor
Copy link

nichmor commented Mar 28, 2025

Me too!

@tdejager
Copy link

Same here!

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

6 participants