|
|
Subscribe / Log in / New account

The Linux Plumbers Conference: a summary

LWN.net needs you!

Without subscribers, LWN would simply not exist. Please consider signing up for a subscription and helping to keep LWN publishing

By Jonathan Corbet
September 23, 2008
Back in the early days of Linux, a developer wishing to meet his or her peers at a conference had a relatively small number of alternatives. Two of those - Linux Expo and the Atlanta Linux Showcase - were held in the United States. But it has been a long time since the US has hosted a serious developer-oriented conference - especially for developers who are working on the lower layers of the system. The US-based conferences died out as a result of a combination of a number of factors, including poor management, competition from the Ottawa Linux Symposium and (yes, really) LinuxWorld, and a feeling among certain developers that becoming the next Dmitry Sklyarov would not be a fun way to spend the rest of the year.

There is a certain appeal to overseas events, but that appeal fades more quickly than one might expect. The need for long-haul travel also excludes US-based developers who are unable to arrange funding. So, for some years, [Kristen Accardi] the development community in the US has been wishing for a local conference. More recently, a dedicated group of Portland-based developers led by Kristen Carlson Accardi, with some help from the Linux Foundation, decided to do something about it. The result was the first edition of the Linux Plumbers Conference, held September 17 to 19. Staging this conference in a world which does not lack for conferences was a bit of a risk, and the organizers added a few risks of their own to the mix. Looking back, your editor can say that those risks were well repaid; the first Linux Plumbers Conference was a great success.

The "plumbing" focus of this event was well chosen. While it is still possible to run a system with a bare kernel and a shell as the init process, Linux systems used for real work increasingly have a layer of user-space software tightly wrapped around the kernel. Quite a bit of kernel-based functionality only works properly in the presence of a tightly-coupled user-space component; examples include system initialization, 3D graphics, and much more. The kernel, along with its collection of user-space software, makes up the "plumbing" layer which makes everything else work. Kernel developers have had ample opportunities to get together in recent years, but there has been no concerted effort to bring together the developers for the full plumbing layer until now.

The other significant change made by the LPC organizers was to do away with the "everybody delivers a paper" format used by most conferences. Instead, the conference was planned as a series of 2.5-hour "microconferences," each with a specific focus. Each microconference, which had its own "runner," was able to select its own mode of operation. They generally included a certain number of presentations on relevant topics; in this sense, the microconferences resemble the topic-specific tracks found at many academic gatherings.

Where things differ, though, is that most of the microconferences were explicitly oriented toward discussion and problem solving. The best speakers did not (just) talk about their own project; they raised challenges for the group as a whole to address. It worked spectacularly well. Throughout the event, your editor saw rooms full of people who were fully engaged in the work at hand. The discussions had wide participation, most of the necessary people were generally in the room, and there were relatively few bored people checking email. And, most importantly, a lot of real work got done. Developers came out of the sessions with a clear idea of what needs to be done, agreement with others on how it was to be done, and, sometimes, working code.

So, what did all of these developers talk about?

  • Developers interested in storage talked about the iogrind tool and a number of outstanding problems; some notes from the session have been posted.

  • The Audio microconference covered a wide range of issues; see this LWN article for a summary.

  • A session on tracing saw presentations by developers of a number of competing technologies, followed by a focused effort to design a unified low-level shared relay buffer.

  • The video input session, for all practical purposes, continued on and off through the entire conference; that group of developers, which had never met before, set in motion some major redesign efforts for the Video4Linux layer.

  • The bootstrap and initialization session was dominated by Arjan van de Ven's five-second boot demonstration; having been given that challenge, developers from multiple distributions set about the task of getting their systems to boot quickly.

  • A session on server management looked for solutions to a number of challenges facing Linux administrators.

  • Kernel/user-space APIs were the topic of another lively session which, while perhaps concluding little, raised a lot of issues on how those APIs should be designed.

  • The power management session concluded that the suspend/resume problem is solved ("if you disagree, you bought the wrong hardware") and made progress on a number of other problems; now, they say, all that is left is the coding.

  • The "future displays" session pounded out the path toward kernel-based graphics mode setting and quite a bit more.

  • And the desktop integration session, while reaching "not a lot of conclusions," examined a number of relevant issues; the discussion on Upstart from that session will be covered here separately.

Beyond that, LPC attendees could choose from a handful of more traditional presentations, a provocative keynote from Greg Kroah-Hartman, a rather less provocative kernel [Linus] update from your editor, a git tutorial taught by some guy named Linus, and no shortage of evening celebrations. All told, the Linux Plumbers Conference was one of the most productive, interesting, and generally worthwhile events your editor has been to in quite some time - and your editor has been to rather more than the usual number of events. There will be a lot of interesting developments kicked off by this gathering, once the exhausted attendees get some rest. This conference is off to a good start.

And it is just a start; the organizers are already working on the 2009 edition. It will, once again, be held in Portland. The general format will likely remain the same, but there will be no kernel summit before the 2009 event (the summit will be in October 2009 in Tokyo). Instead, there is a reasonable chance that a more traditional, presentation-oriented conference will be planned to coincide with the 2009 Plumbers Conference. With this new event, the active local community, and the success of this year's conference, LPC2009 looks promising already.

After 2009, the Plumbers team hopes to take a page from the linux.conf.au playbook and pass the event onto a new set of volunteer organizers somewhere else in North America. This form of organization has helped to keep linux.conf.au vital and interesting for many years; it makes sense to do something similar with the Linux Plumbers Conference. Now might be a good time for any North American community which would like to host this event in 2010 to start thinking about how it could be done.

Index entries for this article
ConferenceLinux Plumbers Conference/2008


(Log in to post comments)

The Linux Plumbers Conference: a summary

Posted Sep 23, 2008 22:57 UTC (Tue) by mchehab (subscriber, #41156) [Link]

In the case of the video input session, the major redesign efforts occured not only at V4L layer, but also at DVB. We've just announced the DVB changes:

DVB API changes

The Linux Plumbers Conference: a summary

Posted Sep 24, 2008 7:04 UTC (Wed) by david.kagedal (subscriber, #29249) [Link]

"Overseas events" would, to me, mean that it's probably somewhere in the Americas.

You (and many others) seem to forget that not all your readers are so US-centric.

The Linux Plumbers Conference: a summary

Posted Sep 24, 2008 8:06 UTC (Wed) by mkerrisk (subscriber, #1978) [Link]

"Overseas events" would, to me, mean that it's probably somewhere in the Americas. You (and many others) seem to forget that not all your readers are so US-centric.
David, I think you need to read the article a little more closely. It starts off with a discussion that leads to the point that there has been a dearth of Linux technical conferences in the US. So, the US developers often have had to go "overseas". There is nothing US-centric in those observations: they're jut describing what has been the state of things in an important region of the Linux development community.

The Linux Plumbers Conference: a summary

Posted Sep 24, 2008 10:09 UTC (Wed) by xav (guest, #18536) [Link]

Sorry, I agree with David. I had to re-read the sentence to understand what "overseas" meant in this context.

Overseas

Posted Sep 24, 2008 13:50 UTC (Wed) by corbet (editor, #1) [Link]

Hmm. I was talking very specifically about US-based developers. I had thought that, in that context, "overseas" would be pretty clear.

As far as we can tell, there are more LWN readers outside of the US than within. I spend a good part of every year going to those readers. We all work very hard to adopt a perspective beyond the US - something that, shall we say, people raised in this country are not normally encouraged to do. I am sorry if you didn't like my phrasing there. I can try to do better - I guess one must use absolute coordinates at all times, even when the origin has been made explicit - but it's hard to feel like this was all that big a mistake.

Overseas

Posted Sep 24, 2008 18:56 UTC (Wed) by mkerrisk (subscriber, #1978) [Link]

Hmm. I was talking very specifically about US-based developers. I had thought that, in that context, "overseas" would be pretty clear.
To my mind it was crystal clear. I think you'd have to be actively looking for US-centrism to find it in your article.
As far as we can tell, there are more LWN readers outside of the US than within. I spend a good part of every year going to those readers. We all work very hard to adopt a perspective beyond the US - something that, shall we say, people raised in this country are not normally encouraged to do. I am sorry if you didn't like my phrasing there. I can try to do better - I guess one must use absolute coordinates at all times, even when the origin has been made explicit - but it's hard to feel like this was all that big a mistake.
Hard to see how it was any mistake at all, actually. Keep up the great work Jon.

Overseas

Posted Sep 24, 2008 20:07 UTC (Wed) by dark (guest, #8483) [Link]

Hmm. I did find it confusing, but not US-centric. I was confused because you went from "a feeling among certain developers that becoming the next Dmitry Sklyarov would not be a fun way to spend the rest of the year" to "There is a certain appeal to overseas events". So I thought you were comparing the appeal of overseas events with the risk of traveling to the US -- in order words, looking at it from the point of view of developers like Alan Cox. It took me a few tries to then make sense of the rest of the second paragraph.

Overseas

Posted Sep 25, 2008 13:19 UTC (Thu) by nye (guest, #51576) [Link]

For what it's worth, this was exactly what I was going to say if I could have been bothered :-).

Not exactly a great deal though - nobody's writing is expected to be perfectly clear to everyone all the time.

The Linux Plumbers Conference: a summary

Posted Sep 24, 2008 14:01 UTC (Wed) by clugstj (subscriber, #4020) [Link]

The first paragraph mentions the United States at least 3 times. Our editor lives in the United States. Unless you skipped the first paragraph, I don't see how one could be confused.

I feel that out editor has an excellent command of the English language.

The Linux Plumbers Conference: a summary

Posted Sep 24, 2008 18:57 UTC (Wed) by nix (subscriber, #2304) [Link]

Ah, good, the last line of your comment has sacrificed to the Irony
Fairy ;)

The GIT tutorial

Posted Sep 24, 2008 10:44 UTC (Wed) by alex (subscriber, #1355) [Link]

Did the GIT tutorial get videoed/recorded? It would be nice to see what features Linus uses in the day to day usage to see if there are tricks I'm missing.

The GIT tutorial

Posted Sep 24, 2008 14:48 UTC (Wed) by tnoo (subscriber, #20427) [Link]

There are pictures from his talk, but without narrative they are somewhat hard to
digest.

http://dkukawka.blogspot.com/2008/09/linux-plumbers-conf-...

The GIT tutorial

Posted Sep 24, 2008 15:21 UTC (Wed) by alex (subscriber, #1355) [Link]

It's a shame no one recorded the audio.

Having said that I have just come across a bunch of screencasts done by the github guys which contain some code examples.

http://feeds.feedburner.com/Gitcasts

The GIT tutorial

Posted Sep 25, 2008 15:13 UTC (Thu) by kushal (subscriber, #50806) [Link]

I really can not understand why no video released for this tutorial ?
Videos are a very easy way to send the *developer* across the world.

The GIT tutorial

Posted Sep 24, 2008 20:29 UTC (Wed) by daniel (guest, #3181) [Link]

IMHO the nicest Git trick to learn is Mercurial. Full disclosure: I use both and I had something to do with both of them existing. They are both miles better than the next best thing. But Mercurial has the user interface that Git should have had.

Face to face versus other forms of interaction

Posted Sep 24, 2008 22:21 UTC (Wed) by scripter (subscriber, #2654) [Link]

In the early days of my career, I wondered why software engineers and their managers occasionally traveled when we had email, instant messaging, wikis and video conferencing. Gradually, I've figured out that face-to-face meetings facilitate trust, collaboration and unity more effectively.

For me, the success of this conference re-emphasizes the value of face-to-face communication. Now I'm going to google "why face-to-face".

Suspend/resume is solved? Really?

Posted Sep 25, 2008 14:51 UTC (Thu) by JLCdjinn (guest, #1905) [Link]

The power management session concluded that the suspend/resume problem is solved ("if you disagree, you bought the wrong hardware")

When did this happen? What's the "right" hardware? And how do I make such hardware safely and reliably suspend and resume? Why does "wrong" hardware exist?

Suspend/resume is solved? Really?

Posted Sep 25, 2008 14:54 UTC (Thu) by corbet (editor, #1) [Link]

At the session wrapup, the "wrong" hardware was pretty much defined as "NVIDIA".


Copyright © 2008, Eklektix, Inc.
This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds