KDevelop Maintainership

[Andreas Pakulat]

On 20.08.08 14:17:14, Matt Rogers wrote:
> Obviously, I haven't had a whole lot of time to contribute to KDevelop  
> lately and so I'm removing myself from the maintainer role and  
> recommending that the group as a whole take over maintainership of the  
> various parts of KDevelop, which is basically what's been happening  
> for the last 6+ months anyways.

I've refrained from answering to this thread until now because I
couldn't really make up my mind.

First of all: Thanks Matt for your previous spare time and effort to
keep KDevelop alive and pull a really great KDevelop3.4 release back
then. I'd also like to thank you to literally push me into this project,
its been a great experience so far and got to meet quite some cool
people from all over the world :)

Now Aleix already proposed that I could be the new maintainer and I've
finally decided that I may be able to actually do that. Unfortunately
neither Amilcar nor Alexander (Dymo) have the time to do that job for
KDevelop4. I hope Amilcar can keep up with KDevelop3 as I'm going to
spend less time on that now that I started to use KDevelop4 even for my
every-day-job.

So unless somebody has objections, I'm going to apply for
release-coordinator for the kdevplatform and kdevelop module's. This
basically means that I'm the single-point-of-contact for anything
release-related. I don't think that part is going to be a lot different
from now as I already do most of the things (see
http://techbase.kde.org/Projects/Release_Team#Functions). I still want
us as a group to do the important decisions, release-schedule,
feature-list for a specific release and also to decide on the
longer-term-future of KDevelop4. However I reserve the "last word" on
any decision that we can't reach a concensus on or at least find a
majority for one side of the discussion.

So what do you guys think?

Andreas

-- 
Your true value depends entirely on what you are compared with.