Skip to content

Conversation

@kenodegard
Copy link
Contributor

@kenodegard kenodegard commented Mar 20, 2025

Description

Adding forms for nominating a new steering council member or moving an existing member to emeritus. See rendered forms:

@kenodegard kenodegard requested a review from a team as a code owner March 20, 2025 16:31
Copy link
Member

@jezdez jezdez left a comment

Choose a reason for hiding this comment

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

This requires updating since the mechanics of the governance policy isn't about "joining" and "leaving" but about "nomination" and "requesting to move to Emeritus". There is no such thing as "leaving" the steering council.

Emeritus members are still on the steering council! Just not active anymore.

Co-authored-by: Jannis Leidel <jannis@leidel.info>
@kenodegard kenodegard changed the title Add form for joining/leaving steering Add form for steering council nomination/emeritus Mar 26, 2025
@kenodegard
Copy link
Contributor Author

@jezdez I was struggling with the wording trying to keep it concise and easy to understand but clearly lost too much information in the process, I accepted your suggests and took another stab at the wording

I also realized it was getting a little too complicated to support both nomination and switching to/from emeritus in the same form so I split the form

- type: markdown
attributes:
value: |
## Charter and Responsibilities
Copy link
Member

Choose a reason for hiding this comment

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

I am not sure an issue would be the best place to add the charter of new teams.
Maybe as an intake but charters IMO should be in a more permanently visible location like and MD document in the governance repo.
Would that be the expectation? Open an issue for discussion/approval then add the charter?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If we adopt something like #147 then yes, replacing this issue forms with a yaml template to edit in a PR makes sense. I see this as a stopgap until we've figured out how to formally document the teams.

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.

3 participants