specutils: Add Brigitta as maintainer because she already is in the team #548
Conversation
because she already is in the team
|
No need to add me, I don't have time or plans for specutils |
|
@bsipocz , then should I remove you from the (GitHub) team? The team is already there, so I am just trying to sync things up. I can do it one way or the other. Please confirm. Thanks! |
|
Btw, the release team was needed to be added here as historically specutils incompatibility with RC was a release blocker for astropy... |
Hmm, good point, though that could happen to any of our downstream packages. We only have two release managers now and they both at limited capacity. I'll reconsider this if it happens again but hopefully not with better CI setup (we improved it recently), more active maintainers, and rudimentary https://github.com/astropy/astropy-integration-testing |
|
As stated in #548 (comment) , I will close this without merge and sync the GitHub team accordingly. Thank you for your prompt response! |
I took the liberty to clean up
specutilsaccess by doing the following:astropy-contributorsTeam with Read access. Not sure what this is for. I didn't see it listed inspecreduce.astropy-project-release-team. This team is forastropyrelease and it is not on the hook for Coordinated packages that are supposed to have their own maintainers.devops-maintainersfrom Admin to Maintain. I think the infrastructure is okay now, so DevOps does not need to be so involved now but I have no doubt the Admin access was needed at some point.specutils-maintainersbut sync it with the Team page (hence this PR). I recognize that every package gets maintained differently but if you find yourselves needing sub-team with Admin and not everyone here, I would be happy to help you set it up.cc @keflavich @eteq @nmearl @bsipocz @rosteen