BP Dev-Chat summary: February 3, 2021

7.2.0 Maintenance release

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

8.0.0 progress

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

Next Dev-Chat

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!

#7-2-0, #8-0-0, #dev-chat, #summary

BP Dev-Chat summary: January 20, 2021

8.0.0 Preps

Features whishlist

  • Invitation to join a BuddyPress community (Network invitations #8139)
  • Edit/display WordPress user fields form BP Profiles (#7162)
  • Welcome email on account activation (#8428)
  • BP Mentions @.JS review (#8001)
  • Build/test tools: use GitHub Actions for CI (#8421) & WP PHP Code Standards (#7228)
  • Attachments for BuddyPress (#8022)

Release regularity

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.

Release lead

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

Dev-chats time

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 🕖

Next Dev-Chat

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!

#8-0-0, #dev-chat, #summary

BP Dev-Chat summary: January 6, 2021

BuddyPress 8.0.0’s kick off

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

Next Dev-Chat

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!

#8-0-0, #dev-chat, #summary

BP Dev-Chat Summary: December 16, 2020

7.0.0 release first feedbacks & results

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!

🎄🎅🏻🤶🏾

#dev-chat, #summary

BP Dev-Chat Summary: December 2, 2020

7.0.0 release tasks progress

We started the dev chat chacking our progress about our next major release tasks.

TasksOwnerProgress
BP REST API documentation updates@im4th100%
BP Survey results@im4th100%
7.0.0 Release note@vapvarun100%
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository
– Translators

@dcavins
@im4th
@im4th

100%
100%
100%
7.0.0 Pizza Restaurant name@dcavins🤫
7.0.0 Announcement post@im4th20%

7.0.0 second release candidate

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.

The RC2 was released very soon after.

7.0.0 release schedule update

  • 7.0.0-RC1: November 20 (string freeze).
  • 7.0.0-RC2: December 2nd
  • 7.0.0: December 9th (asap!)

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!

#7-0-0, #dev-chat, #summary

BP Dev-Chat Summary: November 18, 2020

6.4.0 “PHP 8.0” compatibility release

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.

7.0.0 release tasks progress

TasksOwnerProgress
BP REST API documentation updates@im4th100%
BP Survey results@im4th0%
7.0.0 Release note@vapvarun40%
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository
Translators

@dcavins
@im4th
@im4th

100%
100%
0%
7.0.0 Pizza Restaurant name@dcavins🤫
7.0.0 Announcement post@im4th20%

@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.
  • @vapvarun tested #8394.
  • 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:

LocaleProgress
English 🇬🇧100%
Romanian 🇷🇴100%
French 🇫🇷100%
Chinese 🇨🇳99%
Czech 🇨🇿98%

7.0.0 release schedule update

Next Dev-Chat

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!

#7-0-0, #dev-chat, #summary

BP Dev-Chat Summary: November 4, 2020

7.0.0 latest updates

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

TasksOwnerProgress
BP REST API documentation updates@im4th90%
BP Survey results@im4th0%
7.0.0 Release note@vapvarun0%
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository

@dcavins
@im4th

100%
100%
7.0.0 Pizza Restaurant name@dcavins🤫
7.0.0 Announcement post@im4th0%

Last checks before releasing 7.0.0-beta2

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, #dev-chat, #summary

BP Dev-Chat Summary: October 21, 2020

7.0.0-beta1 feedbacks

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

TasksOwner
BP REST API documentation updates@im4th
BP Survey results@im4th
7.0.0 Release note@vapvarun
7.0.0 Credits update:
– BuddyPress Trac
– BP REST GitHub repository

@dcavins
@im4th
7.0.0 Pizza Restaurant name@dcavins
7.0.0 Announcement post@im4th

NB: we’ll also need to add a patch to #8376 to update our “Hello BuddyPress” modal.

GitHub default branch naming for BuddyPress repositories

This point was moved to a future development meeting. @johnjamesjacoby shared his thoughts about it. Possibilities are main or trunk. FYI WordPress contributors decided to use trunk for repositories of the WordPress organization on August 19.

Open floor

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

#7-0-0, #dev-chat, #summary

BP Dev-Chat Summary: October 7, 2020

7.0.0 cycle updates

@vapvarun announced he will work on 2 tickets in the coming weeks:

  • Multiple member types users table issue (See #8292)
  • Field Visibility Not Honored in PHP 7.1 & above (See #8093)

@dcavins committed fixes, shortly after the dev-chat, to the 2 tickets he assigned himself to during our previous dev chat:

  • The function groups_get_invites_for_user() can return inconsistent total (See #8297)
  • bp_has_groups() should accept status parameter (See #8310)

@im4th informed he will work on the following points during this week:

  • Introduce 3 new BP Blocks into BuddyPress core (See #8369)
  • Fix some issues slated for the 7.0.0 milestone
  • Package the 7.0.0 first beta release (October 15, as initially scheduled)

7.0.0 release schedule

  • 7.0.0-beta1: October 15 👈 🥁
  • 7.0.0 : December 1st

Open floor

@vapvarun is working on making his BuddyX awesome standalone BuddyPress theme hosted on the official WordPress Themes directory. 👨🏾‍🎨

We’ve been talking about the Full Site Editing WordPress feature (announced to be included into WordPress 5.6).

And finally @im4th asked everyone to start thinking about the Pizza restaurant name we will use to name our 7.0.0 release. If you have ideas about it, don’t hesitate to submit them into these post comments 🍕.

#7-0-0, #dev-chat, #summary

BP Dev-Chat Summary: September 23, 2020

First, here’s a clarification regarding the context in which this meeting took place : @im4th thought we were a week before 7.0.0-beta1 release 😆 and urge BuddyPress contributors to review the remaining tickets scheduled for the 7.0.0 milestone! We’re now (October 3rd) 2 weeks away from this beta release 😇.

Postponed features

Due to lack of time, we’ve decided to work on the following features during the 8.0.0 development cycle:

  • Attachments for BuddyPress (#8022)
  • BP Members Invitations (#8139)
  • Block based Activity post form (#8319) *
  • Activity Scheduling (#7953) *

* FYI: the BP Blocks plugin used to develop BP Blocks is also used to develop these two features. You can early play with the Block Based Activity post form and the activity scheduling feature, thanks to this plugin, on a testing site. Contributions are always welcome!

7.0.0 updates

  • BP Types UI have been included into Core. It’s now possible to manage Group & Member types from the WordPress administration. More information about it here.
  • The BP REST API now includes a new endpoint to let logged in users to create new blogs (if the network settings allow it). See this GitHub PR.

7.0.0 remaining tickets

7.0.0 BP Blocks

There will be a new block to embed an activity into a post. During the dev chat we agreed it was important to add 2 more blocks : BP Members & BP Groups blocks. See #8369. (The members one has since been built!)

Some great code improvements has been added by @espellcaste into the BP Blocks plugin. He also suggested we start having regular meetings specific to BuddyPress blocks. So here’s a poll to see if you’re interested about it.

Here are some topics we could discuss about during these specific meetings:

  • How to attract WP Block developers to have fun with BP ones?
  • How to smoothly prepare the Block Based Activity post form merge into Core so that BuddyPress Plugins developer can start working on migrating the feature they add to the legacy post form into the block based one?
  • How BuddyPress could benefit from React, WP React components + BP REST API to improve the user experience?
  • What about a “Block ready” Template pack or a BuddyPress standalone theme?

7.0.0 release schedule

  • 7.0.0-beta1: October 15 💆🏻
  • 7.0.0 : December 1st

Open floor

We’ve been discussing about how to improve the way we communicate towards contributors about features/code improvements added to upcoming BuddyPress releases. @im4th suggested to use this blog to post these kind of updates making sure to use the “Development notes” a sub-category of it for the version number. For instance you can quickly read important changes to expect in BuddyPress 7.0.0 from there: Development notes/7.0.

@IAmTheWebb asked us about how he could update some BP Codex pages. Regular contributors we trust like him can ping me @imath on WP Slack or request an access during our Core dev-chats to make this happen! We are very interested into welcoming new Documentation contributors 🙌 🤝.

Next Dev-Chat

It will happen on October 7 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, #dev-chat, #summary