Skip to content
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

Should we have a co-chair? #1043

Closed
tobie opened this issue Apr 2, 2023 · 4 comments
Closed

Should we have a co-chair? #1043

tobie opened this issue Apr 2, 2023 · 4 comments

Comments

@tobie
Copy link
Contributor

tobie commented Apr 2, 2023

As we're about to run CPC Chair elections again, I'm again concerned about our lack of strategy around maintaining and passing on institutional knowledge for roles like this one.

Should we think about electing a co-chair (or a chair and vice-chair) in order to help with this?

@joesepi's been running an incredible show here. What will happen when he decides to move on? How would we manage that transition?

@Relequestual
Copy link
Contributor

JSON Schema is planning to have a co-chair almost immediatly as the TSC is formed. I think it not only helps with long term sustainability, but reduces the mental burden of a chair.

tobie added a commit that referenced this issue Apr 26, 2023
Closes #1043.

Signed-off-by: Tobie Langel <tobie@unlockopen.com>
tobie added a commit that referenced this issue Apr 26, 2023
Closes #1043.

Co-authored-by: Timmy Willison <timmywil@users.noreply.github.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
ljharb pushed a commit that referenced this issue Apr 28, 2023
Closes #1043.

Co-authored-by: Timmy Willison <timmywil@users.noreply.github.com>
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
@joesepi
Copy link
Member

joesepi commented Jun 20, 2023

No objection on this issue. Let's figure out how to move forward.

@tobie
Copy link
Contributor Author

tobie commented Jun 20, 2023

It’s bundled in #1055.

tobie added a commit that referenced this issue Oct 3, 2023
- Introduction of a CPC Vice Chair.
- Simplification of the various CPC Director roles by tying the number of CPC Directors to the number of active projects in the Foundation (to match how Silver Directors works), capped so that Member Directors always maintain simple majority.

This follows recent [bylaws changes](https://openjsf.org/wp-content/uploads/sites/84/2023/09/OpenJS-Foundation-Bylaws-2023-09-18.pdf).

Closes #1054 and #1043

---------
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Co-authored-by: Rich Trott <rtrott@gmail.com>
Co-authored-by: Timmy Willison <timmywil@users.noreply.github.com>
@tobie
Copy link
Contributor Author

tobie commented Oct 3, 2023

Closed by #1055 in 8b03828.

@tobie tobie closed this as completed Oct 3, 2023
bensternthal pushed a commit to bensternthal/cross-project-council that referenced this issue Apr 23, 2024
…dation#1055)

- Introduction of a CPC Vice Chair.
- Simplification of the various CPC Director roles by tying the number of CPC Directors to the number of active projects in the Foundation (to match how Silver Directors works), capped so that Member Directors always maintain simple majority.

This follows recent [bylaws changes](https://openjsf.org/wp-content/uploads/sites/84/2023/09/OpenJS-Foundation-Bylaws-2023-09-18.pdf).

Closes openjs-foundation#1054 and openjs-foundation#1043

---------
Signed-off-by: Tobie Langel <tobie@unlockopen.com>
Co-authored-by: Rich Trott <rtrott@gmail.com>
Co-authored-by: Timmy Willison <timmywil@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants