Re: Dropping kdelibs4-based applications in KDE Applications 17.12
On Thu, Nov 17, 2016 at 2:55 PM, Kevin Funk wrote: > On Thursday, 17 November 2016 00:51:50 CET Sven Brauch wrote: >> On 11/11/16 16:45, Dominik Haumann wrote: >> > What do you think about having a Randa meeting (or similar) with focus >> > on finishing ports to KF5? Would that make sense? >> >> +1 actually. There are a few applications on that list which would, in >> my eyes, be a real loss if they were not maintained any more; I'm >> especially looking at kcachegrind (I know of no comparable tool and it's >> really good), maybe kopete. kmag is nice too on occasion but I don't >> know if it will die with wayland anyways. > > +1 on kcachegrind, that would be a real loss. Actually there's an actively > maintained frameworks branch, maybe we just need to poke Josef? ;) There's a kf5 branch for kopete too. While I can't say it's seeing active development at the moment, it has been worked on quite extensively and looks near complete. For more : https://marc.info/?l=kopete-devel&m=147851133511821&w=2 > > @Josef: Is the frameworks branch stable? If yes, let's release! > >> I'd be in for a sprint (or a few days of a sprint) to port those. > > Consider me in as well. +1 from me too. Cheers, Harish
Re: kio-gdrive - was - Re: New project moved to review
On Wed, Nov 2, 2016 at 11:34 AM, Elvis Angelaccio wrote: > On Tue, Nov 1, 2016 at 6:44 PM, Albert Astals Cid wrote: >> El dilluns, 31 d’octubre de 2016, a les 17:39:21 CET, Elvis Angelaccio va >> escriure: >>> On Mon, Oct 31, 2016 at 4:29 PM, Albert Astals Cid wrote: >>> > El divendres, 28 d’octubre de 2016, a les 18:21:48 CET, Elvis Angelaccio >>> > va >>> > >>> > escriure: >>> >> Hi, >>> >> what's the status of this review? Do we want to discuss where to move >>> >> this >>> >> repo? >>> > >>> > Yes. >>> >>> So, the repo location was playground/network. Possible destinations could >>> be: >>> >>> 1. extragear/network >>> 2. kdenetwork >>> 3. extrager/pim >>> 4. kdepim >>> >>> I would choose 3 or 4. This slave depends on libkgapi, so from a >>> dependency point of view it makes more sense to have it in the pim >>> module rather than the network module. >>> >>> Thoughts? >> >> I'd go with 3, you've been doing releases relatively rapidly so being tied to >> the "more strict" KDE Applications release schedule may not be ideal for you >> at this stage (maybe I'm wrong?). > > Right, I've also been signing those releases so going with 3. is > better for packagers (they wouldn't need to change the signing key, > etc.) Are we missing something else? Otherwise I'm going to file a ticket for the move to extragear/pim by the end of the week :) > >> >> Cheers, >> Albert > > Cheers > Elvis > >> >>> >>> > Cheers, >>> > >>> > Albert >>> >>> Cheers >>> Elvis >>> >>> >> Cheers >>> >> Elvis >>> >> >>> >> On Mon, Oct 10, 2016 at 12:25 AM, Elvis Angelaccio >>> >> >>> >> wrote: >>> >> > On Sun, Oct 9, 2016 at 11:58 PM, Albert Astals Cid >> wrote: >>> >> >> El dimarts, 4 d’octubre de 2016, a les 11:03:22 CEST, Elvis Angelaccio >>> >> >> va >>> >> >> >>> >> >> escriure: >>> >> >>> On Tue, Oct 4, 2016 at 10:17 AM, Ben Cooksley >> wrote: >>> >> >>> > Hi all, >>> >> >>> > >>> >> >>> > At the request of Elvis Angelaccio sysadmin has moved kio-gdrive to >>> >> >>> > KDE >>> >> >>> > Review. >>> >> >>> >>> >> >>> Thanks Ben. >>> >> >>> >>> >> >>> Just a quick intro, kio-gdrive is a simple kio slave on top of >>> >> >>> libkgapi (PIM's implementation of the Google Drive REST api). Please >>> >> >>> have a look and, if everything looks good, let's decide where we want >>> >> >>> to move it. >>> >> >>> It comes from playground/network, so a possible destination would be >>> >> >>> extragear/network or kdenetwork. But imho this could also live in the >>> >> >>> PIM module, since it depends on libkgapi. >>> >> >> >>> >> >> Can you get a build.kde.org job? >>> >> > >>> >> > Oh right, kde-build-metadata was outdated and still looking in >>> >> > playground. Should be fixed now. >>> >> > >>> >> >> Also why Qt5Keychain instead of kwallet? >>> >> > >>> >> > This should help deploying the slave outside of Plasma (e.g. if one >>> >> > uses Dolphin in Gnome, it will store the gdrive secrets in the Gnome >>> >> > keyring instead of Kwallet). On Plasma it still uses Kwallet as >>> >> > backend. >>> >> > >>> >> >> I have no idea how the remote:/ kio shows its contents, but maybe >>> >> >> would >>> >> >> make sense to check if it allows for "plugins" and show the gdrive >>> >> >> stuff >>> >> >> there? Or that doesn't make sense? >>> >> > >>> >> > No idea either but would be nice to have indeed, I can try to have a >>> >> > look. >>> >> > >>> >> >> Cheers, >>> >> >> >>> >> >> Albert >>> >> >> >>> >> >>> > Regards, >>> >> >>> > Ben Cooksley >>> >> >>> > KDE Sysadmin >>> >> >>> >>> >> >>> Cheers >>> >> >>> Elvis >> >>
Re: Dropping kdelibs4-based applications in KDE Applications 17.12
Hi all, sorry for reading the mailing list very rarely nowadays. On 17.11.2016 10:25, Kevin Funk wrote: On Thursday, 17 November 2016 00:51:50 CET Sven Brauch wrote: On 11/11/16 16:45, Dominik Haumann wrote: What do you think about having a Randa meeting (or similar) with focus on finishing ports to KF5? Would that make sense? +1 actually. There are a few applications on that list which would, in my eyes, be a real loss if they were not maintained any more; I'm especially looking at kcachegrind (I know of no comparable tool and it's really good), maybe kopete. kmag is nice too on occasion but I don't know if it will die with wayland anyways. +1 on kcachegrind, that would be a real loss. Actually there's an actively maintained frameworks branch, maybe we just need to poke Josef? ;) @Josef: Is the frameworks branch stable? If yes, let's release! For my point of view, the framework branch should be as stable as the master regarding features. I recently only added minor stuff in master, and always merged that also into framework (same with some bugs). Further, the last porting TODOs happened a few weeks ago, about reviving icon markers in lists (if a call is part of a recursive call cycle). So yes, I can switch the frameworks branch to become master already today. Josef I'd be in for a sprint (or a few days of a sprint) to port those. Consider me in as well. Cheers, Kevin Greetings, Sven
Re: Dropping kdelibs4-based applications in KDE Applications 17.12
On Thursday, 17 November 2016 00:51:50 CET Sven Brauch wrote: > On 11/11/16 16:45, Dominik Haumann wrote: > > What do you think about having a Randa meeting (or similar) with focus > > on finishing ports to KF5? Would that make sense? > > +1 actually. There are a few applications on that list which would, in > my eyes, be a real loss if they were not maintained any more; I'm > especially looking at kcachegrind (I know of no comparable tool and it's > really good), maybe kopete. kmag is nice too on occasion but I don't > know if it will die with wayland anyways. +1 on kcachegrind, that would be a real loss. Actually there's an actively maintained frameworks branch, maybe we just need to poke Josef? ;) @Josef: Is the frameworks branch stable? If yes, let's release! > I'd be in for a sprint (or a few days of a sprint) to port those. Consider me in as well. Cheers, Kevin > Greetings, > Sven -- Kevin Funk | kf...@kde.org | http://kfunk.org signature.asc Description: This is a digitally signed message part.
