Letās all joinĀ the firstĀ #BuddyPressĀ developer meetingĀ of the year.Ā It is scheduled onĀ January 6 at 19:00 UTCĀ (tomorrow), hereās the agenda:
BuddyPress 8.0.0ās kick off
Features / bug fixes wishlist, please reply to the 8.0.0 call for tickets if you havenāt already!
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 š
About the 8.0.0 features wishlist!
Weāll post a new call for tickets at the very beggining of 2021, the same way we did it for the 7.0.0 release. Everyone will be welcome to contribute to it. You can start looking for Trac tickets youād like to see fixed for 8.0.0.
@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.
Next Dev-Chat
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.
Open floor
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?
Next Dev-Chat
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.
@vapvarun has been working on the release note, the remaining things to write is the changelog. @johnjamesjacoby removed the link to the BP Survey on our official site, @im4th needs to write a post about the results and publish it on BuddyPress.org asap.
7.0.0 first release candidate
Weāve spent the rest of the meeting working on getting the 7.0.0-RC1release ready:
@dcavins reviewed the Hello Screen texts š (#8376).
@im4th worked on improving the Activity Embed block instructions (#8397) as only public activities can be embed into a post or a page.
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 š.
Hello #BuddyPress contributors, what do you think of this last minute improvement I think we should bring to next BP release (7.0.0) ? šhttps://t.co/xUlWyiUcYt
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:
It will happen onĀ December 4 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!
@im4th started the meeting sharing that the ticket (#8179) about the default Blog avatar has been committed and that a developer note has been published on this site. @vapvarun suggested we should respect some consistency about the UI we use when setting a groupās types or a memberās types. A ticket (#8389) has since been reported and fixed: from now on the WP-Admin/Extended Profileās member type metabox will use checkboxes.
@im4th has updated the BP REST APIās Blogs Endpoint so that it enjoys the improvement we brought about the default Blog avatar (#BP-REST-358). He said he had no time to update the BP REST API developers documentation, but as he felt pretty guilty about it, he worked on it lately and made good progress as only the Signups and Friends Endpoints need a documentation review.
@dcavins has been working on updating the list of Props from our Trac environment and @im4th worked on the list of Props from the BP REST plugin GitHub repository. A patch is ready about these updates (#8376). Here are our progress about 7.0.0 release tasks.
Weāve decided to postpone the 7.0.0-beta2 release to tomorrow (November 11th, 2020). @im4th was concerned about a cache issue (#8388) that was reported lately about the xProfile component. @dcavins volunteered to work on it and has since contributed to 2 patches. Donāt hesitate to comment on the ticket to share with him your thoughts about our 2 possible ways to fix this issue. @vapvarun brought to our attention another issue (#8386) that was reported about the BP Nouveau Template pack. @im4th volunteered to work on it. It has been since fixed. @im4th also asked @vapvarun to test the patch attached to the ticket (#8384) about making sure Site Icons / Blog avatars synchronization is also happening when BuddyPress is not network activated on multisite configurations. He recently tested it and we will probably include it into the 7.0.0-beta2 release. Finally @johnjamesjacoby improved the new strings we introduced about the BP Types UI š¤. We finally agreed on this new schedule for the 7.0.0 development cycle.
7.0.0-Beta2: November 11.
7.0.0-RC: November 18.
7.0.0 final release: December 9.
Open floor
@vapvarun shared his enthusiasm about the promising download results of the BuddyX theme he recently submitted on the WordPress.org Themes Directory ššš. As itās a beautiful BuddyPress theme, @im4th asked him to work on a post to share his experience about the process he had to go through to have his theme hosted on the official Themes Directory. We will soon publish this post on BuddyPress.org šØ .
We also talked about the BuddyPress code reference, itās still under construction but @vapvarun ran some tests about it lately so we might progress about it soon!
Next Dev-Chat
It will happen onĀ November 18 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!
7.0.0-beta1 was released on October 16. So far, nothing specific to it was posted into our support forums. At the time we had the meeting, @im4th, thanks to @IAmTheWebb tests, had reported an issue (now fixed) with the Activity Embed block into our Trac environment. This last Friday @k3690 reported a wrong usage of the member term into a Group Type meta property (now fixed).
7.0.0 remaining tickets
#8292@vapvarun submitted a patch during the meeting šŖ, @im4th reviewed it some time after, brought some minor improvements and it has been fixed yesterday. Itās now possible to assigned more than one member types to users from their WP Admin Extended Profile š .
About #8179, @im4th asked @vapvarun to update the ticket with 2 squared corner avatars with these dimensions: 150px x 150px (full) & 50px x 50px (thumb). @im4th will try to progress on a patch in the meantime.
Weāve postponed #8093 (Profile Field visibility improvements) to a next milestone.
#8375 was reopened by the reporter, as the filter weāve added wasnāt matching its needs. @dcavins@johnjamesjacoby & @im4th have been discussing about it last week inĀ #BuddyPress and came to the conclusion a possible better place to allow the invitation tableās name filtering was to include the {$bp_prefix}bp_invitations table name into the global_tables property of the BP_Members_Component object. @dcavins will investigate this week about that possible change.
Finally shortly after our meeting, @boonebgorges reported a new ticket about improving the xprofile_get_field() function so that it only pulls up the data for a field when necessary. The patch he suggested as a first step looks safe to @im4th who thinks it should be included into the 7.0.0 release: itās always great to improve DB performance. Please have a look at #8378 and send him some feedbacks about your thoughts.
7.0.0 release schedule update
We are going to package a new 7.0.0-beta to include as much fixes as possible considering the previous chapter. Packaging will happen shortly after our next BP Dev-Chat.
7.0.0-beta2: November 4th
7.0.0-RC1: around November 18 (string freeze).
7.0.0: December 1st šÆ
7.0.0 release tasks
The following list of tasks needs to be achieved before we package our next major release (7.0.0).
@dcavins asked a question about using the new BuddyPress development environment: when making changes to the BuddyPress source code, he was wondering how is updated the running environment? In other words, do we need to run some specific commands to update it?
@im4th replied changes were automatically taken in account without doing anything more than saving the BuddyPress source code changes. @IAmTheWebb confirmed: āthe folder you see outside docker is mapped to inside, so changes you make should appear automagicallyā
Next Dev-Chat
It will happen onĀ November 4 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!
