-
Notifications
You must be signed in to change notification settings - Fork 135
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
Archiving https://github.com/nodejs/api and perhaps removing the api team? #67
Comments
SGTM
Il giorno dom 18 feb 2018 alle 06:47 Rich Trott <notifications@github.com>
ha scritto:
… The former API working group appears to be defunct.
Any objections to archiving https://github.com/nodejs/api?
Any objections to removing the @nodejs/api
<https://github.com/orgs/nodejs/teams/api> team? Seems like there are
other teams (for things like N-API and maybe async-hooks?) that have
replaced its function, so its existence might be little more than a source
of confusion?
/cc @nodejs/api <https://github.com/orgs/nodejs/teams/api> @nodejs/tsc
<https://github.com/orgs/nodejs/teams/tsc> @nodejs/community-committee
<https://github.com/orgs/nodejs/teams/community-committee>
(I'll wait at least 72 hours before doing anything.)
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#67>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADL4-bj1AS35vSaRVSTRMcX9gh815p0ks5tV7mOgaJpZM4SJlJD>
.
|
SGTM |
6 similar comments
SGTM |
SGTM |
SGTM |
SGTM |
SGTM |
SGTM |
I think we can cover other API related work by starting with the group meeting regularly on the N-API (as well as anybody else who wants to join into related discussions) |
SGTM |
All done. |
(I made a mistake and waited more than 71 hours but not quite 72 hours. Sorry about that.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The former API working group appears to be defunct.
Any objections to archiving https://github.com/nodejs/api?
Any objections to removing the @nodejs/api team? Seems like there are other teams (for things like N-API and maybe async-hooks?) that have replaced its function, so its existence might be little more than a source of confusion?
/cc @nodejs/api @nodejs/tsc @nodejs/community-committee
(I'll wait at least 72 hours before doing anything.)
The text was updated successfully, but these errors were encountered: