BuddyPress integration

[gastronimo]

Feature Request: Buoy-BuddyPress integration.
https://wordpress.org/support/topic/feature-request-buddypress-integration/
https://codex.buddypress.org/buddypress-components-and-features/

HIGH PRIORITY:
-Incorporate Buoy 'emergency contact details information' directly into BP xprofile fields.
--Add support for BP xprofile field groups (like an 'Alert Info' xprofile field group similar to "Contact Info” Buoy heading). (https://codex.buddypress.org/administrator-guide/extended-profiles/#add-new-field-group)
-Include BP profiles/avatars for alerters and responders in Buoy alerts and incident chat rooms.
-Allow users to form Buoy crisis response teams from (hook into) existing BP friends and groups, not just WP users!
--with option to include/exclude certain friends or groups members using checkboxes.
-Include Buoy alerts within BP notifications- so if you surf on the site and a BP friend needs help, you will be notified immediately (https://codex.buddypress.org/administrator-guide/notifications/)
--with option to broadcast alerts directly to specific BP group(s).
-Add privacy option to include/exclude Buoy alerts/media sharing from BP notifications, group notifications, and/or site BP site or group activity streams.
(https://codex.buddypress.org/administrator-guide/activity-streams/)
--with support for BP activity moderation feature (admin screen) for BP admins.
(https://codex.buddypress.org/administrator-guide/activity-stream-management-panels/)

LOW PRIORITY:
-Add option to form BP (Alert!) groups from existing Buoy CRT's???
-- with support for private and hidden BP-Buoy groups
-Add support for including a Buoy 'alert button' onto BP profile page (STEP 6: Bookmark the “activate alert” page)- especially if the Alert button is meant to be placed in the Admin Bar (see below)
-Add support for BP profile page tabs (https://codex.buddypress.org/member-guide/profile-view/)
-Add option to sync alerter profile with BP xprofile fields...
-Add option to pull media from BP user albums (i.e.: Mediapress) for use in Buoy media sharing broadcasts.
-Include some form of SuperAdmin moderation to prevent abuse of Buoy, especially over Buddypress. SKIP- just use activity moderation feature for BP admins.
-Include 'nuclear' option to erase CRT info in case of pending smartphone confiscation.

BEWARE-
-Some website admins disallow (by use of plugin or other means) the use of the Admin Bar at top of the WP page, especially with BP, where it might duplicate access to member's profile pages with extra tabs. (https://wordpress.org/support/topic/frontend-access/) Consider shortcode support for Alert button front-end placement!
-the Buoy STEP 3: (https://github.com/betterangels/buoy/wiki/Buoy-Walkthrough#step-1-make-a-new-user-account) may not be permitted in some instances, if only one WP/BP user account is allowed! In this case, a Buoy alerter may need to petition site Admin for another user account, or better yet, can first ask Admin for help with STEP 7 Buoy demo (temporarily add Admin as responder to CRT).

• BP is moving towards incorporating new terminology for blogs>sites, and sites>networks.
  -Also, there are also two separate BP multi-networking plugins which provide for separate BP networks within multisite installations, one of which allows completely separated user bases for each BP network.

That's all I can come up with for now... I would help you with this, but I'm still new to BP, myself. It took me hours just to research these feature requests!

Saludos!

[fabacab]

Hi, these look like great suggestions, thanks for writing them all out. However, it's difficult to track and evaluate work on various different elements such as these when they're all posted in one issue report. That's why our "Submitting a bug report" guide specifically asks you to submit "One bug report per ticket."

One bug report per ticket! (No separate bugs in a single ticket!)
Please create separate issue tickets for separate issues. Combining different bugs into one ticket forces our volunteers to do unnecessary work to understand and re-categorize your issue, which slows us down and ensures your bug won't get addressed as quickly as it could be.

Would you mind please separating these requests into individual issue reports, so we can triage, prioritize, and otherwise handle them as separate tasks? Thanks!

[gastronimo]

I apologize, did not realize I was submitting a 'bug report'! To my holistic vision, this feature request is all one issue, with distinct but integral parts...already prioritized- not a bug report- so I presented it as one. Give me some time...

[fabacab]

That's okay. :) A "bug report" and a "feature request" are similar: it is a "bug" in some ways that a desired feature is not actually implemented. ;)

[hurtstotouchfire]

Hey folks, I just added an "expansion" label to all of our issues that are for integrating with other platforms / toolsets. Is this issue now a dupe of all the single issues?

[fabacab]

@hurtstotouchfire Is an issue label the right tool for the job here, or should we maybe start making use of GitHub's repository-level Projects instead?