BuddyPress 7.0.0: Call for Tickets

BuddyPress 6.0.0 was released on May 14, we did the 6.0.0 development cycle review during our latest “dev-chat”, today we’re inviting you to contribute to 7.0.0’s kick-off by replying to this call for tickets (just like WordPress does before each release).

The priorities of the BuddyPress community matter, please let us know what:

  • bug(s) you’d like to get fixed for 7.0.0?
  • improvement(s) you’d like to see in 7.0.0?
  • new feature(s) you’d like to see introduced in 7.0.0?

Share your wish-list!

To do so, you simply need to pick the ticket link(s) you think we should prioritize on from our code source management tool and paste them into this post’s comment form. If you’d like to, you can also share your ideas about the corresponding ticket(s). If some “already shared” tickets are also interesting you: use the ⭐️ Like feature to second them.

You need inspiration?

Here are some custom queries you can have a look on to get some! 🤔

PS: don’t hesitate to add a new ticket, if you haven’t found a match into the above queries 😉

PS2: Adding your ticket here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!

Deadline

This call for tickets will end on June 17, but we’ll begin discussing about what we’d like to see in BuddyPress 7.0.0 during our next dev-chat (June 3rd) : so the sooner you share your wish-list the better!

Thanks in advance for your help and let’s all wish a great 17th anniversary to WordPress 😍🎂

#7-0-0

BP Dev-Chat Summary: May 20, 2020

Results and Feedbacks about BuddyPress 6.0.0

6.0.0 was released on May 14. The first subject we’ve discussed about was checking for issues related to this release that may have been published into our support forums. @vapvarun has been very active on support forums lately and confirmed there wasn’t any topics specific to this release.

@im4th talked about statistics and more precisely about this release’s download pike. It was reached on May 15 with 28300 downloads: almost 5K more than the 5.0.0’s download pike.

@im4th congratulated all BuddyPress contributors who got involved into the 6.0.0 release and did a great work.

What we think went well during the 6.0.0 development cycle?

For @mercime we had more contributors, “Fast-and-furious commits” and we kept enough time for polyglots (2 weeks of string freeze) to let them contribute to the translation of the 6.0.0 release.

@dcavins was pleased by the activity & engagement of this release lead 😍.

@im4th was happy we could work on the priority we defined after the 5.0.0 release : work on getting more beta-testers to help us add the final touches to 6.0.0 : the BP Beta Tester plugin has been published on the WordPress.org Plugins directory and it does the job pretty well according to @dcavinsBP Beta Tester is fantastic“.

We also said we were happy:

  • We shipped BuddyPress 6.0.0 huge props to every contributor
  • We shipped the 2020 BP Survey (If you haven’t replied to it yet, do it right away!) Huge props to @mercime
  • We completed the BP REST API and updated the reference documentation. Huge props to @espellcaste and @mercime
  • We moved user profile photos & cover images from xProfile to Members, and so far: nothing broke! Self Props to @im4th 😉.
  • @mercime added: we introduced the 2 first BuddyPress blocks. Props to @karmatosed @espellcaste & @im4th
  • JavaScript translations are working!
  • We gave props to the 4 polyglots contributors who made the plugin available in French, Spanish (Costa Rica), English (UK) & Romanian as soon as the plugin was updated!

What we think should be improved during the 7.0.0 development cycle?

  • We haven’t managed to motivate Spanish, Portuguese, Italian, German, Dutch & Russian polyglots contributors. It’s really too bad BuddyPress is no fully translated into these languages.
  • We haven’t made progress on make.buddypress.org (@imath’s bad), we should try to set up this site to organize contributions and bring our development updates from this site to the BuddyPress.org network.
  • We haven’t moved any AJAX features to the BP REST API, we should try to benefit from the BP REST API (as soon as it’s possible) to improve the performance of the BuddyPress plugin.

PS: if you’d like to share your opinions about these two sections, you’re welcome to do so commenting this summary.

The 2020 BP Survey

@mercime gave us the very first learnings of this survey:

  • the majority of participants are using shared hosting and activate BuddyPress in their root WordPress sites.
  • Most are using the BP Nouveau Template pack.
  • Plugins and themes developer are testing BuddyPress with the latest stable BuddyPress release.
  • 60% of the contributors who are testing BuddyPress are using BP Beta Tester.
  • Most are checking the changelog to see what has evolved during the development cycle.

Of course these points are temporary results. We’ll be more specific as soon as the survey will be ended.

7.0.0 features wishlist

As we were running out of time @im4th suggested to publish a call for tickets on this blog, just like WordPress does on their Make WP/Core blog. We also agreed to think about it for the next 2 weeks and use our next development meeting to share our ideas. @IAmTheWebb suggested to organize a survey to “ask for feedback on features people would want“. @im4th thinks results of such survey are a bit difficult to use. We’ve experienced it for Blocks and we were not so convinced by the involvement it got. He also added he’s rather have something like “what feature do you want to contribute to for 7.0.0 release?“. We’ll test the call for tickets, it’s a good way to show how we are contributing to BuddyPress on our tool to manage the BuddyPress code source.

Next dev chat

It will happen on June 3rd 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!

Start picking the BuddyPress tickets, you’d like us to work on, we’ll soon publish the “BuddyPress 7.0.0 call for tickets” 😉

#6-0-0, #7-0-0, #survey

BP Dev Chat Agenda May 20, 2020

Hi!

Next dev-chat is scheduled this wednesday (May 20) at 19:00 UTC. As usual it will happen in #BuddyPress. Here’s our agenda:

  1. BuddyPress 6.0.0: first results and feedbacks.
  2. BuddyPress 2020 Survey
  3. 7.0.0 first feature ideas
  4. Open floor.

If you have anything you wish to add (or remove) to this agenda or specific items related to those listed above, please leave a comment below.

#6-0-0, #survey

BuddyPress 6.0.0

BuddyPress 6.0.0 is ready for download! > https://buddypress.org/2020/05/buddypress-6-0-0/

Many thanks to our 42 contributors, let’s upgrade to enjoy their great work 💪

#6-0-0, #release

BuddyPress 6.0.0 Release Candidate 2

Hello everyone,

BuddyPress 6.0.0-RC2 is ready for an ultimate round of tests! To know more about this second release candidate, you can read this post https://buddypress.org/2020/05/buddypress-6-0-0-release-candidate-2/

#6-0-0, #release

BP Dev Chat Agenda May 6, 2020

Hi!

Next dev-chat is scheduled today (May 6) at 19:00 UTC. As usual it will happen in #BuddyPress. Here’s our agenda:

  1. Hello screen & BuddyPress 2020 survey,
  2. BP REST API documentation updates,
  3. Discussions about 6.0.0 schedule,
  4. Open floor.

If you have anything you wish to add (or remove) to this agenda or specific items related to those listed above, please leave a comment below.

#6-0-0, #agenda

BP Dev Chat Summary: April 22, 2020

Hello screen & BuddyPress 2020 survey

The ticket for the Hello Screen has been created on Trac (#8270). @im4th started the meeting by asking feedbacks about it. @IAmTheWebb after a brain to html conversion of the patch thinks it looks good. A screenshot of the Hello Screen has been added to the ticket to ease this conversion 😅. @im4th also said there was a placeholder to insert the link to the BuddyPress Survey 2020.

@mercime volunteered to draft the 6.0.0 changelog 😍. She already prepared a first version of it using @rayisme‘s BP Changelog. Here’s the link to its preview if some of us wants to give a hand to fine tune it.

BP REST API documentation updates

@im4th shared the GH issue we can use to follow our progress about this task. He said he would take care of documenting the 6 new endpoints as the process to create new documentation pages using the BP REST API inline documentation is a pain to complete. He just finished adding these 6 new documentation page today (April 29). We still need to check all the other endpoints are up to date with latest BP REST API improvements.

Discussions about 6.0.0-RC1 & 6.0.0 schedule

At the time of the dev-chat there was 3 tickets in the milestone’s queue. As @IAmTheWebb noticed the ticket about the removal of the Legacy BuddyBar (#7729) was needing some extra time to be fixed during this release, so @im4th moved it to next major release. @im4th said he would take a deeper look to the ticket about the privacy data introduced in WP 5.4 (#8266). He did so 40 hours ago and decided to also move this ticket to next major release.

We agreed on a new schedule to leave 2 weeks between RC1 and final release so that translation contributors can help us making BuddyPress 6.0.0 available in as many language as possible. So here it is:

  • 6.0.0 RC1: April 29 (in a few hours 🏃‍♀️🏃‍♂️)
  • 6.0.0: May 14

Open floor

@im4th started by saying a big “TY” to @boonebgorges who packaged the 5.2 maintenance and security release the day before the dev-chat.

About #meta-5141 @mercime suggested to add a new page on BuddyPress.org to introduce our two documentation resources (The Codex & Developer site). @im4th agreed it was a great idea.

Next dev chat

It will happen on May 6 at 19:00 UTC (a 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

#6-0-0, #dev-chat