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, @yoroy
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/KlRnwzXPfgg
Rough transcript of this week's meeting: Drupal Usability Meeting - 2023-05-05.txt
We discussed the following issues:
- #3358524: Users cannot log in if Password Compatibility module is not enabled (created after the meeting)
- #2921133: Remove "Please" from the codebase
NR and RTBC issues marked Needs usability review.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | Drupal Usability Meeting - 2023-05-05.txt | 51.28 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
benjifisherI would like to discuss the changes to password hashing in Drupal 10.1.0. I fear that some site owners will find themselves locked out of their sites.
From Slack (private channel):
References:
Comment #4
yoroy commentedComment #5
benjifisherFollow-up to #3: here is another scenario.
As a site admin, I check the available updates. I see that 10.1.0 has been released and I decide to upgrade the next day. I log out and get a good night's sleep.
The next day, I update the code and log in so that I can run updates ... except that my password is rejected.
Possible solutions:
$settings['update_free_access']insettings.php.Are there other options? How do we communicate them?
Comment #6
aaronmchaleAdded comment to #2921133: Remove "Please" from the codebase and referenced #2969406: Fix incorrect message after resetting password.
Need to add list of participants to the comment.
Comment #9
benjifisherI am adding a link to the recording and a rough transcript. I am also adding a link to #3358524: Users cannot log in if Password Compatibility module is not enabled, which I created after the meeting. I am adding credits to this issue.
We previously linked to the other issues we discussed, and AaronMcHale commented on those issues.
This issue is done.
Comment #11
aaronmchaleAdded participants list to comment on #2969406: Fix incorrect message after resetting password.