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/qJwNgsk-7bg
Rough transcript of this week's meeting: Drupal Usability Meeting - 2023-03-24.txt
We discussed the following issues:
NR and RTBC issues marked Needs usability review.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | Drupal Usability Meeting - 2023-03-24.txt | 59.68 KB | benjifisher |
Comments
Comment #2
aaronmchaleThe group is actively tracking progress on:
Issues brought forward from the previous meeting:
In comment #109 the issue was marked as postponed for needing input from UX, accessibility and media initiative. Apparently there are some outstanding UX/accessibility questions (but I'm not sure what they are). This was echoed in comment #111.
Comment #144 is asking what is needed to move the issue along (the postponed state seems to be causing some delays/confusion as to how to proceed).
Perhaps we can at least take a look at what the issue is doing and provide some recommendations/guidance on how it could be implemented.
Comment #3
rkollerAbout 4 months back we've already briefly touched this issue when we ran into one out of the ten error messages in project browser when the user runs into a problem adding or installing a module #3319116: Drupal Usability Meeting 2022-11-11. Back then those messages weren't in shape yet and @benjifisher already left a few recommendations on the issue. over the course of the last few weeks there were several discussions and iterations. the messages are in better shape now and ready for review. Adding the issue #3323354: Review all pop-up messages shown by the Svelte UI installer for user friendliness to the queue.
Comment #4
benjifisherI would like to have a look at #2717319: Provide better default configuration when re-using an existing field. It was just Fixed, so no action needed (except perhaps to create a follow-up issue), but I would like to celebrate a little.
Comment #5
rkoller@smustgrave has already split out the changes for the block module into an individual issue based on the recommendation in #3345799: Drupal Usability Meeting 2023-03-10. it would be good to finish the review of the permission names for the block module we've skipped the last time #3347517: More granular permissions for block module
Comment #6
aaronmchaleAdded comment to #2989666: Update UI text regarding weight so it's consistent and more helpful to new users, need to add list of participants, will do that once this issue has been updated with the list.
Comment #10
benjifisherI am adding issue credits, a rough transcript, and links to the issues we discussed.
Todo: link to the recording; comment on the issues.
Comment #11
benjifisherI am adding a link to the recording.
Comment #12
aaronmchaleUpdated my comment with list of participants.
Comment #14
rkollerThe comment on the more granular permissions issue was still missing. I've left a comment in #3347517-3: More granular permissions for block module.Aaron left a comment on the other open issue and the reusing field issue got already merged. Since the link to the recording is in place as well as the transcript i'll set the issue to fixed.