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

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/mlNG4v3-6Ag

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

We discussed the following issue:

NR and RTBC issues marked Needs usability review.

CommentFileSizeAuthor
#6 Drupal Usability Meeting - 2023-03-31.txt57.89 KBbenjifisher

Comments

AaronMcHale created an issue. See original summary.

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 credited rkoller.

benjifisher credited simohell.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
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-03-31.txt57.89 KB
benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Issue summary: View changes
Related issues: +#2245767: Allow blocks to be configured to show/hide on 200/403/404 response pages

We discussed #2245767: Allow blocks to be configured to show/hide on 200/403/404 response pages. I am adding it as a related issue.

I previously added issue credits, a rough transcript, and a link to the recording.

To do: add a comment to the issue summarizing our recommendations.

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.

rkoller’s picture

rkoller
he/him
Primary language German
Location Nürnberg, Germany
commented

i have started going through the next batch of still open meeting issues. for this issue no comment was left but the issue in question was committed meanwhile. i've just quickly skimmed to the end of the video but it sounds like that we never explicitly agreed who comments on the issue or i have missed it. i can only vaguely remember the outline of the points we've raised back then and since there were definitely one or two reasonable points how about instead of commenting retroactively on the already closed issue perhaps look through the recording and open a follow up issue?

smustgrave’s picture

smustgrave commented
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

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