This meeting takes place every Friday at 14:00 UTC (currently 6:00am PT, 9:00am ET). See Time.is to see what that is in your timezone.

The meetings are held using Zoom, and a link is posted in the #ux Slack channel 10 minutes before the meeting. Agenda is first come, first serve and set by attendees. Use the Needs usability review issue tag for issues that need review and/or suggest issues in comments here.

List of Slack users to ping 10 minutes before the meeting:
@Gábor Hojtsy (he/him), @worldlinemine, @lauriii, @AaronMcHale, @anmolgoyal74, @Antoniya, @Ravi, @shaal, @ckrina, @simohell, @gauravvv, @penyaskito, @Mike Gifford (CivicActions), @April, @Quynh/Quinn

Go to the issue for the next meeting to add/remove yourself to/from the list.

Recording of this week's meeting: https://youtu.be/veucENc_MfU

Rough transcript of this week's meeting: Drupal Usability Meeting - 2023-04-21.txt

We discussed the following issue:

NR and RTBC issues marked Needs usability review.

CommentFileSizeAuthor
#6 Drupal Usability Meeting - 2023-04-21.txt58.9 KBbenjifisher

Comments

benjifisher created an issue. See original summary.

aaronmchale’s picture

aaronmchale
Primary language English
Location Edinburgh, Scotland
commented

Just tagged #2881892: UX: Hide entity ID in autocomplete widget for review, coudd be an interesting one to discuss, I can see a rational for making this change.

aaronmchale’s picture

aaronmchale
Primary language English
Location Edinburgh, Scotland
commented

I think we should prioritise discussing #3153092: Set Block Category to Bundle in block_content module.

At #3352906: Drupal Usability Meeting 2023-04-14, we discussed #3318549: Rename Custom Block terminology in the admin UI and recommended changing the content block category from "Custom" to "Content block". The fact that the block placement list uses the word "categories" to group blocks was part of our rational for recommending that we simply use "block types" to describe the block content module's block types, and that the term "categories" on the block placement listing and that all content blocks are grouped under a single category, creates enough of a distinction between content blocks and blocks which are provided by code and config.

I don't disagree with the changes the issue is proposing, showing which type a content block is part of I'm sure is a good thing; But if #3153092: Set Block Category to Bundle in block_content module were committed it would make that distinction less clear and blur the lines, where block types would be mixed in with other categories.

rkoller’s picture

rkoller
he/him
Primary language German
Location Nürnberg, Germany
commented
Issue summary: View changes
aaronmchale’s picture

aaronmchale
Primary language English
Location Edinburgh, Scotland
commented

The group is actively tracking progress on:

Issues brought forward from the previous meeting:

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Issue summary: View changes
Status: Active » Needs work
StatusFileSize
new Drupal Usability Meeting - 2023-04-21.txt58.9 KB

benjifisher credited ckrina.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Related issues: +#3153092: Set Block Category to Bundle in block_content module

I am adding issue credits. Previously, we added a rough transcript and links to the issue we discussed and the recording.

We still need to comment on the issue we discussed.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.