Repository navigation
Repo for TSC + CommComm coordination #295
Description
There are a few efforts getting under way that are going to require a very tight coordination of communication and agreement with the TSC and CommComm members. The Chairs can do some of this work through the existing channels, but the most immediate task that comes to mind is the Board ask for a joint travel fund via the June Node.js Foundation Board meeting. This PR has relevant context.
Would repurposing the Collaboration repo, or creating a new repo such as Administration, make sense?
cc @nodejs/commcomm-members
Activity
nebrius commentedon Jul 12, 2017
This dovetails into #269, which I admit I ended up slacking on pushing through. I wonder if it would be worth it to close #269 in favor of this one?
I kinda like the idea of creating a new repo called "administration" or something because I feel the name is more informative.
jasnell commentedon Jul 13, 2017
hmm... if at all possible I'd rather avoid creating yet another administrative repo (we have so many already!)... but this is definitely important. If a repo we must have, then a repo it is :-) perhaps simply renaming the existing defunct
collaborationrepo toadministrationwould work?hackygolucky commentedon Jul 13, 2017
hackygolucky commentedon Aug 9, 2017
Okay, we now have two repos that I -think- need to fall under both TSC AND CommComm joint ownership
Probably just need to come up with a simple sentence for folks to copy/paste into these repos so we know who is responsible, unless one of these orgs really doesn't want to partially own getting-started(but I think it's a swell one for everyone to work on)
mhdawson commentedon Aug 31, 2017
No objections so renamed admin repo as agreed and set so that all of TSC, and CommComm have Admin access. The agreement was to rename as the repo was not being used and we wanted to avoid creating yet another repo.
meta: github organization management policy
meta: github organization management policy