| Summary: | Standardize product name capitalisation. | ||
|---|---|---|---|
| Product: | [Websites] bugs.kde.org | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
| Component: | product/component changes | Assignee: | KDE sysadmins <sysadmin> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | task | CC: | christophe, nate |
| Priority: | NOR | Flags: | 4wy78uwh:
performance-
|
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| URL: | https://bugs.kde.org/describecomponents.cgi | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | https://bugs.kde.org/describecomponents.cgi | ||
|
Description
Roke Julian Lockhart Beedell
2024-05-04 00:21:35 UTC
Yeah, the current state here is currently pretty messy, because some products have a name that echoes the git repo name, and others use a user-friendly name. Neither is obviously correct, but the mix between the two styles is a bit awkward, yeah. Ideally we'd settle on one and use it consistently. The problem is that renaming products has a cost: it breaks people's saved bugzilla queries and search URLs, and we need to react to the renamed products in multiple places to change the names: individual git repos, as well as the shared git-repo-metadata project. Therefore, we have to weigh the disruption of changing anything against the disruption caused by the status quo. I think in this case the pain of changing is going to be worse than the pain of staying where we are. |