JAN
2
2010

Ark Junior Jobs

So let's talk about what's going on in the Ark land.

Some time ago, Lydia blogged about raising the number of bug reports marked as junior jobs on Bugzilla. I've done my part, and currently there are 12 Ark bug reports listed as junior jobs.

If you have some (little) experience with C++ and Qt, fixing a junior job is a very good way to become part of the KDE community: junior jobs are usually easy to fix, you delve into the art of reading and understanding other people's code and, of course, you make KDE better with your contributions! What's more, you get the feeling that you're also part of our community.

Despite being about 12 years old, Ark, KDE's file archiver, does not have a huge code base, and it's fairly easy to understand its source. Most of the bugs marked as junior jobs involve writing support for more file formats (such as RPM), improving the error messages displayed to the user or implementing some easy wishlist items. But that's not all: as I write this blog post, there are 67 open Ark bug reports: only one of them is a more serious crash, and I'm sure there are many other report there which are not marked as junior jobs but are fairly easy to fix or implement.

Take a look at our bug reports, choose one or more you'd like to fix. You can then attach the patches to the reports themselves, mail them to the kde-utils-devel mailing list or send them directly to me. And remember that if you ever get in trouble, there's plenty of places you can look for help: TechBase, the API reference, LXR, the kde-devel mailing list or the #kde-devel IRC channel on Freenode.

Happy hacking! :)

Comments

I'm new in Qt/KDE development, been Java developer for some time, so I don't have a clue how the development of KDE applications goes, but I'm willing to fix a bug or to - that way I'll get myself into Qt better which is what I want. Any hints :) ?

The main questions I would want to know the answers are, which IDE to use for working on Ark, which version of KDE would I need (if there's a preferred one e.g. the latest stable, or the latest in development), and to test it, would the testing go through the IDE, or compiling through Terminal?

As for Arks CVS, the link is http://websvn.kde.org/trunk/KDE/kdeutils/ark/ right?

Thanks :)


By Martin Spasovski at Sun, 01/03/2010 - 00:02

Hi,

I don't use any IDE (just plain old vim on a terminal) and it is just a matter of taste - you could try (g)vim, Emacs, Qt Creator, KDevelop (maybe even Eclipse) and see what fits you best.

As for the KDE version used for development, you'll need trunk, which is our development branch. For more information on getting it running, see Techbase: http://techbase.kde.org/Getting_Started (you'll need at least kdelibs and kdebase besides Ark).

Good luck :)


By Raphael Kubo da Costa at Sat, 01/09/2010 - 00:48