BP Dev-Chat Summary March 4, 2024

• See previously BP Dev Chat summary February 19 (2024)
• In attendance: @dcavins @im4th @emaralive @espellcaste
• Slack archive

⏰ New development meeting day/time

@im4th suggested to change the day and time we meet to discuss about BuddyPress development so that it’s more suitable for contributors located in Asian time zones. Let’s come back to our “legacy” day/time: every other Wednesdays at 19:00 UTC!

@emaralive @espellcaste & @dcavins agreed (even during DST, 19:00 UTC can be problematic for David’s presence during 1st meeting half).

As Documentations chats are also happening at this day/time, we’re always meeting on Wednesdays at 19:00 UTC and depending on the current week number, we’ll be talking about development (even weeks) or documentations (odd weeks).

🧰 BuddyPress 14.0.0

Release lead: imath

@im4th asked if one of us was wishing to lead this release: @dcavins won’t be able to find the time to, @espellcaste volunteered to lead next major release. To let the time to @emaralive to experience a full release development cycle, @im4th volunteered & is the 14.0.0 release lead.

Ticket updates

To view the full tickets list slated for this milestone, go there!

• @emaralive hasn’t progressed yet about #8728 (Allow group moderators to moderate group activities).
• @espellcaste has put together a local site about BP CLI commands reference (See #9113).
• @dcavins has not progressed about #8794. It’s a pretty sensitive subject as it deals with capabilities in WP Admin. Best approach seems to be to build a specific & new Admin screen to let users having the bp_moderate cap to manage site membership requests.
• @im4th reopened #9101 as he was worried about the fact we’re adding 2 accordion sections to the site-health debug screen. It’s closed again as using a single section is not separating nicely settings from constants when using the copy feature.
• @im4th moved the ticket about improving Activity Favorites management out of the 14.0.0 milestone (See #5644). He was the only one of the team in favor of introducing Likes as Activity children and highlight this as one of the top features for 14.0.0. Users will need to wait for a future BP Relationships API.
• Without any news from @rayisme, he also moved the Followers feature (See #7133) out of the 14.0.0 milestone. Moreover the plugin’s scope is larger than following members (using it, you can follow activity or blogs for instance).
• @emaralive wanted to talk about #9098 as re-thinking the Site Wide notices feature can have implications about BuddyPress documentations. But we agreed to talk about it during our next development meeting as it was getting late.

Finally @im4th asked the team to use the 2 coming weeks to think about the 14.0.0 top features as @dcavins said “it’s nice to have a focus, so that the release accomplishes something that seems cohesive”. So far many of the enhancements slated for next release are to make administering a BP site easier.

14.0.0 schedule reminder

• June 3: 14.0.0-beta1.
• July 8: 14.0.0.

Next Dev-Chat

It will happen on Wednesday March 20, 2024 at 19:00 UTC in #BuddyPress.

#14-0-0, #dev-chat, #summary

BP Dev-Chat Summary February 19, 2024

• See previously BP Dev Chat summary February 5 (2024)
• In attendance: @dcavins @im4th @emaralive @espellcaste
• Slack archive

What do we want to keep in the 14.0.0 milestone?

• @espellcaste reminded us why he asked about making this specific point: to have a better visibility of what’s actually planned on the milestone. He added that if there was a ticket we don’t know if we would have the time to work on, it’d be great to put in the next milestone.
• @espellcaste then asked Team members to assign themselves on the tickets they wish to work on during the 14.0.0 development cycle. Once done, his idea was to discuss together about the remaining tickets. He actually took the lead of the meeting to run this tickets review.

Below is the remaining tickets list:

• About #7133 (BuddyPress followers plugin to join the BP Add-ons collection) @im4th contacted @rayisme by e-mail but got no reply from him so far. @im4th already has commit access on the plugin’s WP.org repository but he thinks it’s better r-a-y’s GitHub repository is transfered on the BuddyPress organization account before we can all eventually contribute to it.
• About #9065 it’s an issue Dion Hulse (from the WP Core/Meta team) started contributed to due to potential fatal errors with malformed Request inputs. @im4th thinks it’s important as Dion explained to fix it in BuddyPress waiting for it to be possibly fixed by WordPress, so he assigned himself on the ticket.
• The chat thread was going pretty quick so @emaralive informed it was difficult to follow especially when you try to read a very old ticket like #5644 (Activity Favorites management). This was actually our second point on our meeting’s agenda! @im4th wanted to take the time to explain why he thinks we really should use Activity children like comments to transform Activity Favorites as Activity Likes. @espellcaste, who was probably very focused on reviewing the remaining unassigned tickets, didn’t pay attention to this discussion and carried on his review. (1).
• @espellcaste thought @im4th was the best contributor to work on #9063 so @im4th assigned himself on it and will try to make it possible to add a way to use a slug prefix for BP Directories rewrite rules.
• @emaralive volunteered to work on the Group Moderator cap issue #8728.
• @espellcaste volunteered to work on integrating Group/Member types into the BP REST API and assigned the requested member types improvement tickets to himself (See #8618 & #9092).
• @espellcaste then decided to punt unassigned tickets to next release cycle.

14.0.0 schedule reminder

• June 3: 14.0.0-beta1.
• July 8: 14.0.0.

BP Cli documentation

Then @espellcaste decided to talk about this subject instead of the 2 remaining points we added to our agenda. His goal is to build a BP Cli command reference like the one WP Cli has elaborated. @im4th suggested « if we can do it for BP Cli, then we can also build a code reference for BuddyPress ». @espellcaste informed he would first look into a code reference for BP Cli as a test ground to see what issues we’ll face before eventually working on a BuddyPress code reference.

(1) imath’s Apologies to @emaralive & @dcavins

As I’m @im4th 🤗, the one writing this summary, I’d like to say:

Even if this tickets Review was an interesting experience and even if @espellcaste was really good at running it, I realize I should have stopped him to take the time to make sure @emaralive could catch up when he expressed his difficulties, make sure @dcavins had a chance to express his wishes during the tickets review, and make sure to respect the meeting agenda. I apologize – a hard day at work was probably the reason why I made these mistakes.

Next Dev-Chat

It will happen on March 4, 2024 at 21:00 UTC in #BuddyPress.

#14-0-0, #dev-chat, #summary

BP Dev-Chat Summary February 5, 2024

• See previously BP Dev Chat summary January 22 (2024)
• In attendance: @dcavins @im4th @emaralive @espellcaste
• Slack archive

What do we expect from 14.0.0?

• We started with a very interesting thread about transforming the Private Messages component as a Slack-like chat system where BP Groups could be used as channels to discuss with corresponding group members. The wp-sync package could help us to reach this goal.
• As it’s a pretty huge change, improving the Private Messages component using pagination could be a first step on our road. The potential backwards compatibility obstacle with Standalone BuddyPress themes could be avoided improving the way we currently use the WP Theme support feature adding a list of buddypress features. Eg: add_theme_support( 'buddypress', [ 'messages_pagination', 'etc..' ] ).
• @emaralive suggested to have a look at the Better Messages plugin.
• We talked about #7133: Having @rayisme‘s BP Followers into our Add-ons galaxy would be a great addition. As @im4th already got in touch with @rayisme about this subject he will contact him again to ask him if he’s fine with transferring the GitHub repo into the BuddyPress org so it’s easier for the team to contribute to it.
• @espellcaste see potential Cron related issues about #7953 (Activity Scheduling).
• @im4th thinks we should consider improve Activity favorites to act like bookmarks or likes, see #5644.
• About BuddyVibes @im4th is currently working on making it a WP Block only Theme first. He thinks if we’re waiting for a design contribution it will never happen, reason why he chose to work on a very basic structure.

14.0.0 first schedule!

14.0.0 will be a shorter development cycle than 12.0.0 (which took us almost a year). A 4/5 months development cycle was decided: 14.0.0-beta1 in 4 months, final release in 5 months.

• June 3: 14.0.0-beta1 .
• July 8: 14.0.0.

@dcavins suggested to start discussing on the tickets we should keep into the 14.0.0 milestone during our next meeting. @espellcaste suggested to start looking into it a bit before the meeting to only leave the tickets we should discuss about.

Next Dev-Chat

It will happen on February 19, 2024 at 21:00 UTC in #BuddyPress.

⏰ 🔩

#14-0-0, #dev-chat, #summary

BP Dev-Chat Summary: September 18, 2023

• See previously BP Dev Chat summary September 5 (2023)
• In attendance: @dcavins @im4th
• Slack archive

BP Add-ons & 12.0.0 compatibility

We discussed about reported issues about BP Classic & BP Attachments. The one about BP Attachments was pretty annoying as it was preventing BP Emails to be sent when using the BP Nouveau template pack (where a lot happens using Ajax requests). After some investigations, the issue was even more problematic as it was generating 404 for regular WordPress pages. The 1.2.0 release fixed what appears to be a regression introduced in 1.1.0. We also discussed about the opportunity to transform @rayisme ‘s BP Follow as a BP Add-on maintained by the BuddyPress Core team. In the meantime the needed changes to make this plugin support BP 12.0.0 were merged into its GitHub repository.

12.0.0 latest updates

@im4th shared some information about the improvements he brought to BP_Members_Component::check_parsed_query() (see #8996). In short this function is now checking the requested user page is well registered inside the BuddyPress user navigation. If it’s not the case, it displays a 404.

@im4th also talked about the patch added to #8578 and said he was trying to improve it to make sure to keep a trace about Message subject or content after a missing information interrupts the message creation process.

@espellcaste has been preparing notice errors fixes using pull requests on our GitHub repository (See #163 & #162).

@dcavins said he would soon be able to add a patch to #8959 so that the URLs setting page includes an Help tab to explain how to customize BP URL’s slugs. He has since committed the needed changes to close the ticket.

About packaging a 12.0.0-beta3

@im4th & @dcavins agreed packaging a new beta will be another opportunity to raise BP Plugins/Themes authors attention about the important change introduced into this major release. It should be packaged very soon.

Schedule

• 12.0.0-RC : TBD,
• 12.0.0 : October 30.

Other news about the BuddyPress project

@im4th participated to a french Podcast about the future of BuddyPress. If you understand french, you can listen to the interview: it starts at 7’52”.

Next Dev-Chat

It will happen on October 2 (today!) at 21:00 UTC in #BuddyPress. If you have specific points or ideas you want to discuss about, don’t hesitate to share them in comments.

#12-0-0, #dev-chat, #summary

BP Docs-Chat summary: September 6, 2023

• In attendance: @jasonrouet @dcavins @im4th @bouncingsprout @vapvarun
• Slack archive
• FYI: here’s the agenda we published before the meeting.

Here’s the recap of the BP Docs-Chat on Slack:

1. Follow-up on the actions planned for August

• Starting a discussion with @johnjamesjacoby on how to add a warning message on the codex

-> See last docs-chat summary for more details.

@im4th said he’ll reach out to JJJ about this item (nothing urgent).

• Deploying the tutorial on how to contribute to the new doc directly on Github

@im4th committed it to trunk here: https://github.com/buddypress/buddypress/tree/master/docs/contributor/documentation

As we said during the previous meeting, this PR is kind of a tutorial on its own, as it initiates subdirectories and shows what content might look like on Github.

• Quick news: how are things going for 12.0.0?

@im4th said beta testers are still needed. 12.0.0-beta2 will probably be packaged on September 7.

For now, the documentation team isn’t ready to manage release notes on the new documentation. But it’s an opportunity to think about how we’ll document everything a release adds/removes/changes in the future.

The 12.0.0 release should help us identify the process to be implemented for the documentation team to update the content once the release notes are generated.

@vapvarun shared with us how release notes are generated. When 10.0 and 11.0 were released, the following plugin, built by @rayisme was used to generate release notes: https://github.com/r-a-y/bp-changelog

@im4th and @bouncingsprout quickly said it would be great to improve it to handle markdown formatting and maybe add some github action.

2. Main item of our meeting: how to start working on the content over the next two weeks:

The plan discussed is:

• @im4th will share a csv file listing all the existing content urls from the codev to @jasonrouet who’ll create a spreadsheet on GDrive for the team to work on it easily,
• once the spreadsheet shared with the team, people will be able to:
  • review: we’ll need @im4th and @dcavins help specifically to comment each urls by saying if:
    • the content is up-to-date (maybe it needs more details, but could be imported as is to the new doc)
    • the content needs editing (some parts of the content change but it’s still a relevant piece of content)
    • the content is totally outdated and should be rewritten from scratch (some pages could still be needs, others not anymore if it refers to some feature that doesn’t exist at all)
    • edit: once a url has been reviewed by someone with enough experience, it will be ready for assignment. Someone will then be able to take charge of editing the content (see tutorial on how to contribute to the doc for the steps).
• Alongside, the work on the importing the content from the codex. We’ll have to reconsider how the content is structured. At first we’ll probably start with something close to the current codex structure and then progressively reorganise things based on the updated content.

So basically, the “reviewers” (a.k.a our gatekeepers as @bouncingsprout named them 😀 ) will add some kind of ‘inline comment’ on the spreadsheet. It will help “editors” know what to remove/amend/rewrite.

The initial work on sorting/importing content from the codex once done, we’ll be able to say “we are done with the codex, everything still up to date on the old documentation is already in the new documentation” and focus on producing new content that doesn’t exist on the codex (edited)

Starting by sorting/editing and importing the articles of the codex, we will quickly be able to ensure that what is still up-to-date in the codex is also already available in the new documentation (with updated screenshots, references to the latest versions, etc.). Then we’ll be able to focus on producing new content for the new documentation without having to care about the codex at all (with one exception: the release notes will still be published via the codex for now).

3. Language quality check: how can we ensure that the documentation is written in proper English? Is en-US the default language localisation?

Intro: it’s best to adopt good habits from the start. A significant part of the team won’t be English natives.

The group agreed on having en-US as the default language. Quick note from @jasonrouet: remember to set your tools like Deepl/Grammarly/LanguageTools/… to that specific locale! 😉

We said, language check (spelling/punctuation/grammar) should be part of the quality checks at the same level as Markdown formatting check, technical content check…

For now, Ben and David agreed to check the language. We’ll document this process in /master/docs/contributor/documentation/.

4. Get inspiration from what the WordPress project documentation team is doing

@bouncingsprout said he’ll introduce himself and attend some meetings from that team to collect good practices. Ben said they have a good new contributor onboarding process, internal team processes, etc… All good for the team, any external advice is welcome, we need our own processes, but learning from the team that has been working for years and that has already carried out a migration from their old codex to a new documentation is certainly worthwhile.

Finally, he said he’ll be our cookie dealer, copying @milanacap strategy! 🍪 See you at a WordCamp to share a snack together! 😉

---

Next Docs-Chat

It will happen on September 20 at 19:00 UTC in #BuddyPress. We are a small but friendly team, everyone is welcome to contribute: this may be done by editing the documentation or by sending us feedback on what is missing from the documentation.

#docs-chat, #summary

BP Dev-Chat summary : September 7, 2022

• See previously BP Dev Chat summary (August 17, 2022)
• In attendance: @dcavins @espellcaste @im4th
• Slack archive.

BP Attachments / Activity block editor update

• @im4th has started working on templating to display single media on the front-end.
• He also made it possible to share media using the Activity Block Editor when the BP Attachements plugin is active. This means block developers could soon enjoy a new playground to express themselves.
• The BP Attachments Admin UI now includes an “Edit Item” view. See the screenshot below.

11.0.0 updates

• @im4th shared he was hesitant about #8052. Now the blog post title is directly included into the corresponding activity type’s content, we don’t need to use a blog meta to retrieve it inside the activity action string anymore.
• @dcavins suggested to request a feedback from @rayisme who worked on this part and should be the best of us to know whether it’s safe or not to make this move in 11.0.0.

11.0.0 schedule reminder

• First beta: October 19, 2022.
• Release: December 14, 2022.

Open floor

@im4th started discussing about the drop on the active installations stat we observed on the BuddyPress WP.org plugin’s page as it went down from 200k to 100k 😱. Thanks to @johnjamesjacoby we were able to get more precise numbers about this decrease and it turns out we’re around 190/195k active installs. But the trend since year 2017 is concerning as it’s 📉 not to mention the fact there are less and less contributors to the project 😭. We’ve discussed about the possible reasons for these bad results:

• lack of cool front-end things added to the plugin recently,
• hesitancy to install a big plugin like BuddyPress for a single feature,
• lack of privacy tools, of a media component,
• growth of the use of things like Teams and Slack,
• BuddyBoss’s commercial aggressivity (eg: Google Adwords) or their slick-looking theme attractivity,
• etc..

As the BP Attachments add-on should be available around the 11.0.0 release date, the first action we took was to open a ticket about including a basic private community feature into our next major release.

After some more discussions with @espellcaste we came to the conclusion we need more data from users. A new survey was suggested as well as asking the WordPress Marketing Team for help. We finally thought about posting into our support forum this simple question “what is the most important feature that BuddyPress is missing?“. We decided to test this last idea as soon as we have a text to explain why we are questionning ourselves about it. If you believe you have answers to share with us, don’t hesitate to comment this post 🙏.

Next Dev-Chat

It will happen on September 21 at 19:30 UTC in #BuddyPress. If you have specific points you want to discuss about, don’t hesitate to share them in comments.

#11-0-0, #dev-chat, #summary

BP Dev Chat Summary : september 1st, 2021

• See previously BP Dev Chat summary (August 18, 2021)
• In attendance: @espellcaste @vapvarun @johnjamesjacoby @im4th
• Slack archive.

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

• Big improvements were brought to Group’s slug customization
• Big improvements were brought to backward compatibility with BP Plugins trying to get BP URI globals early.

@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

BP Dev-Chat Summary: june 23, 2021

• See previously BP Dev Chat summary (June 9, 2021)
• In attendance: @espellcaste @vapvarun @dcavins @sbrajesh @im4th
• Slack archive

9.0.0 🎯

During yesterday’s development meeting we’ve discussed about @im4th‘s proposal to run the 9.0.0 development cycle very shortly targeting a release date before WordPress 5.8 final release is made available to the planet (~ July 20, 2021)!

@im4th was a bit worried about being too much directive and/or too ambitious, so he specified it was ok to disagree with this proposal. We quickly agreed, but here are some opinions we shared about this idea:

• “Sounds great.” @sbrajesh
• “I’m OK with your short cycle just for blocks to support the WP release” @dcavins
• “I like the idea of very targeted releases” @dcavins
• “the short release cycle is fine. The reason is good and makes total sense to me” @espellcaste

So we are going to try to do it!

9.0.0 Focus

Blocks!

As WordPress 5.8 is introducing the Widgets Block Editor, we are going to start migrating our legacy widgets. We actually already started the process from the GitHub plugin we use to develop BuddyPress Blocks. The first step is building a block for every BP Widgets and making it possible to transform existing BP Widgets to their corresponding BP Block. BP Widgets won’t disappear in 9.0.0 yet (no worries), but they’ll get a well deserved retirement progressively 😁. You can expect (at least) 10 new BuddyPress Blocks to be introduced in BuddyPress core.

A new follow component (if it’s ready for 9.0.0 release date)

@sbrajesh volunteered to satisfy a frequent request about this feature and he’s very welcome to contribute and lead this effort to make it happen! We talked about the “Followers” plugin @rayisme built which can be a source of inspiration. We’ll organize it from another specific GitHub repository. After the dev-chat, we had a complementary discussion about it, you can have a look at it for more information about early directions about the feature.

And of course, we’ll fix issues related to our latest major release (8.0.0) that may be found.

9.0.0 schedule

• Beta: July 8.
• RC: July 12.
• Final: July 16.

8.0.0 issue “monitoring”

During the dev-chat, we also discussed about the feedbacks we got from the support forums about 8.0.0. We shared our surprise that plugins that appear to rely on BP aren’t tested in the beta window. This is something we need to carry on trying to improve. Working on documentation could be a way. On this topic, @vapvarun informed us he would prepare a list about which documentation resources need updates & then update them one by one 😍. Many thanks to him: it’s a very important work that will benefit to us all.

Next Dev-Chat

It will happen on July 7 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, #summary

BP Dev-Chat summary: May 26, 2021

• See previously BP Dev Chat summary (May 12, 2021)
• In attendance: @vapvarun @johnjamesjacoby @dcavins @im4th
• Slack archive

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

BP Dev-Chat summary: January 6, 2021

• See previously BP Dev Chat summary (December 16, 2020)
• In attendance: @slaffik @johnjamesjacoby @im4th
• Slack archive

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