Opened 6 years ago
Closed 4 years ago
#46293 closed task (blessed) (maybelater)
Credits: Add more titles
Reported by: | pento | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Administration | Keywords: | has-patch |
Focuses: | Cc: |
Description
credits.php
contains just a small set of titles, many of which don't correspond to the roles that people actually do.
Here are a few I've wished for recently, there are probably more:
- Core Designer
- Release Coordinator
- Tester
Related: #41022
Attachments (1)
Change History (21)
#2
@
6 years ago
Good point, thanks @swissspidy. Yes, we should definitely make things easier for translators. 🙂
#3
@
6 years ago
I've taken a first pass at some additional titles.
@swissspidy How do these look for a translation standpoint?
#4
@
6 years ago
Excuse my English here as I might be missing something, but is "Creater" valid in 46293.diff ? I do get the meaning, but can't think of a way translating that on my locale at the moment either :D .
#5
@
6 years ago
- Keywords has-patch added; needs-patch removed
@xkon What about "Bug Reporter"? Is that better from a translation standpoint?
#6
@
6 years ago
@jorbin Not really. For example, "Design Lead" would work better than "Lead Designer", or "Core Testing" rather than "Core Tester". More the role name than a title I guess.
#7
follow-up:
↓ 10
@
6 years ago
Yes @desrosj perfect, translating a Bug Reporter
would make more sense I believe.
To explain a bit so it's easier to follow the language differences, let me try to explain how changing 1 word would mean a worlds difference on some languages (for example mine):
---
A Creator (or Creater in this case if that's valid) would be someone that deliberately creates Bugs, like to break something in the code.
A Reporter on the other hand is actually someone that reports something to be fixed or looked at etc :)
---
I guess nobody wants to be a "Creator" from the above explanation :D .
#8
@
6 years ago
When creating a new ticket on Trac, bug is only one type of tickets,
we also have enhancements and feature requests.
So instead of Bug reporter maybe Ticket reporter or Ticket reporting, using the role name,
would better reflect that it includes all types of tickets.
Other variation that comes to mind is Issue reporter or Issue reporting
when looking at GitHub.
#9
@
6 years ago
- Type changed from defect (bug) to task (blessed)
Beta 3 (soft string freeze) is going to be packaged in a few hours. Since this is About page related, I am going to convert this to a task with the hopes of landing these new titles with the about page and hard string freeze.
Worst case, this just gets punted to 5.3.
#10
in reply to:
↑ 7
;
follow-up:
↓ 11
@
6 years ago
Replying to xkon:
---
A Creator (or Creater in this case if that's valid) would be someone that deliberately creates Bugs, like to break something in the code.
A Reporter on the other hand is actually someone that reports something to be fixed or looked at etc :)
---
Hahaha, right, the "direct" meaning is similar in all languages (afaik). However I think this was probably used as a joke here. Someone that "creates' bugs actually makes large, new, nice features. Bugs are always a "part of life" when coding, and "creating bugs" usually means the person is working and contributing a lot.
I understand the meaning in not straightforward, but perhaps that's a good "Easter egg"? ;)
#11
in reply to:
↑ 10
@
6 years ago
Replying to azaozz:
I understand the meaning in not straightforward, but perhaps that's a good "Easter egg"? ;)
Oh well yes if it was to use it similarly to our "Gardeners" (which again doesn't make much sense at the start when you don't actually know what it is about hahah :D) I guess I missed it but ok I get the idea now :), thank you!
This ticket was mentioned in Slack in #core by jorbin. View the logs.
6 years ago
#13
@
6 years ago
- Milestone changed from 5.2 to 5.3
Punting due to lack of consensus in time for string freeze.
This ticket was mentioned in Slack in #core by jeffpaul. View the logs.
5 years ago
This ticket was mentioned in Slack in #core by david.baumwald. View the logs.
5 years ago
#16
@
5 years ago
Does anyone want to own this? Unfortunately, with soft string freeze for 5.3 in a little over a week, this one's looking like a punt candidate again. It still needs discussion and a consensus.
#18
@
5 years ago
Looking at this after the 5.3 release, thinking the "opposite" idea also has some merit? Having the "Release Lead" role is nice, but instead of adding more roles how about removing the current "Core Developer"? It kind of sounds... a bit strange as all people listed there are core developers :)
#19
@
4 years ago
I believe that starting with WordPress 5.3 no roles were mentioned except for "Release Lead, so this seems fixed?
#20
@
4 years ago
- Milestone Future Release deleted
- Resolution set to maybelater
- Status changed from new to closed
Yeah, in recent releases we've taken the route suggested in comment:18 (dropping the "Core Developer" title and only keeping "Release Lead"), so it looks like there is no need for additional titles for now.
We can revisit this later if we ever need more titles again.
Many locales would translate for example "Release Coordinator" to "Release Coordination" because of unknown gender. Maybe we can keep this in mind here and use gender neutral strings by default? :-)