Introducing myself

[Michael Pyne]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 07 March 2004 03:00 pm, Alan Chandler wrote:
> Still, I have repartitioned the harddrive on my laptop, loaded up linux,
> and downloaded the source from arts, kdelibs and kdebase, and am ready to
> find some bugs to go chasing.  Any suggestions on where to start would be
> most welcome.

Among the other suggestions that you can find in the mailing list archives:

* Add WhatsThis help to applications.
* Convert applications to use .kcfg files for the new KConfig system.
* Test an application thouroughly, and report (or present patches) for not 
just bugs, but minor inconsistencies, layout quibbles, use of non-standard 
GUI elements for which a standard is defined, and the like.  The idea isn't 
just stability, but making the application as "nice" as possible.
* The amaroK project maintainer has asked for help: 
http://wiki.kdenews.org/tiki-index.php?page=amaroK
* KOffice could use a lot of help as well: 
http://www.koffice.org/developer/tasks
* Even compilation problems need to be reported, including configure flags 
that no longer work, or don't work as expected.
* Like you said, documentation is sorely lacking for a lot of applications, 
and those that do have documentation could use an update.
* Perhaps you could update an application that if suffering from bitrot?  From 
what I understand, kdeadmin has many.

Regards,
 - Michael Pyne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAS4Y/qjQYp5Omm0oRAg4WAKDh0vQt6J41gsG5FDgEMteWj3zhawCeOu/Q
+IGGW7J7G3OmzbS+AqwpCrQ=
=GC5p
-----END PGP SIGNATURE-----