[prev in list] [next in list] [prev in thread] [next in thread]
List: konversation-devel
Subject: Re: Getting Konversation releases rolling again (offering myself as release manager)
From: Peter Simonsson <peter.simonsson () gmail ! com>
Date: 2020-09-17 16:48:24
Message-ID: CAO_k-hHDY=fs9qHsebNyfBQzsBqG1YnYG44KyOutdnXvqCs_Kw () mail ! gmail ! com
[Download RAW message or body]
Hi,
Sounds like a good idea to me... I'm such an erratic contributor these days
that I don't feel I got much say about it anyway. As far as I know there's
no unfinished work in master.
//Peter Simonsson
On Thu, Sep 17, 2020 at 6:22 PM Friedrich W. H. Kossebau <kossebau@kde.org>
wrote:
> Hi everyone,
>
> I was to finally try to write a fix for some bug in Konversation which
> annoys
> me since ages, until I discovered that the last release of Konversation
> has
> happened as back as in 2018?
>
> And while IRC might be on the path of dinosaurs, right now it is still
> alive
> and used in some places. So having a maintained Konversation might be good
> to
> have for us who are right now using it.
>
> Having acted as release manager of my own projects (e.g. Okteta) but also
> KDevelop for the last years, I would like to offer to take over myself
> such
> role for Konversation for some time, to help out a bit with my experience.
>
> I do not plan to become new maintainer though or such, and do not plan to
> drive new feature development. No time left for that. Rather want to
> prepare
> Konversation to be moved over to the Release Service, to ensure all the
> tiny
> fixes and translation improvements are steadily rolling to users, while
> there
> is no big feature work happening with full-time maintainers.
> E.g. right now there is 2 years work of translators that has been added
> for
> the 1.7 branch, but never made it to users (cmp. e.g. the in-source
> translation commits since the v1.7.5 tag to get an idea).
>
> What do you think?
> And who would be the one to tag me as release manager, so I could start? :)
>
>
> My rough plan would be this:
> 1. Get some 1.7.6 out ASAP to have all the translation updates (and few
> fixes)
> finally arrive at users
> 2. Prepare master branch to be ready for branch & release
> 3. Propose Konversation for inclusion in Release Service for 20.12
> 4. Make sure Konversation is fully integrated in Release Service cycle
> 5 Profit and pull out again after first RS releases :)
>
> I would also allow myself to do some needed code clean-up/modernization
> work
> by direct commit pushes, to speed up things during my limited time.
> This should not scare you too much, I feel I have a good balance after
> many
> years of contributing to KDE projects (and other C++/Qt things) to know
> what
> patches need review by others and for which I can take confidence in my
> clues
> as well as is the change straightforward (KDevelop contributors might be
> able
> to confirm I hope :) ).
>
> Initial questions (not yet looked closer):
> * Which things would you like to see in 1.7.6, any blockers known?
> * Which unfinished work are you aware in the master branch that needs
> completion?
> * What is the state of the QtQuick port? Anyone interested still in
> driving
> it? Is there anything that needs to be cared about to not make that branch
> harder to drive forward, once someone works on that again?
>
> Cheers
> Friedrich
>
>
>
[Attachment #3 (text/html)]
<div dir="ltr">Hi,<div>Sounds like a good idea to me... I'm such an erratic \
contributor these days that I don't feel I got much say about it anyway. As far \
as I know there's no unfinished work in master.<br clear="all"><div><div \
dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div \
dir="ltr">//Peter Simonsson</div></div></div><br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Sep 17, 2020 at 6:22 PM \
Friedrich W. H. Kossebau <<a \
href="mailto:kossebau@kde.org">kossebau@kde.org</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi everyone,<br> <br>
I was to finally try to write a fix for some bug in Konversation which annoys <br>
me since ages, until I discovered that the last release of Konversation has <br>
happened as back as in 2018?<br>
<br>
And while IRC might be on the path of dinosaurs, right now it is still alive <br>
and used in some places. So having a maintained Konversation might be good to <br>
have for us who are right now using it.<br>
<br>
Having acted as release manager of my own projects (e.g. Okteta) but also <br>
KDevelop for the last years, I would like to offer to take over myself such <br>
role for Konversation for some time, to help out a bit with my experience.<br>
<br>
I do not plan to become new maintainer though or such, and do not plan to <br>
drive new feature development. No time left for that. Rather want to prepare <br>
Konversation to be moved over to the Release Service, to ensure all the tiny <br>
fixes and translation improvements are steadily rolling to users, while there <br>
is no big feature work happening with full-time maintainers.<br>
E.g. right now there is 2 years work of translators that has been added for <br>
the 1.7 branch, but never made it to users (cmp. e.g. the in-source <br>
translation commits since the v1.7.5 tag to get an idea).<br>
<br>
What do you think?<br>
And who would be the one to tag me as release manager, so I could start? :)<br>
<br>
<br>
My rough plan would be this:<br>
1. Get some 1.7.6 out ASAP to have all the translation updates (and few fixes) <br>
finally arrive at users<br>
2. Prepare master branch to be ready for branch & release<br>
3. Propose Konversation for inclusion in Release Service for 20.12<br>
4. Make sure Konversation is fully integrated in Release Service cycle<br>
5 Profit and pull out again after first RS releases :)<br>
<br>
I would also allow myself to do some needed code clean-up/modernization work <br>
by direct commit pushes, to speed up things during my limited time.<br>
This should not scare you too much, I feel I have a good balance after many <br>
years of contributing to KDE projects (and other C++/Qt things) to know what <br>
patches need review by others and for which I can take confidence in my clues <br>
as well as is the change straightforward (KDevelop contributors might be able <br>
to confirm I hope :) ).<br>
<br>
Initial questions (not yet looked closer):<br>
* Which things would you like to see in 1.7.6, any blockers known?<br>
* Which unfinished work are you aware in the master branch that needs <br>
completion?<br>
* What is the state of the QtQuick port? Anyone interested still in driving <br>
it? Is there anything that needs to be cared about to not make that branch <br>
harder to drive forward, once someone works on that again?<br>
<br>
Cheers<br>
Friedrich<br>
<br>
<br>
</blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic