Governance and label `WG-agenda`

[MikeMcC399]

According to https://github.com/nodejs/docker-node/blob/main/GOVERNANCE.md#wg-meetings

---

WG Meetings

This working group does not meet. All discussions and decisions happen in the nodejs/docker-node repository in issues and pull requests. Items that requires a decision by the WG can be flagged with the WG-agenda label. When an issue is tagged with WG-agenda, the WG may invite persons or representatives from certain projects to participate in the discussion in a non-voting capacity.

---

There is however no label listed WG-agenda on https://github.com/nodejs/docker-node/labels

Request

Please update the GOVERNANCE document to reflect how the WG currently works.

According to https://github.com/nodejs/docker-node/blob/main/README.md#docker-working-group-members that would be

Hans Kristian Flaatten (@Starefossen)
Hugues Malphettes (@hmalphettes)
John Mitchell (@jlmitch5)

[MikeMcC399]

There hasn't been any reaction here yet. Is there actually any active formal governance taking place in this repo, or has it become dormant?

[MikeMcC399]

Given that there hasn't been any response for any of the people named as WG members, it looks like the reference to the WG / WG-agenda would need to be removed:

This working group does not meet. All discussions and decisions happen in the nodejs/docker-node repository in issues and pull requests. Items that requires a decision by the WG can be flagged with the WG-agenda label. When an issue is tagged with WG-agenda, the WG may invite persons or representatives from certain projects to participate in the discussion in a non-voting capacity.

This part of the document is 10 years old and doesn't appear to have been edited since then.

[Starefossen]

Sorry for the lack of reply @MikeMcC399, yes, it might be time to revisit that part of the charter.

[MikeMcC399]

@Starefossen

Thanks for responding!

I wonder also if Hugues Malphettes (@hmalphettes) still considers themselves to be part of the WG, given that their last recorded GitHub activity was more than one year ago..

Whatever the outcome, it would be good if the GOVERNANCE document provided up-to-date information.

[MikeMcC399]

Is the repo's Working Group going to be able to update their governing document sometime soon? I don't know that anybody else would carry the authority to change the document.

[MikeMcC399]

Given that there hasn't been any further comment or action based on this issue, I'm going to assume that the only active "working group" consists of those with maintainer privileges who are actively responding to issues and merging PRs.

The description in the GOVERNANCE.md document appears to be unreliable.

It's been almost 3 months since this issue was opened, so I'm going to close it now as unresolvable.

[MikeMcC399]

Requested involvement from Node.js TSC in nodejs/TSC#1818

[MikeMcC399]

The TSC has picked up the topic . They report that they are having internal discussions and the results are not yet ready to be shared publicly.

[MikeMcC399]

This issue is resolved through PR #2383