fix(members): restore Ameer Hamza's handle pending verification - #2
Merged
Conversation
…ster Nothing in the label set covered a change to an entry that already exists, so a renamed GitHub handle, a new LinkedIn URL or a changed employer had neither a label nor a documented path. Add the label, a row in the contributing entry-point table, and a section in members/README.md. No issue template: the change is a one-line pull request with no evidence and no sponsorship to review, so a form in front of it would add a round trip and decide nothing. A renamed GitHub handle is the urgent case. GitHub releases the old name on rename and anyone may claim it, so a stale entry can end up naming a stranger as an organizer. The reviewer check is that the issue in the entry's `request` field now shows the new handle, since GitHub attributes past activity by account rather than by name.
amaanx86
added
the
governance
ameerhamza-io
approved these changes
Aug 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Restores
github: ameerhamza3463inmembers/organizers.yaml, reverting the one-line register edit that rode along in 17886ac.Why
The rename to
ameerhamza-ioreachedmainwithout anyone running the verification step, inside a commit whose subject is about adding a label. A correction to the register should not land as a side effect of a docs change, and it should not land unverified.This is a hold, not a judgement about which handle is correct. The check is now written down in members/README.md: GitHub attributes past activity by account rather than by name, so the founding nomination at cncf/communitygroups#761 should already display the new handle. Confirming that takes one page load. Once it is done, the rename comes back as its own pull request carrying the
register-updatelabel, and movesgithubtogether with theopenprofileslug on line 28, which still readsameerhamza3463and needs opening to check whether the Linux Foundation slug followed the rename.Worth stating plainly that neither state is risk-free while this is open. GitHub releases a username the moment its owner renames, and anyone may claim it, so a register entry pointing at a freed handle can end up naming a stranger as an organizer. Reverting restores a handle that may now be claimable; leaving it kept a handle nobody had verified. The revert wins only because it returns the file to a value an organizer once checked, and because the verification that settles it is cheap.
uv run scripts/validate_members.pypasses. The pre-existing shared-employer warning is unrelated and unchanged.