• Quick status update:

    Hey! long time no see :)

    I have been moving from Madrid to BCN, cities which are around 650km away and that is keeping me busy because I can't neglect work time for doing it and even if I could the process put pressure into your head so you spend more time procrastinating than before. Nevertheless the moving is almost complete and I'm going to be using more and more time in KDE.

    In what I'm going to use my KDE time:

    BlueDevil:

    • Finish 1.3 release
    • Bug triage, fix'em all
    • Fix a known bug in Wizard
    Kamoso:
    • Setup an environment where I can work with latest camerabin2
    • Finish Kamoso port to camerabin2
    libsolid:
    • Make sure that MTP devices work well in KDE
    • This may include write a MTP kio
    Screen Management:
    • Finally start to push code into a scratch repo
    • Having something functional by 4.8 release
    I think I'm going to focus in the latest (Screen Management) because is the one most people is waiting for and I've failed to deliver in a reasonable time.
    This is it for now, see you!


  • BlueDevil 1.0.6, 1.1.3, 1.2.2 and 1.3-rc1

    This weekend I proposed myself to clean the BlueDevil's bug list, at the beginning of the weekend the list had 42 bugs (including wishes), at this moment it has 18.

    When I started the bug triage process, I realize that we had too much crashes so I decided to sit down and fix'em all, well I think I did and because of that we're releasing new versions for each branch including a new one (1.3) which is the only one that includes a huge change in the KDE Daemon that fixes a bunch of crashes.

    Fixed in 1.0:

    • 270064: Crash in bluedevil-wizard while broswing a device in dolpin
    • 280908: Crash in bluetooth input helper
    • 282280: Crash upon removing bluetooth device
    • 269814: kde service krashed on blueman-manager start
    • 271427: bluedevil crash renaming a disapeared device
    • 277992: Removed mouse from device list in KCM while using the connection wizard crashed the KCM
    • 273144: Crash after recieve a file
    • 274772: Cancelling transfer from mobile phone results in technical error message
    • Fixed pairing when the PIN is asked from outside (this happened only some times)
    Fixes only affecting 1.1 adn 1.2:
    • 272230: Bluedevil KCM crashed when editing details of device
    • 281420: Bluetooth Wizard Crash
    Fixed only in 1.3:
    • Fixed 4 crashes in KDE Daemon
    Tarballs can be download from 1.0, 1.1, 1.2 and 1.3


  • BlueDevil 1.1.2 and 1.2.1 released

    Though we released the 1.2 version a while ago we decided to delay the announcement since there were some annoying bugs that now, thanks to the testing performed by the kubuntu community are fixed.

    Relevant posts about BlueDevil 1.2 (with videos and pictures  :p):

    For 1.1 branch there is only one fix that solve an annoying behavior when the wizard is invoked with pre-selected address and uuid (basically it was working behaving poorly, now it works well).
    This is it for now, next thing to do is releasing 1.3 (aka the release that will fix all known crashes).

    You can download them here (1.1.2) and here (1.2.1)
    I hope you enjoy them !

    Note: I forgot to public this post so the releases are actually a few weeks old, and we're about to release new ones in a few days :p


  • Usability at Forge 2011

    One of the most important thing that is happening in Forge 2011 is the amount of work we're doing related to usability, focusing all our efforts in tree projects:

    • Network Management
    • Power Management
    • Places View
    In all three of them we used more or less the same methodology and because of that we have been able to reuse some work we did for Network Management into the rest of the projects; Let me introduce you to Penny and Amy.
    After we defined the vision of Network Management (basically how and in what we think NM should help users) we needed to decide the kind of users we're targeting, for doing that we defined two personas each in one corner case, one is  computer science profesional and the other one is only interested in watching lolcats :p

    Penny: She is only interested in "being" online not into "get" online, meaning that she wants stuff to work out of the box or at least without bothering her alot.
    Amy: She is a sysadmin, she wants to be able to configure all the possible options out there .
    (Click on the name to read the full persona description).

    So,  once we got our two personas defined and the main target selected (Penny) the next step was to list a few places where each persona will use Network Management, for example: "Penny's home, train, park...". Finally we went through all possibilities imagining what our personas will want to do in that location.

    The funny thing about this is that we end up thinking like our personas will do, trying to make our best so Penny will be happy while Amy won't be bothered. And you want to know another funny thing? we discovered that by making Penny's life easier we were making Amy's easier as well, no matter if Amy is an "advanced user".

    I can't talk by others, but I will think as Penny from now on when I'm designing workspace stuff.


  • Forge 2011, day 1 !

    Finally the Solid sprint 2011 (kown as Forge) has started!

    The day has been a little weird since sadly some metalworkers were not able to make it :/ but we had to start so, this being a "Ervin driven sprint" we started creating a kanban.

    That took us a few hours, good thing is that now all we have in front of us is hacking, thats it!! 3 days of non-stop hacking :D

    At dinner time our usability messiah arrived, showing us the light in how to do an "user centred development" model, I will blog about it if nobody else does :p

    I'm arriving at the office so the rest of the blog entry will have to wait until later.

    Kanban from Force 2011

    Happy Hacking !!

    Ps: Donations of high quality Sticky notes are welcomed :p