Our next development meeting will happen on August 28 at 18:00 UTC (an hour earlier than usual!) in #BuddyPress.
Here’s our agenda:
If you have specific/additional points you need to discuss about, please share them into the comments’ area of this post.
Mark your calendars! We’re aiming to release BuddyPress 14.1.0 in early September. While there aren’t any urgent issues at the moment, we’ll be doing a final review in our next dev-chat to ensure everything is shipshape.
Our team is already hard at work for BuddyPress 15.0.0, and we’ve got some exciting features and improvements in the pipeline:
We’re also considering ways to improve the backend configuration process, making it easier for end-users to set up and manage their BuddyPress sites.
Our team has already closed 14 tickets for the 15.0.0 milestone, with 42 more currently open. We’re in the process of reviewing these tickets and prioritizing them for the upcoming release.
We’re tentatively planning to release the first beta for BuddyPress 15.0.0 in mid to late October, with the final release coming 1-2 weeks after WordPress 6.7 (expected around November 12, 2024).
Additionally, we’re exploring the possibility of a new standalone theme for buddypress.org. Stay tuned for updates on this exciting project!
It will happen on Wednesday August 28, 2024 at 18:00 UTC in #BuddyPress.
BP Documentation tracker status:
Documentation progress has risen to 47%, up from 44%. This reflects ongoing improvements in the quality of documentation.
Today, two new pull requests (PRs) were submitted:
The meeting also addressed numerous open tickets that remain unassigned. Previously, these tickets were default-assigned to @imath. The team will select 1-2 PRs for each meeting to manage these tickets more effectively.
Additional topics discussed included:
A new workflow process was agreed upon, where issues will be marked as “In progress” as soon as someone self-assigns them. This change aims to improve task management and ensure clarity on active work. The team will continue to focus on managing and reviewing PRs related to FAQs and bug reporting.
Our next documentation meeting will happen on August 21, 2024, at 19:00 UTC in #BuddyPress.
Hi!
Our next documentation meeting will happen on August 21, 2024, at 19:00 UTC in #BuddyPress.
Here’s our agenda:
If you have specific or additional points to discuss, please do so in the comments section of this post.
Hi!
This will be my first meeting as🧑🏾🍳 15.0.0 Release Leader. So be gentle with me! =P
Our next development meeting will happen on August 14 at 18:00 UTC (an hour earlier than usual!) in #BuddyPress. This is the new time for the dev chat during the 15.0.0 milestone.
Here’s our agenda:
If you have specific/additional points you need to discuss about, please share them into the comments’ area of this post.
@espellcaste renewed his interest to lead the 15.0.0 release. As he has a fixed professional meeting call at 19:00 UTC, @im4th asked other members of the team if everyone was ok to change our meeting time to an hour earlier at 18:00 UTC. Some of us might not be able to join at some meetings, but the majority thinks we’re good to go with this earlier time during the 15.0.0 development cycle.
We’re happy to announce Renato Alves (@espellcaste on WordPress.org, @renato on Slack) is the leader of our next major release (15.0.0) 💪 🇧🇷 😍 🎊.
We took the time to review the way we load deprecated code. Since 11.0.0, we usually:
As 12.0.0 was a huge revolution, we carried on including 12.0.0 deprecated code in 14.0.0 fresh installs and upgraded ones to take in account the fact, unfortunately a lot of Plugin/Theme developers haven’t updated their code to be fully ready for 12.0.0 yet (See #9210).
After discussing about it, we decided:
NB: to force the deprecated code to be loaded, users can always define( 'BP_LOAD_DEPRECATED', true ); into their WordPress configuration file.
We had a quite long discussion about this point to find the best way to deal with deprecating the v1 of the BP REST API. As we’re a small team, maintaining 2 versions of the BP REST API is not doable. Here’s what we finally decided:
buddypress/v1 routes will offer a different message than “No route was found matching the URL and request method.” to inform it’s deprecated when the BP REST plugin is not active.It will happen on Wednesday August 14, 2024 at 18:00 UTC in #BuddyPress.
Hi!
Our next documentation meeting will happen on August 7, 2024, at 19:00 UTC in #BuddyPress.
Here’s our agenda:
If you have specific or additional points to discuss, please do so in the comments section of this post.
The stats – 44%, which is an increase of 2 (two) percentage point – 42% => 44%.
@im4th informed he would soon improve it as he was working on the WP-Admin/Extended profile (it has been committed since) and he still have 2 PRs submitted by @vapvarun to review. @vapvarun self-assigned two other tasks:
This was an important point on the June 26 docs-chat agenda we couldn’t talk about by then. @im4th asked @emaralive to introduce it. He explained it was hard to find out who was actively working on the 35 opened issues. @im4th thinks it’s probably due to the fact we were self-assigning ourselves when creating these issues out of the list of Codex pages to migrate. On his side, @vapvarun informed he was self-assigning himself only when he had a PR ready or was planning to work on a PR about it. @im4th will review PR he’s assigned to and just like @vapvarun will only keep the one he’s planning to work on actively.
@emaralive suggested we change the process to mark issues/tasks as “In progress” as soon as someone is self-assigning himself to one of these. Waiting for a PR to be into its review phase seems to be a bit too late. We all agreed about this change.
We just need to think about moving issues to the “In progress” column as soon as we assigned oneself to it!
@espellcaste asked for some another looks on the PR about creating a pre-release tests checklist. We had a 30 minutes discussion about it to figure out which multisite setups we should test. It revealed we need some more detailed statistics about BuddyPress installs to confirm our guess that on Multisite configs the majority of the Admins are activating it at the Network level. As WordPress.org Plugin directory stats are not very informative about it, it looks like surveys are the best way to have clues about it. According to the results of the latest survey we deployed in 2020 (427 replies), it’s hard to tell if the “WP in domain root” (68%) is including Multisite configs… Moreover we don’t reach 100% when summing figures…
The above table seems to confirm @im4th‘s concern about surveys:
We can have a look at previous surveys for sure, but I’m not confident with this source as end users might have no clue what is their configs!
imath
Finally @emaralive is testing the “Test Reports” plugin which seems to be a nice tool to help people write meaningful reports.
It will happen on August 7, 2024 at 19:00 UTC in #BuddyPress.
Hi!
Our next development meeting will happen on Wednesday July 31 at 18:00 UTC (tomorrow at 1800 UTC) in #BuddyPress. Here’s our agenda:
PS: please note we’ll start one hour earlier than usual to take in account this @espellcaste comment.
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
🏄🏻♂️ 🌊 🪸
Hi!
Our next documentation meeting will happen on July 24, 2024, at 19:00 UTC in #BuddyPress. Here’s our agenda:
If you have specific/additional points you need to discuss, please share them in the comments area of this post.
BP Team Updates 