[wp-meta] [Making WordPress.org] #5652: Plugin Readme Header Spec Upgrade

[Making WordPress.org]

#5652: Plugin Readme Header Spec Upgrade
------------------------------+---------------------
 Reporter:  pewgeuges         |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by pewgeuges):

 Replying to [comment:1 Otto42]:
 > The moment we add explanatory text in the example is the same moment
 when the plugin review team will start seeing it in submitted plugin's
 readme files.

 That’s cool, thanks. Implies that it’s safe to add this needed extra
 information in the header.

 > We already recognize elements of the example file and use that to
 determine when plugin authors aren't paying attention, and thus use that
 information to better help support them and their submitted plugins.
 Changing it is more than just "changing it".

 No doubt that changing the readme header spec requires emailing all plugin
 committers.

 I see a problem though: How will submitting plugins with extended readme
 headers be going to happen as long as WordPress seems to restrain these
 headers to the available template with spec status?

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