Add form for steering council nomination/emeritus#221
Add form for steering council nomination/emeritus#221kenodegard wants to merge 9 commits intoconda:mainfrom
Conversation
There was a problem hiding this comment.
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>
|
@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 |
| @@ -45,16 +52,19 @@ body: | |||
| attributes: | |||
| value: | | |||
| ## Charter and Responsibilities | |||
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
Description
Adding forms for nominating a new steering council member or moving an existing member to emeritus. See rendered forms:
steering.ymlemeritus.yml