[wp-meta] [Making WordPress.org] #4160: Add to w.org plugin's directory the support of additional params from readme.txt - "Coding-Standards:" (like "Tags") and "Micro-Framework:"

[Making WordPress.org]

#4160: Add to w.org plugin's directory the support of additional params from
readme.txt - "Coding-Standards:" (like "Tags") and "Micro-Framework:"
------------------------------+---------------------
 Reporter:  KestutisIT        |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  2nd-opinion       |
------------------------------+---------------------
Changes (by dd32):

 * keywords:   => 2nd-opinion


Comment:

 I have to agree with @Clorith here, does adding these tags benefit the
 target audience of the Plugin Directory?

 If you take the general audience of "WordPress Users" it certainly
 doesn't.

 If you take the audience of "WordPress Developer creating sites" then it
 may, but does it really?
  - Does the developer need to know that under-the-hood it makes use of
 SuperAwesomeLibrary? Or just that it works?
  - Do they need to know that the code is in their preferred PSR format? or
 just the functions/methods it can interface with to perform a task? Any
 decent developer should be able to pick up any PHP code regardless of what
 it's written in and be able to use it as-is, but furthermore, the
 developer shouldn't even need to be able to edit the plugin as they
 shouldn't be doing that at all.

 On the topic of `POT files` though, it's worth noting that plugins in the
 directory do not need to use them directly, as we handle the translations
 through GlotPress unless the author wishes to handle translations
 themselves somehow. WordPress Core only supports po/mo/json files for
 translation, and if that changes in the future plugins will just be able
 to use it without any changes.

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