Laying down the maintainer-hat

[Andreas Pakulat]

On 10.04.10 09:51:58, Esben Mose Hansen wrote:
> In the interest of getting a new maintainer(s), could you outline what the job 
> includes? While I am maintainer of Klipper (on-and-off), I don't generate 
> releases for Klipper, or even steer it's development much since there is so 
> little of it.

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).

Once we find a new maintainer, I'll surely be handholding and providing
more details on the steps to him (or all of us to make sure this is
written down somewhere).

Andreas

-- 
If you think last Tuesday was a drag, wait till you see what happens tomorrow!