Afiestas Blog

Almost 1 week has passed since Solid Sprint took place, and I’m already waiting for the next event, where I can hack side by side with KDE hackers from all the world again (Maybe in the Meego conference?). It was a short sprint but intense, productive and funny, on where we discussed and worked on some different topics. Let’s began from the start.

Organisation:

The organisation of a small Sprint doesn’t require a huge amount of time (at least didn’t this one) basically the tasks to do are:

1. Be sure that you can attend to the sprinters and having a good place for the event (office)
2. Propose the idea and the place to some KDE group (mailist)
3. Decide a date doing a poll
4. Prepare a budget for the e.V board (attendees list)
5. Send the budget to the board, together with the event explanation and wait.
6. Finally book the rooms, and enjoy the event.
7. Additionally, UFOCoders and Interdominios sponsored catering for all the weekend (food and drinks), and Pizza for the Sunday lunch.

Start:

After met everybody in the room where the event took place, we went to lunch. After it we began to organize the Sprint, or better said Kevin Ottens start to explain to the rest of the team all the things that were filling the whiteboard (an entire glass wall), in it we could differ between “Discussing goals” and “Coding goals”, these last were managed by using a Kanban.

The most important point we discussed (imho) is the “Solid as a Team” one. That was something that everybody had in his mind, but it was not official. Now it is, so welcome the new Solid, reborn as a community inside KDE, containing a lot of projects like (in no particular order): libsolid, powerdevil, networkmanagement, bluedevil… So, if you have a project which is related to KDE+Hardware, don’t hesitate to contact us via kde-hardware-devel mailist).

After having discussed all the topics, we started to hack. That night (Friday) we established the first interaction between NetworkManagement and BlueDevil, it not was event using an interface or any BD/NM code, but it demonstrated to us how hard/easy it was, and that it can be done.

After a few hours of Hacking, Sebas, Dario, and I went to take some beers (Voll daaamn ), near de hotel, and discuss about random things. I love these discussions! exchange opinions and ideas about our ecosystem is, a part of entertaining and funny, one learnt a lot of things by listening to other point of views, and make your global vision better. The bad thing (if I can say something) is that I slept 4h that night :p

Middle:

The Saturday was the “Super Hacking Day”, we where in front of the computer for around 18 hours only stopping for dinner. Each person on the sprint had lunch at a different time which shows how deep where were in our personal thought’s.

The first thing I decided to do that Saturday was finish my part of Bluetooth+NetworkManagement. If started to implement some plugins for BlueDevil, when doing it I noticed some interesting stuff from BlueZ, and discover how Network interface work. So, I explained to Will what I discovered and the issues I found, and he started to research how GNOME applet/wizard handle it. I don’t remember when, but we ended up with a solution (Will did), so we hope that sooner than later we’ll have Bluetooth+NetworkManagement interaction done.

The next task I assigned to myself was a technical one (not directly user-related), add asynchronous API to libsolid. After discussin with Kevin his design, I used the next hours to learn how libsolid works, and to connect the current code with the Kevin explanation about the new design. Once I did that, I started to write some tests that will help me to design a good API and at the same time that this new API would be “unit tested” (basicaly I sued Test Driven Development). With the tsdgeos help, we got a PoC working, that helped us to decided which way we should take (use an internal QList instead of inherit it).

An finally, I started to do some fine tune into BlueDevil Wizard, to get the pairing process more stable and perfect with a major number of devices (devices without PIN mainly). I tested the new code with: Apple* stuff I grabbed from the office, Nokia headset, HTC Magic and Wiimote.

We finished the hacking session at 6am, and decided to come back at 10am, so basically I decided to do not sleep (wise decision).

End:

All the ends are sad, even if it is a good end. In the sprint cases, it is sad because the people leave in dribs and drabs, however we managed to get a profitable time to put a good end to the Sprint.

One of the objectives of this sprint was exchange projects or topics, so instead of continue hacking on BlueDevil, I decided to take another project task, in this case PowerDevil UPower Backend. So, as Dario was sitting just left to me, I asked him to explain me how to create a PowerDevil2 backend, and after he explained to me, I started to copy some code from the Hal backend and make it compile. After it we just ordered some pizza’s (Sponsored too, as the tradition says) and well, we bought too much :p

After lunch I continued with my research, this time focused on UPower, basically I compared UPower vs Hal features (the ones we are using) and noticed some things that have to be done by using another piece of software, like xrandr.

Finally we end up Sebas, Ereslibre, and I. In one of the trips to the fridge we noticed something… there were 6 Volldamn left to drink! We decided to add a sticky note (Green + Red which meant Community and Urgency), and add it to “In Progress” column. After a hard work and a lot of chatting, we moved the task to the “Done” column

While packing and cleaning everything, we end up at 02:00 AM talking about random stuff again, sharing ideas about KDE future, Sebas showing to us Lionmail and Crystal etc…

To end the post, I’d like to thank for:

-KDE e.V for sponsoring the event.

-Community: people and companies, who donate money to e.V, so they can sponsor the sprints.

-Interdominios for helping us with the organisation (Specially to Benito, who handled all the catering and Hotel booking)

-Solid team to be awesome.

This is pretty much all, I hope this post help you (reader) to realize how important these sprints are for us, and by extension how important the donations are.

Join the game!

Hi there

As you may have noticed, BlueDevil RC4 is not out (yet), and there is a reason for that.

We’re mainly 2 developers working on it, ereslibre and myself. Ereslibre is studying hard because he has like 5 exams in 2 weeks, and I’m looking for a new place to live downtown (still in Madrid), so those things are stealing our KDE hacking time

But don’t worry, BlueDevil development is not paralyzed, luckily our company (ufocoders) is allowing us to work on BlueDevil all Fridays, and this is why we’re moving the releases to that day.

The current TODO list until 1.0 final is:

• i18n
• A few reported crashes
• Better audio plugin
• Documentation for distributions
• Make kio_obexftp stable (this may involve a rewrite, or maybe wait until kde 4.5.2)
• setup bluedevil.kde.org.

This time, I’m not going to write a date, since we can’t be sure to accomplish it, but we want to release the RC4 in 2 weeks more or less.

Cyap and sorry for the inconveniences!

=-=-=-=-=
Powered by Blogilo

Hi there

As promised, we have released a new RC of BlueDevil.

Highlights:

• Removed BlueZ documentation to avoid licence problems
• Build system fixes by George Kiagiadakis and Kishore Jonnalagadda
• Improved the stability of the kio_obexftp (the / bugs has been fixed too).
• Fixed a crash in the KCM
• Fixed crash in the "reception of files".

Errata:

Take a look at the error list in: KDE Bugtrack

Also, this release is not ready to work on i18n, it is expected in RC3 or 4

Download:

The tarbal can be found here with md5: 9af87be2eeffe3b203a06232ef55bfb9

And git tag: git clone git://gitorious.org/bluedevil/bluedevil.git; git checkout v1.0-rc2

Please, test BlueDevil as much as possible so we can fix the majority of the bugs before the final release.

Next release: 2010/08/11 (next week).

Thanks!

=-=-=-=-=
Powered by Blogilo