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

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

- David Horat の投稿
返信数: 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? 笑顔

Thanks
David Horat への返信

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

- Martin Dougiamas の投稿
画像 Core developers 画像 Documentation writers 画像 Moodle HQ 画像 Particularly helpful Moodlers 画像 Plugin developers 画像 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