Problem/Motivation
As mentioned in #2281763-111: Make Drupal.org user profiles more robust 4. by @danigrrl
Added the UID to the user history, and moved "Community Involvement Stats" to the right, so it's very visible.
(and in #81 12. and #92)
The UID, user id, or account number, is still needed to be known.
Since it is not in the url anymore (/u/username) knowing a trick like looking at the url for the contact form is making it something "insiders" only know to do.
uid is needed to be known for
- using as an argument in some views, eg #2404363: List sandboxes on user profile pages
- for json queries #2431511: Drupal.org API: user.json returns a 403
Proposed resolution
Put UID, account number, on d.o profiles
so people can read it on the page, and
make it available in a format usable, like json)
Remaining tasks
User interface changes
Yes.
API changes
No?
Comments
Comment #1
jhodgdonWhy do people actually need to know the UID any more? I looked at the referenced comments but I'm not seeing an explanation of why the UID is needed. I'm not against displaying it, but I don't understand why you want it. To me, the u/(name) URLs are sooooo much easier to deal with...
Comment #2
YesCT CreditAttribution: YesCT commentedgood point. I thought it was there.
updated the issue summary.
for example:
https://www.drupal.org/project/issues/user/UID
and
https://www.drupal.org/project/user/UID
which lists sandboxes
eg: https://www.drupal.org/project/user/258568
Comment #3
pfrenssenThe UID is also needed for git attribution. The git attribution string is no longer shown on the user profile, but at least it can be reconstructed if the username and user ID are known:
git commit -m "message" --author="username <username@userid.no-reply.drupal.org>"
Comment #4
jhodgdonPlease add that to the user summary.
Comment #5
jhodgdonAlthough regarding #2, I would argue that a more user friendly way of handling those particular URLs than displaying the numeric ID so that a few people who happen to know that those URLs exist would be able to use them, would be to put links on the user profile to "xyz's issues" and "xyz's projects", similar to the links we have when viewing our own profiles.
And regarding #3, that is actually being discussed on #2405787: Restore git attribution string on user profile, so on second thought, don't add it to the user summary.
And regarding JSON, that looks like it's on the related issue that is already linked in the sidebar.
So... I'm still not against displaying the UID, but if those are the reasons it's needed/wanted, there may be better (in the sense of more direct) solutions we can explore to expose those pages/URLs/strings?
Comment #6
pfrenssenI forgot about creating #2405787: Restore git attribution string on user profile, I should get some more sleep. Thanks @jhodgdon!
Comment #7
YesCT CreditAttribution: YesCT commentedRe #5, yep.
#2404363: List sandboxes on user profile pages
but I think there are others also..
and there will be.
Comment #8
YesCT CreditAttribution: YesCT commentedComment #9
Bojhan CreditAttribution: Bojhan commentedHmm, I wonder if we should have a "technical area" for all this type of info.
Comment #10
jhodgdonWhat an excellent idea in #9! Trust the UI expert to come up with it. :)
That way non-techies can easily skip looking at this part of the profile, while those who need this information can still find it easily.
Comment #11
pfrenssenNice idea! That would also be the perfect home of the git attribution string.