Skip to content

Conversation

@pllim
Copy link
Member

@pllim pllim commented Aug 23, 2023

@kecnry and @cshanahan1 already have maintainer access to specreduce for a while as individuals and they are actively maintaining the package. I have taken the liberty to clean up specreduce and specreduce-data permissions by doing the following and this PR just making their existing jobs official.

  • Remove individuals with only Read access to specreduce. This is unnecessary because it is a public repo. If you want them to have access for triage, create a proper triage team. Refrain from providing arbitrary individual access.
  • Added Kyle and Clare to https://github.com/orgs/astropy/teams/specreduce-maintainers and downgrade that team's access from Admin to Maintain.
  • Created a new admin team with existing admins (@eteq and @tepickering) and give them back their existing access but under a new team name.

All in all, there are no changes to existing access. I am just making things official. I think it is nice to give people who are doing the work some credit officially.

as maintainers because they already are.
@hamogu
Copy link
Member

hamogu commented Oct 20, 2023

Only approving comments on this and the two week comment period has run out, so I'm merging.

@hamogu hamogu merged commit f2b8e82 into astropy:main Oct 20, 2023
@pllim pllim deleted the specreduce-maintainers branch October 23, 2023 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants