-
Notifications
You must be signed in to change notification settings - Fork 33
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
Create a steering council GitHub team in the conda GitHub organization #135
Comments
@jezdez We need to add emeritus members to this steering-council team and ensure they have commit access to the governance repo. |
@beckermr Good call! |
Thank you! |
For people not in the org, you may need to accept an invitation here |
@CJ-Wright You're the only steering council member not having accepted the invitation. I've resent it now, please let me know if there are any concerns. @minrk @scopatz @prusse-martin @myancy-anaconda @teoliphant @cjmartian @awwad I've sent you another invite to join the steering-emeritus team, in case you've missed it. |
@jezdez the teams here are getting out of date as people move back and forth from emeritus. (Sorry that's me!) Can we automate the changes or maybe add more team maintainers who can make the changes? |
It's on my TODO list, not super high, but @kenodegard has recently looked at it via #147, and this has some dependencies on the way the legacy conda org is set up currently, via Anaconda's Enterprise billing |
Here's the list of people to add to the new team within the conda org (based on https://github.com/conda/governance/blob/3fe0950d7ee58637fb36b5c1249b83f0bc864a05/steering.csv):
The text was updated successfully, but these errors were encountered: