Next dev-chat is scheduled to tomorrow: January 29 at 19:00 UTC. As usual it will happen in #BuddyPress. We will discuss about :
The BuddyPress 2020 survey,
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 🤗)
Progress about the 6.0.0 main features we agreed on last dev-chat,
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.
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.
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.
@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.
