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

CPC representatives #1504

Closed
Trott opened this issue Feb 14, 2024 · 4 comments · Fixed by openjs-foundation/cross-project-council#1276
Closed

CPC representatives #1504

Trott opened this issue Feb 14, 2024 · 4 comments · Fixed by openjs-foundation/cross-project-council#1276

Comments

@Trott
Copy link
Member

Trott commented Feb 14, 2024

Hi, everyone. I believe Node.js appoints CPC representatives in July. Current representatives are @joesepi and me. However my engagement in Node.js has dropped pretty significantly from several months ago and it wouldn't be a bad thing if someone on TSC who is more engaged wanted to be appointed. If there isn't an obvious person to appoint, I'm happy to finish out my term. I still keep an eye on things. But I also don't want to occupy the seat if there's someone else who is really keen to engage.

@mcollina
Copy link
Member

I'm ok in doing this as I would be there anyway, but it would be even better to have others involved.

@joesepi
Copy link
Member

joesepi commented Feb 23, 2024

Additionally, I'd be happy to come present at most TSC meetings on CPC work and progress.

@mhdawson
Copy link
Member

mhdawson commented Mar 7, 2024

In the last meeting I proposed that we had reached consensus that Matteo will take over as CPC rep from @Trott and there were no objections. @mcollina can you create PRs to swap yourself infor Rich.

Also reconfirmed that there are no objections to invite Joe to the TSC meeting so we have coverage from both of our reps for the CPC update.

@mhdawson
Copy link
Member

Closing as there is a PR for the switch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants