Skip to content
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

Move make-node-meeting-artifacts into the foundation #492

Closed
gibfahn opened this issue Feb 12, 2018 · 13 comments
Closed

Move make-node-meeting-artifacts into the foundation #492

gibfahn opened this issue Feb 12, 2018 · 13 comments

Comments

@gibfahn
Copy link
Member

gibfahn commented Feb 12, 2018

mhdawson/make-node-meeting-artifacts is pretty useful, and is currently used in the TSC and Build repos (and probably others).

It may be too soon (I defer to @mhdawson on that) but we should probably think about bringing it into the foundation.

@mcollina
Copy link
Member

LGTM

@mhdawson
Copy link
Member

I had been meaning to open this issue had just not gotten to it yet :). It is generating the artifacts for a number of WGs and the TSC and CommComm meetings and its time to move over.

After that happens the next step would be to look at moving over the automation I have to actually run at the right interval.

@Trott
Copy link
Member

Trott commented Feb 16, 2018

Unfortunately, the GitHub management policy still says this:

No repository may be deleted, transferred into, or transferred out of the Node.js Foundation GitHub Organization without a simple majority of both the TSC and CommComm in favor of the action.

It also strongly implies that this needs to go in the admin repo rather than the TSC repo.

I would strongly support a PR that altered policy to reflect our current practice. If we want to change that practice, let's actually road-test the change before documenting (and forgetting) it (because forgetting it is what you do if you don't actually do it for a while first--people much more strongly take their cues from what everyone else is doing than from documented policies).

@jasnell
Copy link
Member

jasnell commented Feb 17, 2018

SGTM. The most likely best home for this, however, is the @nodejs/automation WG

@Fishrock123
Copy link
Contributor

Sounds good to me, and also agree about putting it under the automation team.

@Trott
Copy link
Member

Trott commented Feb 20, 2018

Just to be clear:

This cannot happen without a TSC vote and a CommComm vote.

(See #492 (comment) if you're not sure why that is. IMO, that portion of the policy is misguided and should be changed, but for now, it's the policy.)

@fhinkel
Copy link
Member

fhinkel commented Apr 23, 2018

Ping @nodejs/tsc and @nodejs/community-committee. Please vote whether you're in favor of moving the meeting tooling to the foundation, see #492 (comment).
Please use thumbs up/down on the first post.

@mhdawson
Copy link
Member

mhdawson commented May 9, 2018

SGTM just to make my vote clear.

@keywordnew
Copy link

SGTM, on putting the tooling under the stewardship of the automation WG

@mhdawson
Copy link
Member

Added the boilerplate files for AUTHORS, CONTRIBUTING.md and LICENCE.md in preparation to moving over.

@bnb
Copy link
Contributor

bnb commented May 21, 2018

As a CommComm member, SGTM.

Since we got a ping and there have been no CommComm objections, I assume this can happen.

@mhdawson
Copy link
Member

mhdawson commented Jun 6, 2018

Will plan to do this next week unless there are objections before then.

@mhdawson
Copy link
Member

mhdawson commented Jul 5, 2018

Transferred.

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

No branches or pull requests

9 participants