Belated FOSDEM 2013 trip report

February 12, 2013 in conference, fedora, fosdem, packaging, report

I’ve been to FOSDEM this year (again) and as always it’s been an interesting experience. You meet all kinds of people, you can create new contacts and realize different projects can share some code or at least approaches. This is just going to be a rundown of talks that I’ve seen (or most of them anyway).

(R)evolution of Java Packaging in GNU/Linux

I’ll start with talk Mikolaj Izdebski and myself gave in Java devroom titled (R)evolution of Java Packaging in GNU/Linux, since that resulted in some possible interesting cooperation. The  talk went reasonably well without any hiccups. We could have used more time for discussion and generic talk about Java buildsytems, but oh well. 

After the talk Charles Oliver Nutter (headius @ JRuby/JVM projects) mentioned Sonatype is already running conversion of all jar files to rubygems on their infrastructure. His idea (which seems pretty neat) was to make this for RPMs as well. He got us in touch with Jason van Zyl and it seems if we create conversion tool we might get this to run on their infrastructure. This actually ties in nicely with some work we are doing to improve life for Java developers on Fedora because they’d be able to install unlimited number of different Maven artifacts that could tie in directly to Yum/RPM and companies could limit access to Maven Central repository and just allow these RPMs.

The state of OpenJDK & OpenJDK7u & OpenJDK Q&A

These were talks by Oracle guys giving updates where JVM is going, and how does the schedule look. Nothing too interesting or worrying here, but it seems that Oracle is really trying to put more people working on JVM, plus there’s community participation as well. Mark Reinhold’s prediction was that OpenJDK board will stay the same after reelections in next few months.

Interestingly Q&A at the end of Saturday was waaay more calm than previous years. Maybe that has to do something with community around OpenJDK maturing? :-)

Porting OpenJDK to AArch64

One of the more technical talks about intricacies of simulating hardware that (almost) doesn’t exist. Our Andrews (Andrew Haley and Andrew Dinn) had some hard drive issues but they handled it pretty gracefully. The  trick with jumping between AArch64 and x86 code outside of simulator was quite interesting. Also interesting were notes on register usage by JVM and how number of registers helps or hinders implementations.

Community Management in Meat Space

Talk by our very own Leslie Hawthorn and Lydia Pintscher. Basically it was a quick tutorial for dealing with decision making and problems within communities. A sort of small prelude to Leslie’s keynote. It just had more duct tape :-0

Gentoo Hardened

This talk was done by one of more controversial people (one of co-developers of eudev which got a lot of flaming apparently). Francisco Riera used a volunteer to show various features of hardened kernels (not necessarily SELinux style) in Gentoo, how and why they operate in certain ways. Each change was accompanied with quite nice examples how in non-hardened kernels certain things could be misused. I missed last few minutes due to other talk.


Jeremy Allison talked about history and splitting of of Samba4 from Samba3 codebase. Apparently there was almost a fork due to “old” network filesystem guys and new “let’s create an AD” guys. Code still has samba3 & samba4 source directories but they are merging/cleaning them up. They have a lot of code bundled/developed in Samba4 to ease integration and configuration. KerberosLDAP..the list goes on. Makes me wonder if all of this was *really* necessary. I guess that’s why Jeremy added this bit to one of the slides:

We stopped checking for monsters under our beds when we realized they were inside us.

systemd, two years later

Surprisingly no flamewars. During the talk I (perhaps) understood why Lennart is facing so many of them though. I believe he doesn’t clearly state that “Yes, we reimplemented part of X in systemd so that it’s more reliable. BUT! You can still install that old thing, we won’t break it and you can still configure it”. Prime example for me being acpid, which Lennart replaced just to get power button working. That’s probably fine for 99% of use cases, but on a lot of notebooks acpid is primary way to handle interesting buttons that X knows nothing about (and perhaps we need them to work outside of X)

FreedomBox 1.0

FreedomBox is a project by Eben Moglen and Bdale Garbee, now mostly a software solution running on top of Debian systems to make private and secure communication without dependence on governments. And one important feature: it has to be usable by common people. There were already 2 keynotes about it in previous years. Now it’s slowly coming to 1.0. There was an interesting point about replacing CA infrastructure in webservers with p2p/gnupg trust principles and development of apache module that would be able to authenticate these.

LibreOffice: cleaning and refactoring a giant code-base

I really like where LO is going. They’ve been mostly doing huge cleanups, getting rid of old cruft, German comments etc. Java dependency is going away. They have a healthy community, ood code review/unit test processes. All the right pieces. I can’t wait for when they really start adding new things.

Has GNOME community turned crazy?

Talk about various controversial features developed by Gnome is past few years. Mostly Gnome Shell. Vincent Untz made a good point: Gnome 2.0 was nothing like Gnome 2.3x. However when he asked audience if they thought Gnome 3.0 was ready for release even people who like Gnome shell said no. There were a lot of Gnome people in the audience who were co-answering questions.

The Keeper of Secrets

Our Leslie Hawthorn had a closing keynote, which in my mind was a continuation  of her previous talk. It dealt with handling community participants when they have problems they would like to keep secret while still allowing the community to handle their absence. Most valuable part for me was probably resources & references to other literature. Because let’s face it…you can’t really give a silver bullet generic answer, because each situation is different. I guess it could have been articulated more clearly, because some people in the audience never realized this in my opinion.

Now I can start looking forward to DevConf already.

Moving My Blog to WordPress on OpenShift

February 6, 2013 in dns, fedora, google apps, howto, openshift, wordpress

As you might have noticed I moved my blog from blogger to WordPress instance on OpenShift. And then set-up a new DNS record for my domain to point to this OpenShift WordPress. OpenShift has pretty nifty documentation for how to do it. What might not be obvious is that if you are using Google Apps for Domains, you can easily have point to OpenShift WordPress application (or any other OpenShift app for that matter)

To set this up you can follow these steps:

  1. Go to your Google Apps dashboard 
  2. Go to Domain Settings -> Domain Names
  3. Click “Advanced DNS settings”
  4. Note the login details for GoDaddy (mostly Sign-in name and password)
  5. Click “Sign in to DNS console” and login with previously received information
  6. You should be in main DNS panel, click on <yourdomain>
  7. Look for “DNS Manager” and click “Launch” below a list of your current records
  8. There are 3 parts A records, CNAME (alias) records and MX records
  9. You need to add CNAME so click “Quick add” in CNAME section
  10. First field is subdomain name you want to use. For me that was “blog”
  11. Second field is your domain name (i.e <yourapp>-<yournamespace>
  12. Click “Save zone file” in upper right corner
  13. Now you need to teach rhcloud about this new alias as well so run
    rhc alias add -a <yourapp> --alias blog.<yourdomain>.com
  14. You should be able to see WordPress instance at blog.<yourdomain>.com soon enough
  15. Links within WordPress will be pointing to rhcloud still so let’s fix that…
  16. Login to wordpress (if you do it through your domain you will get SSL certificate errors, this is expected)
  17. Go to Settings -> General
  18. Set “WordPress Address (URL)” and “Site Address (URL)” to http://blog.<yourdomain>.com
  19. You should be done