[wp-trac] [WordPress Trac] #35704: Add Groups/Teams functionality to Core

[WordPress Trac]

#35704: Add Groups/Teams functionality to Core
-----------------------------+-----------------------
 Reporter:  catchmyfame      |       Owner:
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:
Component:  Users            |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+-----------------------

Comment (by johnjamesjacoby):

 > Please don't hijack this thread to promote your plugin.

 I think, friend, that you're misunderstanding my intention. Myself and
 @kenshino maintain WordPress's
 [https://make.wordpress.org/core/components/users/role-capability/ Roles &
 Capabilities Component], so I care deeply about the functionality and
 feature-set of what I believe is one of the most critically important APIs
 in all of WordPress.

 My plugin suggestion was only to point you towards code that already
 exists to address one of the issues you're raising, of which I believe
 there are 3 separate issues:

 * Groups of users
 * Using a group as user mask
 * Groups of roles for users (#36939)

 > Also, no one would force you to configure groups ("I can't imagine
 installing WordPress and immediately needing to configure groups of users
 for any post, page, or media publishing purpose.") and many others have
 commented that this would be an excellent addition. You're not
 understanding the concept of groups as a simple container for multiple
 users to edit the same content, whereas now you're forced to make a 1-to-1
 association between content and user.

 It's unfair (not to mention perceivably hostile) to make assumptions about
 what someone does or does not understand. I will not do this to you, and
 I'll ask that you treat others with that same consideration here. Thanks
 in advance.

 To be clear, no one here said or thinks any of the ideas you propose are
 bad – there are no bad ideas.

 > I would like to see WordPress have the simple, yet powerful, ability to
 let a user create content and be able to assign the author or owner to a
 group, not a single person, so that any member of the group can contribute
 and collaborate on it. It's a simple concept and lies at the heart of a
 true CMS. Yes other plugins exist that try and fill this hole, an other
 than Co-authors Plus (developed in part by Automattic) there are none that
 are widely used or actively supported. My suggestion also has nothing to
 do with BuddyPress.

 Conceptually simple; maybe. Relatively complex; absolutely, particularly
 inside of WordPress, which in its current form is not welcoming to many-
 to-many relationships, even less welcoming for User objects.

 For additional context, Co-authors Plus is a plugin I helped maintain
 while at Automattic, so I'm deeply aware of how it does (and does not)
 attempt to address other ideas you present here.

 > Again I ask you to keep this ticket open to continue this discussion
 instead of simply closing it for your convenience. It's a valid
 suggestion, and as I've been repeatedly told this is the place to post
 such requests. My first two posts in this thread sum up the case need and
 explain why we should not have to rely on plugins for this functionality.

 Nobody said the idea is invalid, and tickets do not need to remain open to
 continue discussion in them.

 Please also consider, both a WordPress project lead (Dion) and a
 maintainer of the component that would need improving (myself) do not
 consider this something WordPress itself needs to provide the API for
 currently, but think there's value in keeping it around for later.

 ----

 As an aside, I think the ticket-toggle is wasted energy. Historically no
 one (including myself) reacts very well to seeing their tickets be closed,
 but it rarely means what it maybe seems like it does. No one is shutting
 you down, trying to hijack anything, or trying to tuck anything under any
 rugs. We do want to be open and honest about the likelihood of core
 progress, to you and anyone else that finds this ticket, and the most
 efficient way to do that for everyone is to properly designate &
 categorize them according to our best assessment of viability, level of
 effort, and value added.

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