WordPress.org

Make WordPress Core

Opened 19 months ago

Closed 4 weeks 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)

46293.diff (558 bytes) - added by jorbin 18 months ago.

Download all attachments as: .zip

Change History (21)

#1 @swissspidy
19 months ago

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? :-)

#2 @pento
19 months ago

Good point, thanks @swissspidy. Yes, we should definitely make things easier for translators. 🙂

@jorbin
18 months ago

#3 @jorbin
18 months ago

I've taken a first pass at some additional titles.

@swissspidy How do these look for a translation standpoint?

#4 @xkon
18 months 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 @desrosj
18 months ago

  • Keywords has-patch added; needs-patch removed

@xkon What about "Bug Reporter"? Is that better from a translation standpoint?

#6 @swissspidy
18 months 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: @xkon
18 months 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 @birgire
18 months 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 @desrosj
18 months 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: @azaozz
18 months 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"? ;)

Last edited 18 months ago by azaozz (previous) (diff)

#11 in reply to: ↑ 10 @xkon
17 months 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.


17 months ago

#13 @jorbin
17 months 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.


17 months ago

This ticket was mentioned in Slack in #core by david.baumwald. View the logs.


13 months ago

#16 @desrosj
12 months 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.

#17 @desrosj
12 months ago

  • Milestone changed from 5.3 to Future Release

#18 @azaozz
10 months 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 @francina
4 weeks ago

I believe that starting with WordPress 5.3 no roles were mentioned except for "Release Lead, so this seems fixed?

#20 @SergeyBiryukov
4 weeks 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.

Note: See TracTickets for help on using tickets.