Skip to content

Move directors to launching pad, give them blog permissions #1786

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

Merged
merged 1 commit into from
May 3, 2025

Conversation

ehuss
Copy link
Contributor

@ehuss ehuss commented Apr 23, 2025

I think we can trust directors to post on the blog, so lets give them permissions to do that so they don't need to bug anyone else to do it.

To accommodate the addition of permissions, this promotes it from a marker team to a team in the launching pad (which we are planning to rebrand as a home for cross-cutting teams). There's no expectation that this would change anything in practice, and the membership is still chosen by the council.

cc @rust-lang/leadership-council @carols10cents @JakobDegen @rylev @scottmcm @spastorino

I think we can trust directors to post on the blog, so lets give them
permissions to do that so they don't need to bug anyone else to do it.

To accommodate the addition of permissions, this promotes it from a
marker team to a team in the launching pad (which we are planning to
rebrand as a home for cross-cutting teams). There's no expectation that
this would change anything in practice, and the membership is still
chosen by the council.
Copy link

Dry-run check results

[WARN  sync_team] sync-team is running in dry mode, no changes will be applied.
[INFO  sync_team] synchronizing github
[INFO  sync_team] 💻 Team Diffs:
    📝 Editing team 'rust-lang/inside-rust-reviewers':
      Adding member 'rylev' with member role
      Adding member 'scottmcm' with member role
      Adding member 'spastorino' with member role

@traviscross
Copy link
Contributor

Agreed this is the right handling.

Copy link
Member

@jamesmunns jamesmunns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable to me!

@ehuss
Copy link
Contributor Author

ehuss commented May 3, 2025

@rust-lang/team-repo-admins Just checking if there is anything you consider blocking here?

@traviscross
Copy link
Contributor

Five of us on the council have signed off on this, and I don't think this needs a formal council decision as it comports well enough with our existing ones. I'm raising my hand here and saying this is OK to merge.

@jackh726 jackh726 added this pull request to the merge queue May 3, 2025
Merged via the queue into rust-lang:master with commit 60c6c40 May 3, 2025
3 checks passed
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

Successfully merging this pull request may close these issues.

6 participants