-
Notifications
You must be signed in to change notification settings - Fork 135
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
2nd Director seat- post July 2020 #496
Comments
This is the suggestion that was made in the last TSC meeting for the projects input on the topic: The Node.js project is happy to continue to provide a director representative and has |
In today's @nodejs/community-committee meeting, we discussed this issue. @keywordnew highlights the value we've had in our Node.js meetings to have a member of the board give updates directly. An ask could be to have the new rep, if it is not a Node specific person, to give a monthly update to the top level meetings (TSC/Comm Comm). |
I should also note that in today's comm comm meeting we were essentially on the same page as the TSC statement above. |
FWIW, yes, I'm in strong agreement with @bnb's initial opinion |
Think this can be closed, it was agreed and I believed communicated that the board seat would be open to members from all projects this year. |
Creating issue here so we can put on tsc and commcomm agenda as follow up to the emails sent out.
Issue in the CPC repo:
openjs-foundation/cross-project-council#438
The text was updated successfully, but these errors were encountered: