[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: KDevelop maintainership
From: Aleix Pol <aleixpol () kde ! org>
Date: 2010-07-05 13:17:15
Message-ID: AANLkTinzMFFARtfgU8crIelDW17Z_hDGZTHraqTfh3yN () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Jul 5, 2010 at 2:34 PM, Andreas Pakulat <apaku@gmx.de> wrote:
> On 05.07.10 15:00:58, Alexander Dymo wrote:
> > Hey,
> > I'd like to bring this question to our attention one more time.
> > Andreas stepped down quite a long time ago and nobody stepped up and
> > we definitely need a maintainer (not just release coordinator, history
> > shows we as a team do benefit from having a strong and involved
> > maintainer).
> >
> > So, I'd like to propose this - like in KDevelop3 times, elect two
> maintainers:
> > * one person to do release management (boring stuff: release team
> > participation, packaging, bug management, writing stories, dot
> > articles, etc, etc.)
> > * another person to watch after technical things (fun stuff: watch
> > after code, api, architecture, do reviews, have a say when there's no
> > consensus during technical discussions)
> >
> > Amilcar and I managed to make 5 releases this way (from 3.1 to 3.5)
> > and I think that went quite well.
> >
> > What would you guys to say about electing:
> > * Milian for release coordinator
> > * Andreas for technical maintainer
>
> I'm sorry to say so, but I'm not up for that. I'm currently only using
> KDevelop when hacking on its source code, which means less than 5 hours a
> week and I don't think I should be judging on a codebase that I don't use
> myself.
>
> I'm still playing a bit with the core/ui split as I'm interested in that,
> but beyond that I don't have any plans to work on any kdevelop code in the
> short to mid term. (I'd love to implement a couple of features, but as I
> don't really use kdevelop myself I know I wouldn't ever be maintaining them
> properly)
>
> Andreas
>
> --
> You will have domestic happiness and faithful friends.
>
> --
> KDevelop-devel mailing list
> KDevelop-devel@kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
Given that Andreas is not really up for it, I'd like to help KDevelop with
the remaining co-maintainership. I've been involved with the team for quite
some time I think it could work if you are up for it.
During the next months I plan to spend quite a lot of time with KDevelop so
it makes sense to me, and I hope for you also.
Aleix
[Attachment #5 (text/html)]
<div class="gmail_quote">On Mon, Jul 5, 2010 at 2:34 PM, Andreas Pakulat <span \
dir="ltr"><<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;"> <div class="im">On 05.07.10 15:00:58, Alexander Dymo \
wrote:<br> > Hey,<br>
> I'd like to bring this question to our attention one more time.<br>
> Andreas stepped down quite a long time ago and nobody stepped up and<br>
> we definitely need a maintainer (not just release coordinator, history<br>
> shows we as a team do benefit from having a strong and involved<br>
> maintainer).<br>
><br>
> So, I'd like to propose this - like in KDevelop3 times, elect two \
maintainers:<br> > * one person to do release management (boring stuff: release \
team<br> > participation, packaging, bug management, writing stories, dot<br>
> articles, etc, etc.)<br>
> * another person to watch after technical things (fun stuff: watch<br>
> after code, api, architecture, do reviews, have a say when there's no<br>
> consensus during technical discussions)<br>
><br>
> Amilcar and I managed to make 5 releases this way (from 3.1 to 3.5)<br>
> and I think that went quite well.<br>
><br>
> What would you guys to say about electing:<br>
> * Milian for release coordinator<br>
> * Andreas for technical maintainer<br>
<br>
</div>I'm sorry to say so, but I'm not up for that. I'm currently only \
using<br> KDevelop when hacking on its source code, which means less than 5 hours \
a<br> week and I don't think I should be judging on a codebase that I don't \
use<br> myself.<br>
<br>
I'm still playing a bit with the core/ui split as I'm interested in that,<br>
but beyond that I don't have any plans to work on any kdevelop code in the<br>
short to mid term. (I'd love to implement a couple of features, but as I<br>
don't really use kdevelop myself I know I wouldn't ever be maintaining \
them<br> properly)<br>
<br>
Andreas<br>
<font color="#888888"><br>
--<br>
You will have domestic happiness and faithful friends.<br>
</font><div><div></div><div class="h5"><br>
--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" \
target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</div></div></blockquote></div><br><div>Given that Andreas is not really up for it, \
I'd like to help KDevelop with the remaining co-maintainership. I've been \
involved with the team for quite some time I think it could work if you are up for \
it.</div> <div>During the next months I plan to spend quite a lot of time with \
KDevelop so it makes sense to me, and I hope for you \
also.</div><div><br></div><div>Aleix</div>
--
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic