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

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

Carried over from the previous meetings #3389317: Differentiate visually dragging with and without hierarchy could still need some word smithing for two titles. and #3344498: Improve the manage form display page by untwining field widgets that belong to the main content and sidebar might be revisited. We've discussed it already in august, but i've stumbled across #3007167: [policy] Deprecate field_layout module and move it to contrib where the deprecation of the field layout experimental module is planned moving parts of it still into core #2844302: Move Field Layout data model and API directly into \Drupal\Core\Entity\EntityDisplayBase. Those parts that should go into core deal actually with the same problem underlaying problem space like the issue i wanted to revisit. having a coordinate approach would make sense from my perspective.

benjifisher credited shaal.

benjifisher’s picture

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

rkoller’s picture

rkoller’s picture

Issue summary: View changes
benjifisher’s picture

Issue summary: View changes
StatusFileSize
new58.51 KB
benjifisher’s picture

Issue summary: View changes
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

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

simohell’s picture