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

List:       kde-pim
Subject:    Re: [Kde-pim] Report from KDE PIM BoF at aKademy in Dublin
From:       dcode <de.c0d3 () gmail ! com>
Date:       2006-09-27 14:16:35
Message-ID: 1bd56d3a0609270716g148dc103n7f1aff9559a7abf6 () mail ! gmail ! com
[Download RAW message or body]

I'm a developer that's new to KDE development.  I've tried to get
involved with KDE a couple of different times over the past year, but
the difficulty that I find is not being sure how to get my feet wet.
People in IRC tell me to find something that I like, and start working
on it.  I had a pretty lengthy conversation the other day with a
couple of members that suggested replacing deprecated code with the
newer API for KDE4.

> - Offer mentoring for new developers

I think this is a great idea.  This is the approach that we take with
new members to the robotics club at the university that I attend.  We
take younger, less experienced computer science students and introduce
them to the API that we use to control various subsystems.  Since we
are reworking a large part of the code base, we also ask the new
comers to give their ideas on the system by giving basically an
overview how they think the different systems should work together.
This possibly provides new approaches to solve the same problem, which
may be better than the current implementation.  At the same time,
while the ideas are being discussed, the new members gain a better
understanding of the current system.

Overall, I think the mentoring to a certain degree can help new
developers get their feet wet and also interact directly with people
that really know what's going on.  Once new developers understand how
things work, they'll produce more code and overcome the learning curve
faster.

Just my perspective,

--Derek Ditch

On 9/27/06, Cornelius Schumacher <schumacher@kde.org> wrote:
> We had an one hour BoF at aKademy yesterday and talked about some things.
>
> Volker and Tobias gave an overview about the status of Akonadi. We have
> something like a basic storage, the search providers are being designed. We
> are pretty short on developers, so progress is not as good as we would want
> it to be. There was a discussion about some technical questions. Will took
> some notes if I remember correctly. Attached is a list of some usage
> scenarios for Akonadi which were collected at the BoF.
>
> We also briefly talked about KitchenSync. There is a new release of OpenSync
> 0.19 which is able to sync KDE using the KDE frontend (which is KitchenSync).
> We should think about doing a release of KitchenSync fitting to the OpenSync
> 0.19. A first stable release is depending on the OpenSync schedule.
>
> Then we had a discussion about how to attract new developers. We collected a
> list of ideas how this could be done:
> - Blog about what's going on
> - Hype the hell out of the cool things we are doing
> - Spread positive feelings
> - Invite 10% newcomers to development meetings
> - Make talks in schools, colleges, etc.
> - Offer mentoring for new developers
> - Invite non-developers to meetings
> - Make sure there are up-to-date KDevelop project files
> - Do developer days and invite students to them.
>
> --
> Cornelius Schumacher <schumacher@kde.org>
>
>
> _______________________________________________
> kde-pim mailing list
> kde-pim@kde.org
> https://mail.kde.org/mailman/listinfo/kde-pim
> kde-pim home page at http://pim.kde.org/
>
>
>
_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]