BP Dev Chat Agenda for January 29, 2020

Hi!

Next dev-chat is scheduled to tomorrow: January 29 at 19:00 UTC. As usual it will happen in #BuddyPress. We will discuss about :

  1. The BuddyPress 2020 survey,
  2. First results about the doodle we organized to change the dev-chat day/time. (@espellcaste will share his preferences as soon as he’s back from his current afk status 🤗)
  3. Progress about the 6.0.0 main features we agreed on last dev-chat,
  4. Open floor.

Reminder, 6.0.0 schedule is:

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

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

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 Agenda for January 15

Hi!

Let’s meet for the first time of the year 2020 in #BuddyPress at 19:00 UTC on January 15 (today!!!) to discuss about :

  • The 6.0.0 main features,
  • The BuddyPress 2020 survey
  • Open floor.

FYI, during last dev chat we agreed on this schedule for 6.0.0 :

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

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

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 Agenda for December 18

Hi!

Let’s meet in #BuddyPress at 19:00 UTC on December 18 to discuss about :

  • The latest 5.1.0 release’s feedback,
  • The 6.0.0 development cycle’s schedule,
  • 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.

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

BP Dev Chat Summary: December 4, 2019

5.1.0

A maintenance release will be packaged at the beginning of next week (December 9).

BP Beta Tester

The first version of the plugin has been deployed on the WordPress.org repository. An announcement has been published on BuddyPress.org. A first issue has been raised and @im4th will work on fixing it asap. If you want to contribute to this plugin (you’re very welcome), please make sure to share your issues or pull requests into its GitHub repository.

BuddyPress blocks

The full results of the poll and information about the BP Blocks GitHub repository has been published on BuddyPress.org.

@im4th will work on preparing the data stores for the Groups and Members component and @karmatosed will soon share sketches to help us on the design part.

6.0.0 and up

Tickets needing feedbacks

Moving the BP Devel site (this site) to a new Make.BuddyPress.org site (see #5525). There’s now a test drive you can use to contribute to the BuddyPress contributor documentation or to review the developments made so far. You can read more about it from here.

@im4th insisted to have feedbacks about #8156: Move the Local Avatar and Cover Image features into the Members component. He’d like to early commit the changes and inform about them as there are some functions and hooks to deprecate. The good news is : there’s no need to edit existing templates.

@dcavins would be very happy to get feedbacks about #8139 and @espellcaste will work on #8173 during this development cycle.

A full featured standalone BuddyPress Theme

This is @johnjamesjacoby ‘s plan to improve our users experiences and captivate a new audience. It would be a 3-columns social layout theme (that’s become the obvious go-to for everything from Slack to VSCode).

the original “bp-sn-parent” theme, read more about it here.

In his opinion, the original “bp-sn-parent” theme was what originally attracted many folks to BuddyPress, 10 years ago. It was opinionated, design wise, pretty, and it showcased everything that it could do all at once.

As we are still shipping the BP Default theme and as we kept BuddyPress compatible with standalone BuddyPress themes, it should be easy to replace BP Default or give him a new neighbour into the bp-themes directory of the built BuddyPress.

Finally it could be developed from GitHub. @im4th & @vapvarun volunteered to give a hand. @johnjamesjacoby will soon write a ticket about it on BP Trac.

Next dev-chat

It will happen on December 18 at 19:00 UTC in #BuddyPress.

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

A new site for BuddyPress contributors

During our 5.0.0 development cycle we’ve been working on launching a new site for BuddyPress developers so that they can get help about using the BP REST API, for 6.0.0, I’m proposing to work on launching a specific site for BuddyPress contributors to help them get involved.

Migrating BP Devel to Make.BuddyPress.org

5 weeks ago, I’ve updated #5525-buddypress to inform about the plugins and themes we need to make it happen.

NB: as I’ve noted on the ticket’s comment, we would also need to migrate the BP Devel blog’s subscriptions using the JetPack tool.

Today, I’m informing you I’ve put up a testing site to help us see how it could look, behave and I hope help us start writing a BuddyPress contributors handbook.

BuddyPress contributors handbook

I know that contributing to BuddyPress is very similar to contributing to WordPress and that Make.WordPress.org core’s handbook is a great resource we could use to explain how to report a bug, test a patch, write a patch, etc..

I believe we need more than a link to this tool, I believe we need to get inspired by it to write our very own handbook with command/code examples specific to BuddyPress. For example: we could have a page with detailed step to checkout BuddyPress trunk from SVN like this one.

I’m pretty sure this handbook would greatly help new contributors to get started.

Let’s do it!

If you tried to click on the test drive link, you’ve seen you need to log in to access to it. I think, to avoid confusions with BP Devel or the possible/future Make.BuddyPress.org sites it’s best to restrict its access.

If you want to contribute to the making of this site by testing it or by writing one or more pages of the BuddyPress contributors handbook, you just need to send me a direct message on Slack (@imath) or simply use the form below to send it to me by email. I’ll be very happy to give you an access to it with writing capabilities.

Thanks in advance for your help and interest.

#5525, #6-0-0