Thank you Adrian by your help. I will look the links that you sent me and I will study very much the KDE for help in the developing.<br><br>My interesting are in programmin. I think start with "Junior Jobs" for learn more about developing of the KDE and after help in other thinks as in the developing of new features, projects etc.
<br><br><br> <br><br><div><span class="gmail_quote">On 5/5/06, <b class="gmail_sendername">Adriaan de Groot</b> <<a href="mailto:groot@kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">groot@kde.org
</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;">
[Cross-posting to the lists where these questions appeared *and* kde-devel for<br>general development information; CC'ed to the two original authors.]<br><br>Hi Anderson, hi Dino,<br><br>On Thursday 04 May 2006 19:48, Anderson Fonseca wrote:
<br>> my name is Anderson and I am new in the list.<br>> I would like help in the developing KDE, but I'm a little bit lost as start<br>> and where help.<br><br>On Thursday 04 May 2006 09:28, Dino wrote:<br>> I would like to contribute... in a variety of diffrent ways...
<br>> art, documents, and help files...<br><br><br>As others have already pointed out, two possible starting points are:<br><br><a href="http://quality.kde.org/develop/howto/howtohack.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://quality.kde.org/develop/howto/howtohack.php
</a><br><a href="http://www.kde.org/jobs/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.kde.org/jobs/</a><br><br><br>I recently wrote this to another person who was asking to help:<br>
<br> If you are interested in programming (really, KDE code is<br>
not rocket science; if you can write some basic C++ you<br> can get by; heck, we even *taught* a guy C++ while he<br> was adding email-validation functions to Kontact), then there<br> are "Junior Jobs" which are small bugs or little features that
<br> can be added fairly easily and where an application maintainer<br> has said he or she would be willing to do a little mentoring.<br> You can find the JJ's on <a href="http://bugs.kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
bugs.kde.org
</a> [1].<br><br> If you are interested in documenting things, then there are the<br> API documents [2] [3] which always need work. It can be useful<br> to read them and fix them up a little while learning to program.
<br><br> The websites are always looking for content and editors and<br> people who really want to get the message about KDE out.<br> For instance, <a href="http://Kontact.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Kontact.org</a> is rather lacking in user information;
<br> <a href="http://pim.kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">pim.kde.org</a> is the developer site and could use better links to<br> existing <a href="http://developer.kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
developer.kde.org</a> and <a href="http://quality.kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
quality.kde.org</a> information.<br><br> SpreadKDE.org has a task list and is a good place to start looking.<br><br> > It would be great if someone<br> > would be able to point in the general direction of what i could do to
<br> > start helping, or if someone needs help on something their working on.<br><br> General directions, see above. Specific things .. hm. I'm always<br> a little reluctant to give them because I would name things
<br> that *I* find interesting or useful; those are my itches,<br> not necessarily yours.<br><br> [1]<br><a href="http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=JJ%3A&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://bugs.kde.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=JJ%3A&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED</a><br> [2] <a href="http://developer.kde.org/documentation/library/3.5-api.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://developer.kde.org/documentation/library/3.5-api.php</a><br> [3] <a href="http://www.englishbreakfastnetwork.org/apidocs/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.englishbreakfastnetwork.org/apidocs/
</a><br><br><br>Of course, there are more ways to get involved. Documentation starts at
<br><a href="http://docs.kde.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://docs.kde.org/</a> for the user manuals. If you want to contribute to<br>those, you just write text (in plain english, no markup at all) and send it
<br>to the documentation team. If you want to help out on the documentation
<br>markup front, take a look at the EBN's Docs Sanitizer [4] which tells you<br>what's technically wrong with the documentation. For artwork, start at<br><a href="http://kde-artists.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
kde-artists.org</a>. So Dino needs to be over there; Anderson needs more
<br>coding-type contribution help. Is this enough?<br><br>[4] <a href="http://www.englishbreakfastnetwork.org/sanitizer/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.englishbreakfastnetwork.org/sanitizer/
</a><br><br>Another place to do development-type work is in the bugs database -- pick a
<br>bug, check if it still happens, comment on it. This might not be very much<br>*fun*, though, if your primary motivation is to create things.<br><br><br>One thing about KDE is that most contributors are pretty busy. It's hard to
<br>answer questions like "what should I do?" because then we need to take time<br>to think about what needs doing, consider persons abilities at various tasks,<br>plan, manage, etc. That's not what we really want to do. So instead of
<br>*asking* what to do, just *do* something! Nothing brightens my day -- and I<br>believe I can speak for many KDE developers -- more than a patch. It doesn't<br>need to be a technically perfect patch to the code, any document that carries
<br>the message "There was something wrong and I have fixed it, here's how:" is a<br>valuable one.<br><br>So, get out there, find something that "isn't quite right" and do something<br>about it.<br><br>
<br>[ade]<br><br>PS. We know that the getting started information is fragmented. Another good<br>job would be to hunt down all the different "getting started at coding" pages<br>and consolidate them (I'd say to
<a href="http://developer.kde.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">developer.kde.org</a>). Will Entriken started<br>recently:<br><br> So far I have found these sites explaining how to build and/or port to
<br> KDE trunk:<br> <a href="http://developer.kde.org/build/compile_cvs.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://developer.kde.org/build/compile_cvs.html</a><br> <a href="http://wiki.kde.org/tiki-index.php?page=KDE3To4" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://wiki.kde.org/tiki-index.php?page=KDE3To4
</a><br> <a href="http://edu.kde.org/development/port2kde4.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://edu.kde.org/development/port2kde4.php</a><br> <a href="http://quality.kde.org/develop/cvsguide/buildstep.php" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://quality.kde.org/develop/cvsguide/buildstep.php
</a><br><br>Will found the instructions from the edu site the most accurate -- but all
<br>this is for KDE4.<br><br><br>--<br>These are your friends - Adem<br> GPG: FEA2 A3FE Adriaan de Groot<br><br><br></blockquote></div><br>