Hi everyone, sorry this summary is published very late (the day we’re having another development meeting). We’ve been working hard on improving the security of BP REST API fixing some vulnerabilities. The BuddyPress 7.2.1 security release was published yesterday and we strongly encourage you to update your copy of BuddyPress, from versions 5.0.0 to version 7.2.0, to this 7.2.1 version. If you are using the BP REST plugin, make sure to merge your branches with upstream’s master, 0.3, 0.2 or 0.1 branch to get these fixes into your clones.
@im4th also shared his concern about Jcrop (we use it into the Avatar UI), which is full of deprecated jQuery code.
@vapvarun shared his opinion about ways to progress on #6071 the “Superfield” using repeaters (like ACF), but it doesn’t seem doable during the 8.0.0 milestone (not enough time), @imath promised he would try to look into it if we can make a smaller step before the end of March.
#4747 seems more doable (a profile field to manage pages needing acceptance, eg: terms of service, code of conduct). @vapvarun shared a patch about it and @im4th gave some first feebacks about it.
@im4th made some progress about #7162 (Edit WordPress fields on front-end via new xProfile field types) and is confident he’ll be able to start committing parts of the patch to help making progress on #4747.
Please join our development meeting tomorrow March 3 at 19:30 UTC. It will happen in #BuddyPress. During 30 minutes, we will discuss about our progress on the 8.0.0 milestone. As a reminder, the first beta is scheduled for the end of the month 😱. Here’s the 8.0.0 schedule:
8.0.0-beta1: March 31
8.0.0 stable release: April 30.
If you have specific/additional points you need to discuss about, please share them into the comments area of this post.
We’ve discussed about trying to build a release each four months. There might be downsides doing so such as the time component could become more important than the new code or the quality of it. We’ll see how it works for 8.0.0 before making it a “rule” for this year releases. So here’s the expected schedule for 8.0.0:
8.0.0-beta1: March 31
8.0.0: April 30.
This is something we haven’t talked about for the last 2 releases. @im4th checked if one of us was interested in leading the 8.0.0 release. As no one is confident enough about their available spare time to be able to take this responsibility, @im4th will lead “coordinate” this new release 😉.
19:00 UTC is not ideal for @im4th during winters but at the same time it’s very late for @vapvarun. So we agreed to make dev-chats end at the same hour 20:00 UTC, but starts 30 minutes later. We’ll simply need to make sure to drop by to add to the agenda/ask questions the day before. So we’ll try to meet each other wednesdays during 30 minutes at 19:30 UTC 🕢. If it doesn’t match our needs, we’ll be able to revert to 🕖
It will happen on February 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!
Our next #BuddyPress developer meeting is scheduled on February 3 at 19:30 UTC (tomorrow). This will be our first 30 mins long dev-chat since we’ve decided to start 30 mins later and to end at the same time. Let’s try to be on time and as @dcavins suggested, let’s use the comment area of this post to prepare the specific points we want to discuss during our meeting. I’ll start to follow this suggestion by adding one comment as soon as this agenda is published 😉
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).
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!
BuddyPress 7.0.0 was released on December 9, 2020. We did the 7.0.0 release review during our latest “dev-chat”, just before the end of the year we shared with you a wrap-up post about 2020, today we’re inviting you to contribute to 8.0.0’s kick-off by replying to this call for tickets.
The priorities of the BuddyPress community matter, please let us know what:
bug(s) you’d like to get fixed for 8.0.0?
improvement(s) you’d like to see in 8.0.0?
new feature(s) you’d like to see introduced in 8.0.0?
Share your wish-list!
To do so, you simply need to pick the ticket number(s) you think we should prioritize on from our code source management tool and paste them into this post’s comment form. If you’d like to, you can also share your ideas about the corresponding ticket(s). If some “already shared” tickets are also interesting you: use the ⭐️ Like feature to second them.
PS: don’t hesitate to add a new ticket, if you haven’t found a match into the above queries
PS2: Adding your ticket here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!
This call for tickets will end on January 13, but we’ll begin discussing about what we’d like to see in BuddyPress 8.0.0 during our next dev-chat (January 6) : so the sooner you share your wish-list the better!
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.
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.
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?
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!