I would also love to help by writing documentation/help and providing screenshots.. I sent an email to kde help but got no response..<br><br>Vignesh<br><br><div><span class="gmail_quote">On 5/19/06, <b class="gmail_sendername">
matt</b> <<a href="mailto:matt@cfxnetworks.com">matt@cfxnetworks.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, 18 May 2006 22:10:25 -0600<br> "Aaron J. Seigo" <<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>> wrote:<br>> there is always some degree of planning going on. i will<br>>caution that it is
<br>> pretty rare (though i have seen it happen) that someone<br>>who is brand new to<br>> the development side of the project is able to offer<br>>design considerations<br>> that are compatible with how things Work(tm) or that
<br>>haven't already been<br>> suggested (working from a common starting point: the<br>>current code base and<br>> the state of the art of the desktop in general) it's<br>>common to arrive at<br>> similar ends.
<br>><br>> that and due to the meritocratic way the project<br>>self-coordinates, it's often<br>> less than effective to attempt to influence through<br>>"design" without also<br>> attempting to work on the codebase, artwork,
<br>>documentation, etc... it's with<br>> contribution that one also finds the ability to<br>>influence the project<br>> design-wise. there have been exceptions, but i also<br>>don't want you to start<br>> with expectations that lead to you being frustrated =)
<br><br>Oh, I completely understand. It's not like I'm going to<br>come in and throw comments on a project that I know I<br>really don't understand. I've got a lot of work to do as<br>far as discovering how KDE really functions, and until
<br>then, I wouldn't feel right telling true KDE developers<br>"how it should be" whom actually know what they're doing.<br><br>> the best thing that someone new to the project can do is<br>>to gain a familiarity
<br>> with the code and the design. and the best way to do<br>>that is to start<br>> contributing in some small, even trivial, way. that is,<br>>in fact, exactly how<br>> i started: with a single patch to the run dialog that
<br>>fixed a rather trivial<br>> thing. it was by doing this that i gained an overview of<br>>how things work; and<br>> to be honest: i'm still learning =) that's probably in<br>>part what keeps me<br>> interested in this meta-project we call KDE ... well,
<br>>that and the awesome<br>> people and community around it, of course.<br><br>Definitely. I will definitely take it upon myself to start<br>tinkering with what is already present in the KDE<br>codebase, and hopefully I can submit some useful patches.
<br><br>> however you do decide to get involved is obviously up to<br>>you, but simply get<br>> involved. dive in, enjoy the water, it's warm. =)<br>><br>>> (I'd like to work on the Kaffeine project to give KDE
<br>>> 4 a decent video player).<br>><br>> they have a devel mailing list where you could start<br>>doing so ...<br><br>Will do. Thanks for your help, Aaron, and I'm glad to hear<br>that the KDE project is always open for new suggestions.
<br>_______________________________________________<br>kde-quality mailing list<br><a href="mailto:kde-quality@kde.org">kde-quality@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/kde-quality">https://mail.kde.org/mailman/listinfo/kde-quality
</a><br></blockquote></div><br>