Dev Chat Summary for March 16, 2016

Last week’s meeting focused on reviewing trac tickets slated for BP 2.6.0 which already had patches uploaded.

Activity link moderation doesn’t output useful error message to end users (#6719@rayisme requested feedback on custom error handling for the activity stream using WP_Error. “Would love it if @hnla could test the patch in 6719 and see if that addresses the points in #6822

Suspension of BP comment moderation functionality (#6822) @rayisme wrote about removing the activity moderation feature entirely.

Simplify CSS targeting of radio and checkbox label fields (#6678) @dcavins thanked all for the feedback in trac to change markup to use fieldsets/legends for some profile fields in the front end.
Action: Patch changing the markup has been committed to trunk during the meeting.

Avoid using HTML tags in translation strings (#6898 through #6911) @djpaulgibbs had some concerns about whether the proposed changes would make the strings harder to translate and asked @boonebgorges for his opinion on the tickets.
Update: Boone has committed most of the patches to trunk.

Accessibility: Bump headings in template files (#6875 through #6882) @djpaulgibbs, @hnla, @rayisme, and @mercime had a long discussion about the merits and challenges of updating template files to meet accessibility guidelines. There were concerns that changing them (headings) might cause angst to developers needing to make the changes to established themes and regular users will be posting in our forums. There was a proposal to roll the accessibility updates in a new bp-template pack. @rayisme added, “Let’s roll with the accessibility changes and be ultra-aggressive with the heading styling so bp-legacy CSS rules take precedence.”  @mercime commented that committing the updates early in the 2.6 dev cycle will allow ~ 3 months for developers to update themes.  Accessible BP templates are the way to go forward. @djpaulgibbs: “We need to do these. We also need to get the companion stylesheets updated for these changes (if/as necessary). Let’s post on bpdevel once the changes are in. We can contact the major BP theme builders in advance. ”
Action: First batch of new heading updates have been committed to trunk after the meeting.

Slack log:

#6678, #6719, #6875, #6882, #6898, #6911, #dev-chat

Core Dev Chat Summary for February 3, 2016

Trac Tickets

Autoload BP classes (#6853) @boonebgorges noted the performance benefits in chat and in ticket. Update: “Rough benchmarks are showing a pretty consistent memory savings of between 1.5 and 2MB, on a local dev installation that has about a zillion plugins running … And with some further rearrangement in the future (so that components are loaded in a sleeker way) we could get that number down even further.”

All classes should be in their own files (#6870) @boonebgorges indicated that “it’s possible that full autoload (#6853) will reduce BP’s memory footprint by 10 or 20%” with the moves for all components. Update: This has been committed to core.

Comment syncing between activity and post comments for Custom Post Types (#6482) @im4th mentioned that the feature was not completed yet. Update: This feature has been committed to core.

Screen notifications settings page (#6712) @rayisme will be working to get this in for 2.5.0. Update: Refreshed patch has been uploaded.

BP_Attachment::get_image_data() unit test is failing due to upstream change (#6868) @im4th has created ticket in WP Core because BP unit tests for `BP_Attachment::get_image_data()` were failing due to changes upstream. Update: The fix has been committed to core.

Use WP page names for BP directory pages headings (#6765) @hnla requested dev feedback.

Accessibility: Provide sufficient color contrast in stylesheets to meet WCAG 2.0 AA standards (#6838) @mercime Update: This enhancement has been committed to core.

Suspension of BP comment moderation functionality (#6822)  @hnla and @boonebgorges discussed the pros and cons of removing BP comment moderation.

BuddyPress 2.5.0

  • Beta 1 is scheduled for today, February 8.
  • There are now 86 tickets slated for this cycle. (Closed: 73. Active: 13.)
  • From @boonebgorges: We’ll need to assemble a beta post by Monday. Traditionally, this has been a bullet-point list of big features, along with pointers to anything that needs special attention from users/developers testing the beta. I have outlined some of the new features already, but if people think of other things, they should speak up.

Slack log:

#6482, #6712, #6765, #6822, #6838, #6868, #6870, #dev-chat