[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:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch close   |
------------------------------+---------------------
Changes (by Otto42):

 * keywords:  has-patch => has-patch close
 * type:  defect => enhancement


Comment:

 I'm really not seeing the point of that. For one, that is a horribly ugly
 example to me. But mainly, we have plenty of existing documentation.

 Every plugin developer gets an email when their plugin is just created
 that links to all of our documentation, including the documentation on how
 to make a readme properly.

 We do expect them to read and know this information. All the details that
 you are adding to the example file are documented already.

 I believe this sort of overabundant explanatory text is unnecessary, and
 ultimately harmful to the plugin review team as well as to the directory
 and the ability of authors to properly understand the desired content of
 the readme.txt file.

 To me, this seems like a close with wontfix. My 2 cents.

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