BuddyPress 2.6.0 Schedule
- Beta 1: May 25, 2016
- Release Candidate 1 (string freeze): June 8, 2016
- Target Release Date: June 15, 2016
- There are 95 tickets slated for 2.6.0 to date. Forty-seven of 79 tickets still open have patches.
Weekly Meeting Time
Join us every Wednesday at 19:00 UTC at the #buddypress channel on Slack. @djpaulgibbs encouraged anyone who wants “to participate in these meetings but can’t always make it can leave comments in Slack beforehand” or in posts here at bpdevel.
For newcomers, here’s how to get a WordPress/Slack account.
BuddyPress Work Parties née Bug Fixin’
BP REST-API. @dcavins followed up on the status of this project, i.e., whether we can work on this or should this hold until WP API gets sorted. @djpaulgibbs noted that “WP API is sorted. You/we can work on it now.”
BP Style Modules – A Proposal. @dcavins asked for more information about the proposal. @hnla: “Style modules is an additional enhancement for templates, more for engaging the community and providing a means to add small code blocks, similar in the way frameworks offer them sometimes.” @boonebgorges and @hnla later exchanged a series of enlightening comments about some of the details of @hnla‘s proposal.
A new API to manage single items navigation (#6534) @boonebgorges passes baton to @im4th to save this ticket from oblivion. @im4th brought up the issue of an upgrade routine to implement this feature which requires Framework for bulk data handling after updates (#6841).
Accessibility tickets. @mercime will be working on the ones already in trac and will be adding some more later.
Explore Behat to add a functional testing capability to the project. @djpaulgibbs‘ dream is look into adding a functional testing capability to the project. “I don’t know if this is something that we’ll want, but I need to build it before I can convince everyone.”
New bp-template pack @djpaulgibbs is trying to come up with a plan to answer the never-ending questions around if/when BuddyPress will ever get a new one. “I’ve started with asking about eight of you some questions around that. It’s going to be a lot of work to come up with some kind of plan. I got essay-length replies from everyone and each reply is vastly different. Everyone has a very different opinion. I think some goal-setting needs to occur before we are able to write new templates with 100% buy-in from everyone, but it’s still early days and I reserve the right to change that opinion.”
Activity link moderation doesn’t output useful error message to end users (#6719) @rayisme has made some headway on better error messages in the activity stream. “Question is should we be holding off on this for an
activity_status DB column.” @boonebgorges noted that the “main issue would be documenting that
select * from $bp->activity->table_name queries will have to be adjusted accordingly.”
Slack log: https://wordpress.slack.com/archives/buddypress/p1459364425000688