Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Discussion - Merger - Community Committee across multiple projects #414

Closed
mhdawson opened this issue Nov 13, 2018 · 7 comments
Closed

Discussion - Merger - Community Committee across multiple projects #414

mhdawson opened this issue Nov 13, 2018 · 7 comments
Assignees

Comments

@mhdawson
Copy link
Member

From the bootstrap meetings, the current picture in https://docs.google.com/presentation/d/1qUcvZz4wmQtwcWu9rWjxFNmWw5plD9-4_7mtvQvCegk shows the Community Committee across all of the projects.

I'd think it would be good for the Community Committee to discuss in the next meeting to see if this is what we think makes sense and surface any concerns/issues.

It may be a quick discussion if everybody is aligned, but I think it is good to at least have a short discussion to see if that is the case.

@hackygolucky
Copy link
Contributor

My understanding is that this is the foundation cross community council for all of the projects. That isn't the Node.js CommComm. I think there's a need for project specific focus to be maintained and also for cross-project work to empower all of the projects or whoever is excited for a specific initiative that it makes sense to collaborate on.

@mhdawson
Copy link
Member Author

@hackygolucky thanks, I think that is why we should discuss as I was confused as there has been discussion as to whether CommComm should move to be across all projects and if there should 2, one at the top level and one at the Node.js level. I think the doc might even say that members of the C3 would be the existing CommComm members + some members from JSF.

@amiller-gh
Copy link
Member

Ooh, I'd be very sad if the C3 takes that form. I agree that project-specific focus is very needed post merger. IMO, it should be the goal of C3 to help amplify community initiatives / organizational committees across all foundation projects, much like the CPC. Thats a very separate, dedicated goal.

@amiller-gh
Copy link
Member

@amiller-gh
Copy link
Member

Action Item from CommComm meeting: @joesepi to help organize a dedicated meeting over in Bootstrap about CPC / C3, their responsibilities, and convo around the need for 1 or 2 top level bodies.

@joesepi, once that conversation kicks off feel free to close this ticket 🙂

@joesepi
Copy link
Member

joesepi commented Dec 3, 2018

Opened an issue to gather TLC expectations and proposed to use Dec 10 2pm ET time slot to discuss.

openjs-foundation/cross-project-council#52

@amiller-gh
Copy link
Member

Will keep this on the agenda for this week so @joesepi can give an update on progress, but will close the CommComm ticket after tomorrow and let progress continue in @nodejs/bootstrap 👍

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

No branches or pull requests

4 participants