Archives

imath 8:55 pm on September 28, 2021
Tags: , ,   

BP Dev Chat Summary : september 22, 2021

10.0.0 Progress

  • We started by congratulating @oztaser for the great contribution he brought about SQL performance improvements to the BP Notifications API (See #8426).
  • @dcavins will actively (👈 adding some pressure here 😁) progress about the site membership requests feature. He will also take in charge the issue about the inconsistent behavior of Groups Invites when the friends component is not active inside the Legacy template pack (see #8550)
  • @vapvarun is exploring BuddyPress statistic widgets from a plugin, @im4th challenged him to build Widget Blocks about it in 10.0.0 as well as exploring the mutual friends/mutual groups which are other Widget Block nice candidates (see #8559).
  • Then we had a long discussion about raising the BuddyPress required WordPress version to 5.4 (see #8571). It’s true it’s quite a jump from 4.9 but “Tipton” was released almost 4 years ago, it’s the last WP version before the Block Editor which is probably making it a bit special. WP 5.0 to 5.3 are under 5% of total WordPress installs which makes 5.4 a good candidate for our next required version.

If a WordPress version became obsolete over a year ago, it’s a candidate for removal.
If a WordPress version’s use slips below 5% of all WP installations, it’s a strong candidate for removal.

The BP Codex

Please, share your opinion about the BP 10.0.0 required WordPress version using the comments area 🙏

10.0.0 schedule

  • 10.0.0-beta 1: ~ november 20, 2021,
  • 10.0.0 stable: ~ december 24, 2021 🎄

BP Rewrites feature as a plugin

It’s now possible to enjoy BP Directories as the site’s homepage using the BP Rewrites URL parser.

@sbrajesh shared his first thoughts after testing the plugin. He was a bit surprised not to find the BP Directories into the WordPress pages. In BP Rewrites, BP Directories are using a Custom Post Type without using the corresponding WordPress generated UI. Instead there’s a new URL settings page to customize almost every possible slugs. The last improvement to add about slugs is to support customizable slugs for the Member’s secondary navigation. It’s true the UI used for this settings page should be improved (a lot!).

@im4th informed about the plan for this plugin : it’s not to merge it into BP Core during 10.0.0 (or even 11.0.0) but to release it as a plugin so that a lot more people can easily test it. There’s a ticket about easing hosted on WP.org features as a plugin installation from one of the BuddyPress Admin screens to also simplify this part for users (see #8148). Switching from our Legacy URL Parser to the WP Rewrite API will need a lot more testing to make sure BP plugins and themes are behaving almost like there was no switch!

@im4th strongly encourages all BP Plugin/theme developers to give a test to this feature as a plugin to contribute to the next way BuddyPress will parse URLs.

Open floor

@im4th @dcavins & @vapvarun are going to participate to a Q&A hosted by Birgit Pauli-Haack from the Gutenberg Times on October 28 at 16:00 UTC. If you want to know more about our experience migrating the BP Legacy widgets to Block Widgets during the BuddyPress 9.0.0 “express” release, please join us! More info available there inside the Upcoming Live Q&As section.

Next Dev-Chat

It will happen on October 6 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!

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

imath 8:16 am on September 4, 2021
Tags: , ,   

BP Dev Chat Summary : september 1st, 2021

10.0.0 Progress

  • Shortly before the dev chat started @dcavins shared his progress about the Site Membership Requests feature: he did preparative work needed for the feature by improving the BP Signup Class and fixed 2 tickets (#8540, #7938).
  • Thanks to a discussion between @vapvarun & @im4th about 2 BP plugins @vapvarun will soon make available on the WP plugins directory (about global BP Search and using the big G reCaptcha service to secure some parts of BuddyPress), @im4th will explore the possibility to add 2 new BP Blocks: 1 to perform global search, the other to display a member’s community statistics.
  • To help @sbrajesh organize the BP Relationships API, @johnjamesjacoby created the corresponding repository on BuddyPress’s GH.
  • @espellcaste asked for a dev review about his approach on adding pagination to message threads (#8508) and thanked @im4th for the one he provided about #7614.
  • @espellcaste also introduced some very interesting functions to get a Group object, making it possible to use template functions outside of the Groups loop. You should have a look to this commit.

10.0.0 first schedule

  • 10.0.0-beta 1: ~ november 20, 2021,
  • 10.0.0 stable: ~ december 24, 2021 🎄

BP Rewrites feature as a plugin

Although @im4th only said he was making good progress about the feature during the dev chat, let’s warmly thank the first contributors who joined the adventure of using the WP Rewrite API to replace our legacy URL parser: @shanebp @boonebgorges & @rayisme 🥰.

@im4th strongly encourages all BP Plugin/theme developers to give a test to this feature as a plugin to contribute to the next way BuddyPress will parse URLs.

Next Dev-Chat

It will happen on September 15 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!

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

imath 4:59 pm on September 1, 2021
Tags: , , , ,   

August 18 Dev-Chat summary & September 1st Dev-Chat agenda

Hi everyone, sorry, once again, this summary is published quite late.

August 18 Dev-Chat summary

9.1.1 Security release

@im4th explained the work @dcavins, @johnjamesjacoby and him did about the security fix that was ported back to previous BuddyPress branches (from 9.0 to 2.9): 8 released were packaged in a night. Many thanks to David & John for their help during this amazing night!

10.0.0

  • @sbrajesh informed us he needed some more time to finish the first version of the BP relationships API.
  • We’ve been talking about the Group hierarchy as a possible feature for 10.0.0 @dcavins informed he had previously worked into this area from a custom plugin.
  • The first beta of 10.0.0 should happen on November 20. Target date for the final release is December ~24 🎅🏼

Open floor

  • We’ve been talking about the opportunity to move the dev-chat time but we will finally keep on meeting every other Wednesday at 19:30 UTC. Although it’s very late for @vapvarun & @sbrajesh, they are young enough 👶🏽👶🏾👶🏻 to handle it. Many thanks to them 🤝

September 1st Dev-Chat Agenda

  • Progress about 10.0.0 features.
  • News about the BP Rewrites feature as a plugin.

It will happen later today at 19:30 UTC and of course in #BuddyPress.

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.

#10-0-0, #9-1-1, #agenda, #dev-chat, #summary

imath 6:12 pm on August 3, 2021
Tags: , , , ,   

July 21 Dev-Chat summary & August 4 Dev-Chat agenda

Hi everyone, sorry this summary is published very late (the day before we’re having another development meeting).

July 21 Dev-Chat summary

9.0.0 early results and feedbacks

  • 9.0.0 “Mico” was released on July 19.
  • Download spike for it happened on July 20 and reached ~33.400 downloads 📈 🎈.
  • Nothing major about it into Support forums, so @imath was able to quote @vapvarun saying: “We did not break anything big” 😅.
  • This BP Blocks focused (& short time framed) release was an interesting experience, thanks to a discussion launched by @johnjamesjacoby a bit before the dev chat, we were able to discuss about the benefits of working from a “feature as a plugin” GitHub repository. In short: it can save us some time ⏱, but bringing back code into our Trac is making us feel safer from being completely GitHub dependent.

10.0.0 is a magic number!

  • 10 is after 9, and we all feel we need to make this release a bit specific.
  • @sbrajesh has been working on the BP Relationship API and is confident he’ll be able to share a first alpha around August 18. 💪
  • Below are our first thoughts about 10.0.0:
    • A “regular” development cycle, Christmas🎄 as a release date could be a good idea!
    • It’s time BuddyPress has a Media Component, Releasing 10.0.0 once it’s ready was suggested 😇
    • Using rewrites to parse BP URLs might be a bit too early but we’ll have a “feature as a plugin” really soon to check what it means in terms of back compatibility with Plugins using the BP Legacy URL parser.
    • Carry on improving the BP REST API by using it more frequently into BP features (like we did for BP Blocks in 9.0.0)
    • A new great BP Theme seems difficult to achieve, unless we have a lot of interested contributors jumping in!
    • A site membership requests feature to compliment the site membership invites.

Nothing’s set in stone yet! Don’t hesitate to show your support for one (or more) of the above points to help us decide. And if you have great ideas, be there to share them with us during our next development meeting 👇

August 4 Dev-Chat Agenda

We had 2 weeks to think about possible features for 10.0.0, let’s decide about the ones we’ll work on during this magically numbered release cycle 🪄.

It will happen on August 4 (tomorrow) at 19:30 UTC and of course in #BuddyPress.

If you have specific/additional points you need to discuss about, please share them into the comments area of this post.

#10-0-0, #9-0-0, #agenda, #dev-chat, #summary

imath 12:26 pm on July 11, 2021
Tags: , , relationship-api,   

BP Dev-Chat Summary: June 30/July 7, 2021

June 30 improvised dev-chat

Following the discussion we had during June 23 meeting about the frequently requested Follow feature, and a very interesting discussion between @sbrajesh, @espellcastewe and @johnjamesjacoby, we decided to improvise a new Dev Chat about a possible larger scope about it. We shared our views about building a wider vision for “relationship types” in BuddyPress. A new API that would firstly be used for the Follow feature, but could also be used for potential other needs: user likes, improved user favorites, blocking users, what may come to our mind in the future!

@sbrajesh will lead this new project using the “feature as a plugin” model like WordPress does from a BuddyPress GitHub repository. If you’re interested in contributing to this project, please “raise your hand” commenting this summary.

July 7 regular dev-chat

@im4th starts with an apology: unlike what was scheduled (July 8), we were not able to release the 9.0.0 first beta so far. Sorry about it.

9.0.0 🎯

We’ve migrated 90% of Widgets as Block Widgets from the GitHub repository we use to build BuddyPress blocks. We also improved some BP REST API endpoints and we’re on our way to include a new endpoint to deal with Sitewide Notices. BP Block Widgets have been built on 2 principles: use the BP REST API every time it’s possible and use Modern JavaScript on front-end and the Widget/Post Block Editor’s APIs (mainly built on top of React.JS) on back-end.

@dcavins has made great progress about the Sitewide Notices Block Widget (👉 the last one to reach 100%) and about the corresponding REST API Endpoints. @espellcaste gave great advices about the BP REST API to speed up the process.

We also talked about directly packaging a Release Candidate without doing a Beta release. As the 9.0.0 development cycle is focused on migrating Widgets as Blocks, we have a very limited risk of messing with other parts of BuddyPress. @im4th said he’ll work on merging the BP Blocks code into BuddyPress core and will try to find the time to quickly build a Beta Release and some time after the Release Candidate (he hates when he doesn’t do what he has written he would do).

We finally talked about the great work @vapvarun has done building a test drive to host the BuddyPress code reference. The goal is to make it available asap and before the end of the year here. The main difficulty is to generate the documentation using the WP CLI parser command directly from the server (10 minutes). @im4th wondered if this could be achieved using the WP import/export tool (the documentation plugin is using custom post types). This is an approach we’ll try to test to avoid possible downtimes of the BuddyPress.org network.

9.0.0 schedule

  • Beta: July ? 🤔
  • RC: July 12 to 14.
  • Final: July 16 to 19.

Next Dev-Chat

It will happen on July 21 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!

Additional note about meetings during 9.0.0 development cycle

As we are running a short development cycle, @im4th will be available every Wednesday at 19:30 UTC in #BuddyPress for an hour or more time if needed. Don’t hesitate to ping him (@imath) for help or inputs about contributing to this version of BuddyPress.

#9-0-0, #dev-chat, #relationship-api, #summary

imath 10:38 am on June 1, 2021
Tags: , , ,   

BP Dev-Chat summary: May 26, 2021

8.0.0-beta2 feedbacks

@im4th noticed the only feedback we got from this beta release was about the BP Beta Tester plugin. The issue about this testing tool was fixed in 1.2.0. Does it mean everything’s fine with 8.0.0? We’ll see with the release candidate that was published 4 days ago: if you haven’t tested it yet, please do so 🙏.

BuddyPress 8.0.0 Release Candidate

8.0.0 remaining tasks

  • @vapvarun has been working on the 8.0.0 changelog. He found a bug with the script we’re using to generate it. He shared a fix during the chat. @im4th suggested to build a PR out of it on @rayisme‘s GH repository.
  • @johnjamesjacoby and especially @dcavins copy reviewed the Hello BuddyPress screen text on (#8468). Thanks to them we were able to clean the open tickets about the 8.0.0 milestone.
  • We agreed it was time to package RC and decided to leave less than 2 weeks of string freeze to polyglots. The goal was to avoid postponing too much the 8.0.0 final release date. As you can see above, the RC was released on May 27.

8.0.0 final schedule

  • ✅ 8.0.0-beta1: April 29,
  • ✅ 8.0.0-beta2: May 20,
  • ✅ 8.0.0-RC1: May 27,
  • 8.0.0 stable release: June 7 👀

Open floor

We’ve been talking about the BuddyPress code reference. It’s still under construction and we really need to make it available asap. @vapvarun had the opportunity to test the parser tool and the only thing we need to make sure is to avoid parsing the BP REST API controllers to avoid some kind of duplicate information with the BP REST API documentation. As it was getting late @im4th suggested to have a specific dev-chat about it.

@dcavins shared a proof-of-purpose plugin that adds some limitations on who can send site membership invites.

Screenshot of the Proof of purpose plugin @dcavins built.

If anyone has ideas for limits to add, please let @dcavins know adding issues to this GitHub repository.

Next Dev-Chat

It will happen on June 9 at 19:30 UTC and of course in #BuddyPress. We’ll probably talk about the first results/feedbacks about the 8.0.0 stable release but If you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

PS: we count on you to test the 8.0.0 release candidate!

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

imath 7:19 am on May 15, 2021
Tags: , ,   

BP Dev-Chat summary: May 12, 2021

8.0.0-beta1 feedbacks

@vapvarun checked our support forum and hasn’t found concerning feedbacks relative to this release.

@im4th replied to one of the comments that was posted on the announcement post about the next WordPress Full Site Editing (FSE) & Widgets Block Editor features. He tested the first one before our meeting and told us about his concerns during the chat. In short it’s a breaking change for the BuddyPress Theme Compat API. A pretty long discussion took place between @johnjamesjacoby @im4th and @vapvarun about it. We finally decided to open a very important ticket on our Trac to decide whether it’s on BuddyPress or FSE to adapt. If you have an opinion about it, please take a few minutes to share it with us.

8.0.0 tickets needing attention

  • About the bp_core_new_nav_default()function ticket (#8471), we decided we were too close to release date to do the necessary tests to be sure the patch doesn’t introduce some regression
  • About the BP Directory pages ticket (#8470), we think it’s best to split the ticket in 2 and deal with admin information on the Registration/Activation page during 8.0.0
  • @im4th wants to finish his audit regarding #8459 before packaging a new beta release.
  • @espellcaste reminded us about the GitHub Actions ticket (#8421). He agreed with @im4th about only committing the PHP Unit tests part.
  • We also punted the ticket about including PHPCS to our build tools (#7228) to leave us the time to discuss more about it as we don’t agree all about when to check WP PHP code standards (before committing or as soon as patching). The latter could possibly discourage people to submit patches in @im4th‘s opinion. Feel free to give us your opinion about it, commenting on the ticket.
  • Finally about the remaining release tasks (#8468). @vapvarun will take care of the changelog and @im4th will prepare the credits update.

8.0.0 updated schedule

We agreed to build a new beta release before our release candidate. @im4th will take care of it next week.

  • ✅ 8.0.0-beta1: April 29,
  • 8.0.0-beta2: ~ May 19,
  • 8.0.0 stable release: June 2.

Next Dev-Chat

It will happen on May 26 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!

PS: we count on you to test the 8.0.0 beta release!

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

imath 6:01 pm on February 22, 2021
Tags: , , ,   

BP Dev-Chat summary: February 17, 2021

7.2.0 Maintenance release

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.

8.0.0 progress

  • @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
    • #8001 Replace At/Who JavaScript Libraries by Tribute.

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.

Next Dev-Chat

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!

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

imath 2:20 pm on January 18, 2021
Tags: , ,   

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

imath 5:55 am on December 10, 2020
Tags: , ,   

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