[wp-meta] [Making WordPress.org] #7035: Plugin Directory: Add filters for community & commercial plugins

[Making WordPress.org]

#7035: Plugin Directory: Add filters for community & commercial plugins
------------------------------+---------------------
 Reporter:  ryelle            |       Owner:  ryelle
     Type:  enhancement       |      Status:  closed
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:  fixed
 Keywords:  has-patch         |
------------------------------+---------------------

Comment (by justlevine):

 Replying to [comment:9 coffee2code]:

 I happen to agree with _most_ of what you wrote. Especially the last bit:
 > Any or all of those biases for either views may or may not be true for
 any given plugin or even generally. The "Commercial" classification
 doesn't inherently imply any of them.

 It's the lack of a scoped definition IMO that allows any implication to be
 read into the taxonomy names. Which adds cognitive load and fosters
 implicit biases in multitudes of possible connotations, many of which of
 which could be easily avoided by coming at them from the perspective of
 "what is a user actually trying to find?".

 Additionally, I do not believe that switching to a user-centric taxonomy
 is somehow "more complex" than the existing classification binary. I would
 love to see the user story for searching the directory for a "plugin/theme
 offers commercial upgrades, extensions, and/or support", and the other
 binary where someone only wants to view themes/plugins with _none of
 those_.

 Replacing `Community|Commercial`, with just `has paid features|has paid
 support` (or however it's phrased), gives users the same number of
 choices, but in a way that address their needs more directly and with less
 cognitive load.

 And if the Make post is correct, and  these are just the first tax terms
 with more possibly OTW, then a user-centric taxonomy is going to scale a
 whole lot better than arbitrary (from the users perspective) groupings.
 (E.g. where do the eventual functional categories of `canonical`, `feature
 plugin`, or any other possible category fall on a map along with
 `community` and `commercial`).

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