BP Dev Chat Summary: January 15, 2020

Main features for 6.0.0

BP REST API (improvements and remaining endpoints)

@espellcaste has been working on fixing some issues posted on the GH repository. With @im4th they discussed quite a time about one specific issue that is now resolved (many thanks to @espellcaste for his work on it 💪). About the tasks scheduled for 6.0.0, you can take a look at this GH project. Here are the remaining endpoints:

  • Member’s cover endpoint
  • Group’s cover endpoint
  • Friends endpoint
  • Blogs endpoint
  • Blog’s cover endpoint
  • Blog’s avatar endpoint
  • Signups endpoint

FYI this Core ticket should also be fixed for 6.0.0: #8156 (Move Avatar into the Members component).

BP Blocks

@karmatosed has shared sketches and thoughts about the first 2 BuddyPress blocks we will add in 6.0.0:

@im4th will start working asap on the first implementations of these 2 blocks building an autocomplete control to select the member or the group to display. @dcavins suggested this could be a good opportunity to review our Suggestion API so that it uses the BP REST API.

Network invitations & Membership requests.

@dcavins will work to make it happen in 6.0.0, you can still add your feedbacks on this ticket #8139.

Surprises!

@mercime & @im4th will also try to work on some surprises for this next release. We are keeping the features secret for now 😂

Core improvements

@im4th also shared his wish to use WordPress Rewrites instead of our legacy way of building URLs, see #4954. A possible way of progressing about it could be to use a plugin… He will look into it to see if it needs some Core adjustments.

BuddyPress survey

Discussing about the previous points took us a while and we decided to talk about the survey during our next dev-chat.

Open floor

@espellcaste cannot attend our dev-chats at the date/time they are scheduled. I’ve published this doodle to let us try to find a new day / time of the week for our meetings. I’ve left the current day / time: choose it if you prefer to leave the day / time unchanged.

6.0.0 schedule & main features

  • Schedule:
    • First beta at the end of march.
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints
    • BP Blocks
    • Network invitation & Membership requests
    • & maybe some surprises!

Next dev chat

It will happen next week at the time/date we decide replying to this doodle (and of course in #BuddyPress).

PS: if you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#6-0-0

BP Dev Chat Agenda for January 15

Hi!

Let’s meet for the first time of the year 2020 in #BuddyPress at 19:00 UTC on January 15 (today!!!) to discuss about :

  • The 6.0.0 main features,
  • The BuddyPress 2020 survey
  • Open floor.

FYI, during last dev chat we agreed on this schedule for 6.0.0 :

  • First beta at the end of march.
  • Final release at the end of April.

If you have anything you wish to add (or remove) to this agenda or specific items related to those listed above, please leave a comment below.

#6-0-0

A new site for BuddyPress contributors

During our 5.0.0 development cycle we’ve been working on launching a new site for BuddyPress developers so that they can get help about using the BP REST API, for 6.0.0, I’m proposing to work on launching a specific site for BuddyPress contributors to help them get involved.

Migrating BP Devel to Make.BuddyPress.org

5 weeks ago, I’ve updated #5525-buddypress to inform about the plugins and themes we need to make it happen.

NB: as I’ve noted on the ticket’s comment, we would also need to migrate the BP Devel blog’s subscriptions using the JetPack tool.

Today, I’m informing you I’ve put up a testing site to help us see how it could look, behave and I hope help us start writing a BuddyPress contributors handbook.

BuddyPress contributors handbook

I know that contributing to BuddyPress is very similar to contributing to WordPress and that Make.WordPress.org core’s handbook is a great resource we could use to explain how to report a bug, test a patch, write a patch, etc..

I believe we need more than a link to this tool, I believe we need to get inspired by it to write our very own handbook with command/code examples specific to BuddyPress. For example: we could have a page with detailed step to checkout BuddyPress trunk from SVN like this one.

I’m pretty sure this handbook would greatly help new contributors to get started.

Let’s do it!

If you tried to click on the test drive link, you’ve seen you need to log in to access to it. I think, to avoid confusions with BP Devel or the possible/future Make.BuddyPress.org sites it’s best to restrict its access.

If you want to contribute to the making of this site by testing it or by writing one or more pages of the BuddyPress contributors handbook, you just need to send me a direct message on Slack (@imath) or simply use the form below to send it to me by email. I’ll be very happy to give you an access to it with writing capabilities.

Thanks in advance for your help and interest.

#5525, #6-0-0

BP Dev Chat Agenda: November 13, 2019

Hi BuddyPress contributors!

This is the agenda for our next Dev Chat which will happen this Wednesday at 18:00 UTC (tomorrow!!) in #BuddyPress. Please note we’ve changed our meeting’s time to 18:00 UTC.

  1. 5.1.0
    • 5.1.0-beta was published on November 6, let’s schedule 5.1.0 release.
  2. BP Beta Tester
    • Have you tested it? Is it ready to be published on the WordPress.org plugins directory ? FYI, I’ve just released a 1.0.0-RC.
  3. 6.0.0
  4. BuddyPress.org
    • #8153 BuddyPress survey for 2019.
    • #5525 Move BP Devel (this site) to Make.BuddyPress.org

If you have anything you wish to add (or remove) to this agenda or specific items related to those listed above, please leave a comment below.

#5-0-0, #6-0-0

BuddyPress 5.1.0-beta1 + BP Beta Tester 1.0.0-beta1

The next maintenance release (5.1.0) for BuddyPress is available for testing, you can read more about it here: https://buddypress.org/2019/11/buddypress-5-1-0-beta1/

We’re also testing a new plugin to help you test future BuddyPress beta and release candidates: BP Beta Tester.

Thanks in advance for your tests ♥️

#5-0-0, #beta

Take the BuddyPress Blocks Poll

Dear BuddyPress Contributors, Developers & Users, let’s talk about BuddyPress blocks!

In 5.0.0, we introduced the BP REST API and a BuddyPress Blocks category: these two pieces are the foundation for inserting and organizing BuddyPress content within the Block Editor.

The Development Team has been talking about possible ways BuddyPress could take advantage of what the Gutenberg Project brings to WordPress. We have some ideas but we would like to know what you would use BuddyPress blocks for. Let us know your thoughts by taking this poll.

Take the BuddyPress Blocks Poll

To tease your imagination we’ve added a list of possible BuddyPress blocks, though you should feel free to add your own ideas using the last checkbox. If the checkbox entry form is too limited for explaining your idea, use the comment form below the poll to share your thoughts with us.

Thanks a lot for your contributions ♥️

#6-0-0, #poll

BP Dev Chat Summary: October 2, 2019

5.0.0 development cycle report

BuddyPress 5.0.0 was released on September 30, 2 days before this dev-chat happened.

First feedbacks

@boonebgorges was the first to share his feedback about this release. He congratulated the “5.0 team” for their amazing contributions.

@im4th sent new props to all 5.0 contributors and informed about the first results of the release in terms of downloads. The spike was reached on October 1st with 23562 downloads (~1K less than the one we had for 4.4.0). At the time of the dev-chat, no support topics were posted about issues relative to the 5.0.0 upgrade.

We unfortunately had an issue with po/mo language packs generation. Thankfully, the Meta Team fixed it very quickly and we updated our release process to make sure it won’t happen again.

What have we done well?

For @espellcaste we kept our development meetings (dev-chat) consistent (every two weeks). He also think publishing development notes during the development cycle and before the release was a good practice.

@im4th thinks having the BP REST API documentation ready before the release was a great team achievement. Developing the BP REST API from GitHub was also a great way to save some time (especially when rebasing!)

What can we improve?

We all noticed testing involvement was very low during 5.0.0 beta tests. We’ve tried to understand the reasons behind this fact:

  • lack of interest?
  • lack of time?
  • lack of visibility of our communication?
  • total confidence in our work?

It’s important we try to reach and get the involvement of early adopters, advanced users, plugin and theme developers during BuddyPress major release beta tests.

@im4th then asked if the frequency and the schedule time of meetings were suitable for all. The “every other Wednesday” seems to be fine with everyone but moving the schedule time to one hour earlier seems better.

What’s next in BuddyPress?

6.0.0 priorities

The first priority is to complete the BP REST API with the remaining endpoints (#7156).

About the Gutenberg project and to follow up with a previous conversation we had about it. We need to have a better idea about BuddyPress users needs on the BuddyPress Blocks (#8048) topic: that’s why we’ll share a poll with them. @dcavins thinks the obvious first step is to have a block version of our existing widgets: we all agreed. About the poll, as @boonebgorges pointed out we might have a very limited participation to it, so we will have to analyze the results very carefully. He also pointed out the poll was to consider as one input like any other. @im4th will work on a text about it in order to be able to explain and share the poll on this blog and on one BuddyPress forums topic.

@im4th thinks that more than blocks BuddyPress users are expecting a “BuddyPress maintained” component to manage User Media (#8022). He plans to revamp the BP Attachments plugin he started a while ago to try to have something ready for 6.0.0.

@im4th is also planning to work on migrating the way BuddyPress builds URL to use the WP Rewrites API (#4954). He thinks that as it’s a breaking change, we need to build it so that it can be “tested & deactivated” for a while.

@dcavins will take benefit of the new BP Invitations API to work on Network invitations and membership requests (#8139). He renew his wish to get our feedbacks about the road he plans to take.

After the dev-chat @im4th & @johnjamesjacoby also talked about including the BerlinDB features into BuddyPress.

How can we have more betatesters?

@im4th shared his ideas about this potential improvement we all agreed on during our 5.0.0 cycle development report:

  • A beta tester plugin just like the WordPress one, but for BuddyPress.
  • Migrate this blog into the BuddyPress.org network (#5525) and extend it to include a handbook about contributing to BuddyPress.

How can we improve the way users get help?

Unfortunately we ran short of time and decided to talk about this point during our next dev-chat.

Next dev-chat

It will happen on October 16 at 18:00 UTC in #BuddyPress. We moved our dev-chat time to one hour earlier, don’t miss it!

PS: if you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#5-0-0, #6-0-0