• open365, let's declare war at Google and Microsoft

    Open365 is a public and/or private cloud designed to compete with the likes of Google Drive or Office365 by leveraging all the best free software out there.

    The service is designed to scale horizontally as well as to be resilient to components crashing or going crazy. In order to achieve this we have implemented a microservice architecure that communicate using a bus (rabbitmq) plus some other tricks so we can scale using commodity hardware horizontally. Nothing fancy, nothing revolutionary but it had to be done :)

    Finally, we’ve integrated under the same system very well know software solutions for File sinchronization, PIM (Email, calendar,contacts…) and office.


    For the last two, we re using SPICE and our HTML5/Javascript client to run those applications in the server and send only the interface to the Web browser in a really efficient way.

    This is how it looks like:


    The public service is in open beta so you can go to Open365 and try it out for free.

    As I write this blogpost we are working hard to release all the code as free software. There is a lot to be done before we can release all the code such as: creating a simple installer, preparing documentation and accomodating the new repositories to our CI.

    We expect to release everything within days, but it will be done when it is done :)


  • Where have I been?

    I can’t imagine anything worse than waking up every morning without any energy for going to work.

    The first time I heard that statement I was 17 and it made an impression on me. It made me think of how we use our limited time, which roughly is: 1/3 sleeping, 1/3 at work and 1/3 at what we call spare time. We can’t control how much we need to sleep, but we can take a stance on the other two thirds (work and spare time).

    And this is the reason behind my disappearance, my job at BlueSystems was not fun anymore and every project I mantained at KDE felt more like a chore than anything else. After a month of not jumping out of the bed to head to work it was time to move on. So I passed maintainership to the people that were actually doing the job (special mention to David) and I quit my job as a full time KDE hacker.

    Nowadays I am working at a company called eyeOS, but more on that in the next post :)

    I appreciate all the people that have been asking how I have been during this last year, my apologies for disappeararing without notice.


  • For community free of Trolls

    In light of the last comments containing insults and other attacks to members of our community I have decided to make a video blog explaining my thoughts on the issue.

    The video contains two separate topics:

    • Explanation of why we can't tolerate this behavior
    • Some ideas on the actual matter (Baloo)

    Please, watch the whole thing before commenting and I hope we all work together to push away the trolls in our community.

    Cheers !

  • Desktop applications of tomorrow (I)

    This is the first of three posts where I am going to share my vision for the desktop apps of the short-term future.

    When I am using my workstation or laptop I find myself spending most of my time in the browser, with it I do a lot of different tasks I used to be doing with many different native applications for example: listening to music, watching videos, chatting with friends, sending pictures...

    When I am using my tablet or phone though the situation changes. I find myself rarely using the browser, in fact I only use it to visit some site I saw on another app like Twitter or Facebook.
    At the beginning (HTC Magic, my first Android phone) I thought this was because the browser was so unbearable that they had to come out with an alternative to the web, so they came out with "specific apps", that is one app per each internet service or purpose.

    But things have evolved since, and now my Nexus5 and 7 can render websites some times even better and faster than my laptop, but anyway I still prefer to use Android apps. Why?


    Both web and android apps are way better at managing content than we are.

    They always have something to show to you: perhaps something new that might interest you? perhaps a bold guess based on you previous search? or perhaps just what is "hot" nearby? Two of the best example are Youtube and Spotify.

    Your content is available everywhere, and I am not talking only about putting stuff into the "cloud" but I am talking about your online profile. Continuing with the example of Youtube and Spotify on both apps you will have your: playlist, subscriptions, radios, friend list on any device either via the app or the web.

    Sharing content is damn easy on both either by copying the url on the Web or by clicking the omnipresent share button in Android. As a matter of fact I don't remember the last time I shared a picture or an article using a desktop app... Probably it was really long ago.

    They know what content you like... They know your habits... They know everything and they use it to provide the most convenient content at all time. Oh look! It is Monday, perhaps you want to watch the new video uploaded in this Youtube channel as you do every week?

    Finally, both web and Android apps try to avoid making the user think too much which I find it to be a relief when I am using them. Again they do this by knowing what content you are interested on and by providing it to you in the best possible way.

    That is it for now, In part II I will explain the current situation of the desktop apps and in part III I will show a mockup of a video app I hope to work on someday. In the meanwhile what do you think? Is the same thing I describe in this article happening to you?

  • Demand a KDE Experience from your Distribution !

    If you are reading this blog you probably know how things work in the GNU/Linux Desktop, some people develop software and then some other people distribute that software. This usually works quite well since the people distributing the software (In this case KDE software) work with us, and together we make sure that the final product is awesome.

    This system works as long as both, upstream (KDE) and downstream (Distributions) work together, but some times collaboration does not happen and problems appear. In those cases the experience that the user gets is not the experience we designed from KDE.

    This is quite similar to what happens in the Android world, HTC/Samsung/LG do their own versions of it containing a different set of applications, configurations, services, etc. Google then releases what their think Android should be. In the same way Kubuntu/Opensuse/Fredora/Chakra do what they think is correct when it comes to updates, default applications, modify our software etc, meaning that in most cases the software is delivered in a different way from what we envision.

    This is why I want you to demand to your distribution to offer a full KDE Experience, this means:

    • Not patching our software.
    • Upgrading to all minor releases.
    • Not using software that is no longer supported by us.
    • Offering all pre-releases as optional.
    • Use the latest supported middle-ware and libraries (bluez, networkmanager, udisk, Qt, virtuoso...)

    In order for distributions to do this we need to build some infrastructure we currently lack; what is the latest supported virtuoso? or the latest supported BlueZ? Currently only the respective developers know about these things.

    While we work on setting up those bits of infrastructure there are things you can already demand from your distributions - minor upgrades, no patching, or making all pre-releases available.