Usability: Should we create a "usability" component in Moodle Tracker?

Usability: Should we create a "usability" component in Moodle Tracker?

i le David Horat -
Number of replies: 3
I have discussed with Anthony Borrow the posibility of adding a "usability" component in the tracker. Since one my GSoC projects involves detecting usability problems, it would be a good idea to categorize it directly in the tracker as a usability problem. Do you folks think that it is a good or bad idea? Why? ata

Thanks
Average of ratings: -
In reply to David Horat

Re: Usability: Should we create a "usability" component in Moodle Tracker?

i le Martin Dougiamas -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers
Usability is hard to define as separate from other things, it's like having a component called "Typos" ... I view usability problems as bugs in that component, and likewise most bugs are usability problems in some way.

I'm not strongly against the existence of it as a second label, but I just predict that lots of bugs will be filed against that label only, meaning that the component maintainer who can really do something about it will not see it.

If you want to group the items from the GSOC project together you can add them as subtasks to an issue, similar to what we did for Accessibility for example: MDL-7396
Average of ratings: -
In reply to Martin Dougiamas

Re: Usability: Should we create a "usability" component in Moodle Tracker?

i le Martin Dougiamas -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers
I have created that component by the way. Just remember to include other components when you use it ata
Average of ratings: -