getting involved

[Poletti, Don]

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Poletti, Don wrote:
>> What approach should I take? It seems that changing such a visible
>> UI component should have some consensus? I don't want to spend the
>> effort making the changes just to have them never incorporated.
>> However it seems that in most open source project until you code a
>> change you your opinions are not take seriously.
>
>Development issues are discussed on kde-devel at kde.org and usability 
>issues are discussed on kde-usability at kde.org. You should subscribe to 
>these lists and send your suggestions/questions there.
>
Actually I just gave one example. There are other issues as well, Are
you saying I should adress any particular issue to a more specific
e-mail list?

It wasn't clear from the web site if kde-devel or kde-core-devel
is better. I suspect I want kde-core-devel but the web site says
the list is read-only. I suspect just asking for write permission
would be turned down.

The question is realy what comes first the requirements (change suggestions
from users or otherwise) or code changes. According to all software
classes and I concur the requirements come first. However my expierence in
the open source community is the code has to come first. So should I go
to the dev list or the usablility list first.



>Regards,
>Ingo
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.0.7 (GNU/Linux)
>
>iD8DBQE8zswBqUQWN/hplRsRAscwAJ0RyfDHV86OR5oxPZxWh+/PeqPVAACfWRn6
>SW6cDDESrfEJZI7/Q3coTMM=
>=yvXt
>-----END PGP SIGNATURE-----
>
>___________________________________________________
>This message is from the kde mailing list.
>Account management:  http://mail.kde.org/mailman/listinfo/kde.
>Archives: http://lists.kde.org/.
>More info: http://www.kde.org/faq.html.
>
___________________________________________________
This message is from the kde mailing list.
Account management:  http://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.