[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-quality
Subject:    Re: Potential contributor :-)
From:       "Jos Poortvliet" <jos () mijnkamer ! nl>
Date:       2007-08-30 19:52:20
Message-ID: 5c77e14b0708301252r79d70b19s98cfc78268d5d359 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

[Attachment #4 (text/plain)]

On 8/30/07, inigo@imedina.info <inigo@imedina.info> wrote:
>
>
> Hi people,
>
> I would like to be contributor in Kontact. I like very much issues in
> relation to source development, bugs and so on.
> I would thank you any advice or guide.
>

I am no KDEPIM developer, but I can give you some general guidelines:
- start with techbase.kde.org and set up a development environment. See if
you can get the app running.
- Now there are two things you can do:
* run the apps, and see what you want to improve. Do it.
* look on the SVN server and on bugs.kde.org, there is often a 'junior jobs'
page or location with easy to do jobs.
Finally, send the patch here. You will get some response, ppl will probably
ask you to improve it, and finally someone will commit it in KDE. If you
sent some more patches and you improve your work, they will ask you to get a
SVN account and commit it all yourself. Or get one yourself on
http://techbase.kde.org/Contribute/Get_a_SVN_Account

More info on http://pim.kde.org/development/start.php

Have fun!

Regards
>
> iñ
>

grz
Jos

[Attachment #5 (text/html)]

On 8/30/07, <b class="gmail_sendername"><a \
href="mailto:inigo@imedina.info">inigo@imedina.info</a></b> &lt;<a \
href="mailto:inigo@imedina.info">inigo@imedina.info</a>&gt; wrote:<div><span \
class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <p><br>Hi \
people,</p><p>I would like to be contributor in Kontact. I like very much issues in \
relation to source development, bugs and so on.<br>I would thank you any advice or \
guide.</p></blockquote><div><br>I am no KDEPIM developer, but I can give you some \
general guidelines: <br>- start with <a \
href="http://techbase.kde.org">techbase.kde.org</a> and set up a development \
environment. See if you can get the app running.<br>- Now there are two things you \
can do:<br>* run the apps, and see what you want to improve. Do it. <br>* look on the \
SVN server and on <a href="http://bugs.kde.org">bugs.kde.org</a>, there is often a \
&#39;junior jobs&#39; page or location with easy to do jobs.<br>Finally, send the \
patch here. You will get some response, ppl will probably ask you to improve it, and \
finally someone will commit it in KDE. If you sent some more patches and you improve \
your work, they will ask you to get a SVN account and commit it all yourself. Or get \
one yourself on  <a href="http://techbase.kde.org/Contribute/Get_a_SVN_Account">http://techbase.kde.org/Contribute/Get_a_SVN_Account</a><br><br>More \
info on <a href="http://pim.kde.org/development/start.php">http://pim.kde.org/development/start.php
 </a><br><br>Have fun!<br></div><br><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;"><p>Regards&nbsp;</p><p>iñ&nbsp;</p></blockquote><div><br>grz<br>Jos \
 <br></div></div><br>



_______________________________________________
kde-quality mailing list
kde-quality@kde.org
https://mail.kde.org/mailman/listinfo/kde-quality


[prev in list] [next in list] [prev in thread] [next in thread]