Dev Chat Summary for January 6, 2016

The first dev chat of the year focused on the 2.5.0 release scope. There are currently 104 tickets slated for  this dev cycle: 22 closed and 82 active. The following were mentioned during dev chat (major features have asterisks).

API

*BuddyPress Embeds for activity, user profiles, groups (#6772) @rayisme and @im4th work on ensuring that nested embeds show up as well as preventing embeds from breaking layout, among others.

*Create New Invitations API (#6210) @dcavins has written a bunch of tests for this feature in the last two releases. He’s currently working on the actual code changes and it’s going pretty well. Ultimately, he mentioned he’d like nearly all of the  features of Boone’s Invite Anyone plugin to be rolled in.

*A new API to manage single items navigation (#6534) @boonebgorges

*Email API and customisation features (#6592) @djpaulgibbs will be ready for review in a week or so. He has done lots of work on it and has recently posted an extensive technical update in ticket.

*Group Types API (#6784) @boonebgorges

BLOGS

*Comment syncing between activity and post comments for Custom Post Types (#6482) @im4th has patch which ready for  review/testing.

CORE

Use WP page names for BP directory pages headings (#6765) @hnla

Hooks Documentation Continued @tw2113

GROUPS

Add function to send single invitation (#6025) @dcavins is working on this in relation to the main ticket (#6210) Invitations API above.

NOTIFICATIONS

Comment notification NOT notified (#6057) @im4th will refresh the patch next week.

Screen notifications settings page (#6712) @rayisme

TEMPLATE PARTS

*Companion Stylesheet – Twenty Twelve (#6766) @hnla has committed the first pass of the SASS and compiled CSS files.

BP Users front.php (#6769) @hnla

XPROFILES

*xProfile fielddata visibility should be stored in xprofilemeta (#6413) @boonebgorges has the patch written, “just some work to do on making the migration routine less insane.”

*xProfile fields used for signup should be configurable (#6347) @johnjamesjacoby

xProfile field database schema (#6350) @johnjamesjacoby

BUDDYPRESS.ORG

*developer.buddypress.org (#5129) @tw2113 is working on the parser

GENERAL – ADMIN/UI

Accessibility Upgrades Continued @mercime

FOR NEXT WEEK:

1. REST API
2. “Social Network” vs. “Community Software” marketing direction

#5129, #6025, #6057, #6347, #6350, #6413, #6482, #6534, #6592, #6712, #6765, #6766, #6769, #6772, #6784, #dev-chat

General Summary as of December 23, 2015

This is a compilation of dev chats held in December 2nd, 9th, and 16th. There was no official dev chat last Dec. 23, we just had some BP Holiday fun.

Minor Releases

• 2.4.3 – packaged and released by @im4th
• 2.4.2 – packaged and released by @johnjamesjacoby

BuddyPress 2.4.4

• There are currently two tickets in queue.
• Release date: January 2016

BuddyPress 2.5.0

• BP Beta 1: February 8, 2016
• BP RC 1 (string freeze): February 22, 2016
• BP 2.5.0 Target Release Date: March 2, 2016

Feature scope continued from last November 25:

Email API and customisation features (#6592) @djpaulgibbs reported Things are going well with the new feature.

Comment syncing between activity and post comments for Custom Post Types (#6482) @im4th will try to update patch and write unit tests.

Screen notifications settings page (#6712) @rayisme

Accessibility Improvements Part 2 (has tickets) @mercime

developer.buddypress.org @tw2113 has started work on the parser and fixing errors.

Navigation API tweaks for single items (#6534) @boonebgorges will be working on this for the next 2 weeks.

Create New Invitations API (#6210) @dcavins will update patches. @boonebgorges will be working on this for the next 2 weeks.

BuddyPress Embeds for activity, user profiles, groups (#6772) @rayisme has started working on this. @im4th has given feedback on the ticket.

Companion Stylesheet – Twentytwelve (#6766) @hnla has uploaded the stylesheets to trunk. Feedback welcome.

BP Users front.php (#6769) @hnla

xprofile fielddata visibility should be stored in xprofilemeta (#6413) @boonebgorges

BP JSON REST API @modemloooper. @marmaduka has volunteered to help. @djpaulgibbs and @boonebgorges were in agreement that the project would go through some documentation/vision phases before starting to write code. The BP JSON REST API would be introduced into core when the feature is “complete”, i.e.,  all read-only endpoints or an entire component, etc. This will be built as a plugin first. @djpaulgibbs also suggested that the eventual BP REST API plugin/module/eventual core integration require modern PHP.

#6210, #6482, #6534, #6592, #6712, #6766, #6769, #6772, #dev-chat