-
Notifications
You must be signed in to change notification settings - Fork 162
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
Build stronger ties between At Large maintainers and their CPC Rep #761
Comments
I'm generally booked at that time but I'll see if I can make it once the call is scheduled. |
@joesepi and I had talked about this a while back and had agreed that the best first step would be to create a Slack channel for At Large Maintainers and their CPC reps.
|
Reminder in 6 weeks to check how this is going. |
Reopening to assess outcomes in next quarterly review. |
Would love to discuss the role of the At Large CPC Rep again and see how we can make it more impactful. /cc @eemeli |
@Relequestual suggested incubating project maintainers should have access to "At large" channels. I concur. I feel like the CPC "At Large" Rep role should extend to incubating projects. |
There's one channel which is public, but it seems to have no posts since 2021. |
I would assume incubating X projects are treated as X projects, whether X is At Large or otherwise. |
At Large members have two CPC reps. Historically there hasn't been good communication channels between At Large maintainers and their CPC reps.
We'd like to change this and create stronger ties.
The goal of this issue is to brainstorm/discuss this and find ways the foundation can help support this.
/cc @joesepi @eemeli @jorydotcom
The text was updated successfully, but these errors were encountered: