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, @Mike Gifford (CivicActions), @Quynh, @yoroy, @EricRubino

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/S2oVmkWippQ

Rough transcript of this week's meeting: Drupal Usability Meeting - 2024-02-02.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.

rkoller’s picture

Moving over my suggestion from last week:

I would like to put three issues onto the list. first the issue i've also posted on slack #3389317: Differentiate visually dragging with and without hierarchy (about some word smithing of two titles). second in the context of the field ui i would like to bring up #3370326: Refine labels and descriptions for field types. i've created a google sheet a few weeks ago and revisited the issue starting to work on a draft as well as discussed the topic and got some feedback during the last two drupal dojos. And i wanted to revisit #3344498: Improve the manage form display page by untwining field widgets that belong to the main content and sidebar. We've discussed it already in august, but i've stumbled across #3007167: [policy] Deprecate field_layout module and move it to contrib and noticed that field layout is gonna be deprecated and that parts of it should still go into core #2844302: Move Field Layout data model and API directly into \Drupal\Core\Entity\EntityDisplayBase. that overlaps with the issue to revisit and i think it would make sense to have a coordinated approach.

rkoller’s picture

and @larowlan raised https://www.drupal.org/node/1562776 in the #ux channel

rkoller’s picture

Issue summary: View changes
rkoller’s picture

rkoller’s picture

benjifisher credited shaal.

benjifisher’s picture

Issue summary: View changes
StatusFileSize
new57.72 KB
benjifisher’s picture

Status: Active » Needs work
simohell’s picture

benjifisher’s picture

Issue summary: View changes
Status: Needs work » Fixed

@simohell:

Thanks. With that and the link to the recording that I am posting now, this issue is done.

Status: Fixed » Closed (fixed)

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

simohell’s picture