You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our initial meeting on strategy for the next 10 years of Node.js we agreed we should have a new repo to keep minutes, generating meeting issues etc.
since nodejs is already in the slug for the org, perhaps next-10 or next-ten would be a slightly nicer naming structure? I'm always put off by the verbosity of nodejs/nodejs-{x}.
Activity
mhdawson commentedon Jul 23, 2020
Would also like to ask at the same time for a new team called next10 that is used to manage access to the repo
mmarchini commentedon Jul 23, 2020
+1
bnb commentedon Jul 24, 2020
since
nodejsis already in the slug for the org, perhapsnext-10ornext-tenwould be a slightly nicer naming structure? I'm always put off by the verbosity ofnodejs/nodejs-{x}.Regardless, +1 for creating a repo for this.
mhdawson commentedon Jul 24, 2020
I'm going with
next-10, will plan to use that.mhdawson commentedon Jul 24, 2020
will also make team name 'next-10'
bnb commentedon Jul 24, 2020
that SGTM, +1
mhdawson commentedon Jul 27, 2020
No objections in 72 hours as per: https://github.com/nodejs/admin/blob/master/GITHUB_ORG_MANAGEMENT_POLICY.md#repositories so will go ahead and create the repo and team.
mhdawson commentedon Jul 27, 2020
Repo and team created, closing