You are viewing rvokal

Developer Conference has been started already 7 years ago as a conference that wanted to allow local folks from various open source projects to present their work, ideas and plans. It never had an intention to become an international event, with hundreds of sessions and workshops. Well, this year it again got way bigger that what we've planned.

Last year we've hit the limit at the venue we have always been using. The rooms got crowded, the corridors were packed. It was still great event but we've started discussing moving the conference to new place. Luckily Red Hat setup a closer collaboration with Brno University of Technology and we got an option to use their venue for this year.

The lecture rooms are all recently build up and there's more of them. We have more space for booths, refreshments or even hallway conversations. Well, so why not to use all of that space!

I'm not sure if other event organizers are dealing with the same - but most of the talk submissions appear minutes before the deadline! :-) .. right after this deadline, we've realized that creating the schedule needs more people involved who can pick up tracks and make up the order of talks, avoid conflicts of interest etc. It was tough and we can't please everyone .. sorry folks! Big thanks to all who worked on the schedule and help me to line it up.

It's packed - 155 sessions, same number of speakers, lots of volunteers (we still need more, contact me if you'd like to help), 5 parallel talks tracks, 3 workshop tracks and all this in 3 days including great party at our favorite place - Fleda. If you haven't seen the schedule yet, check it out.

So if you have free weekend, want to see some good developer talks or help with your favorite projects - travel to Brno!

BTW, you can still win a tablet! Just hack up some cool app that runs on OpenShift and submit it to OpenShift Winter of Code!
Winners will be announced on the OpenShift session on Friday at DevConf.


By mistake I've disabled all network notification .. I'm especially interested in my VPN notification cos I tend to mistype my password. Here's a quick trick how to re-enable all disabled notifications

gsettings set org.gnome.nm-applet disable-connected-notifications false
gsettings set org.gnome.nm-applet disable-disconnected-notifications false
gsettings set org.gnome.nm-applet disable-vpn-notifications false

How to download MP3s! From youtube ..

It's fairly easy, just run `youtube-dl --extract-audio --audio-format mp3 -l ` and it's all yours!

OpenShift Winter of Code for DevConf 2014

If you still don't know what you're going to do during Christmas holidays here's a quick tip. Code and win! The OpenShift team is organizing a competition for Developer Conference 2014 - OpenShift Winter of Code. The most interesting, unique, entertaining app will be shown during the conference and the winner will get Nexus tablet!

Not coming to Devconf? Doesn't really matter, you still have a chance to participate, your app will be shown and conference and you will get your price as well as invitation for Devconf next year!

Here's what I did

$ yum install docker
$ docker pull mattdm/fedora

and I waited and waited ..

Well, thankfully I'm not that patient, so I interupted that, looked for docker help to figure that this is really not *that* docker

So this is a note to myself

file /usr/bin/docker from install of docker-io-0.7.0-14.fc19.x86_64 conflicts with file from package docker-1.5-9.fc19.x86_64

and all I ever wanted is

$ yum install docker-io
$ systemctl start docker.service
$ docker pull mattdm/fedora

Hi everyone,

the Developer Conference 2014 Call for participation is still open. We are seeking for presentations for developers and admins as well as workshops focused on the same group. Last year we've covered several interesting topics from kernel space, developer tools, desktop, midlleware and cloud projects. For the upcoming conference we already have couple interesting people from Fedora community, Red Hatters or developers of other projects.

The conference will be again hosted at Masaryk University in Brno Czech Republic. Last year the attendance was around 600 people and we expect the same number of people this year as well. THe call for papers is open till the end of this month, the schedule will be available around Christmas and the actual conference starts on Friday February 7th.

More info is available on our new and redesigned conference pages

Developer Assistant - 0.7.0 release

If you ever wanted to quickly start a project in a new language and wanted to setup the environment accordingly you will like this project. It is still a very fresh code getting a lot of changes that can already do a lot. Developer Assistant just recently got its upstream page - which lists the most cool features. I've enabled rawhide to get the latest available version
# yum search devassistant --enablerepo=rawhide
One think that I find little confusing is the commend line that uses either devassistant or da command where both seem to do that same thing but da also has da-gui. Also GUI is still missing a desktop entry, so it's little hard to find this new feature of devassistant.

The GUI is the latest addition and it looks neat to me. All presented languages has suboptions based on available assistants - fe. in Python I can have a Flask, Django or GTK3 project. I've tried Flask cos I've been recently playing with it. It's nice that DevAssistant offers me an eclipse project and also installs pydev if I don't have it yet. Also it can login to github with your credentials and create a repo there. I'd love to see fedorahosted support as well :-)

The instalation should be little more verbose. It took some time to get dependencies and install packages and any progress bar would probably be more helpful than "In progress" note. At one point I started to worry that the app is stucked in some dead loop. It's nice that I get all sorts of usefull info after the instalation - eg. how to test the project, where to find more documentation.

My project is up there, packages installed and project is in eclipse. Let's look at some more features of Developer Assistant next time.

Bug reporting in Fedora and bug stats

Just few days ago Richard Marko send a notice to fedora-devel about updates in the bug reporting process for Fedora. To start from its origin ABRT server runs on Fedora now for 9 months and collects anonymous reports from Fedora users and generates nice stats about crashes. It can filter out components, distributions, hot issues (the top priority crashes within last couple days) etc. If you agree after your first crash on Fedora, the reports are uploaded automatically. ABRT uses micro-reports, a simplified backtraces with a hashtag. There are very small but still allow to connect duplicates (though this heurestics will never be perfect it has still a very high probability to find duplicates). For example the top issue for last couple days that many users experienced is a crash in libreoffice thumbnailer. You can see that it has been reported 35935 times! It's crashing on F18, F19 and in rawhide and on all archs (well, the two main ones where people are actually using libreoffice). Anyway, I find this very useful for developers. For years we were wondering how many users are actualy experiencing same crash, whether there is someone who has seen this crash with a different reproducer, with different inputs etc.

So how does reporting work now in Fedora?
Here's my quick summary of Richard's email and my observation. User experiences a crash and gets notified about it. Than he/she hits report button and that's where abrt creates the micro-report, sends it to the abrt server and waits for the reponse. At this point, the issue is either already known and user gets a link to the server where all the above described infomation can be found including a bug number if there is one already. The bug is created when at least one user who experienced the crash hits Report in gnome-abrt to provide aditional data. At this point abrt creates a full report, which includes the traceback, few stats about your system. All data can be reviewed before submitting and needs to be checked by user. After uploading these data, a bug gets created, linked to the abrt server report and maintainer can decide whether he'll fix the issue, talks to upstream about fixing that particular problem or provides a new version that fixes the problem.

What's new with the recent abrt server update is that if the number of crashes reaches certain treshold (originally 20 but I think Richard raised that number already) the bug gets opened even without additional data from user. This is a try to get atention from maintainers early enough to start investigating before even more users hit the same problem. On the other hand, maintainers get a very little data at this point and without a reporoducer and full backtrace, there's not much they can do with it. That said, if you report an issue, please fire up gnome-abrt, input the additional data, try to find reproducer, try to be the nice community member who helps others - developers, maintainer and users :-)

Thank you

Why you should not trust Google

Just a very recent announcement that Google will shut down Google reader made a huge wave around me. Those who are using RSS as their primary source of information are now desperately looking for replacement, others are raising eye brows with "I warned you" face. Just look at the history of Google APIs and projects. I guess almost everyone here was bitten once by a project that you found interesting, started using and than suddenly Google changed API or abandoned that whole thing. I was a heavy google user, I still like some of their tools but I hate that they closed several tools I used

- Google code search was one of them. It was fairly easy to find a code you needed, in a language you preferred. I had also a different use case. It was very easy to find source of the code. I did a lot of hiring in the past and I heavily used Google code search to verify whether the candidate is presenting his own work or whether he's lying. Google code search is gone.

- Google docs API - I build a few apps around Google API. Just to make my life little easier. Well, I'm not really following all google announcement but the API has changed twice since I use it and I'm not able to figure out the recent changes especially to google forms. I stopped using it

- Google finance API is also no longer working as my colleague pointed out

- Google Wave was a nice project, where at least Google allowed community to use sources at the time they closed it. I used that couple times for collaborative document editing. It worked well but I must admit that Google docs do the trick as well. Of course it doesn't support a code syntax highlighting like Wave did

We do that in Fedora as well, we change stuff often, break API, change tooling. I'm worried that sometimes we're trying to solve problems that don't exist and in a sake of something nice, new and shiny we're abandoning tools and API that some people use and it works for them. Please think about them when you do changes.

Hey, the conference is over. It's a huge relief for us organizers! Here's my quick summary about the conference.

The conference had two days and during both days it had almost 600 visitors every day. In 3 main lectures rooms we ran the main session - 11 in a row, 3 in parallel, 2 days - that gave us including the lightning talks 75 talks and altogether with labs and meetings almost 100 sessions. We had 120 speakers who had only 5 minutes to get ready for their talk and 45 minutes to show their best. Talking about it, I have to admit that are presenters did fabulous job! All talks that I've attended were well prepared, presenters were able to answer all questions and you could see that the presentations were done by a real pro's :-)

The labs had also great attendance. Since I was little immobile after a skiing injure I haven't attended these but the feedback I got was positive. Seems that all of them got good attendance and again people got what they've expected – they've learned new stuff.

Few other stats. The visitors came from various locations worldwide, just to name few countries – Slovakia, Poland, Bulgaria, Germany, Russia, Ukraine, Austria, Belgium, France, Switzerland, Italy, Greece, UK, USA but even from India or China.

The visitors ate 600 sandwiches, 600 peaces of pastry and 300 hotdogs :-) We've tried to make sure they are some refreshments available during the whole conference but as always, it disappeared quicker than we've planned. The Saturday party on club Fleda was attended by 400 people and with the live band and great food people really enjoyed.

Big thanks to all volunteers who helped during the event, who helped the presenters with the equipment and made sure they are always on time, who helped on the Fedora and Red Hat booth. Special thanks to Miro Hroncok for bringing a 3D printer to Fedora booth, Ludek Smid and Jarda Reznik for creating the mobile apps for Android and Nokia N9/N900, Sirko Kemter for the graphics of the conference and Peter Borsa who helped me to setup the site. And big thanks to Jiri Eischmann, who was running around whole day long and since I temporary crippled myself was the main contact point for all issues. Jiri, you rock! :-)

Interested to see pictures?