2016 BuddyPress Survey for Site Builders and Theme/Plugin Developers

Earlier this year, Project leads @johnjamesjacoby, @boonebgorges, and @djpaulgibbs presented a number of strategic priorities which included defining the primary intended audience for BuddyPress: Site Builders and WordPress Developers, an explicit recognition of what BuddyPress has become, and how people use it.

Help us start the year right in 2017. Your feedback is important to help us improve BuddyPress by ensuring that we’re still building what you want to use and help us determine if any course corrections are necessary.

This survey will run from November 1 – 30, 2016. There are 36 questions and could take around 15 – 20 minutes to complete.

Thank you for your participation !

=> Take the 2016 BuddyPress Survey now.

Dev Chat Summary for November 23, 2016

BuddyPress 2.7.3

  • Release date: TBA
  • There are currently 4 tickets in queue.
  • Can’t upload profile images in Microsoft Edge browser (#7360) Has patch.
  • Empty date profile fields can return the epoch date (#7351) Has patch.
  • Notice: Trying to get property of non-object (#7329) Has patch.
  • readme.txt: Remove link to recommended plugins (#7328) Has patch.

BuddyPress 2.8

BuddyPress Component Maintainers – If you’re interested in contributing to the project, please feel free to comment in the post.

XProfile: do not store serialized arrays for multi-value profile field data (#6789) @offereins will take this on as his first component maintainer ticket.

BuddyPress 2016 Survey

If you haven’t taken the survey yet, please take this opportunity to contribute to the development of BuddyPress for 2017. The survey for BuddyPress Theme/Plugin Developers and Site Builders will be closing next week. Thank you!

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


Dev Chat Summary for November 16, 2016

Trac Gardening

@slaffik has been reviewing old tickets, closing some, adding others to 2.8, and “providing feedback where I see fit.” A friendly reminder to core devs to review tickets marked with `2nd-opinion`⁠⁠⁠⁠ and `⁠⁠⁠⁠dev-feedback`.

Welcome to our New Committers!

Congratulations to @slaffik and @netweb and @offereins for getting commit access! We all look forward to working with you in making BuddyPress greater than ever🙂

Banners for the BuddyPress 2016 Survey

@johnjamesjacoby has added banners linking to the BuddyPress 2016 Survey at https://buddypress.org and https://codex.buddypress.org The survey will run through November 30, 2016.


Bumping Required WordPress Version

BuddyPress 2.8 will require at least WordPress 4.3. (#7350)

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


In accordance with our WP…

In accordance with our WP compatibility policy, BuddyPress 2.8 will require WordPress 4.3. See https://buddypress.trac.wordpress.org/ticket/7350.

#2-8, #wp-requirements

Call for Components Maintainers

All the BuddyPress development takes place in Trac. All the tickets, most of the feature discussions and confirmed bugs, are all managed via Trac. For better tickets management, we use milestones, components, keywords and other ways to categorize everything. So far we have 24 components:

Component Tickets Maintainer
Activity 87 @lmoffereins
Administration 17  @slaFFik
Blogs 15
BuddyPress.org Sites 26
Build/Test Tools 8 @netweb
Core 157 @boonebgorges
Emails 17 @djpaulgibbs
Extended Profile 58 @lmoffereins
Forums 6
Friends 9 @henry.wright
Groups 58
I18N 10 @slaFFik
Media 13
Members 32 @espellcaste
Messages 16
Navigation 2
New User Experience 2
Performance 4
REST API 2 @espellcaste
Registration 6
Route Parser 7 @boonebgorges
Settings 4
Templates 55
Toolbar & Notifications 22

WordPress (as well as some other OSS) uses an interesting approach where a person or a group of people are responsible for a specific component of a software project. The contributors have a specific interest in their chosen component, and enjoy or see the need to focus most of their contribution time on it.

In the long run, this helps that contributor quickly triage tickets in their preferred component, as they specialize in it and build up a knowledge advantage. The overall project benefits by faster review and prioritisation of new tickets.

I propose to implement BuddyPress component maintainers, with the hope that this will help move development even further and faster.

Some components, like Activity, Extended Profile, and Groups, need special love, as the number of tickets there is 50+. These components will benefit from having multiple component maintainers assigned to them.

Component maintainers don’t need to do anything special – just consider reviewing Trac tickets for your component, when you have a will and time to contribute to BuddyPress. You will be expected to look through all existing tickets, as well as new ones, provide feedback and help the larger project prioritise bug fixes and new features.

If you have any thoughts about this, or want to volunteer to become a component maintainer – please write in comments. And remember, it’s good to have several people per component, so join in even if you see someone’s mentioned your favorite component!


Dev Chat Summary for November 9, 2016

Trac Clean Up

@slaffik proposed the following actions to address the 654+ tickets in the Future Release milestone:
1) Go through tickets with 2nd-opinion and dev-feedback – and reply, close, or consider working on it.
2) Go through tickets that were updated years ago – and consider them to be closed by default, but read and investigate the value. If a ticket has been left for a long time in Trac, it’s either not that important, a duplicate, hard, or forgotten.

@johnjamesjacoby noted, “Proper organization, along with timely responses, I think are more important, but I agree that keeping it tidy reduces the cognitive burden of ‘holy moly there are 500 things to do.'”

Components maintainers

@slaffik and @djpaulgibbs will be preparing a post calling for BuddyPress component maintainers soon. Per previous dev chat, there’s a Google Spreadsheet @offereins prepared earlier this year. @slaffik has added a new sheet, ‘Blad 2’, listing components per trac.

Trac Tickets

BuddyPress MU (#4732) Closed as wontfix.

Add Help Pointers to Admin (#4672) Closed as wontfix.

BuddyPress 2016 Survey

The survey for Theme/Plugin Developers and Site Builders will be running through November 30, 2016. https://buddypress.org/2016/11/2016-buddypress-survey-site-builders-developers/

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


Committer updates for BuddyPress 2.8

For the 2.8 dev cycle, we’re pleased to announce that three contributors will be joining us as guest committers:

  • Slava Abakumov (slaFFik) is the BP 2.8 release lead. He’s a longtime contributor to the BuddyPress project, where’s he’s had an especially notable impact on improving internationalization and extensibility.
  • Stephen Edgar (netweb) will be joining the team to focus on build/test tools. He is a member of the bbPress team, and plays an extensive role maintaining build tools for bbPress, BP, and WP.
  • Laurens Offereins (Offereins) has been contributing to BuddyPress since 2014. He’s been key in building out the Member Type and Group Type features over the last few releases, bringing a keen eye for spotting nasty bugs.

Congratulations to Slava, Stephen, and Laurens!

#2-8, #committers

I’ve updated the dates in…

I’ve updated the dates in the Schedule (in the sidebar of the bpdevel.wordpress.com site) for the #2.8 release timetable.