BP Docs-Chat Summary July 24, 2024

BP Documentation tracker status:

The stats – 44%, which is a decrease 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:

Workflow process review

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.

The process change

@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!

Open floor

@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.

Next Docs-Chat

It will happen on August 7, 2024 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

BP Dev-Chat Agenda July 31, 2024

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:

  • Who’s volunteering to lead the 15.0.0 release?
  • Should we change the way we deal with deprecated code? See #9210.
  • BP REST API, going v2: see #9145.
  • Open floor.

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.

🏄🏻‍♂️ 🌊 🪸

#15-0-0, #agenda, #dev-chat

BP Docs-Chat Agenda July 24, 2024

Hi!

Our next documentation meeting will happen on July 24, 2024, at 19:00 UTC in #BuddyPress. Here’s our agenda:

  • BP Documentation tracker status.
  • Review workflow process, e.g., there are currently 41 open issues, of which only 4 are unassigned: does this mean the other 37 are currently being worked?
  • Open Floor.

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

#agenda, #docs-chat

BP Docs-Chat Summary June 26, 2024

The reasons for the delay in posting this summary were due to changes in meeting dates which involved the efforts required to release BuddyPress 14.0.0 and vacation schedules. That stated, we were only able to complete a portion of the intended agenda items due to time constraints; albeit the meeting lasted for, approximately, 1 hour & 29 minutes. The agenda items covered are indicated in this summary.

BP Documentation tracker status:

The stats – 42%, which is a decrease of 1 (one) percentage point – 43%42%.
The reason for the decrease is that a new issue was created while completions remained the same.

Review the 23 open issues that are labeled “user“. ➡ The 23

One of the goals for this agenda item was to determine which of the 23 open issues were related to the WP-Admin area. Of the 23, there were 5 open issues that met this criteria:

The remaining goals for the this agenda item, i.e., the review of the 23, in addition to other pertinent uncompleted agenda items are earmarked to be completed during future docs-chat meetings, see BP Docs-Chat Agenda June 26, 2024

Note: the original list of 23 issues is, as of this posting, currently a list of 22 issues, apparently 1 (one) issue has been closed.

Next Docs-Chat

It will happen on July 24, 2024 at 19:00 UTC in #BuddyPress.

#docs-chat, #documentation, #summary

BP Dev-Chat Summary July 10, 2024

✅ BuddyPress 14.0.0

This meeting main goal was to check we made enough progress to package BuddyPress 14.0.0 on July 12. Short answer is yes as it was released on this day!

  • Credits list: @vapvarun worked on it and shared it with us at the very beginning of our chat.
  • Announcement post: @im4th volunteered to write it out of the BP Hello Screen and asked @dcavins to review it once a draft is ready. He agreed 😍.
  • Full change log: this was the last task to achieve. @vapvarun volunteered and started right away to generate it for the Codex as a bit before the end or our meeting he confirmed it was ready.

We were confident about releasing on July 12, and we were right!

14.0.0 final schedule

🔮 BuddyPress 15.0.0

  • @im4th started to share about the little complexity introduced by our new way of branching (right after the release candidate version): we need to be careful to commit a fix twice or 3 times during the period between RC and final release:
    • trunk,
    • new branch,
    • & possibly old branch in case the commit is a regression from the previous plugin version.
  • Who’s volunteering to lead 15.0.0 release?
    • @dcavins won’t have enough time to commit to leading
    • @emaralive thinks it should be someone that is not him 😄.
    • @vapvarun will monitor all 15.0.0 steps to be ready to lead 16.0.0.
    • @espellcaste wasn’t around during the chat, @im4th said he thinks he was interested to lead 15.0.0
    • Let’s decide about it during our next development meeting.
  • There are already more than 70 tickets into the 15.0.0 milestone 😅. @emaralive thinks we should straighten out registration/invitations/opt-outs + email notifications (it’s on @dcavins todo list!). @dcavins noted there were private messages improvements as well as caching/performance ones.
  • @im4th thinks it would be nice to release 15.0.0 before the end of the year.

20 minutes about the very needed BuddyPress.org new theme

#9193 is the place where we can share/organize our ideas. @im4th shared with other members of the team the nice discussion he and @vapvarun had at Da Lucia’s pizzeria. What about using the Twenty Twenty-Four default WordPress theme and enjoy all possible customizations the Site Editor is providing? It’s an interesting idea to have this change: it would give us some time to work on a great new BuddyPress standalone theme as well as renew BuddyPress.org site’s appearance which has been the same for years! Finally @im4th suggested we really talk about it during a video/audio chat: let’s organize it soon 🎥 🎙️.

Next Dev-Chat Agenda

It will happen on Wednesday July 31, 2024 at 19:00 UTC in #BuddyPress.

PS: no chat next week! Next docs chat will happen on Wednesday July 24, 2024 at 19:00 UTC.

#14-0-0, #dev-chat, #summary

Please welcome BuddyPress 14.0.0 “Da Lucia”

Hi BP Contributors,

This is “Da Lucia” our latest major version. Please upgrade 🙏.

🏄🏻‍♂️ 🏖

#14-0-0, #release

BP Dev-Chat Summary July 3, 2024 + July 10 Dev-Chat agenda

⏳ BuddyPress 14.0.0

After a few minutes of discussions we realized we couldn’t do the Release Candidate party as we planned to 🥲.

  • #9206 this ticket was opened during the chat by @vapvarun: 2 emails were sent to an site invited user once they accepted the invite. @im4th wanted this ticket to be fixed before releasing RC1. This was the main reason we decided to work on a new schedule for 14.0.0 release.
  • #9189 Bump bundled BP CLI to 3.0.1, @espellcaste needed an extra time to have it fixed
  • #9188 Hello Screen updates for 14.0.0 was reviewed during the chat: many thanks to @dcavins & @espellcaste.
  • We also needed to update 14.0.0 credits list + #9196 Team roles update & formalize the fact @vapvarun & @emaralive are part of the BP Team.
  • About #9204 start working on up/next right after current RC1, @im4th asked for some more feedbacks.

We then shared some tasks to finally get ready for an updated schedule we agreed on during the chat (see next section of this summary).

We finally decided to replace today’s docs chat with a new dev chat to see if we would have made enough progress to finally release 14.0.0 on July 12.

14.0.0 updated schedule

Next Dev-Chat Agenda

It will happen on Wednesday July 10, 2024 at 19:00 UTC (today) in #BuddyPress. Below is our agenda!

  • 14.0.0 Credits list
  • 14.0.0 Announcement post
  • 14.0.0 full changelog
  • If we have some time left : start discussing about 15.0.0 Release lead.

#14-0-0, #agenda, #dev-chat, #summary

Here’s BuddyPress 14.0.0 first release candidate!

Please help us testing it 🙏.

#14-0-0, #release, #release-candidate

BP Dev-Chat Agenda July 3, 2024

Hi!

Our next development meeting will happen on Wednesday July 3 at 19:00 UTC in #BuddyPress. Here’s our agenda:

  • 14.0.0 tickets to fix before RC release:
    • #9189 Bump bundled BP CLI to 3.1
    • #9188 Hello Screen updates for 14.0.0
    • #9196 Team roles update & formalize the fact @vapvarun & @emaralive are part of the BP Team.
    • #9204 start working on up/next right after current RC1.
  • Who’s volunteering to lead the 15.0.0 release?
  • RC1 release party! 🥁🎸🎤

PS: this chat will probably last longer than usual, thanks in advance for your understanding, we need to accelerate a bit to be ready to release 14.0.0 stable version on July 8.

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

#14-0-0, #agenda, #dev-chat

Notice of Deprecated Functions in 14.0.0


BuddyPress 14.0.0  has deprecated functions and constants that will no longer be supported. Furthermore, these functions and constants may be removed from future versions, therefore it is  recommended to update any code that uses them, appropriately.

FunctionStatusVersion
bp_block_init_editor_settings_filter()Deprecated14.0.0
bp_block_init_category_filter()Deprecated14.0.0
bp_use_wp_admin_bar()Deprecated14.0.0
bp_admin_email_add_codex_notice()Deprecated14.0.0
bp_activity_admin_screen_options( $value, $option, $new_value )Deprecated14.0.0
bp_groups_admin_screen_options( $value, $option, $new_value )Deprecated14.0.0

See src/bp-core/deprecated/14.0.php for further code details.

ConstantStatusVersion
BP_USE_WP_ADMIN_BARDeprecated14.0.0
BP_SIGNUPS_SKIP_USER_CREATIONDeprecated14.0.0

Additional Suggestions:

For non-developers, here are some tips for resolving deprecation notices in BuddyPress:

  • Update themes and plugins: This is the most common fix.
  • If the plugin or theme developer doesn’t have an update available, contact them directly. 

FYI: 14.0.0 schedule

  • June 13: 14.0.0-beta1 ✅.
  • June 24: 14.0.0-beta2 ✅.
  • July 5: 14.0.0-rc1 ✅.
  • July 8 July 12: 14.0.0 ✅.

#14-0-0, #notification