Chronicling the Fedora Community Area in Millimeters and Pixels

Representing Fedora at the Summit sounded great when I was safely ensconced in my office, chatting on IRC, weeks before the event. But once I approached the booth at the Hynes Convention Center, a horde of heebie-jeebies streaked down my spine screaming, Run away! Run away!.

Face to face, live action conversation? It can’t be paused, reconsidered or erased. Answering direct questions without the luxury of composing my thoughts on paper? Why, oh why hasn’t anyone invented a delete key for my mouth!

During the first full day of booth activities, I retreated behind my cameras to document the constant activity in the Fedora Community area. I photographed attendees visiting the Fedora booth, hanging with Beefy Miracle, and enjoying the mid-afternoon hot dog snack hour. All of the photographs I took during the Summit are posted on my Flickr stream.

fedora booth friends
beefymiracle mustard

I also recorded two talks presented in the Fedora Community area: Ryan O’Hara’s Network Load Balancing for the 21st Century With Keepalived and HAProxy and Dan Allen’s JBoss AS7 on Fedora as well as the server and system installation for the next day’s Fedora ARM demonstration. Once I finish processing the videos, I’ll post them.

Ryan O’Hara Dan Allen

Jon Masters

On Thursday, after Jon Masters' crowd-gathering ARM demonstration, I forced myself to stow the cameras. I took position behind the booth, no camera lenses or laptop to filter my I/O. The gaps in my knowledge soon became apparent.

  1. No, I’m not familiar with the wide variety of acronyms applied to the hardware in the one laptop per per child computer or what version of Fedora it is running.

    Luke Macken saved the attendee from my panicky stare, and now I know it’s an ARM processor, running Sugar on a Stick, and the newest laptop has a much better keyboard.

  2. I don’t know what version of Apache httpd is packaged in Fedora 17

    Tom Callaway fired up a terminal and found the information. 2.2.22.

    And the most popular question at the booth:

  3. How did Beefy Miracle come to be named Beefy Miracle?

    After numerous attempts, I realized I couldn’t succinctly explain the Fedora release naming process steps in the correct order. Ruth Suehle, Sandro Mathys and Tom had to save people from my disordered explanations numerous times. They can iterate the naming process without blinking.

However, I did answer questions regarding one of the new items at the booth, the AS 7 on Fedora 17 flyer. I can recite the commands to install the AS 7 package, start, stop and deploy it, what is and isn’t currently in the packaged profile, what’s on deck to be in updated releases, and where to find help and participate with AS 7 and future packaging goals. I was stumped though when asked about the differences between Fedora and AS 7 versus another distribution and Websphere. I need to brush up on the features of other application servers.

I’m not a well-rounded Fedora representative yet, but manning the booth was a huge kickstart. I learned the answers to tons of questions from the other Fedora representatives and discovered the concerns of potential and current Fedora users. The best thing about volunteering at the booth was meeting so many great people: the conference attendees who visited the booth and the Fedora advocates I had previously only chatted with on IRC. I can’t thank everyone enough times for answering my questions or for sorting through my jumbled explanations.

Oh, there are two questions I can confidently respond to now without pause or consideration because Ruth wrote down the answers.

Yes, it is a Raspberry Pi. No, you can’t have it.

raspberrypi fedora17

If you’d like a specific picture from the Fedora booth in its high-resolution, mega-size version (some are available in large format JPG and some in RAW), just shoot me a message. I’m graphite6 in the Fedora IRC channels.

Molecules and Predators and Arquillian

During the past year Arquillian has matured from a testing harness to a testing platform as it integrates with Selenium, Graphene, Spring, Android and more. In parallel, the Arquillian contributors have channeled their interlanguage and interframework development exploits into an ongoing tale of intergalactic bug extermination. Ike is gathering a crew as he expands into new frontiers. He’s using new tools to hunt for bugs and congifuring weapons with super strong materials to eliminate the bugs.

Crafting the look and feel of Ike, his crew, and their gear has this sci-fi fangirl constantly plotting ways to beam (forgive me, Scotty) the Arquillian platform artwork to the next dimension. However, the platform has diversified so rapidly that I can’t pull off diagrams, icons, and logos during all-night design binges hours before a presentation deadline. Nor does such a draw-and-dash design frenzy do the indvidual extensions, adaptors, and modules the creative and finely polished rendering justice they deserve.

I’m also a bit of a monster after thirty-six hours of no sleep.

Therefore, Arquillian now has a seperate repository where graphics can be conceptualized, drafted, and finalized over multiple iterations. It’s powered by community requests, community contributions, and community feedback.

Initial logo concepts: Graphene and Arquillian Spring Framework extension

Over the past two weeks I’ve been sketching logo ideas for Graphene and the Arquillian Spring Framework extension. I selected the sketches I think have potential and uploaded them for the feedback.

Graphene is designed to enhancement a Selenium project by focusing on rapid development and usability in the Java environment. Graphene takes its name from the semiconducting material composed of a single layer of carbon atoms arranged into a 2D honeycomb lattice. Graphene is one of the strongest materials in existence.

I have to admit, I don’t feel that pencil sketches were great at coveying some of my ideas. Mainly because I realized I really suck at drawing hexagrams.


The next three concepts required lots of hexagrams, so I stopped torturing my eraser and fired up Inkscape.


The Spring extension is Jakob Narloch’s Google Summer of Code project. It injects Spring beans into test cases and supports Spring annotations. Jakob asked for a simple logo, but my disciple went AWOL and I ended up sketching a few, detailed ideas after word webbing like the vocabulary nerd I am.


A Fatal Error. A Problematic Frame. There Goes My Core.

A fatal error has been detected by the Java Runtime Environment:
SIGSEGV (0xb) at pc=0x00007f995359f24d, pid=4003, tid=140296504968960

Translation for mere humans: It’s dead, Sarah. You killed something important-sounding by attempting to build a teeny, tiny little webpage on localhost. Sigh.

Java VM: OpenJDK 64-Bit Server VM (22.0-b10 mixed mode linux-amd64 compressed oops)

Is this an oops my laptop accidentally mixed up some important bits? Or OOPS the official operations processing specialists ARE FROWNING UPON my coding attempts?

Problematic frame:
C  [] Java_org_jruby_cext_Native_freeHandle+0xb7

Oh, so now it’s just problematic not FATAL. Make up your mind already!

Failed to write core dump. Core dumps have been disabled.
To enable core dumping, try "ulimit -c unlimited" before starting Java again.

Core dumps sound bad. They’re always the LAST RESORT in movies. If we detach the rest of the train cars maybe we’ll make the leap across the giant canyon. If we shoot our nuclear reactor out a torpedo tube maybe we’ll kill the bad guys chasing us (but obliterate all life in the Pacific ocean).

Aborted (core dumped)

The heck with the stupid core anyway. Where’s my dilithium crystal virtual machine? Then I could sling shot my laptop around the sun before the terminal would even dare to mention errors to me. Of course, then my laptop would probably learn to cloak itself as well and hide from me. My laptop might not be able to pass the Turing test but I betcha it could score major points on the DSM-IV antisocial personality test.

And I don’t want to hear anything about how one’s computer is a reflection of its user.