+1 to @nodejs/members.

+1

Adding @nodejs/members with "Read" access might not help:

Citing @bnb from #516 (comment):

only people with write access to this repository can now comment, which excludes much of the project's collaborators.

GitHub seems to confirm this.

Any concerns on adding @nodejs/members with write permission? If we want to limit commits here, we could set branch restrictions.

I would rather move the relevant issue ( #516) to a less restricted repo such as core. Adding write permissions to the org members does not seem to align well with the stated purpose of this repo? (Administration for TSC + Community Committee collaborative efforts)

I would rather move the relevant issue ( #516) to a less restricted repo such as core.

This would exclude CommComm from the discussion.

We should probably just unlock #516 then, and delete undesired comments quickly.

This would exclude CommComm from the discussion.

apologies, did not know that, and definitely did not mean it!

apologies, did not know that, and definitely did not mean it!

no offense taken! Just wanted to make sure that it was shared <3

I agree with @tniessen, and if the volume of undesired comments grows quickly, we can lock again and figure out another way to handle this.