Future of KDE Development

[Aaron J. Seigo]

On Monday 14 February 2005 11:32, Aaron J. Seigo wrote:
> i'd like to see UI review become part of the standard operating procedures
> for apps in KDE4 that ship as part of KDE. if we can get the HIG completed
> and adopted by the time libs is ready for apps to be seriously ported to
> it, then we can do these things in tandem. i think this is doable.

seeing as there were no objections to this (or interest? ;) i'm going to 
extend this concept a bit further:

i'd really like to see that _any_ user-facing GUI that goes into the "KDE 
desktop" (konqueror, kicker, kdesktop, kwin, kcontrol; hrm.. what else?) get 
a UI review BEFORE being ok'd for inclusion in release. this would happen 
before, on or around the time of committing it. the review would include 
checking for HIG compliance and, time and resources permitting, a review by 
another KDE contributor for usability and accessibility concerns.

i'd also like to propose that we have another freeze period in the release. 
after feature freeze but before string and documentation freezes, it would be 
very nice to have a UI review freeze.

this release Waldo has been spearheading a review of kcontrol and i've been 
doing clean ups in konqueror, kfiledialog and kontact. these are made more 
difficult by the string freeze and are harder to do before the feature 
freeze. by having a recognized period of time for this it would also draw 
more attention and effort towards getting our GUIs clean and consistent.

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050215/82300175/attachment.sig>