Core Dev Chat Summary for January 27, 2016

Trac Tickets

Comment syncing between activity and post comments for Custom Post Types (#6842)  @im4th needed to run an upgrade routine to add a new activity meta to activities about a blog post and consulted whether he could do this using a regular upgrade routine or wait for #6841 to be fixed to committed to core.  @boonebgorges, @djpaulgibbs, @johnjamesjacoby, @rayisme, and @dcavins joined in the discussion to find the optimal solution in the upgrade routine. @im4th also suggested using a dynamic meta_key so that he could avoid the upgrade routine. Update: @im4th has uploaded a new patch which shows that using the dynamic meta_key can avoid an upgrade routine 🙂

Profile/Cover image upload doesn’t work in MS Edge browser (#6846) Update: @im4th just committed to trunk and 2.4 branch so this one’s fixed already 🙂

Email API and customisation features (#6592)  @djpaulgibbs has started committing section by organized section of this cool new feature last week (Jan. 27). Dev feedback welcome.

BuddyPress 2.5.0

  • Beta 1: February 8, 2016
  • RC 1 (string freeze): February 22, 2016
  • Target Release Date: March 2, 2016
  • There are 126 tickets slated for this cycle to date. (Closed: 41. Active: 85)

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

#6592, #6842, #6846, #dev-chat

Core Dev Chat Summary for January 20, 2016

This summary includes pertinent developer conversations in Slack before and right after the official chat time last week.

Trac Tickets

Email API and customisation features (#6592) Three hours before dev chat, @boonebgorges and @djpaulgibbs had a long and interesting discussion about the new Email API. Topics covered: standardizing verbs for method names, choosing taxonomy for Email Types to give admins the option of implementing multiple templates, among others. Latest: @djpaulgibbs has since updated the `amazing-emails` branch at https://github.com/paulgibbs/buddypress/

XProfile field database schema (#6350) @johnjamesjacoby will be writing down his vision for improving the xProfile tables.

Groups: Add Profile Fields and Profile Field Groups (#6783) From an enhancement for the Groups component, @im4th has proposed a change in direction to making this a generic component which would work for any object (Members, Groups, and Blogs) in ticket. @im4th consulted with @johnjamesjacoby about the best way forward.

Comment syncing between activity and post comments for Custom Post Types (#6482) @imath and @rayisme deliberated and agreed on adding `bp_activity_type_supports()` which works similar to WP’s `post_type_supports()` function. This would provide some flexibility if/when more features are added to BP activity types in the future.

General Administration

Messaging

A lively brainstorming session arose from a proposal by @johnjamesjacoby to replace the old “social network” association used for the past 8 years. There were slogans, taglines, and observations shared during and even after the chat:

• If we’re going to change it, can we think of it more as a strategic/goal/mission statement—more than just a tag line? ~@dcavins
• Social network” and “in a box” are both icky. Something having to do with “community” is better than “social network”. As for “in a box”, it glosses over the developer-focused flexibility of BP, which IMO is one of its strong points. ~ @boonebgorges
• It (“BP as a platform”) seems technically accurate, and speaks to the breadth of purpose, and I think it’s meaningful to a non-technical audience. I think we have two audiences – network builders and developers – so maybe our branding should have two parts too ~ @boonebgorges

BuddyPress. Go Social. Build Communities. Create Networks. ~ @mercime
Enabling Community Platforms ~ @hnla
Building Blocks for your Community ~ @jjj
Community toolbox ~ @karmatosed
Community components you can put together in a very easy and funny way ~@im4th
A suite of social components for building communities ~ @pollyplummer
BuddyPress. A developer/professional platform that can scale up to millions of users. ~ @mercime
BuddyPress: Create your own community space ~ @rayisme
You have the users, BuddyPress (has) the building blocks to kit out your community to the fullest ~@netweb
BuddyPress, an online community building kit ~ @robkk

Fun & flexible software for online communities, teams, and groups.
BuddyPress helps you build any type of community website using WordPress, with member profiles, activity streams, user groups, messaging, and more.
~ @johnjamesjacoby

New BudddyPress.org Theme

@johnjamesjacoby noted that the “theme needs a complete revamp and redesign to make it more attractive. I would like for BuddyPress & bbPress to be powered by the same theme, so that they are effectively co-branded as such.” Someone’s going to be tapped to work on the new theme.

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

#dev-chat

#6350, #6482, #6592, #6783

Core Dev Chat Summary for January 13, 2016

BuddyPress 2.5.0

  • Beta 1: February 8, 2016
  • RC 1 (string freeze): February 22, 2016
  • Target Release Date: March 2, 2016
  • There are 113 tickets slated for this cycle to date. (Closed: 29. Active: 84)

Trac Tickets Mentioned

Comment syncing between activity and post comments for Custom Post Types (#6482) @imath Patch updated. Dev feedback needed.

Comment notification NOT notified (#6057) @imath Has patch. Ready to commit. Dev feedback needed.

Manage Signups on Network Admin dashboard returns Blog Admin URL, not Network Admin URL (#6371) @imath Has patch. Ready to commit. Dev feedback needed.

Deleted activity items remain favourited (#3794) @imath Wants to reactivate the discussion on this issue. Has patch. Dev feedback needed.

developer.buddypress.org (#6812) @tw2113 has gotten the parser to work on the codebase. He will focus next on the “Members based functions” and the theme.

Email API and customisation features  (#6592) @djpaulgibbs Has uploaded separate patches for any “drive-by code reviews”. Dev feedback needed.

Slack Log: https://wordpress.slack.com/archives/buddypress/p1452715302003088

#3794, #6057, #6371, #6482, #6592, #6812, #dev-chat

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

BuddyPress 2.4.4

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

Dev Chat Summary for November 25, 2015

BuddyPress 2.4.1

  • As of 11/30/15, 2.4.1 will be released this week.
  • Six of the 7 tickets slated for this release are all good to go.
  • (#6675) WP 4.4. deprecates wp_title() will be moved to BP 2.4.2 which is scheduled sometime after WP 4.4.0 is released.

BuddyPress 2.5.0

  • @djpaulgibbs proposed start of dev cyle on Wednesday, Dec. 2, and release by March 2, 2016. He also mentioned that “we will lose probably a few weeks’ worth of development over Christmas, but I’d rather keep the pace up even if that means a smaller release.”
  • @boonebgorges noted that “in the last couple releases we’ve done fairly long beta/RC periods. I think it’s been good to be conservative. But they’ve also been too long for what we’ve actually needed. So if we think the release might be a bit smaller, we might consider a somewhat condensed period between feature-freeze and release. Not something we have to decide today.”

Wishlist

These are a few of our favorite things and suggestions for this dev cycle:

Improve BP Navigation from @im4th. @boonebgorges has started work on ticket last week refreshing the `BP_Nav` ideas. He will “dive into it after WP 4.4 comes out.”

Clear out all trac bugs from@tw2113.

Update Member home page to match new functionality of Group home page from @hnla. Can start off with user’s own `front.php` template and expand on top of this later.

BP Emails from @djpaulgibbs. This involves “architectural improvements to emails, and customizable emails. (#6592)

xProfiledata_meta from @boonebgorges.  Fix the way xProfile field visibility is stored (move from usermeta to xProfiledata_meta), which will make the data schema saner and also allow us to fix some search-related bugs.

Do the @todo items in codebase from @tw2113.

Improved caps from @im4th. Currently doing it in his template pack project.

Hashtags from @jconti. @slaffik noted that there are two BP-compatible hashtag plugins in WP repo. Chat continued on whether hashtags will be used for search vs. auto-completing hashtags or both.  @rayisme has worked on a fork of etiviti’s older hashtags plugin, will require at least some form of unicode support. He will be working on “Better compatibility when using ‘BP_ENABLE_USERNAME_COMPATIBILITY_MODE’ and UTF-8” which would also support emoji hashtags mentioned by @djpaulgibbs.

BP Template Versioning from @hnla. Feedback requested on current ticket to move the project forward.  (#6642)

developer.buddypress.org from @mercime. @djpaulgibbs noted the logistics required and testing will be needed before deployment. @boonebgorges mentioned some devs expect projects with stable APIs to have web-based documentation generated even when they are already big fans of the inline documentation.

Add “semi-private group” from @mercime. @boonebgorges pointed out that there were a couple tickets about separating the various parts of group status into standalone bits, so that you could make custom group types  like visibility vs join/invite vs who-can-invite etc. A version of “semi-private” would be some combination of these things. (#6094)

Bulk mentions for Groups from @jconti.  Feature is akin to Slack’s @ {here} {channel} {etc}. @djpaulgibbs noted that “the complexity there is around updating the notifications and probably a per-group setting to turn that on/off, when I rewrote the auto-suggest lookup stuff about a year ago, I had it in mind to be able to support group mentions, so there’s some work done already. @im4th brought up concern about notifications (emails) if a group has 200,000 members.

Reactions instead of favorites, dream from @im4th@boonebgorges replied with “A dream: BuddyPress Relationship Table and API.”  @djpaulgibbs: both ideas fill me with memories of many hours spent on those, I have like a quarter-done github branch somewhere porting Posts2Posts over if anyone’s really really keen. “

Update default templates from @hnla. Explore what we can do to update the default templates – perhaps with a focus on markup in core that can be extracted out to template directories.

There are more features, bug fixes, and enhancements not mentioned above that already have tickets in Trac and some that will have tickets soon. Join the fun in making this dev cycle another awesome one for the community!

Trac Tickets for the 2.5.0 milestone are available on this page.

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

#6094, #6592, #6642, #6675, #dev-chat

Dev Chat Summary for September 30, 2015

BuddyPress 2.3.4

  • Tickets slated for this minor release are available on this page.
  • Release date: TBA.

BuddyPress 2.4.0

  • BP 2.4.0 Beta: October 7, 2015
  • BP 2.4.0 Release: October 28, 2015
  • Fifty tickets have been closed to date. The list of tickets completed so far is available on this page.
  • There are 91 tickets left in queue.

Add UI for adding Profile Header Images for Users and Groups (#6570) Feature is in trunk. https://bpdevel.wordpress.com/2015/09/30/buddypress-2-4-0-will-introduce-cover-images-for-members-groups/
Per @im4th: Testing and feedback welcome!

Groups single item home : improve the way we deal with custom front and activity component (#6388) Feature is in trunk. https://bpdevel.wordpress.com/2015/10/03/get-ready-2-4-0-will-introduce-important-changes-in-groups-homes/ Per @im4th: Testing and feedback welcome!

Twenty Sixteen BP Companion Stylesheet. Per @hnla, this stylesheet for the upcoming default theme along with the BP companion stylesheet for Twenty Thirteen (#6533) will be released for 2.4.0. As always, testing and reporting areas which need improvements are welcome.

Template Versioning (#6642) @hnla is working with @im4th on this new feature to provide users with a list of changes to BP template files during a dev cycle @ https://github.com/imath/bp-template-checker. Discussion held in chat touched on specific processes and expectations, including: the possibility of including this for BP 2.5.0; not showing message to admins/regular users, i.e., feature is enabled when developer adds define('WP_DEBUG', true); in wp-config.php; and “show this information in a developer-y way – maybe via_doing_it_wrong() – but to be able to suppress specific notices”, among others.

Email API and customisation features (#6592) @djpaulgibbs said that he’s not sure whether this feature would make it for 2.4.0 where it would also allow time for testing and feedback. He thanked @timersys and @shanebp for feedback on his latest updates. Calling those who volunteered to get involved on Slack 🙂

Use wp_editor for “multi line text area” xprofile field in frontend (#5625) @boonebgorges is working on this ticket and will “try to carry it across the finish line for 2.4.0.”

@since standard not parseable with phpDocumentor 2 (#6576) @tw2113 has completed the standardization of @since tags for all components to pave the way for the upcoming developer.buddypress.org. In addition, he left a friendly reminder that “WP docs standards do say to have inline comments treated as proper sentences, so capitalize the first letter and provide punctuation please.”

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

#5625, #6388, #6533, #6570, #6576, #6592, #6642, #dev-chat