Dev Chat Summaries as of August 17, 2016

This is a compilation of our dev chats for Aug. 3, Aug. 10, and Aug. 17. Thanks for your patience 🙂

BuddyPress 2.6.2

@dcavins packaged and released BuddyPress 2.6.2 last August 4, 2016. This was a maintenance release.

BuddyPress 2.7

  • September 21 – Beta 1
  • October 5 – Release Candidate 1 (string freeze)
  • October 12 – Target Release date
  • There are currently 84 tickets in queue (44 closed, 40 open).

Trac Tickets

  • Hierarchical groups (#3961) @dcavins had a patch which added the parent_id column to the groups database and support for querying by parent_id via groups_get_group() and @rayisme has uploaded a new patch which includes cache invalidation, among others. Dev feedback requested.
  • Group type frontend integration (#7210) @rayisme has patch which includes new UI. Dev feedback requested.
  • Display and filter by member type on Dashboard > Users (#6060) @slaFFik has patch. Dev feedback requested.
  • xprofile field support for WordPress Profile Fields (#7162) @djpaulgibbs: “We’ve not touched the xprofile sync code in years. So if anyone has any ideas about this … and what a new implementation should work like, please comment on the ticket.” He might work on this for BP 2.8.
  • Only load component action and screen code when we’re on the component’s page (#7218) @rayisme has patch for the activity component.
  • Select All link missing in BuddyPress Menu Selection (#5260) @tw2113 has patch and ready to commit. Review and testing requested.
  • BP-legacy: split group single admin.php in separate template files (#7079) Patches by @offereins, @hnla, and @rayisme. Dev feedback requested.
  • Date xprofile field enhancement (#5500) @boonebgorges has patch which includes new UI. Dev feedback welcome.
    Related: @djpaulgibbs has been talking to Miguel from the https://wordpress.org/plugins/buddypress-xprofile-custom-fields-type/ plugin about porting some of that plugin’s field types into core. Tickets will be created when ready.
  • Implement user capabilities for Activity component (#7176) @djapulgibbs has patch. Needs feedback from anyone who knows roles/caps API well.
  • Screen notifications settings page (#6712) @rayisme is working on this ticket. Related to Central place to manage all notifications and delivery preferences (#7168). Needs wireframes. @mercime has volunteered.
  • Extract & relocate core markup functions: Theme compat include functionality & search forms file (#6844) @hnla has patch. Dev feedback requested. @boonebgorges has agreed to review patch.
  • Member/Group Type management in wp-admin @boonebgorges: “If my schedule loosens up in the next few weeks, I will make a first go at a first patch “
  • Accessibility Tickets. @mercime – Goal is to make our front-end templates and at least  85% of BP admin screens accessible-ready by 2.7 launch. There are some style issues for the headings at this time, but will resolve them before deadline.

Notes

  • @djpaulgibbs: “I’m always available for code review and playing the devil’s advocate in feature discussions.
    I would also like to remind regular contributors they are very welcome to leave feedback on tickets in Awaiting Review and Under Consideration milestones on Trac. There’s a backlog, and we really need to do better here. So if anyone wants a change from forum support or development or translation, check out Trac.”

#3961, #5260, #5500, #6060, #6712, #6844, #7079, #7162, #7168, #7176, #7210, #7218, #dev-chat

Dev Chat Summaries for July 20 & 27, 2016

BuddyPress 2.6.2

  • Release date: TBA
  • There are currently 7 tickets in queue (3 closed. 4 open).
  • 404 errors when using HHVM on BP 2.6.1.1 (#7197) @rayisme has patch.
  • BP no longer filters wp_mail_from_name when using wp_mail() (#7024) @djpaulgibbs has patch. Might close this ticket.
  • @mentions break instagram oembeds if same username exists on site as instagram (#7084) needs patch.
  • Unit tests failing on PHP 7.0.9 (#7204) needs patch.

BP 2.7 Trac Tickets

Implement user capabilities for Activity component (#7176) @djpaulgibbs has patch. Feedback requested.

Groups: Draft, Locked or Suspended status (#6677) @dcavins has patch. Feedback requested.

Single items for the Blogs component (#6026) @im4th has patches. Feedback requested.

Hierarchical groups (#3961) @dcavins has patch. Feedback requested.

Components: BuddyPress.org Sites There are a number of tickets in Trac which need to be double-checked if the issues are still valid. If it is and you want to patch it up:
go svn co http://meta.svn.wordpress.org/sites/trunk/buddypress.org/,
create the patch, and upload the patch to the appropriate BP trac ticket.

Slack logs:
July 20: https://wordpress.slack.com/archives/buddypress/p1469041213000135
July 27: https://wordpress.slack.com/archives/buddypress/p1469646028000542

#3961, #6026, #6677, #7024, #7084, #7176, #7197, #7204, #dev-chat

BP 2.7 Kickoff Meeting – July 13, 2016

Project Schedule

  • July 13, 2016 – Kickoff – scoping/wishlist
  • September 21, 2016 – Beta 1
  • October 5, 2016 – Release Candidate 1 (string freeze)
  • October 12, 2016 – Target release date for BuddyPress 2.7

Release Lead for BuddyPress 2.8

Slava Abakumov Slava Abakumov (twitter) has been translating BuddyPress to Russian since October 2008 (long before the very first beta) and has submitted many BuddyPress plugins to the WordPress repository. He is a doting father, developer, and project manager, who also enjoys road-cycling and roller-skating. His motto is “Be good, have fun, create things”.

Congratulations @slaffik! 🙂

BuddyPress Leads in the Windy City

Watch out Chicago! @johnjamesjacoby, @boonebgorges, and @djpaulgibbs will be spending some time together at an undisclosed location in the city this Monday, July 18. 🙂

Images of BuddyPress leads - John, Boone, and Paul.

bbPress 2.5.10

bbPress 2.5.10 was packaged and released by @johnjamesjacoby Wednesday, July 13. This was a security release so please upgrade if you haven’t already.

Navigation API in Codex

@boonebgorges has posted a new article about the new Navigation API. Check out all the examples to help you with customizations.

BP 2.7 Scoping/Wishlist

BLOGS

CORE

  • Accessibility fixes for BP Admin screens and templates @mercime
  • Widget for logged-in user Notifications used in wp-toolbar (#7183)

DOCUMENTATION

GROUPS

MEMBERS

REST API@boonebgorges and @rayisme

TEMPLATES

  • Extract & relocate core markup functions @hnla

TOOLBAR AND NOTIFICATIONS

Though not mentioned during dev chat, following are a few of many interesting tickets which you might like to contribute to or kibitz about:

  • Merge BuddyPress Followers into BuddyPress Core (#7133)
  • UI to pick Template Packs (#7157)
  • Admin UI options for all template features (#7160)
  • Add #hashtag auto-suggest (#7165)

Slack log: https://wordpress.slack.com/archives/buddypress/p1468436417003180
(Slack account is required)

#3961, #6026, #6677, #6712, #6812, #7133, #7157, #7160, #7165, #7179, #7180, #7181, #7182, #7183, #dev-chat

Priorities for the Next 12 Months

Written by @mercime and @boonebgorges.

July 6, 2016 — Dev Chat. Project leads @johnjamesjacoby, @boonebgorges, and @djpaulgibbs presented a number of strategic priorities to help guide BuddyPress development in the upcoming year. These priorities are meant to reflect more accurately the arc of core development over the last few years, as well as the team’s understanding of how BuddyPress is actually used.

An Increased Focus on Site Builders and WordPress developers

One of these strategic priorities involves defining the primary intended audience for BuddyPress. Traditionally, BP has tried to balance the flexibility and power demanded by developers and site builders with the simplicity and out-of-the-box functionality desired by end users. In the upcoming releases, BuddyPress will be focusing increasingly on site builders and developers.

@djpaulgibbs: BuddyPress is used by many different kinds of people. We’ll improve BuddyPress by focusing on a narrower target audience: site builders and WordPress developers. This will cause many subtle but meaningful changes throughout the project. However, this is not a big change — it’s just an explicit recognition of what BuddyPress has become, and how people use it.

@boonebgorges: It will no longer be our #1 priority for BP to be 100% turnkey. We have often closed tickets and decided against certain features because we wanted to adhere closely to WP’s “decisions, not options” principle. This principle is designed to serve the non-technical owner who wants something as great as possible, immediately on activation. What the new ideas suggest is that we should embrace configurability a bit more. I think we can and should continue to strive to have a great out-of-the-box experience but we should be OK with deciding to emphasize the developer and site-assembler experience.

@djpaulgibbs The original tagline for BP was “a social network in a box”. It’s now become a set of tools or resources to let you ​build things with it. An example of more configurability/options that came up during discussion was https://wordpress.org/plugins/buddyextender In time I imagine all of those and more (like, the default option for select boxes for the filters on the Directory screens) would become contenders for inclusion in BuddyPress core.

@boonebgorges A general consequence of this reorientation is that we don’t have to say “plugin territory” as much because we are not tied to the idea of “no config screens”, “80% rule”, etc.

BP REST API and BP wp-admin screens

@djpaulgibbs: The two key strategic priorities for the project are the REST API and wp-admin management screens. These are the most important because, alongside the existing front-end templates, we’ll have 3 different “views” of BuddyPress data, empowering our audience to use as little or as much BuddyPress as they need, however they want.

Why there are two strategic priorities when front-end templates as a third view also mentioned: as @dcavins says, we already have those built, and we are building new templates now. It’s also the way BuddyPress has always been, which we’ll continue to support. But to attract new developers and new uses for BuddyPress, the REST API is pretty huge.

REST API is very important because it’ll expose BuddyPress data in a different way, and make it easy for developers to use that data to build anything. Like, mobile apps, JS-only React sites that don’t even use WordPress for templating (instead only as a data store), etc. In such cases where the front-end templates won’t be used, the REST API will provide a way to programatically update that data.

Also, the wp-admin management screens will let site owners manage that data, if they’re only using the REST API as a read-only data source. Providing shortcodes (#7159) will let people disable the front-end templating, yet still access BuddyPress data in their blog posts, or custom templates, etc.

BP REST API is being developed at Github – https://github.com/buddypress/BP-REST

bp-nouveau Template Pack

@djpaulgibbs: Our new template pack has momentum. Because the front-end templates will no longer have to be all things to all people, our template pack can be much bolder and more opinionated with our design choices.

Major strides have been made since the new template pack project launched last April 13 with @im4th at the helm with @hnla. You can help make the new template pack happen. Join us!

  • Meetings: Every Thursday at 19:00 UTC
  • Github Repository: https://github.com/buddypress/next-template-packs

BP Trac Component Maintainers

In order to move to the direction we want to focus on, there will be a post calling for component maintainers with tasks similar to WP core’s maintainers. An upcoming post will include more information for anyone interested.

Slack log: https://wordpress.slack.com/archives/buddypress/p1467831687002740
(Slack account is required)

#dev-chat

Dev Chat Summary for June 15, 2016

BuddyPress RC 1

@dcavins packaged and released BuddyPress 2.6.0 RC 1 (string freeze) last Wednesday, June 15, 2016.
* Developers: Please test your BP plugins and themes with our new features this dev cycle 🙂
* Translators: We need translators for BuddyPress. If you’re interested in contributing, @danbp has written a topic about how you can get involved.

BuddyPress 2.6.0

RC 1 Release Preparation

We discussed two tickets remaining in trac: moving stylesheet of activity embed to to bp-legacy’s /css/ folder (#7123 fixed.) and the Welcome Screen for 2.6 (#7108 fixed).
* Thanks to @im4th for preparing the video demonstrating BP’s new Activity Embed feature on our Welcome Screen.
* Thanks to @djpaulgibbs and @jerrysarcastic for facilitating the transfer of the video to WordPress.tv.
* And thanks @dcavins, @rayisme, and @hnla for improving the text of the Welcome Screen.

New Codex articles for BP 2.6

Thanks to @rayisme for publishing the following articles:
* Activity Embeds
* Group Types API

Improving Management of Trac Tickets

@djpaulgibbs will be implementing some changes to Trac over this weekend per his post here at bpdevel. @dcavins reminded all to comment on @offerein’s suggestions about BP trac ticket categories and focuses.

Slack log: https://wordpress.slack.com/archives/buddypress/p1466017239000114

#7108, #7123, #dev-chat

Dev Chat Summary for June 8, 2016

BuddyPress 2.6.0

  • Release Candidate 1 (string freeze): June 15, 2016
  • 2.6.0 release: June 22, 2016
  • There are currently 106 tickets in queue (Closed: 103. Open: 3.)

Trac Tickets

A new API to manage single items navigation (#6534) Issue on backward compatibility with groups navigation. Update: @boonebgorges has committed fix to trunk.

Activity link moderation doesn’t output useful error message to end users (#6719) @rayisme will be making a string change. Update@rayisme has committed the fix to trunk.

Welcome Screen for 2.6.0 (#7108)
* Activity embeds will be the main feature of the About page. A short video will be embedded for WP 4.5+ installations and an image for installations less than WP 4.5. @im4th was volunteered to make the video. Update: @im4th has uploaded a patch.
* Other items to be featured included the new Group Types API and Custom Users Front Page
* In the midst of testing the Activity embeds feature for the About page, @tw2113 found a bug. Update: @im4th created a new ticket and he and @rayisme have uploaded patches to fix the issue.
* In addition, the WP icon was seen in BuddyPress.org’s activity embeds. @im4th pointed out that a ready-to-use BuddyPress icon exists on the “official fonts and logos” page. Update: @djpaulgibbs has uploaded the icon.
* “Under the Hood” section: New API to manage single items (Member or Group) navigation, various caching improvements, among other items.

Slack log: https://wordpress.slack.com/archives/buddypress/p1465412393000100

#6534, #6719, #7108, #dev-chat

Trac milestone improvement ideas

I’ve been reviewing how we manage trac tickets to try to improve how we manage and prioritise feature requests and suggestions. We have many great ideas in our Future Release milestone, but all too-often that’s become the place where great ideas go to die. At time of writing, the milestone contains nearly 700 tickets, and not even I know what’s good in there, or even what was once good but now redundant.

Our current workflow is: new ticket -> [Awaiting Review] -> [Under Consideration] -> [Future Release] or [Release Milestone] or closed ticket.

“Under Consideration” is where new suggestions live while we evaluate them and gather further feedback and comment. This is a relatively recent addition in the last couple of years, and it’s helped seperate tickets we haven’t looked at yet (“Awaiting Review”) to those we are looking at.

I propose we should try tweaking how we approach the “Future Release” milestone so we gain better understanding and awareness of vetted suggestions and bug reports, which in turn will help existing and new contributors find exciting tasks to work on. Et voilà!

trac milestone screenshot

  • At the top of the pyramid, we have the two next release milestones (major and minor releases) which will work the same as they do today.
  • “Up Next” is a new milestone containing important or strategic tickets that our regular contributors have expressed in working on within the next two releases.
  • “Maybe Later” is a new milestone containing tickets that our regular contributors have decided that we have significant interest in working on, or are of a strategic importance, but less so than those in “Up Next”.
  • “Awaiting Contributions” is a new milestone. It contains tickets that our regular contributors have decided would be valuable enhancements for BuddyPress, but which are unlikely to be worked on by those regular contributors for the forseeable future — because they are less important than those in the other milestones.
  • This is pyramid-shaped on purpose. The milestones at the bottom should always contain more tickets than those at the top.

If this idea has support, we’ll have to spend alot of time reviewing the entire Future Release milestone, which is a great opportunity to close any tickets that are now irrelevant for some reason. The “Future Release” name itself would no longer be used to avoid confusion.

I would be very happy to hear your feedback on the proposed milestone changes (would they work? are they solving the right problem?).

Dev Chat Summary for June 1, 2016

BuddyPress 2.6.0 Beta 1

@dcavins packaged and released BuddyPress 2.6.0 Beta last Wednesday, June 1, 2016. Please help us test the exciting new features like the new API for Member/Group navigation, Activity embeds, Group Types API, and more!

BuddyPress 2.6.0 Schedule

  • Release Candidate 1 (string freeze): June 15, 2016
  • BuddyPress 2.6.0 release: June 22, 2016.
  • As of this post, there are 101 tickets in queue (Closed: 98. Open: 3.).

Trac Tickets

Companion Stylesheet – Twentyten and Twentyeleven (#7000) Kept open for any revision in stylesheet.

Add a “data-timestamp” attribute to all templates requiring timestamps (#5757) @rayisme needs more time to address localization issue. Update: This has been punted to BP 2.7.0.

Need to clear user cache after running direct query to update user displayname (#7050) Update: @djpaulgibbs has committed fix to trunk.

Activity link moderation doesn’t output useful error message to end users (#6719) Positive reviews during dev chat. Update: @rayisme has committed fix to trunk.

Use WP page names for BP directory pages headings (#6765) @boonebgorges would like to spend more time on the migration routine. “I think we’d been waiting for rewrite rules, but actually, we could build the UI first,” noted @boonebgorges. Update: This has been punted to Future Release.

Extract & relocate core markup functions: Theme compat include functionality & search forms file (#6844) Needed OK from Lead Dev. Update: Ticket has been punted to BP 2.7.0.

Emails: real unsubscribe functionality (#6932) Update: Ticket has been punted to BP 2.7.0.

Add a global scope option to the BP taxonomy wrapper functions (#7077) Ticket was reopened. @boonebgorges will take a look at it during Beta. Update: He has committed fixes to trunk.

oembed activity review (#7104) @rayisme has been committing fixes per review. Update: All review items have been fixed in trunk.

Slack log: https://wordpress.slack.com/archives/buddypress/p1464807686004763

#5757, #6719, #6765, #6844, #6932, #7000, #7050, #7077, #7104, #dev-chat

Dev Chat Summary for May 25, 2016

BuddyPress 2.5.3

@boonebgorges packaged and released BuddyPress 2.5.3 last Tuesday, May 24. This is a maintenance and security release, a recommended upgrade for all BuddyPress installations.

BuddyPress 2.5.4

BuddyPress 2.6.0

@dcavins postponed Beta 1 release last week, along with the RC 1 and 2.6.0 releases. The schedule for this dev cycle is updated as follows:

  • Beta 1: June 1, 2016
  • Release Candidate 1 (string freeze): June 15, 2016
  • 2.6.0 release date: June 22, 2016
  • There are currently 98 tickets in queue (Closed: 88. Open: 10.).

Trac Tickets

Companion Stylesheet – Twentyten and Twentyeleven (#7000) @hnla has committed stylesheets to trunk.

Harmonize structure of radio and check box input groups (#7083) @dcavins requested comments on patch. @im4th mentioned some code changes. @rayisme gave thumbs up. Comments in ticket are welcome.

Autocomplete (#4824) Ticket has been punted for future release. Update: @boonebgorges has committed patch to trunk.

Add a “data-timestamp” attribute to all templates requiring timestamps (#5757) @rayisme has uploaded new patch. Needs polyglot help for time strings output by the JS library are not the same as we currently generate. This ticket has been punted to get localization on point.

`get_group_extras` function doesn’t “respect” the `user_id` variable from `groups_get_groups()` function (#6431) Ticket has not been updated for some time and has been punted to Future Release.

Blogs: Improvements to `bp_blogs_record_existing_blogs()` (#6370) Update: @rayisme has committed the improvements to trunk.

Activity replies posting as new items (#6683) @im4th has patch and requested feedback. Positive feedback from @boonebgorges, @im4th, @dcavins, and @djpaulgibbs. Update: @im4th has punted ticket to Future Release.

Activity link moderation doesn’t output useful error message to end users (#6719) @rayisme has patch. Comments welcome. @djpaul mentioned that patch was good to commit.

Escape HTML in RSS Feeds (#6990) @djpaulgibbs noted that this is a new issue but won’t block Beta 1 and left comments in ticket. Update: @djpaulgibbs has committed fix to trunk.

Can’t set ‘Text size’ in Email Customizer (#7041) Update: @dcavins has committed fix to trunk.

@mentions break instagram oembeds if same username exists on site as instagram (#7084) @djpaulgibbs and @johnjamesjacoby have comments in ticket. @boonebgorges is also looking into this. Update: @dcavins has moved this ticket to upcoming BP 2.5.4.

PHP Notice in Customizer (#7086) Issue when entering the email preview pane in the Customizer. Update: @djpaulgibbs has committed fix to trunk.

Groups: Replace `BP_Group_Member` static method DB queries with updated group membership functions (#7078) Update: @rayisme has committed this enhancement to trunk.

xprofile_updated_profile actions pass different args (#7049) @dcavins will review patch submitted by nickmomrik. Update: @dcavins has committed fix to trunk.

Administrator not able to delete user notifications (#7023) @rayisme has revised patch. Update: The fix has been committed to trunk.

“Full name” field setting doesn’t work on non-primary blog admin in multiblog mode (#7003) Ticket has been punted to Future Release.

Emails: real unsubscribe functionality (#6932) @djpaugibbs will review patch this weekend. Update: New patch uploaded.

BuddyPress Embeds for activity, user profiles, groups (#6772)@rayisme and @im4th have updated patches. Update: New feature has been committed to trunk.

Slack log: https://wordpress.slack.com/archives/buddypress/p1464202837003779

#4824, #5757, #6370, #6431, #6683, #6719, #6772, #6932, #6990, #7000, #7003, #7023, #7041, #7049, #7078, #7083, #7084, #7086, #dev-chat

Dev Chat Summary for May 18, 2016

BuddyPress 2.5.3

BuddyPress 2.6.0

  • Beta 1: May 25, 2016
  • Release Candidate 1 (string freeze): June 8, 2016
  • Release Date: June 15, 2016
  • There are currently 91 tickets slated for this dev cycle. (Closed: 70. Active: 21.)

Trac Tickets

Route /me/*/ to /members//*/ (#6325) @rayisme has patch and has created a new ticket (#7075) for the internationalization patch. Update: @rayisme has committed this feature to trunk.

BuddyPress Embeds for activity, user profiles, groups (#6772) @im4th noted the security concerns about the embedded embeds. @rayisme: “The right way is to dynamically replace the image with the embedded content. However, the WP model makes this hard since we start in an IFRAME to begin with.” @im4th mentioned that he was going to test the new patch. Update: @rayisme and @im4th have uploaded new patches.

Activity post form template improvements (#6680) @dcavins had posted screenshots after testing @rayisme‘s patch on the WP default and some premium themes. @boonebgorges: “It looks like the specific improvements in the ticket do break some things, so let’s not do it right now. But maybe we can revisit for the next release.” Update: Ticket punted to next dev cycle.

Administrator not able to delete user notifications (#7023) @rayisme requested dev feedback. @boonebgorges: “The change to `displayed` rather than `loggedin` seems right. It’s what we do everywhere else. If you need to add a param to all functions to make it work, so be it. Strategy seems fine.” @djpaulgibbs: “to my eyes that looks like it’s an in-progress ticket that I don’t need to pay much attention because I trust the people (Ray and David) working on it 🙂 “

Notifications: Pass the notification ID to the notification callback (#7066) @rayisme has patch but requires patch in (#7067) to resolve the issue. @boonebgorges gave the green light. Update: @rayisme has committed both to trunk.

Improved caching for group membership (#6327) @boonebgorges will look into this. In addition: “I commend @dcavins for pulling that into the milestone. Now I feel obligated to look at it. A quality of a good release lead :+1: ” Update: @boonebgorges has improvements to trunk.

Emails: real unsubscribe functionality (#6932) @djpaulgibbs wants to get this in for 2.6 and will take a look at progress early next week.

Date xprofile field enhancement (#5500) @boonebgorges and @djpaulgibbs discussed the patch and missing feedback from reporter. Update: Ticket punted to next dev cycle.

Add a “data-timestamp” attribute to all templates requiring timestamps (#5757) The discussion between @rayisme, @im4th, @boonebgorges, and @djpaulgibbs touched on the 2 new libraries introduced for this new feature – moment.js and livestamp.js – and who has the time to shepherd this for 2.6.0. Update: @rayisme has uploaded revised patch.

Blogs: Improvements to bp_blogs_record_existing_blogs() (#6270) @rayisme is ready to commit patch in ticket.

Widgets: add support for customizer selective refresh (#7030) Update: @rayisme has committed patch to trunk.

Creation of developer.buddypress.org (#6812) @tw2113 reported that he has uploaded everything he has locally to https://github.com/buddypress/developer.buddypress.org. @tw2113 and @djpaulgibbs discussed the items needed to update the theme for developer.buddypress.org.

Slack log: https://wordpress.slack.com/archives/buddypress/p1463598018002648

#5500, #5757, #6270, #6325, #6327, #6680, #6772, #6812, #6932, #7023, #7030, #7066, #7067, #7075, #dev-chat