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:
@worldlinemine, @lauriii, @AaronMcHale, @anmolgoyal74, @Ravi, @shaal, @ckrina, @simohell, @Quynh, @yoroy, @Regu.pl

This list gets copied to the issue for the next meeting. If that has already happened, then go to that issue to add/remove yourself to/from the list.

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

Rough transcript of this week's meeting: Drupal Usability Meeting - 2025-10-17.txt

We discussed the following issue:

NR and RTBC issues marked Needs usability review.

The group is actively tracking progress on these issues:

Remaining tasks

  1. Add issue credits for the participants.
  2. Add the issue(s) we discussed to the issue summary and as related issues.
  3. Add a rough transcript.
  4. Add a link to the recording on YouTube.
  5. Comment on the issue(s) we discussed.

Comments

benjifisher created an issue. See original summary.

benjifisher’s picture

I plan to continue the discussion from the 2025-10-10 meeting. See the long comment there.

I suggested this on Slack, and @rkoller agreed. Let's get some other opinions before making this change.

Looking again at the telephone field, I think we should strike "Store" from

> Store a telephone number

But then we are left with just "a telephone number". Usually, if the description does not say any more than the label, it is best to leave the description off.

Perhaps we should say something like this instead:

> A telephone number, stored as a simple string.

That will clarify that Drupal does not store it as any sort of complex data structure. It does not store country code, area code, or anything else. That is kind of unfortunate, since it limits what you can control when displaying it.

benjifisher’s picture

Issue summary: View changes
Status: Active » Needs work
benjifisher’s picture

rkoller’s picture

Issue summary: View changes

commented on the issue: #3370326-92: Refine labels and descriptions for field types and also had the time to apply the changes we've discussed today. MR is updated and issue is NR.

benjifisher’s picture

Issue summary: View changes
StatusFileSize
new45.32 KB
rkoller’s picture

Issue summary: View changes
Status: Needs work » Fixed

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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

quietone’s picture

Issue tags: -Usabilty +Usability