Difference between revisions of "Get Involved/Quality"

Jump to: navigation, search
(moved user interface section to http://techbase.kde.org/Contribute)
Line 7: Line 7:
  
 
There is no active KDE quality team, but if you are interested in contributing improvements to KDE, you will be well received at [irc://irc.kde.org/kde-devel <nowiki>#kde-devel</nowiki>] on irc.freenode.net.
 
There is no active KDE quality team, but if you are interested in contributing improvements to KDE, you will be well received at [irc://irc.kde.org/kde-devel <nowiki>#kde-devel</nowiki>] on irc.freenode.net.
 
== User Interface ==
 
 
User interface is a very wide subject, and very subjective too, as something obvious to someone is absurd to others and vice versa. Therefore, don't assume, argue clearly, stating your logical steps. Your main tool discussing it are objective reasoning and good sense.
 
 
It is easy to perform a quick user interface analysis, but it is hard to convince people to change the interface. A good, convincing analysis can gain much if it incorporates information from the KDE guidelines, competing program and operational system analysis, general design principles found in many books, user testing or individual (anecdotal) feedback. It is a volunteer project, and even if everybody agree with you, someone has to implement it.
 
 
The [http://mail.kde.org/mailman/listinfo/kde-usability KDE Usability Mailing List] is very active and a good place for discussing your ideas, and their homepage is at http://techbase.kde.org/Projects/Usability. If you are already an usability expert, please check [http://www.openusability.org/ OpenUsability.org], a project that brings open source developers and usability experts together, and is collaborating closely with KDE.
 
 
Some documents guiding documents include the [http://developer.kde.org/documentation/standards/kde/style/basics/index.html  KDE User Interface Guidelines (design standards)] and [http://developer.kde.org/documentation/design/ui/index.html KDE User Interface Guidelines (design principles)].
 
 
Some projects for analysis of user interfaces may include: checking that shortcut keys are coherent across KDE applications, making sure that dialogs are directly relevant to the interaction that the user would expect, and finding users of KDE software to see how they perform common workflows.
 

Revision as of 16:50, 5 April 2012

Becoming a KDE Tester

Testing

In the early 2000's there was a specific team at KDE which was focused on finding loose ends in KDE applications and tying them together. This was a task of user case studies, writing articles, documentation, creating missing artwork for consistency, and other miscellanea. Ultimately, this team contributed patches of code and documentation that really rounded out the KDE experience.

Communicating with the team

There is no active KDE quality team, but if you are interested in contributing improvements to KDE, you will be well received at #kde-devel on irc.freenode.net.


Content is available under Creative Commons License SA 4.0 unless otherwise noted.