BP Dev Chat summary: April 8, 2020

BuddyPress Survey

@mercime has decided to wait for 6.0.0 final release to launch the survey. We will be able to add a link to it inside the “Hello BuddyPress 6.0.0” screen (See #8270). There will be 17 questions into the survey. If one of the team members wishes to request a new one, the deadline to make it happen is the day before the release date.

Progress about 6.0.0 release

6.0.0-beta1 was released on March 31 at 10:43 PM (WP Plugins directory’s time) : just before the end of march as announced 💪⏱. The WP Tavern wrote a great post about it and shared a very interesting feedback that has been converted to this ticket (#8271) since. The patch will soon be committed.

@johnjamesjacoby will try to find a way to get more information about future beta/RC downloads as we are always worrying to have very few feedbacks about them.

@rayisme is requesting your feedback about the 2 new exportable privacy data types, please do so adding your comment to this ticket: #8266.

He also fixed a very annoying error about a deprecated WP privacy function: it’s already available into the 5.0 branch and will be shipped during our next maintenance release. FYI: the problem is WP moved the deprecated function into a file that is only loaded into the /wp-admin context.

@im4th will package a new beta release (the second) on April 15.

BP REST API documentation update.

@im4th said he was sorry he couldn’t find the time to write some explanations about how to updated the documentation. He has since done using the Swagger UI tool. Here are the explanations (NB: in this Gist, there’s a file over the bp-custom.php one, you will also need).

Open floor

@espellcaste asked about the BP GraphQL documentation’s ticket on Meta Trac since it has not evolved for a while. 😬

@mercime has suggested to include a link to the developer.bp.org’s site inside the BuddyPress.org main menu. She wrote a ticket about it on Meta Trac. 💡👍

@im4th thanked Varun & IAmTheWebb for their very interesting contributions to the dev chat: everyone is welcome to do like them 🤝.

6.0.0 schedule & main features

  • Schedule:
    • Beta-2 April 15
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints ✅
    • BP Blocks ✅

Next dev chat

It will happen on April 22 at 19:00 UTC (a big week before final release ) 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!

🏡 Stay safe & Happy Easter 🥚

#6-0-0, #dev-chat

BP Dev Chat Summary: March 25th, 2020

BuddyPress Survey

@mercime has prepared 17 questions for the survey. She asked about the possible GraphQL question @espellcaste suggested to add during our previous dev-chat. If Renato has ideas about it, she will be able to insert it. About the survey publication date, @im4th suggested to add a link inside the “Hello BuddyPress 6.0.0” screen. @mercime was thinking about publishing it earlier to be able to close it before 6.0.0 release. @mercime will decide what’s the best option.

Progress about 6.0.0 release

@im4th reminded the dev-chat participants, the beta was scheduled 6 days later (at this time, today at the time I’m writing this summary!). He asked if a ticket or a feature needed an extra delay to be fixed : it wasn’t the case.

@mercime and @dcavins said they will give a test to the new BuddyPress blocks that had just been added to BuddyPress core (See #8048).

@im4th shared he still needed to work on the inclusion of the BP REST API remaining endpoints into BuddyPress 6.0.0. #7156 has been committed since.

BP REST API documentation update.

Once BuddyPress 6.0.0-beta1 will be released, we’ll need to update the BP REST API reference so that the new endpoints are documented before 6.0.0 stable release.

@mercime & @dcavins volunteered to give a hand 😍. @im4th will write some explanations about how to update the documentation on the https://developer.buddypress.org site.

6.0.0 schedule & main features

  • Schedule:
    • First beta in a few hours!
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints ✅
    • BP Blocks ✅

Next dev chat

It will happen on April 8 at 19:00 UTC (a few days before first beta 🙄) 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!

#6-0-0

BP Dev Chat Summary: March 11th, 2020

BuddyPress Survey

We’ve been discussing about adding questions about 2 topics : BuddyPress integration with e-commerce plugins and BuddyPress alternatives. We found a compromise about the second topic and @mercime will add this question:

What other networking/membership plugin/software have you considered or used?

@espellcaste suggested to add a question about BP GraphQL consideration. @im4th suggested to add this feedback to the Google doc @mercime uses to work on the survey questions.

Progress about 6.0.0 release

@im4th asked about the BP REST API complete merge into BuddyPress core now all remaining endpoints are ready. @espellcaste prefers to keep maintaining it from its GitHub repository for now.

@im4th has decided to merge the BP Blocks plugin into BuddyPress core, following @johnjamesjacoby advice to reconsider his first idea about only merging “JavaScript built” blocks. A complete merge seems a better option to make sure to generate a pot file taking in account JavaScript translations. He recently added a patch on #8048 to make this happen, feedbacks welcome.

@dcavins was a bit worried he needed more than 2 weeks to end the Network invites work. If it’s the case, he will only include a portion of the code into 6.0.0.

Finally @im4th asked for help about #7729 @rayisme has been working on during. It’s about removing the legacy BuddyBar.

6.0.0 schedule & main features

  • Schedule:
    • First beta at the end of march.
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints ✅
    • BP Blocks ✅
    • Network invitation & Membership requests 😬
    • & maybe some surprises! 😬

Next dev chat

It will happen on March 25 at 19:00 UTC (a few days before first beta 🙄) 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!

#6-0-0

BP Dev Chat Summary: February 26, 2020

6.0.0 Progress

@espellcaste shared about the work he’s been doing about improving the BP REST API (activity scope, member type, group type, friendship). The last issue we need to deal with is the Blogs Avatar endpoint (2 unit tests are failing mysteriously). @im4th will give it a second look before next dev-chat.

@dcavins & @im4th didn’t find the time to work on #8139 & #8048 😬

@im4th shared about his wish to solve two tickets (#8156 & #8172) asap to inform the BuddyPress contributors early about the introduced changes. They are now solved, so please make sure to have a look at these 2 posts:

BuddyPress Survey

Open floor

@im4th asked if anyone had an opportunity to look at GitHub actions to see if this was a way to ease the release packaging process. If a BuddyPress contributor could explore it, he’d be very happy 😍

@espellcaste asked about the status #5525 : the testing site is still open for review, but @im4th already found some issues about o2 as soon as it’s not used on the home page of the site. He will work on a fix about it.

@espellcaste shared his worries about the meta ticket related to the BP GraphQL handbook creation for the developer.buddypress.org site. @im4th is confident it will be fixed soon 🤗

6.0.0 schedule & main features

  • Schedule:
    • First beta at the end of march.
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints
    • BP Blocks ✅
    • Network invitation & Membership requests
    • & maybe some surprises!

Next dev chat

It will happen on March 11 at 19:00 UTC ( ~ 2 weeks before first beta 🙄) 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!

#6-0-0

BP Dev Chat Summary: February 12, 2020

BuddyPress Survey

@mercime shared her progress about her first pass on the BuddyPress survey for 2020 (see #8153). She prepared 16 questions.

  • We’ll use CrowdSignal to publish the survey.
  • On a side note @johnjamesjacoby suggested BuddyPress could have a lightweight Questionnaire component, @im4th believes it’s a great idea !
  • @mercime shared with all of us the questions she worked on after the dev-chat. Please take some time to review it before our next dev-chat

BuddyPress dev-chat are maintained on every other wednesday at 1900 UTC.

Unfortunately @espellcaste can’t join us on all the alternative days of week we’ve found into the doodle 😦 As the result it doesn’t worth changing our dev-chat meeting day/time.

6.0.0 Progress

@dcavins is making good progress about Network invites (#8139). He’s getting some inspiration from the Invite Anyone plugin. @im4th asked if it would be possible to invite a user not yet registered to the site to join it using a group invite, and the reply is yes 🙌

@im4th confirmed BuddyPress 6.0.0 will ship 2 Blocks and shared his progress about the Group Block. Here are 3 early screenshots of how it could look like :

The team also shared their thoughts about whether we should ship the JavaScript built blocks or include the complete JavaScript source files into trunk and build the Production scripts from there. At the minimum we’ll need to move to using WP CLI to generate our POT file so that JavaScript translations are available within GlotPress. @im4th will work on this asap from this trac ticket #8048.

Finaly we’ve talked about the fact the project behind the JavaScript library we are using for our suggestions feature is no longer maintained. We shared thoughts about moving to the Tribute library and using the BP REST API instead of AJAX. So far there are no impacts on the suggestions feature and we are taking some more time to think about it, having in mind we could also benefit from the BP AutoCompleter React component we’ve built for our 2 BP Blocks.

6.0.0 schedule & main features

  • Schedule:
    • First beta at the end of march.
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints
    • BP Blocks ✅
    • Network invitation & Membership requests
    • & maybe some surprises!

Next dev chat

It will happen in 2 days on February 26 at 19:00 UTC and of course in #BuddyPress.

PS1: sorry it took me so long to write this summary 😬

PS2: if you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#6-0-0

BP Dev Chat Summary: January 29, 2020

BuddyPress Survey

@mercime asked for the questions we’d like to include for this new version of the survey (see #8153). In other words, what do we need to know from BuddyPress users to help us in our decisions?

  • We agreed we need to keep questions from previous surveys to be able to compare results.
  • Knowing which components are mostly used should help us to validate/improve the activation process. How could we improve/facilitate the BuddyPress setup process?
  • We’d like to know how people choose to “display” BuddyPress content. Are they using a regular WordPress Theme with a template pack (and which one? Legacy or Nouveau?), are they using a BuddyPress standalone theme like BP Default ?
  • We need to evaluate the idea of including a new full featured BuddyPress Theme.
  • @im4th shared his wish to know what approach people prefer between BuddyPress bundled optional components Vs optional components as plugins (see #8148). @mercime noted that, in previous surveys, people usually ask to bundle new optional components or to include BuddyPress plugins into Core.

We shared some other potential questions during the meeting (What are you using BuddyPress for? Would you be willing to switch to a BP Specific Theme? What are must have customizations? What are the every BuddyPress installs components?…), @mercime will work on a first pass of the 2020 survey so that we can discuss about it during our next dev-chat.

New day of week for our dev-chat?

@im4th thanked again the members of the team who gave their preferences into the Doodle poll. We have a first important information: 19:00 UTC will stay our time of meeting. We are now waiting for @espellcaste preference about the day between these possible ones: Monday, Tuesday, Wednesday or Thursday?

6.0.0 Progress

@im4th began to talk about the many PHP/JavaScript code standards patches that has been submitted by new contributors such as Passionate, WPAmitkumar, Mukesh27. Thanks a lot for your work and feel free to carry on helping us.

@dcavins is making good progress about Network invites and membership requests and is confident this feature will land into the 6.0.0 release.

@im4th shared his progress about BP Blocks and thanked @karmatosed for her great help contributing to design sketches of the single Member and single Group blocks. BuddyPress 6.0.0 will include these 2 blocks. Here are 3 early screenshots of what could look like the Member one.

6.0.0 schedule & main features

  • Schedule:
    • First beta at the end of march.
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints
    • BP Blocks
    • Network invitation & Membership requests
    • & maybe some surprises!

Next dev chat

It will happen next week on February 12 at 19:00 UTC (unless @espellcaste informs us about his preferred day 😉soon) and of course in #BuddyPress.

PS: if you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#6-0-0

BP Dev Chat Summary: January 15, 2020

Main features for 6.0.0

BP REST API (improvements and remaining endpoints)

@espellcaste has been working on fixing some issues posted on the GH repository. With @im4th they discussed quite a time about one specific issue that is now resolved (many thanks to @espellcaste for his work on it 💪). About the tasks scheduled for 6.0.0, you can take a look at this GH project. Here are the remaining endpoints:

  • Member’s cover endpoint
  • Group’s cover endpoint
  • Friends endpoint
  • Blogs endpoint
  • Blog’s cover endpoint
  • Blog’s avatar endpoint
  • Signups endpoint

FYI this Core ticket should also be fixed for 6.0.0: #8156 (Move Avatar into the Members component).

BP Blocks

@karmatosed has shared sketches and thoughts about the first 2 BuddyPress blocks we will add in 6.0.0:

@im4th will start working asap on the first implementations of these 2 blocks building an autocomplete control to select the member or the group to display. @dcavins suggested this could be a good opportunity to review our Suggestion API so that it uses the BP REST API.

Network invitations & Membership requests.

@dcavins will work to make it happen in 6.0.0, you can still add your feedbacks on this ticket #8139.

Surprises!

@mercime & @im4th will also try to work on some surprises for this next release. We are keeping the features secret for now 😂

Core improvements

@im4th also shared his wish to use WordPress Rewrites instead of our legacy way of building URLs, see #4954. A possible way of progressing about it could be to use a plugin… He will look into it to see if it needs some Core adjustments.

BuddyPress survey

Discussing about the previous points took us a while and we decided to talk about the survey during our next dev-chat.

Open floor

@espellcaste cannot attend our dev-chats at the date/time they are scheduled. I’ve published this doodle to let us try to find a new day / time of the week for our meetings. I’ve left the current day / time: choose it if you prefer to leave the day / time unchanged.

6.0.0 schedule & main features

  • Schedule:
    • First beta at the end of march.
    • Final release at the end of April.
  • Main Features:
    • BP REST API remaining endpoints
    • BP Blocks
    • Network invitation & Membership requests
    • & maybe some surprises!

Next dev chat

It will happen next week at the time/date we decide replying to this doodle (and of course in #BuddyPress).

PS: if you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#6-0-0

BP Dev Chat Summary: December 18, 2019

5.1.0 summary/feedbacks

The maintenance release has been published on December 9. The download spike happened on December 10 with 24125 downloads (a bit more than the amount we got when releasing 5.0.0).

This was the first time @im4th used the edited steps of our prelaunch checklist to deploy the release on WordPress.org. He confirmed these edits made sure the POT file (used to generate translations) has been updated the right way on GlotPress.

No specific support topics has been posted about this release so far.

The 6.0.0 development cycle’s schedule

  • First beta at the end of march.
  • Final release at the end of April.

Open floor

BuddyPress survey 2020

With @mercime ‘s help we’re going to organize a new survey early next year (#8153). Results will be published shortly before 6.0.0’s first beta. @dcavins thinks it would be great to include questions relative to the direction @johnjamesjacoby suggested to take about theme/templates (see previous dev chat summary for details). @im4th requested to find questions to help us figure out if #8148 is a good idea or an absolute no go.

Upgrade tasks

@dcavins shared his concerned about the reliability of our upgrade routines (See #8141). Instead of doing these upgrade tasks at first admin load, he suggested to move these tasks into the Tools Administration Screen where we already have some maintenance features in there. With @im4th they discussed about a possibility to run these tasks in smaller steps using JavaScrip and AJAX or REST requests.

Merry Christmas to the BuddyPress Community!

🎄🎁

#5-0-0, #6-0-0

BP Dev Chat Summary: October 16, 2019

The Dev Chat started 20 minutes late: we’re not completely used to the new meeting time (NB: 18:00 UTC every other wednesday)

“Think”

The BuddyPress Blocks poll

@im4th posted the poll on this site and into a topic of the BuddyPress forums on October 10. After 6 days, the community participation is very week. It’s difficult to figure out what are people expectations. Here are the “top blocks” :

  • A block to share a post or a page via the Activity Stream (14 votes)
  • A block to list the recently published posts from across your network (Exists as a widget) (13 votes)
  • A block to dynamicaly list the recently active, popular, newest, or alphabetical groups (Exists as a widget) (11 votes)
  • A block to display Sitewide Notices posted by the site administrator (Exists as a widget) (11 votes)

The least we can say is there doesn’t seem to be a great enthousiasm for BuddyPress Blocks… As JJJ said maybe “the concept of BuddyPress blocks is not an easy one”.

How can we improve the way users get help?

This is a subject we couldn’t talk about during previous dev chat. There are a lot of topics posted on forums, and a lot are remaining without replies. @johnjamesjacoby thinks and I guess he’s right:

I believe, in general, the more activity there is from BuddyPress maintainers on the site, the more that others are likely to engage with us and each other.

So the first thing we can do is to try to contribute ourselves to forum replies as much as we can. Then here are the other ideas we had :

  • A styling refresh of the homepage and forums area.
  • Add some self care content. Eg: the replies to common issues users may encounter when starting with BuddyPress.
  • Moving the “bpdevel site” (this site) to a new make.BuddyPress.org site might help to bring some new contributors to forums. (@im4th announced he will soon share the work he has been doing about this project).

Let’s organize a BuddySesh!

To follow up the nice discussion @im4th had with David Bisset (@dimensionmedia) we’ve been briefly talking about this possible way of gathering BuddyPress contributors from all around the world for a day of conferences / chats. We’ll come back on the subject with David once the WordCamp US is behind us as he’s pretty busy contributing to its Programming team.

“Do”

BuddyPress Beta Tester plugin (& 5.1.0 minor release)

The GitHub repository for the BuddyPress Beta Tester plugin has been published. According to @im4th‘s tests, it’s working fine. To test it with a real Beta Version, @im4th suggested to soon package a 5.1.0-beta. We’ll need to publish it on the WordPress.org official directory once we feel it’s ready.

BP REST API

@espellcaste made great progress about the remaining endpoints of the BP REST API. There are now 3 more endpoints available for testing using the BP REST API Plugin :

BuddyPress Survey for 2019

@im4th suggested to carry on doing the survey @mercime used to do every year for a while now. The last one was done at the end of 2017 for 2018.

Next dev-chat

It will happen on October 30 at 18:00 UTC in #BuddyPress. Friendly reminder that we moved our dev-chat time to one hour earlier, 🙏 don’t miss it!

PS: if you have ideas or questions, feel free (and we are strongly encouraging you) to comment this summary to share them!

#5-0-0, #6-0-0

BudyPress 2.9.0 ‘La Lombarda’

We’re  happy to announce the launch & availability of it’s latest release 2.9 ‘La Lombarda’ available for download or updatable from your WordPress install plugin directory.

As always this release has been a huge team effort from both the core contributors and many new contributors with first time patches and we thank everyone for their time and effort put in to bring this release home.

I personally thank everyone for the support I’ve had as a first time release lead, an interesting experience. special thanks must go to @mercime for acting as release deputy, keeping the devchats abridged and posted on bpdevel and for the help on the first beta packaging run at an ungodly hour of the morning 🙂

A full changelog can be viewed here – Codex Changelog 2.9.0

Please report any issues to our Trac home

Happy updating!

hnla.

#2-9-0, #new-release