Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-17 Thread Ivan Čukić
> Nepomuk in 4.10 being too slow. Whichever bottlenecks they may be, are > "most probably" in our code. Not theirs. There are bottlenecks in nepomuk, but there are in V as well. Once upon a time, I did some benchmarks with sql (sqlite) and sparql (virtuoso/soprano) queries for the things that a

Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-17 Thread Vishesh Handa
On Sun, Feb 17, 2013 at 5:04 PM, Ivan Čukić wrote: > On Sunday, 17. February 2013. 12.20.00 Aaron J. Seigo wrote: > > On Sunday, February 17, 2013 08:55:38 Martin Graesslin wrote: > > > * which pulls in Virtuoso > > Just a small off-topic here: Virtuoso *is* one of the fastest rdf databases > out

Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-17 Thread Ivan Čukić
On Sunday, 17. February 2013. 12.20.00 Aaron J. Seigo wrote: > On Sunday, February 17, 2013 08:55:38 Martin Graesslin wrote: > > * which pulls in Virtuoso Just a small off-topic here: Virtuoso *is* one of the fastest rdf databases out there. The problem is not that much with its speed, but more w

Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-17 Thread Aaron J. Seigo
On Sunday, February 17, 2013 08:55:38 Martin Graesslin wrote: > * which pulls in Virtuoso afaict this is now the main problem. (which speak volumes to how far akonadi and nepomuk have both come in the last 2 years!) I was speaking with Georg from Kolab Systems the other day over coffee and this

Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-16 Thread Martin Graesslin
On Sunday 17 February 2013 02:08:57 Aaron J. Seigo wrote: > On Saturday, February 16, 2013 16:54:03 Martin Graesslin wrote: > > I wouldn't call KDE Plasma lightweight > > indeed; those 1Ghz ARM cpus with 512MB of RAM running it are just *beasts* > of the modern age I tell you. ;) > > razorqt may

Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-16 Thread Aaron J. Seigo
On Saturday, February 16, 2013 16:54:03 Martin Graesslin wrote: > I wouldn't call KDE Plasma lightweight indeed; those 1Ghz ARM cpus with 512MB of RAM running it are just *beasts* of the modern age I tell you. ;) razorqt may be lighter still (i haven't looked, but i can imagine all sorts of wa

Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-16 Thread Kevin Krammer
On Saturday, 2013-02-16, Martin Graesslin wrote: > On Saturday 16 February 2013 18:55:17 Sebastian Kügler wrote: > > All good points. From my side, they're totally welcome. (I'd need to know > > in time in order to make space for them during the sprint.) Are you in > > contact with the developers a

Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-16 Thread Marco Martin
On Saturday 16 February 2013, Sebastian Kügler wrote: > > > > *Comments?* > > All good points. From my side, they're totally welcome. (I'd need to know > in time in order to make space for them during the sprint.) Are you in > contact with the developers already? Maybe in that case, you could ask

Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-16 Thread Martin Graesslin
On Saturday 16 February 2013 18:55:17 Sebastian Kügler wrote: > All good points. From my side, they're totally welcome. (I'd need to know in > time in order to make space for them during the sprint.) Are you in contact > with the developers already? Maybe in that case, you could ask if they're > in

Re: [RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-16 Thread Sebastian Kügler
On Saturday, February 16, 2013 16:54:03 Martin Graesslin wrote: > I want to suggest that we invite Razor-Qt developers to our next Workspaces > Sprint in Nuremberg. > > *Why?* > At FOSDEM there was a presentation about Razor-Qt and I attended it > together with many other KDE developers. For me

[RFC] Invite Razor-Qt to next Workspaces Sprint

2013-02-16 Thread Martin Graesslin
Hi all, I want to suggest that we invite Razor-Qt developers to our next Workspaces Sprint in Nuremberg. *Why?* At FOSDEM there was a presentation about Razor-Qt and I attended it together with many other KDE developers. For me the most important information I took out of that talk was that Ra