really you could just say if kde had no contact with distro's, such as not having a website or anyone who can clearly market kde. There wouldn't be much of a succesful kde as it attracts programmmers and users who help developers get it how the users want.
<br><br>It is like now for me testing something for a project i am doing, something could be really brilliant in design and how it has been done - but one simple or basic had put me off badly. <br><br>I may not be an expert on these matters but even if you didn't have the time to do anything for kde, at least you could do is download a demo disc and give it to a friend to try out.
<br><br>there's always something to do<br><br><div><span class="gmail_quote">On 22/02/06, <b class="gmail_sendername">Philip Rodrigues</b> <<a href="mailto:philip.rodrigues@chch.ox.ac.uk">philip.rodrigues@chch.ox.ac.uk
</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;">> Believe me, if I had the skills, I would absolutely LOVE to submit tons of
<br>> patches and code to KDE. But I'm no coder. But I try to help in other ways.<br>> And my help does not include patches. Does it mean that my help is less<br>> appreciated?<br><br>Well, Aaron answered this much better than I could, but I should just clarify
<br>that I didn't in any way mean to suggest that you can only contribute to KDE<br>by coding. I consider myself a "KDE contributor", and in the 5 or so years<br>I've been contributing, I've never written a line of code - many others are
<br>in the same position. The point I was trying to make is that *doing* is much<br>more valuable than *talking*. That "doing" need not necessarily be "writing<br>the code."<br><br>Here are some things off the top of my head that are valuable to KDE but
<br>aren't coding:<br>* Writing docs<br>* Writing whatsthis help<br>* Bug triage (*very* useful!)<br>* Writing promo articles<br>* Working on websites<br>* Translation<br>* Artwork<br>* User technical support<br>No doubt there are many things that I've missed out there, but that's a
<br>taster.<br><br>I'd also like to repeat what Aaron said about learning to code - none of the<br>KDE coders came out of the womb writing C++, they all learnt. That's not to<br>say that we all can, or should (I haven't), but if you want to contribute
<br>code, it doesn't become impossible just because you haven't spent the last 20<br>years learning the difference between <insert two complicated coding terms<br>here>.<br><br>I have some ideas about ways to help features get implemented/bugs get fixed
<br>without writing the code yourself, but I'll leave that for another message,<br>if anyone's interested.<br><br>Regards,<br>Philip<br>--<br>KDE Documentation Team: <a href="http://i18n.kde.org/doc">http://i18n.kde.org/doc
</a><br>KDE Documentation Online: <a href="http://docs.kde.org">http://docs.kde.org</a><br><br><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><br><br><br></blockquote></div><br>