BP Dev Chat Agenda: October 16, 2019

Hi BuddyPress contributors!

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

  1. “Think”
    • First results about the BuddyPress Blocks Poll (🙏 take it if you haven’t done so already !)
    • How can we improve the way users get help? (We didn’t had time to discuss about this during our last dev-chat).
    • Let’s organize a BuddySesh!
  2. “Do”
    • 5.1.0 minor release.

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

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

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

BP Dev Chat Agenda: October 2, 2019

Hi BuddyPress contributors!

This is the agenda for our next Dev Chat which will happen this Wednesday (tomorrow) at 19:00 UTC in #BuddyPress.

5.0.0 “Le Gusto” was released yesterday: thanks everyone who got involved in making it happen 😍, let’s take some time to share our thoughts about the following points.

  1. 5.0.0 development cycle report
    • First feedbacks about this new release?
    • What have we done well?
    • What can we improve?
  2. What’s next in BuddyPress?
    • 6.0.0 priorities?
    • How can we improve the way users get help?
    • How can we have more betatesters?

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

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

BuddyPress 5.0.0 “Le Gusto”

We’re very happy to announce the immediate availability of BuddyPress 5.0.0 🍕. Please upgrade and share the news 😉

Here’s the official announcement post.

#5-0-0, #release

BuddyPress 5.0.0-RC2

Hi!

The second release candidate for BuddyPress 5.0.0 is now available for an ultimate round of testing!

Thanks in advance for your help 😍

#5-0-0, #rc

BP Dev Chat Summary, September 18

5.0.0’s schedule

🎯 5.0.0 release: ~ September 30.

About 5.0.0 RC1

The release candidate was packaged on September 17. A few hours late comparing to the schedule: @im4th explained this was due to last minute fixes he had to do about failing unit tests for WordPress trunk (5.3 dev cycle).

So far no feedbacks were published about this release candidate in BP Trac or in BP Support Forums.

BP Rest API Documentation site

A first version of it is now available on developer.buddypress.org. There is still work to achieve to improve the responsiveness of the theme and the way it integrates itself into the BuddyPress.org network.

@boonebgorges and @im4th agreed it was ok to launch it in this state. @im4th will soon post about it on BuddyPress.org so that BuddyPress developers are informed about the BP REST API handbook availability.

5.0.0 remaining tasks

@boonebgorges will work on extracting the release props next week. As the BP REST API has been maintained on GitHub so far, we’ll need to incorpore manually these contributor names. He & im4th will also review the “Recent Rockstars” list.

@im4th will take care of drafting the first version of the announcement post and writing the release page on the Codex.

About the 🍕 name of the 5.0.0.. It’s a surprise !

Next dev-chat

It will happen on October 2 at 19:00 UTC in #BuddyPress slack channel 2 days after the 5.0.0 release. We will talk about its first feedbacks and about our first ideas for the next(s) development cycle(s).

#5-0-0

BP Dev Chat agenda: September 18, 2019.

This is the agenda for our next Dev Chat which will happen this Wednesday (tomorrow) at 19:00 UTC in #BuddyPress.

  • 5.0.0-RC1 first feedbacks.
  • A first version of the BP REST API Documentation site is ready. Let’s discuss about how to announce it to our community.
  • 5.0.0 remaining tasks :
    • Announcement post,
    • Release page on the Codex,
    • Recent rockstars & release props,
    • 🍕 name for the release!

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

#5-0-0