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

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

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

We discussed the following issue:

  • TODO

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

rkoller’s picture

and another one raised by @smustgrave on the #ux channel yesterday:

#3471896: Inconsistent use of language regarding plugins

benjifisher’s picture

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

Issue summary: View changes

At today's meeting, we discussed the general issue of how to document decisions.

In particular, when someone opens an issue with a suggestion that has already been considered and rejected, we should close the issue (works as designed). When we do that, we should thank the person who opened the issue for contributing to the discussion. We should also give them a link to an ongoing discussion, if there is one, or to some documentation of the decision.

Typically, the decision is made in the comments on an issue that is now closed. Closed issues are pretty bad for discoverability.

One option is to use change records for these decisions. The Coding Standards group already does this: see https://www.drupal.org/list-changes/coding_standards.

Since we did not discuss any particular issues in detail, I am marking some of the standard "Remaining tasks" as complete.

benjifisher’s picture

Issue summary: View changes
StatusFileSize
new59.82 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.