Add explicit collaborator list into README.md as per GOVERNANCE.md

[sxa]

Adding copy of the collaborator list into here in order to allow Pull Requests to be used for the process as per the governance doc

Ref: discussion in #2448

Description

Motivation and Context

Testing Details

Example Output(if appropriate)

Types of changes

• Documentation
• Version change (Update, remove or add more Node.js versions)
• Variant change (Update, remove or add more variants, or versions of variants)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (none of the above)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• All new and existing tests passed.

[MikeMcC399]

See PR #2456 to fix the markdown-link-check issues that suddenly started to appear today in several workflow runs https://github.com/nodejs/docker-node/actions/workflows/markdown-link-check.yml

[aduh95]

It would probably make sense to add a workflow similar to https://github.com/nodejs/node/blob/HEAD/tools/lint-readme-lists.mjs / https://github.com/nodejs/node/blob/dd3fe4997bc2a50cfb06282ba53d3af6877c907e/.github/workflows/linters.yml#L257-L286 to help keep the README in sync with the actual team

[sxa]

Above force was to rebase on top fo the linker fixes.

It would probably make sense to add a workflow simila to https://github.com/nodejs/node/blob/HEAD/tools/lint-readme-lists.mjs / https://github.com/nodejs/node/blob/dd3fe4997bc2a50cfb06282ba53d3af6877c907e/.github/workflows/linters.yml#L257-L286 to help keep the README in sync with the actual team

Yep, we could look at that later but for the purposes of this PR (Which is ultimately to assist with giving Mike collaborator access in the repository) let's not expand the scope. The issue we've had with this repository is not having many people active to be able to do fixes etc.

[MikeMcC399]

I suggest to have the list of names appear before the comment about how to add names.

[sxa]

I don't mind it being before, but I've made that change and also removed "Additional" since "managed" implies addition and removal.

[MikeMcC399]

This GitHub user was last active in 2024

[sxa]

Fair comment however since they are currently in the list of people with access we should list them and subsequently update it if required.

[MikeMcC399]

I agree that it's cleaner to make that a separate PR (unless of course they themselves respond here, which I wouldn't expect, given their inactivity).

[sxa]

I expect we can reasonably have a separate subsequent PR to move them to emeritus and consider a lack of response to be a sign that it's ok. It can always be reversed if needed. Having the list in here will give us a process for doing exactly that.

[MikeMcC399]

According to the GOVERNANCE document, it is the responsibility of Maintainers to manage and approve membership, so at least one of the following would need to approve this PR actively:

• Laurent Goderre (@LaurentGoderre)
• Simen Bekkhus (@SimenB)
• Peter Dave Hello (@PeterDaveHello)
• Rafael Gonzaga (@RafaelGSS)
• Matteo Collina (@mcollina)

Since the list of Collaborators is now being published, it would also make sense for Collaborators to confirm their agreement:

• Hugues Malphettes (@hmalphettes) - no activity in GitHub since 2024
• Tianon Gravi (@tianon)
• ttshivers (@ttshivers)
• yosifkit (@yosifkit)
• Nick Schonning (@nschonni)
• Stewart X Addison (@sxa) - Author of this PR

[MikeMcC399]

Thanks for responding to comments!