On Sun, Nov 20, 2016 at 5:04 PM, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: > In data domenica 20 novembre 2016 13:24:50 CET, Elvis Angelaccio ha scritto: >> On Sun, Nov 20, 2016 at 12:39 PM, Boudhayan Gupta <bgu...@kde.org> wrote: >> > Hi all, >> > >> > I seem to have missed this discussion and since there's a ticket to >> > move this I've become aware of this now, and am asking here. >> > >> > If we *are* to move to extragear, Extragear/network is the more >> > appropriate location for this. Reasons: >> > >> > 1) GDrive is not PIM related - it is networked file storage. >> > >> > 2) It depends on a Google Account, sure, but that account does not >> > need to have GMail enabled on it. It need have nothing else enabled on >> > it but Google Drive. >> > >> > 3) If I'm browsing the archives, I'm never going to think looking into >> > PIM for a Google Drive client. I *will* look at network though. >> > >> > Inputs? >> >> I think both locations would be fine (and in fact, it used to live in >> playground/network). I proposed to move it to PIM because it depends >> on libkgapi which is a PIM library. This would avoid a "cross-module" >> dependency, but perhaps this is not an issue? > > IMHO it is not an issue. Extragear means "something with its own release > schedule", so it does not really matter. > I see it too closer to network than pim. > >> Though imho the ideal >> solution would be making libkgapi a framework (but requires someone >> willing to do the work). > That's up to Dan, but I don't think it would prevent kio-gdrive from being > moved (or kept in) to network
Sysadmin has moved kio-gdrive to extragear/network. @Luigi: can you please update the i18n metadata? > > Ciao > -- > Luigi Cheers Elvis
