This is a multi-part message in MIME format. --===============0771246643303770250== Content-Type: multipart/alternative; boundary="nextPart10951270.9uaPXyMiir" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart10951270.9uaPXyMiir Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Hello, Regarding the software to use, KDE uses Git and CMake. These are pretty= much the (new) only things that you need. For editing code you can use= any text editor or IDE you prefer. You need to get familiar with kdelibs and how a KDE project is structur= ed. The best way to do this is to choose a bug from a project of your l= iking and try to fix it. http://bugs.kde.org[1] Look for junior jobs at first.=20 https://bugs.kde.org/buglist.cgi?keywords=3Djunior-jobs&bug_status=3DUN= CONFIRMED&bug_status=3DCONFIRMED&bug_status=3DASSIGNED&bug_status=3DREO= PENED&list_id=3D758623[2]=20 Then submit the patches to the review board: https://git.reviewboard.kd= e.org[3]=20 Also on IRC #kde and #kde-devel is a good place to ask questions. The p= roject you choose might also have it's own IRC channel. I hope this will be helpful. P.S. It's motivating to fix a bug that bugs you. --=20 *Ovidiu-Florin Bogdan* GeekAliens.com[4]=20 Kubuntu Rom=E2nia[5]=20 =CEn ziua de Wednesday 18 December 2013, la 22:34:03, Myriam Schweingru= ber a scris: > FYI, I think this is better suited for the developer mailing list > instead of the user support list :) >=20 >=20 > ---------- Forwarded message ---------- > From: Cruceru Calin > Date: Tue, Dec 17, 2013 at 11:20 PM > Subject: [kde] Getting started > To: kde@mail.kde.org >=20 >=20 > Hello, >=20 > I heard from a friend about KDE and since I have knowledge about C++,= > which is the main used programming language ( from what i heard and > read ), I decided to get involved and find out more about KDE. >=20 > I have already read almost everything from the Getinginvolved website= > but as it is mentioned at some point, getting started may be pretty > hard, so I need assistance. >=20 > Firstly, I need to know more about what software I need in order to > start repairing bugs and working in a KDE environment and then, how > exactly I do this. I found the list with the junior-jobs but I cannot= > find any source code there, so I'm a little bit confused. >=20 > I'm waiting for your explanations! > Thank you! >=20 > Cruceru Calin-Cristian, > University Politehnica from Bucharest >=20 > ___________________________________________________ > This message is from the kde mailing list. > Account management: https://mail.kde.org/mailman/listinfo/kde. > Archives: http://lists.kde.org/. > More info: http://www.kde.org/faq.html. >=20 >=20 > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsu= bscribe << -------- [1] http://bugs.kde.org [2] https://bugs.kde.org/buglist.cgi?keywords=3Djunior-jobs&bug_status=3D= UNCONFIRMED&bug_status=3DCONFIRMED&bug_status=3DASSIGNED&bug_status=3DR= EOPENED&list_id=3D758623 [3] https://git.reviewboard.kde.org [4] http://geekaliens.com [5] http://ro.kubuntu.org --nextPart10951270.9uaPXyMiir Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1"

Hel= lo,

 

Reg= arding the software to use, KDE uses Git and CMake. These are pretty mu= ch the (new) only things that you need. For editing code you can use an= y text editor or IDE you prefer.

You= need to get familiar with kdelibs and how a KDE project is structured.= The best way to do this is to choose a bug from a project of your liki= ng and try to fix it. http://bugs.kde.org

 

Loo= k for junior jobs at first.

https://bugs.kde.org/buglist.c= gi?keywords=3Djunior-jobs&bug_status=3DUNCONFIRMED&bug_status=3D= CONFIRMED&bug_status=3DASSIGNED&bug_status=3DREOPENED&list_= id=3D758623

 

The= n submit the patches to the review board: https://git.reviewboard.kde.org

 

Als= o on IRC #kde and #kde-devel is a good place to ask questions. The proj= ect you choose might also have it's own IRC channel.

 

I h= ope this will be helpful.

 

P.S= . It's motivating to fix a bug that bugs you.

 

-- =

Ovidiu-Florin Bogdan

GeekAliens.com

Kubuntu Rom=E2nia

 

=CE= n ziua de Wednesday 18 December 2013, la 22:34:03, Myriam Schweingruber= a scris:

>= ; FYI, I think this is better suited for the developer mailing list

=

>= ; instead of the user support list :)

>= ;

>= ;

>= ; ---------- Forwarded message ----------

>= ; From: Cruceru Calin <crucerucalincristian@gmail.com>

>= ; Date: Tue, Dec 17, 2013 at 11:20 PM

>= ; Subject: [kde] Getting started

>= ; To: kde@mail.kde.org

>= ;

>= ;

>= ; Hello,

>= ;

>= ; I heard from a friend about KDE and since I have knowledge about C++,=

>= ; which is the main used programming language ( from what i heard and

>= ; read ), I decided to get involved and find out more about KDE.

>= ;

>= ; I have already read almost everything from the Getinginvolved website=

>= ; but as it is mentioned at some point, getting started may be pretty

>= ; hard, so I need assistance.

>= ;

>= ; Firstly, I need to know more about what software I need in order to

>= ; start repairing bugs and working in a KDE environment and then, how

>= ; exactly I do this. I found the list with the junior-jobs but I cannot=

>= ; find any source code there, so I'm a little bit confused.

>= ;

>= ; I'm waiting for your explanations!

>= ; Thank you!

>= ;

>= ; Cruceru Calin-Cristian,

>= ; University Politehnica from Bucharest

>= ;

>= ; ___________________________________________________

>= ; This message is from the kde mailing list.

>= ; Account management: https://mail.kde.org/mailman/listinfo/kde.

>= ; Archives: http://lists.kde.org/.

>= ; More info: http://www.kde.org/faq.html.

>= ;

>= ;

>= ; >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub t= o unsubscribe <<

--nextPart10951270.9uaPXyMiir-- --===============0771246643303770250== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << --===============0771246643303770250==--