Hi,

I'm keen to do some development work for KDE. At the moment there must be a ton of things to do to get the core KDE programs ported and debugged as well as respond to early feedback. Is there some place I can go to find a prioritised list of tasks?

Thanks.

Hmmm... posted a little too quickly. I like how organised KDE appears to be http://www.kde.org/getinvolved/development/

Hi, these are also some links to start:

http://techbase.kde.org/Schedules/KDE4/4.2_Feature_Plan
http://techbase.kde.org/Contribute

You should not add new features to the 4.2 feature plan, b/c it is soft feature freeze. This means, that for version 4.2 the developers concentrate on implementing and fixing the issues on the list.

Cheers, m.

If you're interested in Plasma, check this page:
http://techbase.kde.org/Projects/Plasma/Tasks

You might want to ask on #plasma@freenode if the list is still valid.

Thanks,

Today I'll be happy to get my machine to the point where I can start KDE hacking (svn checkout etc). I think I will start by looking at the jobs and bug lists as I still have a bit of learning to do regarding KDE development. Implementing and fixing sounds like a good way to do this.

Here's hoping I can contribute something useful in my (limited) spare time

One thing... I'm currently using kubuntu (actually I installed from an ubuntu cd, then installed kubuntu on top and subsequently upgraded to 8.10)

1. In this distro you can install the package kdesdk which gets you the scripts and misc tools

2. The instructions on the kde "Getting Started/Build/KDE4/Kubuntu and Debian" page only talk about Kubuntu 7.10 (Gutsy) and Debian (Testing/Unstable) so they are perhaps a year old... I'm following them anyway. So far no complaints about package names (however I have only installed the "required" packages). These instructions are a little confusing to read as there seem to be two sets of instructions for fetching the same set of packages. I used the first instructions (top of page) but after reading the whole page wasn't sure this was the best choice... still not.

3. the "Getting Started/Build/KDE4" page says
svn checkout svn://anonsvn.kde.org/home/kde/branches/KDE/4.0/kdelibs
Hmmm time for a version bump... or to put a link in the repo for "stable"


4. Can anyone tell me what impact the following instructions might have on the deb package management?

cs # Note: cs is not a typo.
svn checkout svn://anonsvn.kde.org/home/kde/trunk/qt-copy
cd qt-copy
./apply_patches
cb # Build Qt in a separate build directory
../../src/qt-copy/configure -prefix $QTDIR
make -j2 # use 'make -j(X+1)' where X is your number of processors, to compile faster
# if we don't install, we'll just clear obj files to
# save disk space
if [ "$QTDIR" = "`pwd`" ]; then
find . -name '*.o' -delete ;
else make install; fi;

Hi, have a look at http://techbase.kde.org/Getting_Started/Build/kdesvn-build

This is a more easy to start.

Cheers, m.

msoeken wrote:Hi, have a look at http://techbase.kde.org/Getting_Started/Build/kdesvn-build

Gah! you are so right... As I was enduring the endless svn checkout I was thinking how much easier it would be to have a tar ball that could be updated.

Unfortunately this useful advice came a little late for me as I only had the weekend

Where I got to...
- created a new account for development
- installed kubuntu package kdesdk
- installed required kubuntu packages
-- seemeed to also require the automoc package which was not included on the list
- svn co'd kdelibs kdebase kdepimlibs kdesupport and qt-copy
- started build for qt-copy

FWIW, ./apply patches failed:
1 out of 1 hunk ignored
Patch 0255-qtreeview-selection-columns-hidden.diff failed!

I applied this patch manually

also the instructions on http://techbase.kde.org/Getting_Started ... and_Debian contain instructions for building qt-copy that don't work:

kdev@acer:~/kde/build/qt-copy$ ../../src/qt-copy/configure -qt-gif -debug -fast -system-libpng -system-libjpeg -system-zlib -dbus -webkit -nomake examples -nomake demos -prefix $QTDIR

This is the Qt/X11 Open Source Edition.

You cannot make a shadow build from a source tree containing a previous build.
Cannot proceed.

So I am building in-place (you have to install anyway)... in answer to my own last question the install of qt-copy has no effect on installed qt because the recommended shell environment sets QTDIR to ~/qt-copy