@dcavins made interesting progress about the Network invites ticket (#8139) working on a new patch to manage optouts (see #8448). He was happy to get feedbacks from @boonebgorges and @im4th about it. As it would be really great to have this feature added to Core for the 8.0.0 milestone @im4th has offered his help with the BP Nouveau Template pack JS/PHP parts needed to be improved to welcome the feature. @dcavins will update the main ticket with directions about this area.
@vapvarun will submit new patches about these two tickets:
new BP Email when a user has successfully validated their account (#8428)
@im4th added some patches about improving the signup form customization (#6347), feedbacks are very welcome, there’s a demo of the first patch after this bullet list.
@im4th suggested, once again, we update the initial 8.0.0 schedule to give us 1 extra week (3 more than the initial schedule) to try to have the Network Invites feature ready for 8.0.0 and finally decide about its inclusion in 8.0.0 during next dev-chat.
@espellcaste did a great job about caching the item schemas to improve the BP REST API performance (#GH386). He will try to work on the ticket about migrating BP Core builds to GitHub Actions (#8421) in the coming weeks.
Updated 8.0.0 schedule
8.0.0-beta1: April 22
8.0.0 stable release: May 26.
@vapvarun shared the latest plugin he submitted to w.org Plugins Directory. If you’re looking for a nice way to preview any links into your activities, give it a try 😉
It will happen on April 14 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!
@dcavins made interesting progress about the Network invites ticket (#8139). He asked for a review by @im4th about the patch he added on #8444 and still hopes to have it ready for 8.0.0. Some work still has to be done for the BP Nouveau template pack.
@im4th suggested we update the initial 8.0.0 schedule to give us 2 extra weeks as we’ve been pretty busy working on the 7.2.1 security release lately. The team agreed to this suggestion.
To help @vapvarun to carry on progressing about the Acceptance Checkbox Field (#4747)@im4th will start committing – asap – the parts he needs from the ticket about updating WordPress fields from the xProfile fields API (#7162).
@im4th thinks we should use the Acceptance Checkbox Field to manage the GDPR consent checkbox we’re including into the signup form since BuddyPress 4.0.0 and believes users would really enjoy all these new field types if we could fix #6347 (Let admins pick signup fields).
@espellcaste did a great job with starting the migration process from Travis to GitHub actions about BP REST API unit tests (#GH383).
@vapvarun posted a first patch about adding a new BP Email when a user has successfully validated their account (#8428).
Updated 8.0.0 schedule
8.0.0-beta1: April 15
8.0.0 stable release: May 19.
It will happen on March 31 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!
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.
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.
@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
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.
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!
@im4th believes we should package this maintenance release soon. Targeted date is the day before next dev chat (February 16). He asked the team to do some testing of BP Nouveau using the Twenty Twenty-one WordPress theme as the 2 commits added to the 7.2.0 was about improving the BP Nouveau companion stylesheet. Let’s try to improve our default template pack before februry 16. @vapvarun will check it (as well as @im4th).
@im4th added a first patch to the ticket about introducing new xProfile field types to manage WordPress fields (description, first & last name, Website) from the front-end member’s profile (#7162). He understood it was very expected by BuddyPress users, so please do test the patch and share your feedbacks and improvements about it.
@dcavins updated the swap-atwho-for-Tribute patch he had created before about #8001. It’s working as expected. He will next move the suggestion lookup from wp-ajax to the BP REST API. He’ll post a new patch soon.
It will happen on February 17 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!
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!
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!
2 bugs related to the 7.0.0 release were posted on Trac:
#8411 The Groups Administration screen was not reachable anymore for configs using the multiblog constant BP_ENABLE_MULTIBLOG. ✅ It has been fixed.
#8414 Using the BP Blogs component tool to repair site icon / blavatar synchronization on non multisite configs was generating an error due to a WordPress function not available. ✅ It has been fixed.
We also spent some time investigating a possible bug about Activity recorded dates but it turned out it wasn’t involving the plugin. We’ve decided to package a minor release (7.1.0) before christmas. It should be available for download later today (around 21:00 UTC).
The 7.0.0 release had the best download spike of our 2020 releases. It was reached on December 11 with 34326 downloads 🙌
@slaffik will personally take a look at good-first-issue tasks, on those that he has created a while ago, and will open a new ticket to work on bringing Twenty Twenty One compatibility improvements to our default Template Pack 👍.
Finally and more globally about development cycles, we’ll have a discussion about how we can improve things such has release regularity, release leading, etc.
It will happen next year on January 6 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!
Many thanks to all BuddyPress contributors for their help during 2020, we wish you all great holidays and to stay safe. See you in 2021 for some great BuddyPress times!
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!
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.
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: