Below are the 25 most recent journal entries.


  june.10.2014  09.55 am
Chromium revisited

It's been more than a year since I've had a successful build of Chromium that I was willing to share with anyone else, but last night I pushed out a Fedora 20 x86_64 build of the current stable Chromium. Here's where you can go and get it:

1) Get this repo file: and put it in /etc/yum.repos.d/
2) EDIT - I've signed the packages with my personal GPG key, upon request. This means you also need to download my public key. You can either get it from:
or by running:
gpg --recv-key 93054260 ; gpg --export --armor 93054260 > spot.gpg
Then, copy it (as root) to /etc/pki/rpm-gpg/
cp -a spot.gpg /etc/pki/rpm-gpg/
3) Run yum install chromium chromium-v8

Why has it been so long?

A) I really believe in building things from source code. At the very least, I should be able to take the source code and know that I can follow instructions (whether in an elaborate README or in src.rpm) and get a predictable binary that matches it. This is one of the core reasons that I got involved with FOSS oh so many years ago.

B) I'm a bit of a perfectionist. I wanted any Chromium builds to be as fully functional as possible, and not just put something out there with disabled features.

C) Chromium's not my day job. I don't get paid to do it by Red Hat (they don't mind me doing it as long as I also do the work they _do_ pay me for).

D) I also build Chromium using as many system libraries as possible, because I really get annoyed at Google's policy of bundling half the planet. I also pull out and package independently some components that are reasonably independent (webrtc, ffmpegsumo).

If my schedule is reasonably clear, it takes me about 7-10 _days_ to get a Chromium build up and going, with all of its components. Why did it take a year this time around? Here's the specifics:

AA) I changed jobs in November, and that didn't leave me very much time to do anything else. It also didn't leave me very motivated to drill down into Chromium for quite some time. I've gotten my feet back underneath me though, so I made some time to revisit the problem....

BB) ... and the core problem was the toolchains that Chromium requires. Chromium relies upon two independent (sortof) toolchains to build its Native Client (NaCl) and Portable Native Client (PNaCl) support. NaCl is binutils/gcc/newlib (it's also glibc and other things, but Chromium doesn't need those so I don't build them), and PNaCl is binutils/llvm/clang/a whole host of other libs. NaCl was reasonably easy to figure out how to package, even if you do have to do a bootstrap pass through gcc to do it, but for a very long time, I had no success getting PNaCl to build whatsoever. I tried teasing it apart into its components, but while it depends on the NaCl toolchain to be built, it also builds and uses incompatible versions of libraries that conflict with that toolchain. Eventually, I tried just building it from the giant "here is all the PNaCl source in one git checkout" that Google loosely documents, but it never worked (and it kept trying to download pre-built NaCl binaries to build itself which I didn't want to use).

** deep breath **

After a few months not looking at Chromium or NaCl or PNaCl, I revisited it with fresh eyes and brain. Roland McGrath was very helpful in giving me advice and feedback as to where I was going wrong with my efforts, and I finally managed a building PNaCl package. It's not done the way I'd want it to be (it uses the giant git checkout of all PNaCl sources instead of breaking it out into components), but it is built entirely from source and it uses my NaCl RPMs. The next hurdle was the build system inside Chromium. The last time I'd done a build, I used gyp to generate Makefiles, because, for all of make's eccentricities, it is the devil we understand. I bet you can guess the next part... Makefile generation no longer works. Someone reported a bug on it, and Google's response is paraphrased as "people use that? we should disable it." They've moved the build tool over to something called "ninja", which was written by Google for Chromium. It's not the worst tool ever, but it's new, and learning new things takes time. Make packages, test packages, build, repeat. Namespace off the v8 that chromium needs into a chromium-v8 package that doesn't conflict with the v8 in Fedora proper that node.js uses. Discover that Google has made changes to namespace zlib (to be fair, its the same hack Firefox uses), so we have to use their bundled copy. Discover that Google has added code assuming that icu is bundled and no longer works with the system copy. Discover that Google's fork of libprotobuf is not compatible with the system copy, but the API looks identical, so it builds against the system copy but does not work properly (and coredumps when you try to setup sync). Add all the missing files that need to go into the package (there is no "make install" equivalent).

Then, we test. Discover that NaCl/PNaCl sortof works, but nothing graphical does. Figure out that we need to enable the "Override software rendering list" in chrome://flags because intel graphics are blacklisted on Linux (it works fine once I do that, at least on my Thinkpad T440s, your mileage may vary). Test WebRTC (seems to work). Push packages and hope for the best. Wait for the inevitable bugs to roll in.


I didn't do an i686 build (but some of the libraries that are likely to be multilib on an x86_64 system are present in i686 builds as well), because I'm reasonably sure there are not very many chromium users for that arch. If I'm wrong, let me know. I also haven't built for any older targets.


  february.11.2014  02.38 pm

FOSDEM is pretty much _the_ European community FOSS event. I've been going on and off for a few years now, but in the last few years, it has had a dedicated Legal devroom, and I really enjoy that aspect of it. I spoke in a short session in the Legal devroom on H264 and Cisco's donation of openh264. I thought that talk went okay, but every time I give a new presentation, I immediately realize 10-20 ways I could have improved it (even if I never give that talk again). Afterwards, someone from Mozilla came over to argue that the Cisco release of openh264 was a net win for FOSS and Linux distros, and I think we had to agree to disagree on that point. His point eventually boiled down to "we're losing users to Chrome, we desperately need openh264 to compete", which is a bit like me saying "Fedora is losing users to other distros, we desperately need non-free software to compete". Ahem.

Anyways, I was also on a panel about Governance in FOSS communities, which I thought went well, even if most of us on the panel were not entirely sure whether we were qualified to speak on that topic. :) Karen Sandler had some good questions, as did the audience, and it was a packed room.

Not to take away from any packed room, but FOSDEM has really really outgrown its venue. The Université libre de Bruxelles is nice, and it is free (or mostly free from what I hear), but 3 out of 4 sessions I'd have liked to see were full before I even had a chance. They need a lot bigger rooms (or more days with repeat sessions).

I also brought a Lulzbot Taz 3 3d printer with me, but because I'm an idiot (and assumed an auto-switching power supply), I cooked the power supply in the first hour. Later, we thought we had a working power supply replacement, but it was a 110V (and the Taz 3 really needs a 230V supply). Thankfully, the Fedorans had brought some Rep Rap printers, so we had 3d printing the whole time, just not on the Taz 3 so much. Lesson learned. Lulzbot donated that Taz 3 (and a replacement power supply) to

I had a lot of good hallway discussions with people (there were a larger than normal contingent of US Fedora people around because of, which was a week after FOSDEM, but I opted out this year), and a good sampling of delicious Belgian beer. After FOSDEM, I flew to Prague for two days, to scope out the venues for Flock 2 (Electric Boogaloo).


  october.03.2013  04.13 pm
Changing the GNOME 3.10 lock screen art

I upgraded to the Fedora 20 work-in-progress tree on my laptop recently, and one of the first things I noticed about GNOME 3.10 was the new lock screen. Specifically, this:

My wife walked by, saw it, and asked me "what is that ugly thing on your computer?" I was forced to simply shrug in agreement.

Now, I admit, I do not possess the finest of tastes. My tastes are less caviar and champagne and more bacon and beer, but that's fine for me. I know what I like, and I know that this pink spray is not it. I figured there might be others who don't appreciate the choice of artwork here either, so I took a few moments and figured out how to change it.

If you go into the gnome-control-center (accessible from the top right menu, then clicking the "tools" bubble), then click on "Background", it will open a window where you can change Background and Lock Screen. Clicking on Lock Screen brings up an interface where you can choose from a set of art (either Wallpapers, Pictures, or Colors) that has been hardcoded by the GNOME upstream for your viewing pleasure. Pick one of these pictures and the Pink Panther nightmare is gone.

... but what if you want a custom picture there? I like to customize my desktop. I changed my background to one of the optional F19 backgrounds (the one with the tree frog), and I've been using a custom plymouth plugin for the bootsplash with an animated Hypnotoad for a while now. I found a clever picture of the Futurama splash screen on the internets:

Okay, so maybe that's only funny to me, but I kept thinking that the Pink Volcano reminded me of that. Download a copy of that file (or whatever JPG or PNG you like), and put it into ~/Pictures. Now, it will show up in the gnome-control-center tool when you restart it. Then you can select your custom lock screen.

I can't help but wonder why they do not have a file selector here. Seems like the sort of thing that would be nice. Maybe it is coming soon.

EDIT: Documented using ~/Pictures instead of altering the hardcoded wallpaper XML list.


  september.08.2013  12.10 pm
Fedora running UNDERWATER

I've been very very busy lately writing frantically for the Raspberry Pi Hacks book (OMG deadlines everywhere), but I made a little video to go with one of the hacks, and I thought people might be interested in it.

I painted a Raspberry Pi with NeverWet paint and ran it completely submerged in a container of water, with no case. Running Pidora, of course.

I apologize for the video quality. Cell phone was all I had handy.


  august.19.2013  01.56 pm
Updated scribus packages

At the request of Mo Duffy, I've updated my scribus 1.5 packages to the latest SVN trunk code, and built them for Fedora 18 and 19 (the currently stable releases of Fedora).

I tweaked the layout a bit, but if you want to use these packages, it should be as easy as downloading the new repo file here:

Put it into /etc/yum.repos.d/

Then, yum update scribus.

I mostly do this as a convenience to Mo, but if you poke me politely, I can probably be coerced into updating them from time to time.


  august.16.2013  11.06 am
Running todo list

I've been trying to shove everything that needs doing into a running todo list, but I'm sure I'm missing something.

This is your chance to point out anything that you think I need to do, but haven't done (or shown any signs of doing). No need to point out Chromium, I know about that one.


  august.14.2013  09.13 am

At the end of FUDCon Lawrence, one thing was obvious to me: Bar Camp style conferences were not working for Fedora. Attendance was dropping, we were seeing the same talks over and over again, and we were spending a large chunk of time just shuffling these same talks into a schedule. It was a sort of echo chamber, where the same people presented the same ideas on the same topics, just in a different place and time. I talked this over with Ruth and Robyn and we all agreed that we wanted to try to restart the idea of what a Fedora conference means, and from that came Flock.

We didn't have a lot of time to put Flock together, and that meant that we had to make a lot of quick decisions without the ideal transparency or community involvement. Wherever possible, we tried our best to be open about the process and solicit help from others, but at the end of the day, we had basically 3 months to make the first Flock event happen. We had a guaranteed venue cancel on us after we had started planning around them and had to restart that whole planning process. Thankfully, the College of Charleston (and the fine folks at the Charleston Linux Users Group) volunteered their space, time, and networks for us.

Putting Flock together was one of the most hectic and crazy things I've ever done, and it wouldn't have happened if not for the help of everyone on staff, but especially Ruth Suehle. Ruth was doing so many things behind the scenes to tie all the loose threads together. To put it bluntly, anything at Flock that you liked was probably her handiwork. Her job was mostly a thankless one, but she was always there, trying to make things more awesome up until the final hackfest ended.

Of course, none of this would be possible without Red Hat. Red Hat believed in the idea of overhauling the Fedora conference and funded it at a scale never before thought plausible. They helped us navigate the financial complexities, made it possible for us to involve third party sponsors, purchased/loaned/rented equipment so that we could stream big chunks of the conference over the internet, and gave us carte blanche to put it all together as we saw fit.

I go to a lot of technical conferences every year. I wanted to try to bring some of the nice things that I've seen at other conferences to the Fedora contributors, and to try to bring as many of those contributors together as I could. I'm pretty proud of what we accomplished together. I hope that everyone came away from Flock energized, excited, and ready to work on making the world a better place through Fedora.

Next year, we have an ever bigger challenge for Flock: to do it again, but in Europe. We're going to have a call for bids coming up in the next few weeks, and we're going to be looking to our community to work with us to make an even better Flock for 2014. It is a lot of work, but the end result is worth it.


  july.13.2013  11.39 pm
In Memory of Seth Vidal

Today, I said goodbye to Seth Vidal. Eunice, his partner, asked me to speak at his funeral, on behalf of those of us in the open source community. I've read a lot of fantastic remembrances in the last several days, and honestly, I'd tried and failed to write my own several times. The words just seemed incomplete, that they couldn't do him justice. Nevertheless, last night, I sat down and wrote something that was the best I could do. I wanted to share it with everyone else who could not be at his funeral today.


Seth was a good man, and that is a rare thing in our world. He believed that our world is what we make of it, and he was determined to make it better. He was passionate in his beliefs, but never a zealot. He was brilliant, the sort of brilliance that lights up a room. When I first met him, 15 years ago at a Linux Users Group meeting, I thought to myself that this was someone I wanted to know, someone I wanted to learn from. His flame burned so brightly that you were just drawn to him, you wanted to work with him, and you couldn't turn away. I was lucky enough to have that chance, as a co-contributor to the Fedora community, and eventually, as his manager at Red Hat. I remember giving him problems to solve, difficult problems. You could see him thinking it through, dissecting them, asking questions, and working out solutions, and it was just inspiring. I've read so many stories in the last few days about how he planted seeds in other people, how he inspired others, how he made them better people. He truly cared about everyone (and everything) around him, and would selflessly give of himself, his time, his talents, and his heart. His code is used by millions of people, all over the world, but his generous spirit, his passion, and his caring, that lives on in the hearts and minds of so many. Those seeds that he planted in us all, he contributed without a second thought, representing the purest spirit of open source. To put it simply: his legacy is not only that he made the world a better place, although, he did, but truly that he inspired us all to do the same, and to do it together.

I think it is telling that my favorite memories of Seth are not tied to work or code, but rather, of laughing with him, playing games with him, suggesting books to each other, even listening to him sing Beastie Boys songs in the worst New York accent ever. I remember him comforting me when I was sad, calming me when I was angry, and always, always, being honest with me.

Seth was humble, I think he'd be a bit bothered that I said all that about him.

Carl Sagan once said, "For small creatures such as we, the vastness is bearable only through love." Seth made our corner of the universe bearable with his love, and we all miss him terribly.


  may.23.2013  04.53 pm
Flock deadlines approaching - May 31, 2013

The call for talks (and workshops/sprints/hackfests) for Flock 2013 is due to close on May 31, 2013. We've got some great submissions already, but we really would love some more.

Flock is your chance to present your project or your ideas to the Fedora Community for consideration. Think we should do something differently? This is the forum to do that. Want to influence the future for releases like Red Hat Enterprise Linux and CentOS? It happens in Fedora first. Want to teach others how to do something in Fedora? Propose a workshop. Want to build something new for Fedora? Lead a hackfest!

It is easy and cheap to complain about something, but it is more worthwhile to contribute to solving a problem or making something better. Flock is that chance, and we need you!

To register:
To propose a talk/workshop/hackfest:

For more details on Flock:


  may.07.2013  05.40 pm
Tuesday Notes

Today was the day of "stuff I can't talk publicly about". Sorry.

* Talked with Ruth about Flock hotels, good progress there! She is kicking butt. :D
* Updated matreshka to 0.4.0 in rawhide, now that gcc has a fix for the ada bug that was blocking it. Tagged gcc override into F19, but the buildroot never regenerated... so I will have to keep waiting to rebuild it there.
* Updated perl-Config-IniFiles to 2.79 in f19 and rawhide (Fix test failures with Pod-Simple-3.28)
* Walked 2.5 miles on the treadmill (I need to lose weight!)
* Updated fedora-logos to 19.0.2 in f19 and rawhide, added new Fedora logo specifically for use with GDM login screen in Fedora 19
* Went to last ultrasound appointment with Pam, baby is coming soon. :)
* Updated perl-Gtk2 to 1.247 in F18, added explicit list of provides to resolve bz 960358


  may.06.2013  05.05 pm
Flock Call For Papers (and Registration) is Open!

For eight years, Fedora users and developers have gathered at an event named for them, the Fedora Users and Developers conference (FUDCon). But we’ve grown, and it’s time for a new approach: Flock.

Flock will bring together the Global Fedora communities for three days of scheduled content with one optional day at the end for open hacking. Unlike the barcamp style we've used in the past for FUDCon, Flock will accept submissions in advance for talks, hackfests, sprints, and workshops. The schedule will be built based on the community's votes on those submissions.

This is a Fedora focused event, but we welcome participation from the entire Free Software community. If you have an idea on how we can improve Fedora, we'd love to hear it!

Dates: August 9-12, 2013
Location: College of Charleston (Charleston, SC, USA)

Both pre-registration and talk submissions are now open! Submissions should be for one of the following:

* Talk (45 minutes)
* Hackfest (2 hours)
* Workshop (2 hours)
* Sprint (2 hours)

You may submit as many topics as you feel qualified to deliver.Suggested topics include but are in no way limited to:

* Cloud
* Community
* Design
* Desktop
* Fedora Ambassadors
* Fonts
* Games
* Infrastructure
* Marketing
* Open hardware
* QA
* Security
* Special Interest Groups

Ready to submit a talk or register? Go to
All submissions must be received by May 31, 2013 at 11:59 p.m. ET.


  may.02.2013  04.38 pm
Thursday Notes

* Fixed nightview in rawhide. Still not entirely sure how.
* Enabled a bunch of kernel bug triage CC aliases, with Toshio & Kevin's help
* Did internal manager paperwork stuff
* Pushed julian-voxforge new package updates
* Research possibilities for secret summit project
* More Flock sponsorship work


  may.01.2013  05.31 pm
Wednesday means halfway

* Lots of meetings. LOTS.
* Created new libxdiff to try to eliminate bundling in git and libgit2. Not tested yet, ran out of time.

Feels like an unproductive day.


  april.30.2013  04.33 pm
Tuesday's Notes

* Wrote my monthly internal team status report
* Update librecad to 2.0.0beta5 in the review ticket (and fixed the missing BR: boost-devel)
* Add fixes from librecad to libdxfrw, made new updates
* Had a meeting with Fedora Kernel team and the Sustaining Engineering team, to discuss bug triage
* Converted git-daemon from xinetd to systemd (bz 737183)
* Finished julius-voxforge review
* Posted on flock scheduling concept


  april.29.2013  05.36 pm
Monday (and away we go)

* MOAR Flock sponsor work
* Learned how to recycle old vendor loaner systems
* Push several F19 updates to stable
* Do a legal review on Cosmosmash (looks good, as long as it avoids referring to itself as a clone)
* Learned about dmesg --human (or -H) from Karel Zak's blog post. Aliased it to dmesg on my laptop. :)
* Setup Provides/Obsoletes for musixtex bits in texlive (I hope I did it right, the texlive package is... special)
* Wrote a lengthy funding request for Fedora involvement in a new space (is that cryptic enough for you)
* Lots of internal meetings, scheduled some more


  april.26.2013  08.43 pm
Work From Home Friday

Working from home today. More flock sponsorship stuff, Google is committed at the Gold level (hooray for Ruth!).

* Packaged up the julius-voxforge files for review -
* Looked into nightview again, ghostscript is still broken.
* Discussed kernel bug triage options
* Fixed bug where a few R packages were still using ancient and unnecessary scriptlets.
* Made internal slides to explain Flock to the rest of Red Hat


  april.25.2013  05.04 pm
Thursday's Status

* The 3d printer is no longer printing properly. I thought it might be an incorrect Z-stop height setting, but if so, I can't seem to get it right. Also, the filament keeps getting jammed and the gears just chew it up and it stops printing. :/ Spent an hour or two trying to get it working again, then gave up.
* Fixed bamf in Fedora 19/rawhide
* Fixed gnomint in Fedora 19/rawhide
* Fixed mygui in Fedora 19/rawhide. Remembered why I dislike CMake.
* Fixed skyviewer in Fedora 19/rawhide
* Fixed most of the issues in nightview, ran into some sort of ghostscript bug (already filed:
* Fixed tex-musixtex in Fedora 19/rawhide
* Tried to fix matreshka, got it to build cleanly, but it fails %check... :/ Committed my changes to rawhide, hopefully it will inspire someone else to finish.


  april.24.2013  04.57 pm
Wednesday In Notes

* Got the 3d printer working again! Hooray! It is so touchy.
* Built julius packages for f17-f20. That was only outstanding since October 2012. Whoops.
* libdxfrw reviewd and packaged in Fedora (f17-f20)
* Brainstorming on the future of software that isn't in RPM format
* Looked at fixing dragonegg, looks like it needs
* Looked at LLVM when fixing dragonegg, my eyes hurt now.
* Fedora Packaging Committee Meeting
* More Flock thinking (still waiting on those final dates!)


  april.23.2013  05.48 pm
What I did with my Tuesday

* Last night, I went over to visit Ray Strode (and Mo Duffy) with my Lulzbot AO-101 3D printer. I'd managed to break one of the wires on it, and Ray helped me fix it. It still isn't printing properly, but it's not broken as far as we can tell. It isn't extruding plastic reliably, and I strongly suspect the replacement part that we had to install (that part holds the plastic filament against a gear, and the gear turns to "extrude" the plastic filament into the hot end. Going to try a few more things, but then I'm going to reach out to the manufacturer again. This is my first 3d printer, and while it is very cool, it sure is finicky.

* Asked Kevin Fenzi to create "flockpress@" and "flockinfo@" email aliases.
* Observed (and talked a little) during the Fedora Badges IRC discussion
* Sent more emails to possible Flock sponsors
* Fixed clementine in f19/rawhide -
* Claimed ownership of volpack, revived in f19/rawhide
* Updated amide to 1.0.4 in f19/rawhide -,amide-1.0.4-1.fc19
* Update connman to 1.13 in f19/rawhide -
* Fixed a bug in graphviz (f19/rawhide) where the libgvc.pc file was pointing to a non-existant libgraph
* Fixed flowcanvas (f19/rawhide) so that it builds against graphviz 2.3 (thanks FreeBSD!) -,flowcanvas-0.7.1-10.fc19


  april.22.2013  04.17 pm
Today I ...

* finished the R 3.0.0 rebuild for Fedora 18 - here
* wrote up the initial wiki page for Flock -
* Started reaching out to possible Flock sponsors
* removed all but one SPARC system from my cube
* stayed awake through the entire Staff Meeting!


  april.19.2013  12.48 pm
Spot's Irregular Status Report

Lately, I've felt a lot of frustration and unhappiness, and that has affected me in a lot of different ways. I'm trying to take steps to turn that around, and one of them is to try to write more about what I'm working on or thinking about.

== Fedora 19 ==
Now that the Alpha is done, I'm in the process of updating my laptop to Fedora 19. Wish me luck!

== Flock ==
I've been working closely with Ruth and Robyn to try to put together a new conference for Fedora Contributors, called Flock. We were waiting on the Red Hat budget to finalize before we started, then when that happened, we found out that there was a good chance that we'd have a very nice conference venue donated to us, so we started doing some very initial planning around that. Unfortunately, that venue wasn't applicable over a weekend, so we couldn't use it. We evaluated several sites as possibilities, one of which was Charleston, SC, which was especially compelling because they were also willing to let us use them as a venue space at no cost.

I spent a lot of time looking at how other Linux distributions run their events (Debian, OpenSUSE, Ubuntu), and trying to base Flock in that model.

One of the main goals of Flock is to bring together as many of our contributors as we can to learn, hack, and improve Fedora. As part of this goal, we want to use as much of the budget as we can to cover travel costs for contributors. We're going to need sponsors to help us do this (Red Hat gave us a generous budget allocation, but it will only go so far). I've been working with Ryan Lerch to make a prospectus PDF, and he finished it up last night. We might still tweak it a bit, but the meat should be fine. Here is a link to it:

We had a pretty productive IRC meeting yesterday to discuss Flock, and we setup two mailing lists (flockinfo, for low-traffic announcements about flock, and flock-planning, a high-traffic mailing list for planning the event).

I talked a bit about the format of the conference, where things are mostly scheduled in advance. Luke Macken has been making an improved registration app that can also handle submissions for talks (or other scheduled things like sprints), based on the work that Ian Weller did for FUDCon Lawrence. I also talked about how we wanted all the talks to be live-streamed, with volunteers coordinating questions from IRC and running a clock.

I also brought up the idea of having a "Social Outing" day at Day 3 (the middle of the schedule driven conference), where the Flock attendees could go do something fun together and build new friendships. People really seemed to like that idea a lot. I can't take credit for it, I stole it from DebConf. :)

Several suggestions came out of that IRC meeting that were very useful (and that I like a lot):

* tatica suggested that we have a scheduled split between talks (45min-1hr) and workshops/sprints/mini-hackfests (2 hrs).
I liked that idea, and proposed that we use the morning for talks, then lunch, then after lunch, scheduled workshops/sprints/mini-hackfests. We already wanted to block off two days at the end for unscheduled hacking, this is in addition to that.
* j_dulaney pointed out that we need good quality audio for streaming talks, something that didn't happen very often in Lawrence.
* inode0 suggested that it would be better if the scheduled part of Flock ended on the weekend, so we are strongly considering
August 7 - 13, 2013 for the dates (August 12 and 13 would be optional "hackfest days" with no assigned schedule in advance).

Because we wanted to get something moving on Flock quickly, I wasn't as open or transparent as I could (and should) have been on what was going on. I'll definitely try to do better on that going forward. From here on out, everything is happening on the mailing lists and IRC meetings. :)

== LibreCAD ==
I packaged up LibreCAD and libdxfrw (dependency) for review in Fedora. libdxfrw got reviewed this morning, and it has some items I need to fix up.

== R ==
Over the last several days, I've been working on updating R to 3.0.0 in Fedora. Normally, my position on updating R is that I push updates for new stable releases to all stable branches of Fedora (and EPEL 5 & 6), but with 3.0.0, because of core changes, it requires that all R modules be rebuilt against R 3.0.0. Initially I was going to just do this for rawhide, but then I thought it might be good to do it for Fedora 19 before it releases. I did EL6 too (there are not very many R modules packaged for EPEL, so it wasn't too hard).

In parallel, there is also a bug in the "kmeans" function in R that wasn't fixed until 3.0.0.

As a result, I'm going to push R 3.0.0 to Fedora 18 too, which will also require all R modules in Fedora to be rebuilt. This is trickier than it sounds, since most of these modules are dependent upon each other. In doing the initial round of rebuilds, Pierre and I only found one dependency loop (R-GenomicRanges and R-IRanges), which I fixed with a conditional bootstrapping. R is very good about not having these sorts of circular build dependencies, but when you run the R check routines, they often check for things that are not otherwise dependent for the R module to build. This just means we need to conditionalize some BuildRequires as being only needed for the %check section.

Also, since we cannot chain-build (automatically tag builds into the buildroot, then kickoff dependent builds) in any branch except Rawhide, I have to manually kick off a build, then tag it, and then kick off another build. Takes a while. :)

I also want to rebuild things for EL5, but I can't get R to build in the EPEL-5 buildroot, seems like something might be broken with the EL-5 builders, I need to check into that.

== Enlightenment ==
I'm helping Rahul update some of the core E components to their current releases in Fedora 19 and Rawhide.

== Sponsorship ==
I sponsored a new packager into Fedora this week, Lokesh Mandevar. He packaged up spectrwm for Fedora.

== OpenCASCADE ==
I reached out to the OpenCASCADE upstream and asked them to consider:
* Dropping the wording in their existing license which makes it non-free
* Relicensing to a standard license to make OpenCASCADE GPL-compatible (LGPL is the obvious one, but there are plenty of others).

I got a good response from them, they're going to look into it. I hope this results in a positive outcome, because that codebase is pretty interesting and useful for CAD and 3d printing tools.

== Alien Arena ==
I contacted the Alien Arena upstream and asked them if they would be willing to drop the commercial distribution restriction on their content, and they were willing. They couldn't drop the requirement that the alienarena content not be distributed independently, but it isn't separated in Fedora, and that requirement shouldn't be a problem for us. (The reason they can't drop that requirement is because they purchased licenses for some of their content.) It hasn't happened yet, as far as I can see, but it is a good sign of intent.


  july.25.2012  12.01 pm
Fedora Summer of Open Hardware and Fun!

Today (at 12:00 PM Eastern Daylight Time), we're launching a sweepstakes for our Fedora Contributors called the Fedora Summer of Open Hardware and Fun! We wanted to do something nice to thank our Fedora community for all that they do for Free Software and Content, and we thought that giving away a lot of Open Hardware would be a great way to do that.

We're giving away 220 total hardware units, including:
* [50] OLPC XO 1.75 units
* [150] Raspberry Pi (B) units
* [20] Arduino Uno R3 (assembled) units + choice of shield (8 different shields to choose from)

Unfortunately, we don't have enough hardware to give something to every Fedora Contributor, so this is a sweepstakes, and sweepstakes come with all sorts of rules and restrictions.

This sweepstakes is for Fedora Contributors (defined as users in the Fedora Account System who have signed the FPCA and are in one additional group). There are some geographic and age restrictions, the reason for this is that it is extremely costly and time-consuming to determine whether or not it is possible to run a sweepstakes in a given country. Sweepstakes laws and regulations vary considerably from country to country, and many countries have strict registration requirements and fees associated with running sweepstakes. Other countries simply prohibit sweepstakes entirely. As a result, we are only offering this sweepstakes in countries where we know that the sweepstakes is lawful. We sincerely apologize for any inconvenience this may cause you.

Also, please note that Red Hat employees are not allowed to enter the sweepstakes.

To learn more, read the full sweepstakes rules, and to enter, please go to:

(You can jump straight to the complete legal sweepstakes rules here: )

And now, a quick FAQ:

Q. Hey, it's not summer where I am!
A. That's not a question.

Q. Why does it say Summer when it isn't Summer where I am?
A. Just close your eyes and pretend it is Summer. Think of the warm fuzzy feeling you'll get from winning one of these sweet prizes.

Q. Where did the money come from for this?
A. I'm going to assume you mean that in a specific way, not in the "Daddy, where does money come from way". If you are really asking the more generic question, just watch this video ( For everyone else, the money for this sweepstakes came from a special allocation from the Open Source and Standards group at Red Hat, and did not take away from the normal Fedora community budget in any way.

Q. Why can't Red Hat employees enter? We contribute a lot to Fedora!
A. Because in the eyes of the law, it seems shady when a company runs a sweepstakes and their employees end up winning.

Q. Why is there an age restriction on this?
A. Because it is a sweepstakes, and that's the law. It varies by region, but our app is clever enough to adjust it accordingly.

Q. I am sad that my state/country/unicorporated region prevents me from entering this sweepstakes. Is there anything you can do for me?
A. We feel sad that we have to exclude you. Much sadder than the time that Tasha Yar got eaten by that sentient oil spill. Short of sending you hardware, money, or other legal impossibilities, feel free to leave a comment on this post with a suggestion on how we can make it up to you. Also, feel free to mention your country. If there are hundreds of people left out in the cold in Luxembourg, we might be able to do a legal review and have it added for future sweepstakes eligibility (no promises though).

Q. What about Fedora users?
A. We love you too, but we really wanted to give an extra-special thank you to those Fedora Contributors who take that next step and help us make Fedora better. You can become a contributor and be eligible when we do something like this again, see:

Q. If I win, how will I get my hardware?
A. We'll ship it to you, on our dime. We'll ask the winners for that information later.

Q. I can't decide which hardware I want, can I pick them all?
A. No. You need to pick one. Just one.

Q. Can I enter multiple times?
A. No. (Actually, I think the app will let you re-enter if you change your mind, but only the latest entry will stick.)

Q. How do you choose the winners?
A. Completely at random from all valid entries.

Q. How did you get so many OLPC XO units?
A. The wonderful folks at donated them for us to give away.

Q. How did you get so many Raspberry Pi units?
A. Black magic. Deep black magic.

Q. Why Arduino? It doesn't run Fedora Linux!
A. So what? It's open, its fun, and you can do all sorts of Open Source geekery with it.

Q. Why didn't you choose to give away instead?
A. Our crack team of Fedora experts (okay, me, Robyn, and Ruth) generated a list of hardware, then ranked them by coolness, cost, and availability. Except for the awesome and well dressed folks at, no one had any cool free hardware lying around (although, I offered to put some old SPARC systems in the mix, which was vetoed), so we ended up spending our money on the coolest things we could get the most of at the least cost. We'd love to do this again, so feel free to leave a comment here with your suggestions.

Q. Hey, I'm a hardware vendor and I want to work with you to give away more awesome Open Hardware to Fedora people in the future, who do I contact to help out?
A. Tom Callaway <>

Q. Anyone else you'd like to thank?
A. Why, how nice of you to ask. I'd also like to thank Ruth Suehle & Robyn Bergeron for brainstorming, researching, and generally being awesome to make this a reality. Luke Macken for writing the app code (and making changes at the last possible minute). Mo Duffy for making it simple, clean and beautiful to enter. The wonderful folks at Farnell, Adafruit, Sparkfun, and for all of my export and ordering related questions. Pam Chestek and Erin Dutton, for helping this sweepstakes be fully blessed and legally awesome. Amy Ross, for addressing our many export needs. Kevin Fenzi and the folks on the Fedora Admin team for making sure we had this webapp running, and sitting in the proper location (except for that brief minute where all mainpage traffic was pointing at the webapp, whoopsy!). And of course, Red Hat and OSAS for paying for it all.


  july.02.2012  01.20 pm
Fedora ARM opening

Red Hat is looking to fill an open position to work on Fedora ARM, specifically:

Red Hat's Global Engineering Services (Embedded Linux) team is looking for an installation and configuration software engineer to actively engage with and advance both internal and upstream systems architecture around emerging hyperscale computing platforms. This will involve assisting in the design of scalable installation and configuration solutions as well as the implementation of such features within standard Red Hat software tools . This includes the creation of appropriate new tools as required. In consideration of the technology shift surrounding future systems provisioning and management (especially systems featuring on-chip management controllers), this role will require a certain amount of unconventional design philosophy. The ideal candidate will have experience working with the Fedora and RHEL (Enterprise Linux) community, will understand the emerging market for "hyperscale" computing solutions, and will have a keen interest in advancing the state of the art in the management and provisioning of such systems.

(My Note: This is mostly a userspace role, candidates should have a strong understanding of ARM and ARM assembly.)


Red Hat is also looking for an Embedded Kernel Architect, specifically:

Red Hat's Global Engineering Services (Embedded Linux) team is looking for a Senior/Principal Level Kernel Generalist to actively engage with and advance both internal and upstream architecture development on various next generation Embedded systems. This will involve heavy community involvement with both the Fedora Linux Project, as well as various Enterprise related activities. The ideal candidate will have experience in working with Embedded Linux systems (including but not limited to ARM), and System-on-Chip technologies. Strong experience with new and existing architectures is a plus, as well as experience with libc and uboot.

Primary Responsibilities:

* Participate and collaborate in ongoing technology discussions with partners and upstream contributors for Embedded device specific design and development.

* Assist in the development and upstream kernel integration of Embedded device support additions to Linux.

* Interact with customers, partners and internal team members.

Required skills

Strong background in kernel level development and maintainership capabilities, preferably in Embedded architectures. Existing relations with members of the Linux kernel community are a strong plus.

Prior administrative experience with Fedora Linux is desired. Familiarity with other Linux distributions also desirable.

Some travel may be required.

Education: Completion of a 4 year College or University computer program.

(My Note: This job is more of a traditional Embedded Linux Kernel Hacker role. It also isn't live on the website yet, so if you're interested, just send resumes to me at


  march.30.2012  02.48 pm
The Strong, the International Center for the History of Electronic Games, and the Promised Land

I've been out in Rochester, NY for most of this week. Red Hat has been partnering with RIT for the last year or so to generate, produce and teach Open Source courses (for an example, see ritfloss). I represented Red Hat at the RIT spring career fair, and the rest of the week, we've been meeting with various RIT students and faculty.

But to be honest, the coolest thing was what happened yesterday. One of the key advisors in RIT's open source initiatives is also the scholar in residence with The Strong museum, so he offered to take us over there and get a behind-the-scenes tour. The Strong National Museum of Play is dedicated entirely to "play", including tons of stuff on toys, books, comics, a working carousel and passenger train, and all sorts of kid friendly awesomeness.

All of that is good on its own, but the museum is also home to the International Center for the History of Electronic Games. Or as I now refer to it, the Promised Land. Jon-Paul Dyson, the Director, took me and Luke around the exhibits,then he took us into their archives.

The amount of stuff they have is just mindblowing. These pictures do not do it justice. Luke and I were so stunned that we're lucky we managed to take any pictures at all. Rows and rows of shelves. Shelves with video games in their cases, stacked tight, three sets deep. Loose items of all types. A Power Glove next to a Virtual Boy, besides an original Breakout cabinet.

Shelf after shelf of electronic gaming history. Every game I ever loved or ever wanted to love, here. Ken Williams's name badge from Sierra. A retired World of Warcraft server blade.

A wall of electronic (PC and console) gaming magazines. Every Nintendo Power, in order.

Each shelf? Three rows deep. This picture? Just a few of the shelves.

They had an RIT co-op who was gently and carefully playing a game for about 10 minutes and video recording it for archival purposes. That was a paid co-op, btw. He was a happy dude.

I'm sure I'm doing a terrible job describing this, but it was a mind-blowingly awesome experience. I've been a gamer for my entire meaningful sentient existence, and I never thought I'd see a collection like this. I wish I could have stayed there all day taking pictures of the stuff they had, but we only got a walkthrough. They're also collecting all of the gaming ephemera, everything from E3 swag to the original designer notes. The vast majority of their collection isn't on display (the stuff they do have on display is cool too, but it is just a drop in the ocean).

They had a large arcade's worth of cabinet games too, most of which seemed like they were in the process of receiving some love before going on display. A few pinball tables too.

I wish we had taken more pictures, with a better camera. I wish they would have left me in there to roam the stacks. After the tour, we played in their museum arcade until we ran out of tokens. Just a fantastic experience. I'm brainstorming on how Red Hat and FOSS can help them out, feel free to leave suggestions in the comments.


  february.27.2012  12.04 pm
Red Hat Job Openings in the Fedora Universe

There are currently two job openings at Red Hat for people who wish to work on Fedora.

= Fedora Virtualization Maintainer =
Do you enjoy working with the Fedora community? Are you interested in working with the leading edge of the virtualization stack? We are looking for someone to maintain the core virtualization packages in Fedora!

Responsibilities include:
* Interract with the Fedora community on all things virt (Mailing lists, irc, FUDCon.)
* Virtualization Test Day organization
* Coordinate the Fedora feature process for virtualization features
* Maintain the fedora-virt mailing list
* Maintain the virtualization pages on the Fedora wiki
* Maintain the virtio-win drivers repository
* Maintain the virtualization preview repository for Fedora
* Primary package maintainer for the following Fedora packages:
qemu (qemu-kvm)
gpxe (ipxe)
* Work with the kernel team on kvm specific bugs
* Assist in bugs for related virt packages

Qualified candidates will have experience with:
* C, C++, Linux (kernel and userspace), KVM, qemu

(This opening is not currently live on the Red Hat website as far as I know, so please email me your resume/CV along with a short note about why you think you'd be awesome for this opening. I am _not_ the hiring manager for this position, but it is Fedora focused.)

== Web Application Developer ==

The Fedora Engineering team is looking for qualified candidates to assist us in creating and improving Free Software solutions for the Fedora Community. Fedora only uses Free Software solutions in all of its infrastructure and hosting, and you can help us in that effort. Our infrastructure is mostly driven using Python frameworks, delivering applications and contents over the web to the Fedora user and contributor communities. Travel requirements are minimal, although, participation at relevant conferences and events is expected. This position is a fantastic opportunity to develop new and interesting Free Software and Open Source solutions with a rich community of developers and users. Upstream contributions are an expected part of this position.

Existing team members in this role have created web applications like:
* Bodhi -
* Fedora Packages -
* Fedora Tagger -

These skills are the sort of skills that are desirable, however, it is not necessary that any candidate possess them all.

* Python
* TurboGears
* SQL Databases (especially Postgresql)
* Xapien
* Linux
* Pyramid
* Javascript

A bachelors degree or greater in Computer Science is preferred for this role, although, not necessary if there is extensive expertise in the desired areas for this position.

Candidates would not necessarily be required to relocate for this position.
If you're interested, please apply on the website, and send me an email telling me why you'd be an awesome fit for this position. I am the hiring manager for this position, so you would get the added bonus of working for me. ;)



technorati profile