Codeberg/Community
54
325
Fork
You've already forked Community
12

Use username throughout the UI to reference users instead of full name. #836

Open
opened 2022年12月16日 09:22:04 +01:00 by rohandebsarkar · 12 comments

Gitea UI uses username to reference users mostly but at some places it uses the full name instead of the username of the user. Like for example, the full names are used in the commit history, reaction references (tooltip), etc. Whereas the usernames are used in issue discussions, pull requests, etc.

I personaly find it very confusing, and quite a few times made the mistake of thinking a user is different (from another user) only to notice later that I was actually looking at the full name rather than the username and both the users are same.

Gitea UI uses `username` to reference users mostly but at some places it uses the `full name` instead of the username of the user. Like for example, the full names are used in the commit history, reaction references (tooltip), etc. Whereas the usernames are used in issue discussions, pull requests, etc. I personaly find it very confusing, and quite a few times made the mistake of thinking a user is different (from another user) only to notice later that I was actually looking at the full name rather than the username and both the users are same.
Member
Copy link

Yes! Just wanted to note that I've continiously gotten confused by this as well.

Yes! Just wanted to note that I've continiously gotten confused by this as well.
Owner
Copy link

Might be good to collect a list.

First thing in my head:

  • reactions to issuse / comments
Might be good to collect a list. First thing in my head: - reactions to issuse / comments
Member
Copy link

Second: email subject when receiving a notification :-).

This list basically writes itself in this thread. ;-)

Second: email subject when receiving a notification :-). This list basically writes itself in this thread. ;-)
Owner
Copy link

Organization name display, e.g. in settings

Organization name display, e.g. in settings

Title for Avatars in comments (left).

Only visible on hover though.

Edit: Also in participant list but there is also a custom one with the username.

Title for Avatars in comments (left). Only visible on hover though. Edit: Also in participant list but there is also a custom one with the username.
Owner
Copy link

#930 is an important piece to consider.

https://codeberg.org/Codeberg/Community/issues/930 is an important piece to consider.
Upstream PR: https://github.com/go-gitea/gitea/pull/24087

Oh, didn't know that this was an issue. Glad to see that I'm not the only one that noticed the same problems, please do let me know if you think that my work is in any way counterproductive here.

Oh, didn't know that this was an issue. Glad to see that I'm not the only one that noticed the same problems, please do let me know if you think that my work is in any way counterproductive here.

Is this the correct config file used for the deployment of the forgejo instance https://codeberg.org/Codeberg-Infrastructure/forgejo/src/branch/codeberg-7/custom/conf/app.example.ini#L1297? It seems that the option DEFAULT_SHOW_FULL_NAME is not set. See also forgejo/forgejo#4287. I’d prefer to see the full name everywhere, but currently it is weird to have at some places the full name and others the username on https://codeberg.org.

Edit: Related commit with introduction of this feature from 5 years ago: forgejo/forgejo@4508380cf7

Is this the correct config file used for the deployment of the forgejo instance https://codeberg.org/Codeberg-Infrastructure/forgejo/src/branch/codeberg-7/custom/conf/app.example.ini#L1297? It seems that the option DEFAULT_SHOW_FULL_NAME is not set. See also https://codeberg.org/forgejo/forgejo/issues/4287. I’d prefer to see the full name everywhere, but currently it is weird to have at some places the full name and others the username on https://codeberg.org. Edit: Related commit with introduction of this feature from 5 years ago: https://codeberg.org/forgejo/forgejo/commit/4508380cf7937aef0bf6f99fe3eefb6c530e38e3
Owner
Copy link

No, this is just the default config file from Forgejo ("example"). The relevant config for Codeberg is in https://codeberg.org/Codeberg-Infrastructure/build-deploy-forgejo/src/branch/codeberg-7/etc/gitea/conf ("base" and "gitea-production" apply).

We can try this setting, but as I understand it, it would replace the username with the full name. Which has issues on its own. There should be one consistent way across Forgejo instances, and I'd even recommend to remove the setting. This will take some time, but I'll try to do some user research on this.

No, this is just the default config file from Forgejo ("example"). The relevant config for Codeberg is in https://codeberg.org/Codeberg-Infrastructure/build-deploy-forgejo/src/branch/codeberg-7/etc/gitea/conf ("base" and "gitea-production" apply). We can try this setting, but as I understand it, it would *replace* the username with the full name. Which has issues on its own. There should be one consistent way across Forgejo instances, and I'd even recommend to remove the setting. This will take some time, but I'll try to do some user research on this.
Owner
Copy link

Indeed, it replaces the username with full name in many places. This would mean that this very open issue that asks for username instead of full name would be worsened again.

Indeed, it replaces the username with full name in many places. This would mean that this very open issue that asks for username instead of full name would be worsened again.

Indeed, it replaces the username with full name in many places. This would mean that this very open issue that asks for username instead of full name would be worsened again.

Or improved ;) as it is clearly a matter of taste ... (See motivation in the issue description of forgejo/forgejo#4287). Anyhow, thanks for your follow-up. Certainly, this is not the most urgent issue to solve ;)

> Indeed, it replaces the username with full name in many places. This would mean that this very open issue that asks for username instead of full name would be worsened again. Or improved ;) as it is clearly a matter of taste ... (See motivation in the issue description of https://codeberg.org/forgejo/forgejo/issues/4287). Anyhow, thanks for your follow-up. Certainly, this is not the most urgent issue to solve ;)
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#836
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?