sebb wrote on 9/18/23 6:17 PM:
On Mon, 18 Sept 2023 at 20:18, Daniel Gruno <humbed...@apache.org> wrote:

Hi, whimsy folks,
Could you please remove the GitHub ID field from the whimsy roster service?
The field is not canonical/authoritative, and mostly just serves to confuse new 
committers these days. The only authoritative place for GitHub IDs is through 
https://gitbox.apache.org/boxer/

If this is causing problems for Infra, we absolutely need to at least clearly annotate the field, and provide a link to gitbox, to ensure users don't keep asking questions in the wrong place.

The GitHub ids in Whimsy are provided by their owners, so can be
considered authoritative, even if they might not be the ones that are
linked to ASF accounts.
I am told that people find them useful.

Maybe a solution would be to add a note that the id might not be the
one that is linked to the ASF id.
Even better would be if the boxer system could validate which GH Id is
being used for linking?

Having GitHub ID in whimsy is useful, because many committers know it as a place to find information about accounts. However, we should deprecate/document any fields that have specific ties to other systems, especially which ones are authoritative either for viewing or writing.

Proposal: Leave a "user supplied githubid" field here, with a clear note about how it gets populated. Some new committers may not have tied them together yet, and will be curious.

Also have a "GitBox Registered GH ID" field or the like, which is read-only and just pulls whatever gitbox tells us, and if you click on it, takes you to the gitbox login or register screen.

If we just delete it completely from whimsy, some committers will wonder where it went.

Does that make sense?


--
- Shane
  Whimsy PMC
  The Apache Software Foundation

Reply via email to