SEP
2
2004

Junior Jobs: A Cool Way to Start Hacking KDE

Today on the kde-quality
list
, Christian Loose of Cervisia fame celebrated
the initial success of the Junior Jobs, which helped him get three patches. Junior
Jobs were suggested by
Adriaan de Groot back in May
. They serve as a "you are welcome to
hack here" sign, and mark bugs or wishes that are suitable for someone
who is starting to hack KDE.

As Christian puts it: "I started to mark some bugs as JJ some months
ago. Now I already received three high-quality patches from two
different people (Thanks Sergio and Dermot!) for those reports.
That's much more than I expected."

So, developers, remember to mark those easy bugs with a 'JJ'.
Some coaching for the new developers who accept the challenge would
represent a nice incentive as well.

Or, if you always wanted to develop KDE and never knew where to start,
check the open Junior
Jobs
out. I am sure you will find something fun to do!

Comments

And if, like me, you don't know how to code, tell your programming friends about the Junior Jobs list. Some of them might even get hooked on KDE-devel :)


By Mikhail Capone at Thu, 2004/09/02 - 5:00am

How can I mark a bug report as JJ? I already tried this but found no option on bugs.kde.org. Is it just adding a JJ: at the beginning of the bug title?

Sebastian


By Sebastian Stein at Thu, 2004/09/02 - 5:00am

> Is it just adding a JJ: at the beginning of the bug title?

Yes.


By Anonymous at Thu, 2004/09/02 - 5:00am

There is a "Junior Job" query at the start page of http://bugs.kde.org (for example if you want to test that you renamed the title of bug correctly.)

Have a nice day!


By Nicolas Goutte at Thu, 2004/09/02 - 5:00am

JJ is Joachim Jakobs, media guy of FSFE.

:-)


By Jan at Thu, 2004/09/02 - 5:00am

I'm interested in doing JJ's, but I don't know where to send the patches or code I'll write. Is it a public CVS so everyone can check out/in ??


By Uwe Liebrenz at Thu, 2004/09/02 - 5:00am

I think posting the patch as an attachment to the bugreport would work ok. Otherwise, send it to the maintainer(s) listed in the About box of the application.


By Andre Somers at Thu, 2004/09/02 - 5:00am

I had tried to make a tutorial on how to send patches:
http://developer.kde.org/documentation/misc/sendingpatches.php

For bug reports, the best is indeed to attach the patch to the bug report.

Have a nice day!


By Nicolas Goutte at Thu, 2004/09/02 - 5:00am