BP Dev-Chat Summary: May 6, 2020

Before discussing about the points on our agenda, @im4th explained why he quickly packaged a second Release Candidate on May 3rd. His goal was to early fix an issue about the BuddyPress build process regarding how JavaScript i18n strings can be identified by GlotPress on our WordPress.org plugin repository. The idea was to leave as much time as possible to Polyglots Contributors to help us make available our next major release in as much languages as possible.

BuddyPress 6.0.0 Hello & Credits Screens, & the 2020 survey

We’ve been discussing about an a11y issue @mercime raised into this comment. @im4th said he will look into it asap to try to fix it before 6.0.0 release. The improvements @dcavins (many thanks for your help) brought to the initial patch has been taken in account during the first commit about the Hello Screen. We will add the link to the 2020 survey at the last minute. @mercime already opened a ticket on Meta Trac to request for survey banners on our sites (BuddyPress.org, the Codex and the Developer Ressources site). @mercime (many thanks to you too!!) also committed to update the props of the Credits Screen for 6.0.0. The 2 last steps about props are to:

  • include the Polyglots contributors to the Props list.
  • introduce a new section “Noteworthy Contributors to 6.0.0” and do the required updates about the drop of the “Recent Rockstars” one.

About this new section @im4th suggested to add  @vapvarun @IAmTheWebb and @Passoniate to it and left “nomination” opened if other members of the team want to add other important contributors to 6.0.0.

Finally, we’ve listed the ultimate tasks to achieve before 6.0.0 release.

  1. Fix last PHP 7.4 issues. Many thanks to @rayisme for dealing with it and fixing it 💪.
  2. Update the 6.0.0 changelog.
  3. Write the 6.0.0 announcement post.
  4. Choose the Pizza name for this release (@im4th will reach out to team’s member privately in Slack to keep it secret until d-day!).

BP REST API Documentation updates

After @im4th‘s first pass about it less than 10 endpoints needed a review/update. He thinks it’s doable before the release date and since the dev-chat, it’s important to mention that @mercime has been doing an amazing job about it reviewing and updating 11 endpoints so far 👏🏆.

6.0.0 Final schedule

BuddyPress 6.0.0 is slated for release on May 14

@im4th is confident we will be able to release it for May 14th. No blockers were raised during the meeting, so let’s do it !

Next dev chat

It will happen on May 20 at 19:00 UTC (a week after release) and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#6-0-0, #dev-chat

BP Dev Chat Summary: April 22, 2020

Hello screen & BuddyPress 2020 survey

The ticket for the Hello Screen has been created on Trac (#8270). @im4th started the meeting by asking feedbacks about it. @IAmTheWebb after a brain to html conversion of the patch thinks it looks good. A screenshot of the Hello Screen has been added to the ticket to ease this conversion 😅. @im4th also said there was a placeholder to insert the link to the BuddyPress Survey 2020.

@mercime volunteered to draft the 6.0.0 changelog 😍. She already prepared a first version of it using @rayisme‘s BP Changelog. Here’s the link to its preview if some of us wants to give a hand to fine tune it.

BP REST API documentation updates

@im4th shared the GH issue we can use to follow our progress about this task. He said he would take care of documenting the 6 new endpoints as the process to create new documentation pages using the BP REST API inline documentation is a pain to complete. He just finished adding these 6 new documentation page today (April 29). We still need to check all the other endpoints are up to date with latest BP REST API improvements.

Discussions about 6.0.0-RC1 & 6.0.0 schedule

At the time of the dev-chat there was 3 tickets in the milestone’s queue. As @IAmTheWebb noticed the ticket about the removal of the Legacy BuddyBar (#7729) was needing some extra time to be fixed during this release, so @im4th moved it to next major release. @im4th said he would take a deeper look to the ticket about the privacy data introduced in WP 5.4 (#8266). He did so 40 hours ago and decided to also move this ticket to next major release.

We agreed on a new schedule to leave 2 weeks between RC1 and final release so that translation contributors can help us making BuddyPress 6.0.0 available in as many language as possible. So here it is:

  • 6.0.0 RC1: April 29 (in a few hours 🏃‍♀️🏃‍♂️)
  • 6.0.0: May 14

Open floor

@im4th started by saying a big “TY” to @boonebgorges who packaged the 5.2 maintenance and security release the day before the dev-chat.

About #meta-5141 @mercime suggested to add a new page on BuddyPress.org to introduce our two documentation resources (The Codex & Developer site). @im4th agreed it was a great idea.

Next dev chat

It will happen on May 6 at 19:00 UTC (a week before final release) and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

😷 Stay safe

#6-0-0, #dev-chat

BP Dev Chat summary: April 8, 2020

BuddyPress Survey

@mercime has decided to wait for 6.0.0 final release to launch the survey. We will be able to add a link to it inside the “Hello BuddyPress 6.0.0” screen (See #8270). There will be 17 questions into the survey. If one of the team members wishes to request a new one, the deadline to make it happen is the day before the release date.

Progress about 6.0.0 release

6.0.0-beta1 was released on March 31 at 10:43 PM (WP Plugins directory’s time) : just before the end of march as announced 💪⏱. The WP Tavern wrote a great post about it and shared a very interesting feedback that has been converted to this ticket (#8271) since. The patch will soon be committed.

@johnjamesjacoby will try to find a way to get more information about future beta/RC downloads as we are always worrying to have very few feedbacks about them.

@rayisme is requesting your feedback about the 2 new exportable privacy data types, please do so adding your comment to this ticket: #8266.

He also fixed a very annoying error about a deprecated WP privacy function: it’s already available into the 5.0 branch and will be shipped during our next maintenance release. FYI: the problem is WP moved the deprecated function into a file that is only loaded into the /wp-admin context.

@im4th will package a new beta release (the second) on April 15.

BP REST API documentation update.

@im4th said he was sorry he couldn’t find the time to write some explanations about how to updated the documentation. He has since done using the Swagger UI tool. Here are the explanations (NB: in this Gist, there’s a file over the bp-custom.php one, you will also need).

Open floor

@espellcaste asked about the BP GraphQL documentation’s ticket on Meta Trac since it has not evolved for a while. 😬

@mercime has suggested to include a link to the developer.bp.org’s site inside the BuddyPress.org main menu. She wrote a ticket about it on Meta Trac. 💡👍

@im4th thanked Varun & IAmTheWebb for their very interesting contributions to the dev chat: everyone is welcome to do like them 🤝.

6.0.0 schedule & main features

  • Schedule:
    • Beta-2 April 15
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints ✅
    • BP Blocks ✅

Next dev chat

It will happen on April 22 at 19:00 UTC (a big week before final release ) and of course in #BuddyPress. If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

🏡 Stay safe & Happy Easter 🥚

#6-0-0, #dev-chat

BP Dev Chat Summary: March 25th, 2020

BuddyPress Survey

@mercime has prepared 17 questions for the survey. She asked about the possible GraphQL question @espellcaste suggested to add during our previous dev-chat. If Renato has ideas about it, she will be able to insert it. About the survey publication date, @im4th suggested to add a link inside the “Hello BuddyPress 6.0.0” screen. @mercime was thinking about publishing it earlier to be able to close it before 6.0.0 release. @mercime will decide what’s the best option.

Progress about 6.0.0 release

@im4th reminded the dev-chat participants, the beta was scheduled 6 days later (at this time, today at the time I’m writing this summary!). He asked if a ticket or a feature needed an extra delay to be fixed : it wasn’t the case.

@mercime and @dcavins said they will give a test to the new BuddyPress blocks that had just been added to BuddyPress core (See #8048).

@im4th shared he still needed to work on the inclusion of the BP REST API remaining endpoints into BuddyPress 6.0.0. #7156 has been committed since.

BP REST API documentation update.

Once BuddyPress 6.0.0-beta1 will be released, we’ll need to update the BP REST API reference so that the new endpoints are documented before 6.0.0 stable release.

@mercime & @dcavins volunteered to give a hand 😍. @im4th will write some explanations about how to update the documentation on the https://developer.buddypress.org site.

6.0.0 schedule & main features

  • Schedule:
    • First beta in a few hours!
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints ✅
    • BP Blocks ✅

Next dev chat

It will happen on April 8 at 19:00 UTC (a few days before first beta 🙄) and of course in #BuddyPress. 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 Summary: March 11th, 2020

BuddyPress Survey

We’ve been discussing about adding questions about 2 topics : BuddyPress integration with e-commerce plugins and BuddyPress alternatives. We found a compromise about the second topic and @mercime will add this question:

What other networking/membership plugin/software have you considered or used?

@espellcaste suggested to add a question about BP GraphQL consideration. @im4th suggested to add this feedback to the Google doc @mercime uses to work on the survey questions.

Progress about 6.0.0 release

@im4th asked about the BP REST API complete merge into BuddyPress core now all remaining endpoints are ready. @espellcaste prefers to keep maintaining it from its GitHub repository for now.

@im4th has decided to merge the BP Blocks plugin into BuddyPress core, following @johnjamesjacoby advice to reconsider his first idea about only merging “JavaScript built” blocks. A complete merge seems a better option to make sure to generate a pot file taking in account JavaScript translations. He recently added a patch on #8048 to make this happen, feedbacks welcome.

@dcavins was a bit worried he needed more than 2 weeks to end the Network invites work. If it’s the case, he will only include a portion of the code into 6.0.0.

Finally @im4th asked for help about #7729 @rayisme has been working on during. It’s about removing the legacy BuddyBar.

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 on March 25 at 19:00 UTC (a few days before first beta 🙄) and of course in #BuddyPress. 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 Summary: February 12, 2020

BuddyPress Survey

@mercime shared her progress about her first pass on the BuddyPress survey for 2020 (see #8153). She prepared 16 questions.

  • We’ll use CrowdSignal to publish the survey.
  • On a side note @johnjamesjacoby suggested BuddyPress could have a lightweight Questionnaire component, @im4th believes it’s a great idea !
  • @mercime shared with all of us the questions she worked on after the dev-chat. Please take some time to review it before our next dev-chat

BuddyPress dev-chat are maintained on every other wednesday at 1900 UTC.

Unfortunately @espellcaste can’t join us on all the alternative days of week we’ve found into the doodle 😦 As the result it doesn’t worth changing our dev-chat meeting day/time.

6.0.0 Progress

@dcavins is making good progress about Network invites (#8139). He’s getting some inspiration from the Invite Anyone plugin. @im4th asked if it would be possible to invite a user not yet registered to the site to join it using a group invite, and the reply is yes 🙌

@im4th confirmed BuddyPress 6.0.0 will ship 2 Blocks and shared his progress about the Group Block. Here are 3 early screenshots of how it could look like :

The team also shared their thoughts about whether we should ship the JavaScript built blocks or include the complete JavaScript source files into trunk and build the Production scripts from there. At the minimum we’ll need to move to using WP CLI to generate our POT file so that JavaScript translations are available within GlotPress. @im4th will work on this asap from this trac ticket #8048.

Finaly we’ve talked about the fact the project behind the JavaScript library we are using for our suggestions feature is no longer maintained. We shared thoughts about moving to the Tribute library and using the BP REST API instead of AJAX. So far there are no impacts on the suggestions feature and we are taking some more time to think about it, having in mind we could also benefit from the BP AutoCompleter React component we’ve built for our 2 BP Blocks.

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 in 2 days on February 26 at 19:00 UTC and of course in #BuddyPress.

PS1: sorry it took me so long to write this summary 😬

PS2: 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 Summary: October 30, 2019

Actions

The BuddyPress Blocks poll

@im4th shared the final result of the poll. There was 161 votes and top results are mostly corresponding to existing widgets. Here are the “top expected blocks” :

  1. A block to share a post or a page via the Activity Stream (17 votes)
  2. A block to list the recently published posts from across your network (Exists as a widget) (13 votes)
  3. A block to display Sitewide Notices posted by the site administrator (Exists as a widget) (12 votes)

@johnjamesjacoby confirmed Widgets were obvious converts and @boonebgorges suggested to work on the block highlighting a single Group (10 votes) as a starting point. Highlighting a single group is not something we make possible yet and he confirmed it’s something people want. We’ve decided to:

  • Start working on this block for 6.0.0 from a specific GitHub repository: BP Blocks
  • Merge the « JavaScript built » blocks into BuddyPress Core to avoid adding too much node modules to it.
  • Publish the full results and the decision above on BuddyPress.org

Moreover, we’re very happy to announce @karmatosed (Tammie Lister) will give us a hand about designing BuddyPress Blocks 😍 🙌

5.1.0

Before releasing this maintenance version to fix these issues, @im4th will package a 5.1.0-beta release so that we can test the BP Beta Tester plugin with a “real world” example. Once the results of this test are satisfying, we’ll publish the plugin on the WordPress.org directory.

BP REST API

@espellcaste shared the latest news about it. We’ve been talking about adding a controller to manage the Blogs avatar. Renato is wondering why we are falling back to the Blog’s Administrator’s avatar if the site does not include a Site icon. @dcavins thinks it only makes sense when displayed blogs are really “weblogs”. @im4th will soon create an issue on the GH repository of the BP REST API to explain why this fallback choice was made.

NB: To work on the Blogs avatars, we first need to have this ticket (#8150) fixed (in particular for the get_item() controller’s method).

@espellcaste also talked about the historical dependency of users local avatars to the xProfile component. So far, it’s not possible to upload/delete a local avatar using the Member’s Avatar controller if the xProfile is inactive. As a result, the BP REST API documentation has been updated and 5.1.0 will move this controller’s loading into the xProfile component’s class. @im4th as he “promised” during the dev-chat has been working on trying to make the local avatar and the cover image Members features for 6.0.0. There’s already a first patch available for testing/review on this ticket (#8156).

@espellcaste finally talked about the decisions he made about developing a BP GraphQL API using the WP-GraphQL plugin: he’ll focus more on specific components rather than adding support to several components.

Tickets needing feedbacks

As there were only 5 minutes left, @im4th briefly announced the work he has been doing about moving the BP Devel site (this site) to a new Make.BuddyPress.org site (see #5525). This ticket contains screenshots and the needed plugins and themes to make it possible. Please have a look at this 🙏

@dcavins also reminded everyone he was expecting more feedbacks about his ticket dealing with “Network Invitations and Membership Requests” (see #8139). Thanks in advance for looking at it 👀

2 other tickets are needing feedbacks: please have a look at them before our next dev-chat:

  • #8148 A new direction regarding optional components management (using the WordPress.org Plugins API).
  • #8153 BuddyPress survey for 2019.

Next dev-chat

It will happen on November 13 at 18:00 UTC in #BuddyPress.

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