[wp-meta] [Making WordPress.org] #6106: Deprecate readme.txt plugin name header

[Making WordPress.org]

#6106: Deprecate readme.txt plugin name header
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |
------------------------------+---------------------

Comment (by wplmillet):

 So, if I understand correctly and to exaggerate a bit, a developer who
 creates an extraordinary plugin will be penalized by the fact that their
 plugin is not translated by the community for a particular locale. I'll go
 further. The plugin is ultimately penalized because some strings are not
 validated. Most WordPress users don’t even know how extensions are
 translated for and by the community. Even I, who am a GPTE in fr_FR, only
 learned this by chance in 2020, even though I have been working on WP for
 much longer.

 If I took ACF as an example in my case, it's simply because it's a typical
 situation of the principles of plugins dependent on other plugins, a kind
 of ecosystem within the ecosystem. Many plugins connect to it and use it.
 Therefore, in the readme and the strings of these plugins, there are quite
 a few occurrences of the searched word. It is therefore abnormal to find
 Yoast SEO in the first position on a search that contains just the word
 ACF in French. It’s not intuitive at all. If I go into the readme of Yoast
 SEO, there is only one occurrence of ACF. This is highly penalizing for
 anyone not in the US who just wants to access the plugin they are asking
 for. Most people who come to search just enter its name (sometimes even
 the one they understood). As it stands, they are certain not to find it.

 There are tags, so why not make a local glossary of main tags, just like
 we have a translation glossary. Search engine users like Google, Bing,
 Yahoo, Yandex, or any other search system do just that, and users are
 accustomed to it. Furthermore, following the reasoning used to tell me
 about the failures of search, can someone explain why Wordfence is ranked
 first in fr_FR with only 13% of the readme translated and 42% of the
 plugin?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6106#comment:11>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org