-
Notifications
You must be signed in to change notification settings - Fork 134
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
Comments
LGTM |
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. |
Unfortunately, the GitHub management policy still says this:
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). |
SGTM. The most likely best home for this, however, is the @nodejs/automation WG |
Sounds good to me, and also agree about putting it under the automation team. |
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.) |
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). |
SGTM just to make my vote clear. |
SGTM, on putting the tooling under the stewardship of the automation WG |
Added the boilerplate files for AUTHORS, CONTRIBUTING.md and LICENCE.md in preparation to moving over. |
As a CommComm member, SGTM. Since we got a ping and there have been no CommComm objections, I assume this can happen. |
Will plan to do this next week unless there are objections before then. |
Transferred. |
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.
The text was updated successfully, but these errors were encountered: