[wp-trac] [WordPress Trac] #32101: Ability to mark plugin as unmanaged

WordPress Trac noreply at wordpress.org
Thu Apr 30 18:31:33 UTC 2020


#32101: Ability to mark plugin as unmanaged
-------------------------------------+----------------------------
 Reporter:  damonganto               |       Owner:  DrewAPicture
     Type:  task (blessed)           |      Status:  assigned
 Priority:  normal                   |   Milestone:  WordPress.org
Component:  Plugins                  |     Version:  4.1.2
 Severity:  major                    |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+----------------------------

Comment (by apedog):

 I'm not in disagreement with WP.org plugin naming policy.
 I see what you deal with on a regular basis. I'm confident your decisions
 in the matter are well-thought-out and balanced.

 I'm only saying these are two ''entirely'' separate issues: The WP.org
 naming policy (which is what you're talking about), and how plugins should
 communicate their status to WP core (which is what I and @jb510 above
 trying to address).

 If five years from now WP.org changes its naming policy (for whatever good
 reasons may arise), plugin authors today should still have a way to
 safeguard their plugins from accidentally being associated with a plugin
 hosted on WP.org. Which is the current default in core.


 ----


 And on an unrelated (and slightly facetious) note:
 > Besides the fact that 'google-tag-manager' is disallowed for trademark
 reasons (unless you're Google)
 Really?
 I actually use this plugin. Please don't remove it. It does what it says
 it does.
 https://wordpress.org/plugins/google-tag-manager/

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32101#comment:72>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list