[policy, no patch] Timeframe for tickets needing usability

There is a weekly usability meeting (Fridays at 14:00 UTC) held on Zoom. The purpose of the meeting is to handle issues that benefit from a synchronous discussion with several points of view. Typically, that meeting covers 2 issues per week: sometimes only 1, sometimes 3. The long-standing policy for the meeting is, "Agenda set by who shows up."

If the only way to get usability review were to discuss it at the weekly meeting, then only 1-3 issues would be resolved per week, and it would be impossible to say anything about how long it takes to get a review. So do not assume that getting a usability review is the same as being discussed at the weekly meeting.

Remember that there is no Usability initiative (neither a strategic initiative nor a community initiative). That means there is no initiative lead. However, usability is on of the core gates → , and there are 3 "Topic maintainers" for it: @bojhan, @ckrina, and @yoroy.

Personally, I have an interest in usability but no formal training and not much expertise. I have taken the role of moderating the weekly meeting. The meeting itself, with some preparation and follow-up, takes a few hours each week. I do not have the capacity to take a larger role.

Definitely appreciate taking on that role!

But not all users are on slack and not all users are able to attend a slack meeting. Not sure that should exclude their work or deprioritize it. If a ticket can sit in usability for indefinite amount of time. Should people be warned that a ticket probably won't make it before spending time on it. Should the ticket just be closed?

Just feel bad for users who work on a ticket, or show interest in it, put in some work but then it essentially gets stuck.

As a community that's seen a down trend in involvement think that having some policy to reference can better help prepare a ticket for usability and users know it will be looked at in a certain time period.

Once a policy is made think it should be posted as comments when issues are tagged for usability.

I believe this can be closed out.

Changing to latest version when this was fixed and updating credit.