Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Update README for new use #9

Closed
wants to merge 3 commits into from
Closed

Conversation

hackygolucky
Copy link
Contributor

Finally updating this repo to its newly intended use per nodejs/TSC#295. This converted use of a repo will oversee joint responsibilities such as the Travel fund and repositories within the Node.js project that require hearty collaboration between the top-level orgs to sustain a healthy project.

jasnell

This comment was marked as off-topic.

jasnell

This comment was marked as off-topic.

bnb

This comment was marked as off-topic.

@bnb
Copy link
Contributor

bnb commented Sep 14, 2017

Additionally, we'll want to update the repo tagline and add appropriate repo topics once this is merged.

@jasnell
Copy link
Member

jasnell commented Sep 14, 2017

Another quick note: Only the TSC Director, TSC Chair, CommComm Chair, Executive Director and Education Director should have write access to this repo. If there is eventually a CommComm Director, they would have write access also. The TSC and CommComm members weigh in on the discussions, but write access to this should be limited only to that smaller group.

williamkapke

This comment was marked as off-topic.

@williamkapke
Copy link
Contributor

@jasnell The Individual Directors are the CommComm board representatives currently.

@jasnell
Copy link
Member

jasnell commented Sep 14, 2017

Yes, I know the Individual Director's are associated with the CommComm but that's not what I'm referring to. If one of the Individual Director seats hypothetically happens to be refactored into a CommComm Director seat, or if a CommComm Director seat happens to be established, then the CommComm Director would also be given write access. This is as defined in nodejs/TSC#295

@williamkapke
Copy link
Contributor

I just checked to make sure I didn't miss it - but I do not see it defined there... and either-way it's still an open discussion.

Let's just have write access for all Admin members as @mhdawson seems to suggest? (any ED and CM)

@jasnell
Copy link
Member

jasnell commented Sep 14, 2017

Feel free to push a commit to nodejs/TSC#295 clarifying who should have write access.

@mhdawson
Copy link
Member

looks like @jasnell pushed the change to nodejs/TSC#219 to address who should have access (all of TSC and CommComm)

mhdawson

This comment was marked as off-topic.

@mhdawson
Copy link
Member

@bnb are your comments addressed ?

bnb

This comment was marked as off-topic.

Fishrock123

This comment was marked as off-topic.

@mhdawson
Copy link
Member

Going to land this and make update to say moderation repo is private at the same time as that seems to be the only outstanding comment and I want to get this landed now.

@mhdawson
Copy link
Member

Actually see that comment was already address, will just land as is.

@mhdawson
Copy link
Member

Landed as 03b8089

@mhdawson mhdawson closed this Sep 19, 2017
@targos targos deleted the hackygolucky-patch-1-1 branch March 18, 2021 16:01
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants