discussions icon indicating copy to clipboard operation
discussions copied to clipboard

Properly list the organization members

Open UlisesGascon opened this issue 2 months ago • 8 comments

While working on https://github.com/expressjs/express/pull/5600, it was suggested that we list the organization members and teams to make it easier to identify the individuals helping the project (cc: @CBID2 @mertcanaltin). Node.js provides a great example of this (see).

Historically, only the TC members were listed in the community section of the website (see). Recently, in the Security WG, we decided to include the team members of the teams in the README.md file (see), and we also documented the Captains initiative in the CONTRIBUTING.md (see).

I think it's a great practice for our organization to maintain an updated list of all the people who have been part of the organization, both currently (active) and over the years (emeriti). It is a fantastic recognition of the effort invested by many individuals and a great exercise in transparency.

In the past, we had some discussions about this, and if I remember correctly, we thought that keeping the list in the main repository README.md might generate a lot of PRs and so on. I personally don't think this is an issue, as Node.js follows this practice and even includes those commits in the release notes, so the changelog also reflects the organization changes.

In my opinion, we should keep both lists updated (website and the Express README.md) and include all the teams and roles, what do you think?

UlisesGascon avatar Apr 17 '24 11:04 UlisesGascon