[buddypress-trac] [BuddyPress Trac] #8148: A new direction regarding optional components management

buddypress-trac noreply at wordpress.org
Mon Oct 21 19:52:42 UTC 2019


#8148: A new direction regarding optional components management
-------------------------+-----------------------
 Reporter:  imath        |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  6.0.0
Component:  Core         |    Version:
 Severity:  normal       |   Keywords:  has-patch
-------------------------+-----------------------
 In short: I’m suggesting to progressively migrate optional components as
 BuddyPress plugins, starting by making the BP Attachments component (I’m
 working on for 6.0.0) a plugin.

 Why?


 1. BuddyPress is becoming a really huge plugin (zip is 3 MO which
 represent 1/4 of WordPress size), making us hesitant about adding new
 components.
 2. Only keeping the Core + Members components in BuddyPress can open new
 opportunities for hesitant users who only need to organize users on the
 front-end (or to build on top of a lightweight BuddyPress).
 3. We could welcome new components & contributors to improve BuddyPress
 popularity. Being listed into the “BuddyPress” Plugins sub directory could
 be very interesting for developers.
 4. Components could evolved at a different rhythm than core and be updated
 as soon as they need to be.
 5. Users would have a real and wider choice for their community site: they
 could trust “BuddyPress supported components” packaged as plugins.
 6. We have a strength: the WordPress Plugins Directory API, making it very
 easy to install new components, we just need to list the ones we support
 to ease their discoverability. (Some alternative paid softwares do not
 have this advantage).
 7. It seems the natural evolution of Components when we look at the
 Components management screen which look like the Plugins management
 screen.
 8. With the “space economy” we could include new tools like an API to
 handle huge upgrades which would be very interesting for any plugins.

 How ?

 - A simple JSON file hosted into the assets directory of our WP repository
 ([https://gist.github.com/imath/5442cfa3799ee116b7cb03d3c3635b58 like this
 one]) would be enough to build the BuddyPress Components directory.
 - The BuddyPress Components directory replaces the “retired” view of our
 Components Management screen.
 - A simplified installation/activation process so that it’s not taking too
 long for users to add new components to their community site.
 - The attached patch can give you a better idea of how it could look like.
 Below is a link to a video demonstration of it.

 https://vimeo.com/367830458

 Possible steps

 - 6.0.0: no more new components into Core. BP Attachments is the first
 Component as a plugin. It's easily installable from the BuddyPress
 Components directory.
 - 7.0.0: the Site Tracking and Private Message components migrate as
 plugin,
 - 8.0.0: the Friends and Account Settings components migrate as plugins.
 - 9.0.0: the Notifications and Groups components migrate as plugins.
 - 10.0.0: the Activity component migrates as a plugin.

 Let’s talk about it!

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/8148>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac


More information about the buddypress-trac mailing list