Better frame responsibilities

[florian-lefebvre]

END OF VOTE: 2025/02/04 2:56 PM CET

• Updates L2 and TSC responsibilities to be framed as reponsibilities (ie. update verbs)
• Updates the Project Steward responsibilities to actually be framed as responsibilities, not rights/privileges
  • Although the Project Steward responsibilities section may looks like it contain less things, it is not the case!
  • It rephrases responsibilities to be clearer, and incorporates how/when to use some of these specific rights (eg. "veto for emergencies")
  • This also allow to clarify how services are managed, since the governance did not reflect reality (see Remove the Staff role #65 comments): eg. L3 members having admin rights over the GH org.

So to be clear, no right is removed!

[florian-lefebvre]

This was written in a way that allows using services even if Astro the open-source project doesn't own the account. Eg. technically the GH org belongs to CF

[sarah11918]

I can't think of what this might exclude. A generic "administer accounts" seems reasonable to me! With the responsibility to also "create", I think we sidestep the issue where different people had created some of the accounts initially, then left the project. So this seems to cover everything well!

[sarah11918]

Just a comment that I'm in favour of sections titled "Responsibilities" being actual responsibilities! Thank you for kicking this off, Florian!

[FredKSchott]

"provide guidance" is too vague, not sure what responsibility this entails (provide guidance to who? on what?). better to remove or make more explicit, or make more explicit in the #moderation section and then link there, similar to my suggestion on voting.

[FredKSchott]

similarly: "when necessary" what does this mean? is this defined anywhere? probably better to just remove this or just everything after Discord, ... and assume that that's all already covered by the moderation docs, no need to summarize/restate here.