From konversation-devel Thu Sep 17 16:48:24 2020 From: Peter Simonsson Date: Thu, 17 Sep 2020 16:48:24 +0000 To: konversation-devel Subject: Re: Getting Konversation releases rolling again (offering myself as release manager) Message-Id: X-MARC-Message: https://marc.info/?l=konversation-devel&m=160036133504175 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--000000000000b6c55305af8527ab" --000000000000b6c55305af8527ab Content-Type: text/plain; charset="UTF-8" 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 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 > > > --000000000000b6c55305af8527ab Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
Sounds like a good idea to me... I'm such an e= rratic 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

<= /div>

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 anno= ys
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 aliv= e
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 <= br> 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.<= 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 prepar= e
Konversation to be moved over to the Release Service, to ensure all the tin= y
fixes and translation improvements are steadily rolling to users, while the= re
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 fix= es)
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=C2=A0 Profit and pull out again after first RS releases :)

I would also allow myself to do some needed code clean-up/modernization wor= k
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 wha= t
patches need review by others and for which I can take confidence in my clu= es
as well as is the change straightforward (KDevelop contributors might be ab= le
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


--000000000000b6c55305af8527ab--