We have a 'usability' component on drupal project issue queue: http://drupal.org/project/issues?projects=3060&components=usability&stat...

How to make sure that

1) issue submitters know when mark items as 'usability'
(there are always be edge cases -- is evey UI-affecting patch is a
usability patch or not? Is copywriting usability or UI string?)

2) kludgy polluting of issue namespace with "Usability: " finally ends

3) old usability issues will be correctly marked?

Background:
http://groups.drupal.org/node/12972#comment-41948
http://lists.drupal.org/pipermail/development/2008-July/030446.html

Comments

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Project: Drupal.org infrastructure » Drupal.org site moderators

This is probably better off in the documentation queue.

Also does anyone know when this was added? I only spotted it the other day and it doesn't seem to have been announced anywhere (other this issue and kika's development list post).

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Project: Drupal.org site moderators » Drupal.org infrastructure

Just saw killes' post on the devel list, back to infrastructure.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented

I added this after an IRC discussion a few months back... thought I posted to the webmasters queue, but I searched and guess not. :( My bad. :(

kika’s picture

kika CreditAttribution: kika commented

...and how this is related to User Experience 'project' http://drupal.org/project/issues/user_experience ?
All we need is a single simple marker to filter issues.

(Tagging UI/UX/usability issues have historically been Um Grande Confução :)

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
CreditAttribution: webchick commented

The problem with the "User experience" project is that maybe 20 people look at that. About 2,000 people look at Drupal core, and if user experience bugs are filed under the correct project, then the people who actually develop on those projects will see them.

I would actually advocate removing the "User experience" project.

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented

+1 for removing "user experience" as a project. I doubt even 20 people look at it.

kika’s picture

kika CreditAttribution: kika commented

Still I keep looking at d.o issue queue and a LOT of stuff can easily marked as 'usability' component. But I do not have a hearth to do that since I feel important metadata (eg "forms", "installer" are lost this way). Usability should imho be a attribute in a different axis. How far is the issue freetagging feature and can it help us?

aclight’s picture

aclight CreditAttribution: aclight commented

unfortunately, work on comment_alter_taxonomy, my module that was written with the idea of allowing issue free tagging, is on hold until the D6 port of project* is finished. I do think that issue free tagging would be useful in this situation, however.

eliza411’s picture

eliza411 CreditAttribution: eliza411 commented
Status: Active » Closed (fixed)

Closing since issues have free tagging. Please re-open if needed.