keurocalc status

keurocalc has been ported to KF5 but there seems to have been no release.
Does anyone plan to make a release? Or should it go into KDE Applications?
Or should it be marked as unmaintained?



Re: keurocalc status

By Eric Bischoff at 06/06/2019 - 02:12

Le mercredi 5 juin 2019, 18:23:50 CEST Jonathan Riddell a écrit :
Hi Jonathan,

It is maintained (by me), but I don't know how to "make a release". I would
need help on that. With some help, I'd be happy to do it.

I'll be in the clinic until Monday for a small surgery, so don't be surprised
if I'm not responsive this week-end :-).


Re: keurocalc status

By Jonathan Riddell at 06/06/2019 - 06:03

The easiest way to get it released is to ask for it to be moved into KDE
Applications and then that gets taken care of for you.

Otherwise it's a case of following the page here
<a href="" title=""></a>
Much of it can be eased with the releaseme scripts which does the branching
and tarring and tagging for you.

Let me know if you need help.

Good luck with the surgery.


Re: keurocalc status

By Eric Bischoff at 06/08/2019 - 07:19

I will try to learn that, thanks for the pointer. I will do on next week-end.

It went well, thanks.

What means having an application in "KDE Applications" - was - R

By Albert Astals Cid at 06/06/2019 - 18:09

El dijous, 6 de juny de 2019, a les 12:03:17 CEST, Jonathan Riddell va escriure:
Can we please discuss what being in KDE Applications is first?

You're telling apps they can join KDE Applications if they want, so to you it's just "release as a service".

I disagree, to me it's a "we as a community vouch to try to maintain this to the best of our ability/time".

So [to me] adding more things to KDE Applications needs at least a vague consensus that it's worth making that kind of promise.



Re: What means having an application in "KDE Applications"

By Jonathan Riddell at 06/16/2019 - 16:30

On Fri, Jun 07, 2019 at 12:09:27AM +0200, Albert Astals Cid wrote:
I think KDE should offer services to apps which want to be part of the
apps bundled release along with making the tars such as recommending
version number, promo, maybe helping out with packaging for Snaps and
Flatpaks and Appimage if there's teams happy to do that. But just
trying to get agreement on renaming the bundle shows to me that KDE
isn't ready to take on much more of a role such as maintainance. I
think the most KDE could offer is to say that everything in the bundle
works as intended and once it bitrots enough that is no longer the
case then it will be kicked out. I don't think worry that it can't be
maintianed should be a barrier to including an app.


Re: What means having an application in "KDE Applications"

By Luigi Toscano at 06/16/2019 - 17:41

Jonathan Riddell ha scritto:
I think that you are conflating the "help with the release" with the need for
applications to be part of the bundle.

My dream is an automated server-side tarball generation, in a way that
developers can simply ask to release from a specific tag and don't care about
uploading the file to the right place on the incoming ftp/ssh server. But that
service could exist independently from the bundle.

Re: What means having an application in "KDE Applications"

By Nate Graham at 06/16/2019 - 18:33

On 6/16/19 3:41 PM, Luigi Toscano wrote:
Can we please not turn every discussion about adding, removing, or
modifying apps in or to the bundle into into a discussion about the
bundle's nature and future? Every time we do this, it seems like nobody
can agree on what we should turn it into and nothing changes. If we're
stuck with the status quo, IMO let's just embrace it and use it.

I support adding things to the bundle that are currently being neglected
in terms of both development and release resources. Putting them into
the bundle seems like a good way to improve these things, rather than
prerequisites to doing it.


Re: What means having an application in "KDE Applications"

By Luigi Toscano at 06/19/2019 - 17:57

Nate Graham ha scritto:
I may turn the question: can we please not propose every application for
inclusion into KDE Applications on the basis of unproven reasons? See below.

The data shows that there is no correlation between a project being part of
KDE Applications and how much it is taken care of.

We have projects part of KDE Applications in a "stable" state, and that's
fine. Sometimes sadly in a almost unmaintained state (the Telepathy stack).
Sometimes they suffered during the Qt4->Qt5 transitions. Many times they are
more than alive.
The same can be said for projects outside KDE Applications. We have a lot of
projects which are maintained. We have unmaintained ones. And we have an
interesting of projects which have been resurrected, sometimes going from an
unreleased Qt4 version to a fully released Qt 5 version.

My point is that that if the main driver for the inclusion is raising the
awareness about a certain project and attracting new developers, given that no
data support this correlation, then maybe the inclusion itself should be

Re: What means having an application in "KDE Applications"

By Nate Graham at 06/20/2019 - 02:18

On 6/19/19 3:57 PM, Luigi Toscano wrote:
While I agree that inclusion doesn't guarantee higher awareness, the
inverse seems more likely to me, for maintainerless apps at least: with
no maintainer to request and coordinate releases, apps not in KDE
Applications don't get released, so their awareness gradually drops to
zero over time. Inclusion in the KDE Applications bundle may not be a
panacea, but how else are maintainerless/community-maintained apps
supposed to get released?


Re: What means having an application in "KDE Applications"

By Luigi Toscano at 06/20/2019 - 03:43

Nate Graham ha scritto:
That's a good question. In the past few applications have found a new
maintainer "out of the blue" and got a release. Some of them opted for joining
KDE Applications (but only after getting a maintainer, not before), other did not.

From a community point of view, an interesting effort - which would require a
new team and, more important, new coordinator, has been the KDE Gardening Project:
<a href="" title=""></a>
(k3b was not part of KDE Applications at that time but regardless of that it
had a bunch of bugs that required some fixes).

On the other hand I'd like to mention that the last two applications that have
been proposed (not by their maintainer) to join KDE Applications do have
maintainers (keurocalc and yakuake).

Re: What means having an application in "KDE Applications"

By Jonathan Riddell at 06/18/2019 - 06:21

On Sun, Jun 16, 2019 at 11:41:50PM +0200, Luigi Toscano wrote:
Automating any app releases more would be great. But I tried to put much
of it into a CI for Plasma once and got stuck because there are access
needed stages that are hard to CI such as GPG signing tars, updating
version numbers, gpg signing and pushing tags. Still there should be
some scope for improvements there.


Re: What means having an application in "KDE Applications"

By Ben Cooksley at 06/17/2019 - 05:09

On Mon, Jun 17, 2019 at 9:42 AM Luigi Toscano <luigi. ... at tiscali dot it> wrote:
That would be reasonably straight forward to implement in a Jenkins Pipeline.
Only part you wouldn't be able to do is GPG signing using the developers key.


Re: keurocalc status

By Luigi Toscano at 06/05/2019 - 14:34

Il 5 giugno 2019 18:23:50 CEST, Jonathan Riddell < ... at jriddell dot org> ha scritto:
Yes, there is a plan for a release. I've been in contact with the maintainer for a while. There have been few troubles with the release process. No unmaintained for sure.

Re: keurocalc status

By Eric Bischoff at 06/06/2019 - 02:14

Le mercredi 5 juin 2019, 20:34:03 CEST Luigi Toscano a écrit :

Thanks Luigi.