July 21 Dev-Chat summary & August 4 Dev-Chat agenda

Hi everyone, sorry this summary is published very late (the day before we’re having another development meeting).

July 21 Dev-Chat summary

9.0.0 early results and feedbacks

  • 9.0.0 “Mico” was released on July 19.
  • Download spike for it happened on July 20 and reached ~33.400 downloads 📈 🎈.
  • Nothing major about it into Support forums, so @imath was able to quote @vapvarun saying: “We did not break anything big” 😅.
  • This BP Blocks focused (& short time framed) release was an interesting experience, thanks to a discussion launched by @johnjamesjacoby a bit before the dev chat, we were able to discuss about the benefits of working from a “feature as a plugin” GitHub repository. In short: it can save us some time ⏱, but bringing back code into our Trac is making us feel safer from being completely GitHub dependent.

10.0.0 is a magic number!

  • 10 is after 9, and we all feel we need to make this release a bit specific.
  • @sbrajesh has been working on the BP Relationship API and is confident he’ll be able to share a first alpha around August 18. 💪
  • Below are our first thoughts about 10.0.0:
    • A “regular” development cycle, Christmas🎄 as a release date could be a good idea!
    • It’s time BuddyPress has a Media Component, Releasing 10.0.0 once it’s ready was suggested 😇
    • Using rewrites to parse BP URLs might be a bit too early but we’ll have a “feature as a plugin” really soon to check what it means in terms of back compatibility with Plugins using the BP Legacy URL parser.
    • Carry on improving the BP REST API by using it more frequently into BP features (like we did for BP Blocks in 9.0.0)
    • A new great BP Theme seems difficult to achieve, unless we have a lot of interested contributors jumping in!
    • A site membership requests feature to compliment the site membership invites.

Nothing’s set in stone yet! Don’t hesitate to show your support for one (or more) of the above points to help us decide. And if you have great ideas, be there to share them with us during our next development meeting 👇

August 4 Dev-Chat Agenda

We had 2 weeks to think about possible features for 10.0.0, let’s decide about the ones we’ll work on during this magically numbered release cycle 🪄.

It will happen on August 4 (tomorrow) at 19:30 UTC and of course in #BuddyPress.

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.

#10-0-0, #9-0-0, #agenda, #dev-chat, #summary

BP Dev-Chat Summary: June 30/July 7, 2021

June 30 improvised dev-chat

Following the discussion we had during June 23 meeting about the frequently requested Follow feature, and a very interesting discussion between @sbrajesh, @espellcastewe and @johnjamesjacoby, we decided to improvise a new Dev Chat about a possible larger scope about it. We shared our views about building a wider vision for “relationship types” in BuddyPress. A new API that would firstly be used for the Follow feature, but could also be used for potential other needs: user likes, improved user favorites, blocking users, what may come to our mind in the future!

@sbrajesh will lead this new project using the “feature as a plugin” model like WordPress does from a BuddyPress GitHub repository. If you’re interested in contributing to this project, please “raise your hand” commenting this summary.

July 7 regular dev-chat

@im4th starts with an apology: unlike what was scheduled (July 8), we were not able to release the 9.0.0 first beta so far. Sorry about it.

9.0.0 🎯

We’ve migrated 90% of Widgets as Block Widgets from the GitHub repository we use to build BuddyPress blocks. We also improved some BP REST API endpoints and we’re on our way to include a new endpoint to deal with Sitewide Notices. BP Block Widgets have been built on 2 principles: use the BP REST API every time it’s possible and use Modern JavaScript on front-end and the Widget/Post Block Editor’s APIs (mainly built on top of React.JS) on back-end.

@dcavins has made great progress about the Sitewide Notices Block Widget (👉 the last one to reach 100%) and about the corresponding REST API Endpoints. @espellcaste gave great advices about the BP REST API to speed up the process.

We also talked about directly packaging a Release Candidate without doing a Beta release. As the 9.0.0 development cycle is focused on migrating Widgets as Blocks, we have a very limited risk of messing with other parts of BuddyPress. @im4th said he’ll work on merging the BP Blocks code into BuddyPress core and will try to find the time to quickly build a Beta Release and some time after the Release Candidate (he hates when he doesn’t do what he has written he would do).

We finally talked about the great work @vapvarun has done building a test drive to host the BuddyPress code reference. The goal is to make it available asap and before the end of the year here. The main difficulty is to generate the documentation using the WP CLI parser command directly from the server (10 minutes). @im4th wondered if this could be achieved using the WP import/export tool (the documentation plugin is using custom post types). This is an approach we’ll try to test to avoid possible downtimes of the BuddyPress.org network.

9.0.0 schedule

  • Beta: July ? 🤔
  • RC: July 12 to 14.
  • Final: July 16 to 19.

Next Dev-Chat

It will happen on July 21 at 19:30 UTC 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!

Additional note about meetings during 9.0.0 development cycle

As we are running a short development cycle, @im4th will be available every Wednesday at 19:30 UTC in #BuddyPress for an hour or more time if needed. Don’t hesitate to ping him (@imath) for help or inputs about contributing to this version of BuddyPress.

#9-0-0, #dev-chat, #relationship-api, #summary

BP Dev-Chat summary: May 26, 2021

8.0.0-beta2 feedbacks

@im4th noticed the only feedback we got from this beta release was about the BP Beta Tester plugin. The issue about this testing tool was fixed in 1.2.0. Does it mean everything’s fine with 8.0.0? We’ll see with the release candidate that was published 4 days ago: if you haven’t tested it yet, please do so 🙏.

8.0.0 remaining tasks

  • @vapvarun has been working on the 8.0.0 changelog. He found a bug with the script we’re using to generate it. He shared a fix during the chat. @im4th suggested to build a PR out of it on @rayisme‘s GH repository.
  • @johnjamesjacoby and especially @dcavins copy reviewed the Hello BuddyPress screen text on (#8468). Thanks to them we were able to clean the open tickets about the 8.0.0 milestone.
  • We agreed it was time to package RC and decided to leave less than 2 weeks of string freeze to polyglots. The goal was to avoid postponing too much the 8.0.0 final release date. As you can see above, the RC was released on May 27.

8.0.0 final schedule

  • ✅ 8.0.0-beta1: April 29,
  • ✅ 8.0.0-beta2: May 20,
  • ✅ 8.0.0-RC1: May 27,
  • 8.0.0 stable release: June 7 👀

Open floor

We’ve been talking about the BuddyPress code reference. It’s still under construction and we really need to make it available asap. @vapvarun had the opportunity to test the parser tool and the only thing we need to make sure is to avoid parsing the BP REST API controllers to avoid some kind of duplicate information with the BP REST API documentation. As it was getting late @im4th suggested to have a specific dev-chat about it.

@dcavins shared a proof-of-purpose plugin that adds some limitations on who can send site membership invites.

Screenshot of the Proof of purpose plugin @dcavins built.

If anyone has ideas for limits to add, please let @dcavins know adding issues to this GitHub repository.

Next Dev-Chat

It will happen on June 9 at 19:30 UTC and of course in #BuddyPress. We’ll probably talk about the first results/feedbacks about the 8.0.0 stable release but If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

PS: we count on you to test the 8.0.0 release candidate!

#8-0-0, #dev-chat, #release-candidate, #summary

BP Dev-Chat summary: May 12, 2021

8.0.0-beta1 feedbacks

@vapvarun checked our support forum and hasn’t found concerning feedbacks relative to this release.

@im4th replied to one of the comments that was posted on the announcement post about the next WordPress Full Site Editing (FSE) & Widgets Block Editor features. He tested the first one before our meeting and told us about his concerns during the chat. In short it’s a breaking change for the BuddyPress Theme Compat API. A pretty long discussion took place between @johnjamesjacoby @im4th and @vapvarun about it. We finally decided to open a very important ticket on our Trac to decide whether it’s on BuddyPress or FSE to adapt. If you have an opinion about it, please take a few minutes to share it with us.

8.0.0 tickets needing attention

  • About the bp_core_new_nav_default()function ticket (#8471), we decided we were too close to release date to do the necessary tests to be sure the patch doesn’t introduce some regression
  • About the BP Directory pages ticket (#8470), we think it’s best to split the ticket in 2 and deal with admin information on the Registration/Activation page during 8.0.0
  • @im4th wants to finish his audit regarding #8459 before packaging a new beta release.
  • @espellcaste reminded us about the GitHub Actions ticket (#8421). He agreed with @im4th about only committing the PHP Unit tests part.
  • We also punted the ticket about including PHPCS to our build tools (#7228) to leave us the time to discuss more about it as we don’t agree all about when to check WP PHP code standards (before committing or as soon as patching). The latter could possibly discourage people to submit patches in @im4th‘s opinion. Feel free to give us your opinion about it, commenting on the ticket.
  • Finally about the remaining release tasks (#8468). @vapvarun will take care of the changelog and @im4th will prepare the credits update.

8.0.0 updated schedule

We agreed to build a new beta release before our release candidate. @im4th will take care of it next week.

  • ✅ 8.0.0-beta1: April 29,
  • 8.0.0-beta2: ~ May 19,
  • 8.0.0 stable release: June 2.

Next Dev-Chat

It will happen on May 26 at 19:30 UTC 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!

PS: we count on you to test the 8.0.0 beta release!

#8-0-0, #dev-chat, #summary

BP Dev-Chat summary: February 17, 2021

7.2.0 Maintenance release

It was released just after the dev-chat. Its main goal is to fix an ugly issue about the BP Nouveau twentytwentyone.css companion stylesheet (See #8425). Some other tickets relative to this companion stylesheet has been fixed and added to the release.

8.0.0 progress

  • @im4th suggested we should improve the registration process, and this led us to consider fixing the following tickets for 8.0.0:
    • #6347 Let admins select profile fields to use during registration,
    • #4747 Add a profile field to manage pages needing acceptance (eg: terms of service, code of conduct),
    • He also believes the password should be set once users activated their account, he’ll probably open a new ticket about it soon.
  • @im4th requested some patch testing about 2 tickets, please help us progress on these:
    • #7162 Edit WordPress fields on front-end via new xProfile field types
    • #8001 Replace At/Who JavaScript Libraries by Tribute.

PS: about #8001, At/Who libraries contain some deprecated jQuery code and @im4th thinks we should try to keep the Mentions autocompleter to show in tinyMce as it is used into the BP Nouveau Messages UI.

Next Dev-Chat

It will happen on March 3 at 19:30 UTC 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!

#7-2-0, #8-0-0, #dev-chat, #summary

BP Dev-Chat summary: January 6, 2021

BuddyPress 8.0.0’s kick off

Unfortunately, the meeting started 30 mins later than scheduled, so we were not able to talk about all the scheduled points. @johnjamesjacoby congratulated the great work the team has accomplished during the 7.0 development cycle and the recent updates we’ve published on the BuddyPress.org’s blog.

Features / bug fixes wishlist

The call for tickets is now closed (it ended on January 13), the least we can say is it didn’t gather much wishes 😬. @im4th seems to be motivated to progress on the BP Attachments’ front, 8.0.0 might be a good milestone to have some user media feature included into BuddyPress core.

@slaffik shared his concerns about introducing the Activity scheduling feature (#7953). He thinks it should be handled by a BuddyPress plugin rather than be included into Core.

He and @im4th agreed on the fact we should deprecate the BuddyBar into this development cycle (#7729). @rayisme ‘s patch was very close to make it during the 6.0.0 release, let’s have it done!

We then talked about continuous integration and build tools. The Travis CI (.org) shutting down announcement with no specific date is concerning. @im4th has tested the Travis CI (.com) migration with 2 of his free and open source plugins and is now requested to pay for the service after a bunch of builds done. The documentation about the migration seems to be a bit misleading about this subject. @slaffik is going to work on moving to GitHub Actions (#8421) 😍 . He also opened a ticket to modernize our composer.json file (#8420). He and @im4th are thinking we should start working on WP Code Standards (#7228).

Next Dev-Chat

Let’s carry on talking about 8.0.0 during our next dev-chat: it will happen on January 20 at 19:00 UTC 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!

#8-0-0, #dev-chat, #summary

BP Dev-Chat Summary: December 2, 2020

7.0.0 release tasks progress

We started the dev chat chacking our progress about our next major release tasks.

BP REST API documentation updates@im4th100%
BP Survey results@im4th100%
7.0.0 Release note@vapvarun100%
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository
– Translators


7.0.0 Pizza Restaurant name@dcavins🤫
7.0.0 Announcement post@im4th20%

7.0.0 second release candidate

The main goal of this release candidate is to beta test improvements brought to the BP Nouveau’s compatibility with the WordPress 5.6 new default theme “Twenty Twenty-One” (see #8395). @im4th insisted on the fact it was important to make sure text was readable in both modes : dark and light and as the 7.0.0 final release will happen one or two days after WordPress 5.6, it’s important BuddyPress looks nice in Twenty Twenty-One. The initial patch attached to the ticket is using the companion stylesheet feature so that styles are only loaded for this theme or this theme’s child themes.

@vapvarun said he would test the patch asap and that he would probably improve it. That’s what he did a few days after the development meeting.

The RC2 was released very soon after.

7.0.0 release schedule update

  • 7.0.0-RC1: November 20 (string freeze).
  • 7.0.0-RC2: December 2nd
  • 7.0.0: December 9th (asap!)

We still need to finish the announcement post of the release, so we couldn’t have it packaged to the scheduled date 😞. As soon as it is ready, we will package it. Thanks in advance for your comprehension.

Open floor

Topics we’ve been talking about:

  • How to find ways to get more contributors to beta test BuddyPress? @vapvarun suggested:
    • Write a todo list about tasks to achieve for next release (8.0)
    • Improve documentation about BP support for themes
    • Make template customization easier for users (WP FSE?)
  • Possible 8.0 early tasks: #7162 & working on giving more control to the user about the registration form (allowing users to select what xProfile fields to use in this form).
  • What about having a new BP Standalone theme? @johnjamesjacoby shared his wishes about it:
    • a 3 columns bp-default looking “chat app” theme.
    • It’s time to take advantage of all the work that’s gone into BuddyPress since the beginning, and use that to rethink what a “bp-default” looking theme would be today.
    • It should be responsive and use the BP REST API.
  • What about having a BP Specific area into WP Admin to manage every feature?

Next Dev-Chat

It will happen on December 16 at 19:00 UTC 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!

#7-0-0, #dev-chat, #summary

BP Dev-Chat Summary: November 18, 2020

6.4.0 “PHP 8.0” compatibility release

BuddyPress 6.4.0 has been released yesterday, as we’ve been discussing during the development meeting, it includes fixes to PHP 8.0 deprecated notices for BP Core & BP REST. It also includes a security fix. Read more about this release.

7.0.0 release tasks progress

BP REST API documentation updates@im4th100%
BP Survey results@im4th0%
7.0.0 Release note@vapvarun40%
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository


7.0.0 Pizza Restaurant name@dcavins🤫
7.0.0 Announcement post@im4th20%

@vapvarun has been working on the release note, the remaining things to write is the changelog. @johnjamesjacoby removed the link to the BP Survey on our official site, @im4th needs to write a post about the results and publish it on BuddyPress.org asap.

7.0.0 first release candidate

We’ve spent the rest of the meeting working on getting the 7.0.0-RC1release ready:

  • @dcavins reviewed the Hello Screen texts 😍 (#8376).
  • @im4th worked on improving the Activity Embed block instructions (#8397) as only public activities can be embed into a post or a page.
  • @vapvarun tested #8394.
  • Finally we decided to include the feature to list the displayed Member’s Member Types into their profile header (#8394) as the poll @im4th made on Twitter got 83% votes for 🙌.

7.0.0-RC1 has been released 2 days late (November 20) according to the initial schedule. It’s an important step, BuddyPress plugin/theme authors should really test their piece of work against it so that our users can fully enjoy 7.0.0. If you find a bug, please open a ticket to report it on our Trac environment or use this support topic.

RC1 also marks the string freeze point of the 7.0.0 release schedule. So we will not add/edit or delete i18n strings until 7.0.0 is released. Just like what we did for 6.0.0, we will credit people who contributed to translating BuddyPress into as many languages as possible. Don’t hesitate to join the effort!

Here’s 7.0.0 (development column on GlotPress) translation tops so far:

English 🇬🇧100%
Romanian 🇷🇴100%
French 🇫🇷100%
Chinese 🇨🇳99%
Czech 🇨🇿98%

7.0.0 release schedule update

Next Dev-Chat

It will happen on December 4 at 19:00 UTC 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!

#7-0-0, #dev-chat, #summary

BP Dev-Chat Summary: November 4, 2020

7.0.0 latest updates

@im4th started the meeting sharing that the ticket (#8179) about the default Blog avatar has been committed and that a developer note has been published on this site. @vapvarun suggested we should respect some consistency about the UI we use when setting a group’s types or a member’s types. A ticket (#8389) has since been reported and fixed: from now on the WP-Admin/Extended Profile’s member type metabox will use checkboxes.

@im4th has updated the BP REST API’s Blogs Endpoint so that it enjoys the improvement we brought about the default Blog avatar (#BP-REST-358). He said he had no time to update the BP REST API developers documentation, but as he felt pretty guilty about it, he worked on it lately and made good progress as only the Signups and Friends Endpoints need a documentation review.

@dcavins has been working on updating the list of Props from our Trac environment and @im4th worked on the list of Props from the BP REST plugin GitHub repository. A patch is ready about these updates (#8376). Here are our progress about 7.0.0 release tasks.

BP REST API documentation updates@im4th90%
BP Survey results@im4th0%
7.0.0 Release note@vapvarun0%
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository


7.0.0 Pizza Restaurant name@dcavins🤫
7.0.0 Announcement post@im4th0%

Last checks before releasing 7.0.0-beta2

We’ve decided to postpone the 7.0.0-beta2 release to tomorrow (November 11th, 2020). @im4th was concerned about a cache issue (#8388) that was reported lately about the xProfile component. @dcavins volunteered to work on it and has since contributed to 2 patches. Don’t hesitate to comment on the ticket to share with him your thoughts about our 2 possible ways to fix this issue. @vapvarun brought to our attention another issue (#8386) that was reported about the BP Nouveau Template pack. @im4th volunteered to work on it. It has been since fixed. @im4th also asked @vapvarun to test the patch attached to the ticket (#8384) about making sure Site Icons / Blog avatars synchronization is also happening when BuddyPress is not network activated on multisite configurations. He recently tested it and we will probably include it into the 7.0.0-beta2 release. Finally @johnjamesjacoby improved the new strings we introduced about the BP Types UI 🤝. We finally agreed on this new schedule for the 7.0.0 development cycle.

  • 7.0.0-Beta2: November 11.
  • 7.0.0-RC: November 18.
  • 7.0.0 final release: December 9.

Open floor

@vapvarun shared his enthusiasm about the promising download results of the BuddyX theme he recently submitted on the WordPress.org Themes Directory 🍕👏📈. As it’s a beautiful BuddyPress theme, @im4th asked him to work on a post to share his experience about the process he had to go through to have his theme hosted on the official Themes Directory. We will soon publish this post on BuddyPress.org 🎨 .

We also talked about the BuddyPress code reference, it’s still under construction but @vapvarun ran some tests about it lately so we might progress about it soon!

Next Dev-Chat

It will happen on November 18 at 19:00 UTC 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!

#7-0-0, #dev-chat, #summary

BP Dev-Chat Summary: October 21, 2020

7.0.0-beta1 feedbacks

7.0.0-beta1 was released on October 16. So far, nothing specific to it was posted into our support forums. At the time we had the meeting, @im4th, thanks to @IAmTheWebb tests, had reported an issue (now fixed) with the Activity Embed block into our Trac environment. This last Friday @k3690 reported a wrong usage of the member term into a Group Type meta property (now fixed).

7.0.0 remaining tickets

  • #8292 @vapvarun submitted a patch during the meeting 💪, @im4th reviewed it some time after, brought some minor improvements and it has been fixed yesterday. It’s now possible to assigned more than one member types to users from their WP Admin Extended Profile 🙌 .
  • About #8179, @im4th asked @vapvarun to update the ticket with 2 squared corner avatars with these dimensions: 150px x 150px (full) & 50px x 50px (thumb). @im4th will try to progress on a patch in the meantime.
  • We’ve postponed #8093 (Profile Field visibility improvements) to a next milestone.
  • #8375 was reopened by the reporter, as the filter we’ve added wasn’t matching its needs. @dcavins @johnjamesjacoby & @im4th have been discussing about it last week in #BuddyPress and came to the conclusion a possible better place to allow the invitation table’s name filtering was to include the {$bp_prefix}bp_invitations table name into the global_tables property of the BP_Members_Component object. @dcavins will investigate this week about that possible change.
  • Finally shortly after our meeting, @boonebgorges reported a new ticket about improving the xprofile_get_field() function so that it only pulls up the data for a field when necessary. The patch he suggested as a first step looks safe to @im4th who thinks it should be included into the 7.0.0 release: it’s always great to improve DB performance. Please have a look at #8378 and send him some feedbacks about your thoughts.

7.0.0 release schedule update

We are going to package a new 7.0.0-beta to include as much fixes as possible considering the previous chapter. Packaging will happen shortly after our next BP Dev-Chat.

  • 7.0.0-beta2: November 4th
  • 7.0.0-RC1: around November 18 (string freeze).
  • 7.0.0: December 1st 🎯

7.0.0 release tasks

The following list of tasks needs to be achieved before we package our next major release (7.0.0).

BP REST API documentation updates@im4th
BP Survey results@im4th
7.0.0 Release note@vapvarun
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository

7.0.0 Pizza Restaurant name@dcavins
7.0.0 Announcement post@im4th

NB: we’ll also need to add a patch to #8376 to update our “Hello BuddyPress” modal.

GitHub default branch naming for BuddyPress repositories

This point was moved to a future development meeting. @johnjamesjacoby shared his thoughts about it. Possibilities are main or trunk. FYI WordPress contributors decided to use trunk for repositories of the WordPress organization on August 19.

Open floor

@dcavins asked a question about using the new BuddyPress development environment: when making changes to the BuddyPress source code, he was wondering how is updated the running environment? In other words, do we need to run some specific commands to update it?

@im4th replied changes were automatically taken in account without doing anything more than saving the BuddyPress source code changes. @IAmTheWebb confirmed: “the folder you see outside docker is mapped to inside, so changes you make should appear automagically

Next Dev-Chat

It will happen on November 4 at 19:00 UTC 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!

#7-0-0, #dev-chat, #summary