BP Dev-Chat Summary: May 6, 2020

• See previously BP Dev Chat summary (April 22, 2020)
• In attendance: @vapvarun @IAmTheWebb @mercime @dcavins @boonebgorges & @im4th
• Slack archive

Before discussing about the points on our agenda, @im4th explained why he quickly packaged a second Release Candidate on May 3rd. His goal was to early fix an issue about the BuddyPress build process regarding how JavaScript i18n strings can be identified by GlotPress on our WordPress.org plugin repository. The idea was to leave as much time as possible to Polyglots Contributors to help us make available our next major release in as much languages as possible.

BuddyPress 6.0.0 Hello & Credits Screens, & the 2020 survey

We’ve been discussing about an a11y issue @mercime raised into this comment. @im4th said he will look into it asap to try to fix it before 6.0.0 release. The improvements @dcavins (many thanks for your help) brought to the initial patch has been taken in account during the first commit about the Hello Screen. We will add the link to the 2020 survey at the last minute. @mercime already opened a ticket on Meta Trac to request for survey banners on our sites (BuddyPress.org, the Codex and the Developer Ressources site). @mercime (many thanks to you too!!) also committed to update the props of the Credits Screen for 6.0.0. The 2 last steps about props are to:

• include the Polyglots contributors to the Props list.
• introduce a new section “Noteworthy Contributors to 6.0.0” and do the required updates about the drop of the “Recent Rockstars” one.

About this new section @im4th suggested to add  @vapvarun @IAmTheWebb and @Passoniate to it and left “nomination” opened if other members of the team want to add other important contributors to 6.0.0.

Finally, we’ve listed the ultimate tasks to achieve before 6.0.0 release.

1. Fix last PHP 7.4 issues. Many thanks to @rayisme for dealing with it and fixing it 💪.
2. Update the 6.0.0 changelog.
3. Write the 6.0.0 announcement post.
4. Choose the Pizza name for this release (@im4th will reach out to team’s member privately in Slack to keep it secret until d-day!).

BP REST API Documentation updates

After @im4th‘s first pass about it less than 10 endpoints needed a review/update. He thinks it’s doable before the release date and since the dev-chat, it’s important to mention that @mercime has been doing an amazing job about it reviewing and updating 11 endpoints so far 👏🏆.

6.0.0 Final schedule

@im4th is confident we will be able to release it for May 14th. No blockers were raised during the meeting, so let’s do it !

Next dev chat

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

#6-0-0, #dev-chat

BP Dev Chat Summary: April 22, 2020

• See previously BP Dev Chat summary (April 8, 2020)
• In attendance: @vapvarun @IAmTheWebb @mercime @dcavins & @im4th
• Slack archive

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

BP Dev Chat Agenda for April 22, 2020

Hi!

Next dev-chat is scheduled today (April 22) 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-RC1 & 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, #dev-chat

BP Dev Chat summary: April 8, 2020

• See previously BP Dev Chat summary (March 25, 2020)
• In attendance: @mercime @boonebgorges @dcavins @johnjamesjacoby @espellcaste & @im4th
• Slack archive

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

BuddyPress 3.0 Dev Cycle

Paul Gibbs is Release Lead for BP 3.0

Paul (twitter) is a BuddyPress Lead Developer, Senior WordPress Engineer at Human Made, master of memes extraordinaire, and lives in the UK. His latest project is WordHat, a Behat extension. When not working, Paul enjoys playing video and board games, and luxury travel. You can also find him at byotos.com and at github.com.

Following are a few of his plans for this dev cycle.

Nouveau Template Pack

The items listed below need to be resolved before we ship bp-nouveau and BP 3.0:
1. Review all the superglobals and JSON handlers and nonces, for security.
2. Review all i18n strings.
3. Review of custom SQL.

BuddyPress.org Redesign

Paul is also reviving the development of the site’s redesign. If you’d like to participate, get in contact with Paul on our Slack. The current code is at https://gitlab.com/paulgibbs/bporg and there’s a staging site at http://dev-bporg.pantheonsite.io

Dev Chats

In lieu of the weekly dev chats in Slack, Paul would be using this site for async contribution updates and explore other avenues for developer chats like video hangouts, etc. Expect an announcement soon.

Schedule of Release

BP 3.0 is expected to be released early in the first quarter of 2018. We won’t be following the 3- to 4-month scheduling as in the past BuddyPress releases. BP 3.0 will be a focused release, specifically introducing the new Nouveau template pack along with other bug fixes and enhancements along the way.

BuddyPress Case Studies

Thanks to all who have shared their BuddyPress use cases with the community! The list of published articles this year are available in the BuddyPress Codex for your reference. If you’re interested in sharing your own BuddyPress use case, fill up this form and we’ll get back to you ASAP.

#3-0, #dev-chat

General Summary as of May 17, 2017

This post covers the BuddyPress Dev Chats for May 3, 10, and 17. Information has been updated to current status.

bp-nouveau

A friendly reminder from @hnla re testing and patches for bp-nouveau.

@hnla has committed styling updates, concentrated on some issue areas with what’s new update form and user screens, in particular messaging and the bulk action filters & search form elements, hacking away at the Backbone templates to bring the markup into line with the general selector and search form visual styles & updating the JS show/hide events to work with classes rather than jQuery .hide().

@hnla: “The what’s new form could still do with some further attention on the general show/hide nature of its control actions, I removed some earlier styles & tidied up the new autocomplete input where `post in groups` is selected, however we currently have no onBlur event to hide the controls so anyone that fancies delving into backbone could help out looking at what we could do to add some fun to the what’s new form. At this stage We have clean code supporting this feature, pretty much a blank canvas for playing around with effects that might look good rather than our rather staid `onfocus` open.”

@r-a-y reviewed bp-nouveau. Fixed issues for loading Ajax on component request and updated actions now they’re button elements, comments counts, notice errors, and set up the `buddypress-wrap` class dynamically.

@netweb has kept on top of the tooling for the project, updating the style-lint config modules, updating grunt file and fixed linting issues.

@mercime has been working on #130 where consensus during dev chat was to use option 2 for the implementation.

@dcavins was added to the sitewide notices ticket #137.

At this stage we need more devs taking tickets/project cards and moving into In Progress column.

Trac Tickets

Include BP Edit Group Slug into the core (#6014) @dcavins has committed patch to trunk.

Messages: member page messages are queried for the loggedin user (#7096) @dcavins has refreshed patch. @r-a-y and @Offereins have provided feedback.

Remove/Replace `title` attributes with Tooltips usable in all devices (#7188) @mercime has examples in ticket. The choice was the second example, though  @dcavins is making a case for the third example.

Only load component action and screen code when we’re on the component’s page (#7218) @r-a-y has patch.

Use JOIN rather than Subquery on user search (#7442) @brandonliles has patch. Needs dev feedback.

Resize member avatar error with cyrillic (not latin) filename (#7484) @r-a-y has patch which relies on newer PHP functions (v5.4). It’s either that or wait for WP core to fix #WP22363 #WP24661 #WP15955. Dev feedback requested.

bp_group_has_members performs unnecessary query (#7513) @r-a-y has patch. Dev feedback requested before committing.

BuddyPress Case Studies

Thanks to all who have shared their BuddyPress use cases with the community! The growing list of published articles are available in the BuddyPress Codex for your reference. If you’re interested in sharing your own BuddyPress use case, fill up this form and we’ll get back to you ASAP.

Slack logs:
May 3: https://wordpress.slack.com/archives/C02RQBYUG/p1493838015001913
May 10: https://wordpress.slack.com/archives/C02RQBYUG/p1494442868540761
May 17: https://wordpress.slack.com/archives/C02RQBYUG/p1495047787891614
(A WordPress Slack account is required to view the logs.)

#dev-chat

Dev Chat Summaries for April 19 & 26, 2017

BuddyPress 2.9

• June 7 – Beta 1
• June 14 – Beta 2
• June 28 – Release Candidate 1
• July 5 – BP 2.9.0 Release Date
• There are currently 45 tickets slated for this release (19 closed, 26 open).

bp-nouveau

@hnla updates:

• @mercime and I have been tackling various tasks including a11y aspects for form elements.
• Made adjustments to the message displays to improve those adding icons as separate child elements rather than hooking to the parent element to be able to hide using aria roles.
• New buddypress-wrap class added to the main wrapper so we don’t use the same class for body as we do the inner div.
• Improving the ease of updating search & filter wrapping elements extracting to one include file so we only need to work in three files for all elements.
• Created a new function to manage group descriptions excerpts to change $length values if the list display is set as grid boxes, which was required to effect an equal height-ish box.
• Improved group grid layouts to improve those for min-heights and general breakpoints.
• Refactored action elements in list layout views for better positioning & flow, removing absolute positioning in favor of stacking to the left on larger screens.
• General refining of elements such as title sizes, metadata, and displays. A little attention was given to single screen subnavs to try and define them better visually at small/mobile screen layouts.
• Travis CI is now up and running for bp-nouveau. Thanks @netweb. to the project

BP Trac Tickets

Only load component action and screen code when we’re on the component’s page (#7218) @r-a-y has refreshed patch. Requests opinion on the approaches taken before proceeding.

friends_add_friend() should convert accepted arguments (#7506) @r-a-y has committed fix to trunk.

Add identifying tag parameter to bp_has_*() loop arguments. (#7503) @dcavins requested dev feedback.

When user is not logged, if he/she clicks email link to view new messages gets 404 page when should get login page (#7349) @r-a-y has committed fixes for redirection issues and improving UX. Has refreshed patch after commits. Dev feedback requested.

Use stylelint to lint SCSS & CSS replacing Ruby Gem `scss_lint` (#7028) @hnla follows up with @netweb. We need to get this in early in dev cycle to test.

Move asset template parts away from bp-legacy (#7116) @r-a-y’s proposal only applies to core functionality like emails, embed, and attachments.

bp_group_has_members performs unnecessary query (#7513) @dcavins has patch for dev feedback.

JS Enqueued On Non-BuddyPress Admin Pages (#7512) @r-a-y has looked into issue posted by @kstover and requested more information since BP’s caret.js is enqueued correctly on admin pages.

Resize member avatar error with cyrillic (not latin) filename (#7484) @r-a-y has patch for dev feedback.

Fix for profile image upload on Microsoft Edge breaks iOS Safari and Chrome (#7416) @r-a-y has patch. Needs a Mac user to test.

Take advantage of BP_Groups_Group magic methods in groups component setup (#7416) @dcavins has patch. Ready to commit. Dev feedback requested.

BP_PHPMailer needs to set the `Date` header (#7509) @r-a-y has committed fix to trunk.

Test depends on PHP EXIF support; should fail more gracefully when absent (#7432) @r-a-y has committed fix to trunk.

{{user.site_url}} token not using HTTPS when site is on SSL (#7508) @r-a-y has committed fix to trunk.

BP Use Cases from BP Developers/Site Builders

@mercime announced that guest posts from BP Developers/Site Builders will be published soon at BuddyPress.org. The first batch of informative and interesting case studies have been submitted by developers who signed up during the BuddyPress 2016 Survey.

Slack logs:
April 19: https://wordpress.slack.com/archives/C02RQBYUG/p1492628459684302
April 26: https://wordpress.slack.com/archives/C02RQBYUG/p1493233250835528

#dev-chat