New label `membership changes` across the org? about admin HOT 14 CLOSED

cc @nodejs/tsc @nodejs/community-committee

from admin.

Is there an established process for reviewing them at the end of the year?

from admin.

@oe I don't think so, but I think @Trott (or @jasnell ?) does some review from time to time.

from admin.

@oe I don't think so, but I think @Trott (or @jasnell ?) does some review from time to time.

No established process, but I look through teams nearly every day to try to identify obsolete teams and sometimes obsolete members. I always have some goal in mind (like making sure access to the moderation repository is reasonably locked down or trying to make it so the members team does not need to be manually curated anymore).

from admin.

I'm 👍 in a 'membership changes' label

from admin.

Sgtm

from admin.

Is this exclusively membership changes in terms of members of a committee, WG, initiative, or team, or does it also include membership in a committee (like that of an initiative like i18n being a "member" initiative of the CommComm)?

Additionally, with new repos spinning up, is there a way to automate adding labels? I know there've been discussions in the past of having good-first-issue as a global label, but looking at some newer repos (like modules) it's not included.

If there's not a way to automate this, we should codify the org-wide repo guidelines/requirements as a doc in this repo and link to it from both the CommComm and TSC.

from admin.

@bnb There is https://www.npmjs.com/package/org-labels haven't tried it out yet though.

from admin.

@joyeecheung may be worth pinging @Fishrock123 to see if it's still usable 😅

from admin.

I think this would be useful. I imagine we may want to get more granular in the future, but don't think we want to get ahead of ourselves.

from admin.

SGTM

from admin.

Sounds good! 👍

from admin.

Reading the consensus so far, folks seem in favor of labels and automation.

@Fishrock123 Would it be advisable to use https://www.npmjs.com/package/org-labels to manage labels org-wide?

from admin.

going to close this since it's been ~4 years and several folks involved aren't involved anymore. I'm +1 to this change but it seems like we've not implemented it. I'd be happy to see it revived/implemented.

from admin.