This meeting takes place every Friday at 14:00 UTC (currently 7:00am PT, 10: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, @yoroy, @EricRubino
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/2bqTj97QiJ8
Rough transcript of this week's meeting: Drupal Usability Meeting - 2023-09-15.txt
We discussed the following issues:
- #463106: Improve search settings help text (recently fixed)
- #3379293: Make it easier to add a child menu item (recently fixed)
- #3381734: Locate drupalisms that might create confusion among users
- #2099099: Indicate maintenance mode status on database update page
NR and RTBC issues marked Needs usability review.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | Drupal Usability Meeting - 2023-09-15.txt | 45.43 KB | benjifisher |
Comments
Comment #2
rkoller@smustgrave brought up the following two issues on Slack: #3273173: Allow to JS-filter blocks in regions on the block layout administration page and #3325551: Add "Disable image resize" setting to image fields and @quiteone added a brief one with #2099099: Indicate maintenance mode status on database update page
Comment #3
benjifisherThe 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 #7
benjifisherI am adding issue credits and linking to the issues we discussed.
Comment #8
worldlinemine commentedSee this comment I left regarding today's discussion about gathering information on Drupalisms.
Comment #10
Comment #9
rkollerAdded a comment to #3381734-11: Locate drupalisms that might create confusion among users and updated the issue summary accordingly.
Comment #10
benjifisherI am adding a rough transcript and a link to the recording.
Comment #11
rkollerComments to both issues discussed listed in the issue summary were left in #8 and #9, a transcript was added in #10, and the link to the recording was added to the issue summary. So all necessary steps done.
Comment #13
rkollerBy accident I've set this issue to fixed prematurely. Since there were two comments about leaving comment on the issue I thought those were left on each of the issues we've discussed, but both were on the same issue. But left the missing comment on #2099099-52: Indicate maintenance mode status on database update page now.