This meeting takes place every Friday at 10:00am ET (7:00am PT, currently 15:00 UTC). 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.

ping:
@Gábor Hojtsy (he/him), @worldlinemine, @lauriii, @Aaron McHale, @anmolgoyal74, @Antoniya, @Ravi, @shaal
Go to the issue of the next meeting to add/remove yourself to/from the list.

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

Transcript of this week's meeting: Drupal Usability Meeting - 2022-02-25.txt

We discussed the following issues:

NR and RTBC issues marked Needs usability review.

Comments

benjifisher created an issue. See original summary.

benjifisher’s picture

dww’s picture

dww’s picture

Also, there's a cluster of issues about obsolete extensions that might want a look:
#3258782: Do not display obsolete modules at admin/modules
#3266397: Highlight non-stable modules on the admin/modules/uninstall form
#3266308: %extensions placeholder not extension names printed on the Status report warning about obsolete extensions
#3266449: Add a link to the Status report warning about obsolete extensions so site owners can fix the problem

If you have an obsolete module installed, the status report currently has a warning that says:

Obsolete extensions found: %extensions. Obsolete extensions are provided only so that they can be uninstalled cleanly. You should immediately uninstall these extensions since they may be removed in a future release.

I've proposed that the words "uninstall these extensions" becomes a link to /admin/modules/uninstall so there's an action site owners can take to fix it. That's in #3266449.

It'd be great to get the UX team's perspective on the end goal, regardless of exactly which issues end up implementing which parts:

  1. Status report warning includes a link as the call to action on how to fix itself.
  2. The link brings you to the Uninstall form where the obsolete modules are clearly marked as such.
  3. Should the uninstall form be grouped by module lifecycle instead of the current giant flat table?

Thanks!
-Derek

ckrina’s picture

I'd like to discuss an idea to create an initiative or list of small improvements we can add to form to help site builders stay more informed.

benjifisher credited shaal.

benjifisher’s picture

I am adding issue credit for the participants.

benjifisher’s picture

I am adding links to the issues we discussed and updating the issue description.

I think that leaves just a link to the recording.

benjifisher’s picture

StatusFileSize
new54.54 KB

I am uploading a rough transcript of the meeting.

The transcript is generated by Zoom, using a voice-to-text algorithm. Thanks to @rkoller for pointing me to the documentation on how to enable it: https://support.zoom.us/hc/en-us/articles/115004794983-Audio-transcripti...

Zoom provides timestamps correlated with the original recording, and the file has the extension .vtt. I trim the beginning of both the transcript and the video, but the timestamps might still be useful.

benjifisher’s picture

Issue summary: View changes
Status: Needs work » Active

I may as well add the transcript link to the issue summary.

benjifisher’s picture

Issue summary: View changes

typo fix

benjifisher’s picture

Issue summary: View changes
Status: Active » Fixed

Oops, I accidentally set the issue status to Active in a previous comment.

I am adding a link to the recording, so the change to Fixed is not accidental.

Status: Fixed » Closed (fixed)

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