BP Dev-Chat summary : October 5, 2022

We’ve started the meeting talking about the 17 replies our call for feedbacks got at the time of the meeting. There are great remarks, ideas and suggestions. Many thanks to the contributors who shared their very inspiring thoughts. We value them a lot 😍.

11.0.0 updates

  • #8590: Cache improvements. The initial PR made by @nickchomey has been committed. We had a discussion about whether to include the other improvements that were added by a buddyboss-platform team member (This ticket was firslty added as a PR to the buddyboss-platform GitHub repository). The majority of the team thinks as code is open source & GPL compatible, there’s no reason not to enjoy these improvements as long as we properly credit its author and the buddyboss-platform project.
  • #8734: we’ve discussed about @dcavins first patch about how to implement a basic “private community” feature. Although the patch is already doing a great job and is a very interesting first approach, @im4th agrees with @johnjamesjacoby : a better one would be to think of it as a community visibility “level”. As announced during the chat, @im4th had a closer look to the patch and started an alternative PR to suggest the introduction of a bp_read cap which led to interesting new feedbacks on the ticket. Don’t hesitate to test it, and contribute to the ticket’s discussion.
  • #4184: being able to exclude a list of users from the activity stream is now possible in Core. This commit closed the ticket.
  • @im4th reminded the team we had 2 weeks left before the date we initially scheduled 11.0.0 first beta and asked @espellcaste to try to make the list of the tickets he owns for 11.0.0 less bigger (selecting the tickets we absolutely need to include in 11.0.0 and punting others to a next release).

11.0.0 schedule reminder

  • First beta: October 19, 2022 🚨 that’s tomorrow!
  • Release: December 14, 2022.

10.5.0 Maintenance release

@im4th announced he will package this maintenance release shortly before WordPress 6.1 is released so that BuddyPress behaves the best way into the next WP Default theme (Twenty Twenty-Three). If he finds the time, he’d like to finish optimizing some CSS rules about it. Don’t hesitate to give him a hand contributing to this ticket.

Open floor

About the BuddyPress.org website @johnjamesjacoby really wants us to feel more comfortable iteratively improving it, and asked the team to think about how we want to contribute to it. @im4th volunteered to give John’s a hand and maybe try to work on the list of submitted tickets about the website. As @dcavins noted, some of their authors are first time contributors and it would be great to include their suggestions. @espellcaste wants to spend more time on developer.buddypress.org along with PHPDoc improvements.

The new & gorgeous BuddyPress theme has a name and a GitHub repository, don’t hesitate to contribute to it.

Next Dev-Chat

It will happen tomorrow on October 19 at 19:30 UTC in #BuddyPress. If you have specific points or ideas you want to discuss about, don’t hesitate to share them in comments, the agenda will be published shortly.

#10-0-0, #11-0-0, #dev-chat, #summary