-
Notifications
You must be signed in to change notification settings - Fork 34
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
Comments
Thanks! I consent to being added. |
I consent to being added! |
me too. |
Me too! |
1 similar comment
Me too! |
Same here! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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
The text was updated successfully, but these errors were encountered: