Laying down the maintainer-hat

[Niko Sams]

On Sat, Apr 10, 2010 at 11:33, Esben Mose Hansen <kde at mosehansen.dk> wrote:
> On Saturday 10 April 2010 10:50:58 Andreas Pakulat wrote:
>> Well, my experience with KDevelop is that the "steering the development
>> into the right direction" part is not really needed. The team is pretty
>> much clear on what we want and how to achieve it. So it basically boils
>> down to things like proposing release plans or at least dates for the
>> next beta and then taking care of actually doing it (in time, which is
>> one part I really suck at due to not having any kind of calendar app).
>> That includes taking care of the version, tagging it, tarballing and
>> uploading it. And taking care of having a dot-announcement and a blog
>> entry too. Oh and nowadays its also good to send a mail to amilcar to
>> make sure our website is updated with a news entry (as he seems to have
>> little time currently).
>
> So basically, it is release management?
Well, Andreas did a lot more:
- he took care of almost all incoming bug reports
- he looked at all of us commits and did even revert some broken ones
and commented
  others that must be improved
- he was involved in most design (ui and technical) discussions
(BTW: thank you for all this)

But I think this must not be done by a single "maintainer" person, we should
help together. Maybe we could even convince Andreas to continue maintainership
if we do burden-sharing of those jobs :D

Niko