• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Finally, you can manage your Google Docs, uploads, and email attachments (plus Dropbox and Slack files) in one convenient place. Claim a free account, and in less than 2 minutes, Dokkio (from the makers of PBworks) can automatically organize your content for you.



Page history last edited by Christopher St. John 12 years, 9 months ago

FUDCon Raleigh 2008 :: 11-13 January 2008 :: Raleigh, NC (NC State University Campus and Red Hat Headquarters)

FUDCon? Bar Camp? Read this First!


FUDCon stands for Fedora User and Developer Conference. FUDCon Raleigh 2008 will be held as a Bar Camp. A Bar Camp is an "un-conference" where people interested in a wide range of issues come together to teach and learn. Unfamiliar with the un-conference format? Here's the idea in a nutshell. Rather than having scheduled speakers, everyone pitches sessions the morning of the Bar Camp. Those sessions are put on a schedule, and lots of little groups form for intense group learning. Everyone is expected to teach, to talk, to participate. Yeah, it's different from a regular conference - but it works!


The idea of an un-conference came together when people realized the best times they were having at conferences were the times between sessions - where people with like interests could meet ad hoc. The goal of Bar Camp is to facilitate this type of interaction for an entire day. We supply the food, the space, the wireless, the projectors - you show up to teach and learn.


For reference, here is last year's FUDCon Bar Camp page -- http://barcamp.org/FudconBoston2007



Planning on attending? PLEASE edit this page and add your name/title/affiliation as you'd like to see it on your badge.


We will get final confirmation as we approach the event itself. Note: we have a limit of 150 participants, but we will create a wait list if necessary.


Current Attendees

  1. Max Spevack, Fedora Project Leader, FUDCon organizer.
  2. Greg De Koenigsberg, Red Hat Community Manager, FUDCon organizer, former Fedora Board member.
  3. Bill Nottingham, Fedora Board member
  4. Seth Vidal, Fedora Board member
  5. Jesse Keating, Fedora Release Engineer, package ninja
  6. Mike McGrath, Fedora Infrastructure Leader
  7. Warren Togami, Fedora Founder, FESCo Member, Rel-Eng, LTSP
  8. Kevin Fenzi, FESCo member, cvsadmin, package-maintainer
  9. Robert 'Bob' Jensen, Fedora Unity founder
  10. Matthew Miller, Boston University Linux Project, random package maintainer, mailing-list whiner, etc.
  11. Ricky Zhou, Fedora Infrastructure/Websites
  12. Michael DeHaan, Cobbler, Func, RH Emerging Technologies Group
  13. Dave Jones, kernel hacker, eater of cheetos.
  14. Tom \"spot\" Callaway, FESCo member, FPC member, Fedora Board candidate, cvsadmin, package maintainer, ninja, ninja rap, go ninja, go ninja, go ninja, go!
  15. Dennis Gilmore, FESCo, Infrastructure, Board, OLPC, and SPARC
  16. Kyle McMartin, kernel hacker, international hacker of mystery
  17. Phillip Rhodes, AggroNinja, Chief Architect - OpenQabal
  18. G.Wolfe Woodbury, tester, enthusiast
  19. Nalin Dahyabhai, developer
  20. Nitin Dahyabhai, developer
  21. Paul W. Frields, Fedora Documentation paratrooper, ninja wannabe, and general gadabout
  22. Jeroen van Meeuwen, Fedora
  23. Jesus M. Rodriguez, developer/user
  24. Ben Williams, Fedora Unity Contributor
  25. Matt Domsch, Fedora Board member, Mirror Wrangler, troublemaker
  26. Will Woods, Fedora QA Lead, bug herder, ne'er-do-well
  27. Paul Wouters, Package Maintainer of crypto and dns related packages, DNSSEC/IPsec/OTR advocate
  28. Mark Hamrick, tester, user
  29. Brenton Leanhardt, developer/user
  30. Steve 'Ashcrow' Milner, developer, package maintainer, user
  31. Karsten Wade, Board bizi, Docs dude, shootin' that trouble
  32. Jef Spaleta, Fedora Board member
  33. Russell Harrison, tester, user
  34. Clint Savage, Fedora-Tutorials.com, Utah Open Source Foundation
  35. Chris Tyler, Seneca College, Fedora Daily Package, 'Fedora Linux' author
  36. Will Cohen, developer
  37. Luke Macken, Fedora developer
  38. Jared Smith author, trainer, Asterisk evangelist, IT commando
  39. Andy Gospodarek, kernel developer
  40. Josef Bacik, kernel developer
  41. Karl Abbott, developer/user
  42. Mike McLean, Koji developer
  43. Scott Henson, package maintainer, user
  44. Tim Kiernan, digital media designer
  45. Robin Norwood, Fedora developer
  46. Chris Church, Fedora user, Python lover
  47. Adrian Likins, developer
  48. Molly Tamarkin, Fedora user, outgoing IT dean (Duke), incoming CTO (Univ. Puget Sound)
  49. Jason Tibbitts, FESCo member, FPC member, cvsadmin, package reviewer
  50. David Woodhouse, FESCo, PowerPC, OLPC, Promoter of Violence.
  51. Adam Dutko, package maintainer, writer, developer/user
  52. Bascha Harris editor-type geek, Red Hat Magazine
  53. Kevin Sonney programmer/visionary, Percolate
  54. Scott Zekanis sysadmin/head honcho, Percolate
  55. Joe Komenda QA Engineer/Cartoonist, Percolate
  56. Matt Frye business dude, Percolate
  57. John Eckersberg, user and fledgling developer
  58. Chris Negus, Linux author
  59. David Both Fedora user and evangelist
  60. Steve Dickson, Fedora Board Member, Linux Kernel developer
  61. Dimitris Glezos, Localization ninja, Fedora Websites wrangler
  62. Rodney Radford, Tekelec, SDE
  63. Steve Burnett Steve Burnett
  64. John (J5) Palmieri Software Engineer, GNOME Foundation Board Member
  65. Peter Jones some guy
  66. Rob West, FUD
  67. Doug Newcomb, Open Source Geographic Information Systems user
  68. Chris Murphy, Desktop Administrator, Castle Branch Inc
  69. Yaakov Nemoy, Smolt, University of Pittsburgh
  70. John Poelstra, Feature Wrangler
  71. Jeff Layton, kernel developer
  72. Tyler Owen, package maintainer, user, tester
  73. Steve Salevan, Local Music Director @ WKNC, Intern QA Engineer
  74. Satyajit Malugu, user and recent graduate from NCSU
  75. Douglas Warner developer/user
  76. Bob McWhirter, Fedora board member; JBoss.org
  77. David Aquilina, user
  78. Casey Dahlin, user/developer
  79. Jon Stanley, Bug triage/Ambassador
  80. Gavin Romig-Koch, user, developer
  81. Mark Hinkle Community Manager[Zenoss Core]
  82. Grant Gainey, geek
  83. James Laska, Quality Assurance Engineer, installation test
  84. Greg Wallace, Open Source Marketing Guy
  85. Evan McNabb, user / lurker
  86. Dave Wysochanski, developer/user
  87. Jonathan Steffan Fedora
  88. Lee Lorentz, Fedora Infrastructure, Group 3 Marketing
  89. Michael Teal, lurker
  90. Robin 'Roblimo' Miller, press
  91. Matthew Yates, user / lurker
  92. Robin Price, Fedora User / RH Employee
  93. Jack Neely, NCSU Linux Architect
  94. Justin Sherrill, user/closet developer
  95. Will Foster, sysadmin / user
  96. Brad Hinson, zLinux support
  97. Benjamin Kreuter, random developer #3.1415926535897932384626433832
  98. Eric Christensen Fedora User
  99. Tim Kramer, user
  100. Steve Berry, user
  101. Lisa Berry, user
  102. Todd Zullinger, packager, user, pedant, gpg enthusiast
  103. Mike Kolbas, lurker
  104. Zach Cox, Aspiring XO Developer, [http://www.henscratch.org]
  105. Rex Dieter, FPC, KDE-SIG dude. Fri/Sat only.
  106. Chris Lumens, anaconda developer, Red Hat
  107. John W. Linville, kernel wireless networking maintainer
  108. Jeff Ellis, User
  109. Colin Devine, user / observer / doubt eliminator
  110. Maria DiMaio, User, Socialite
  111. Eric Paris, SELinux Nerd / Kernel Hacker
  112. Robert Frank, Fedora User / Developer
  113. James Brown III, Godfather of FOSS
  114. Keith Shaw, user
  115. Sarat Sreepathi, Doctoral Student, North Carolina State University
  116. Pablo Destefanis, FOSS for Development
  117. Nick Goldwater, user
  118. Bill Baroniunas, newbie / user
  119. John Holder, Zimbra Developer Relations
  120. Vamsi Sripathi, MS Student, North Carolina State University
  121. Matthew Opoka, Systems Analyst
  122. Sarah Bacik, user
  123. Scott Dodson, user / SA
  124. Lee Joseph User / Ambassador / KDE-SIG / Fedora-Store-SIG
  125. Scott Lambdin, user / SA
  126. Arjun Roy, Fedora user, CS Student, aspiring developer
  127. Christopher Blizzard Lame Duck Fedora Board Member
  128. Michael Tiemann Open Source Initiator
  129. David Huff, Fedora user, RHX
  130. Clifford Perry, Linux Geek, and long time Red Hat Linux and Fedora user
  131. Michael Spurlock, Linux, UNIX, Mac geek (Admin/Architect)
  132. Ian Hands, Linux Enthusiast / IBM lab lackey
  133. Mary Rozas, Linux Enthusiast
  134. Jeff Johnson, Reverse Engineer
  135. Robert Jackson, Fedora user / RH Employee
  136. Doug Ledford, Red Hat Antique / InfiniBand Monkey
  137. Chris Woodbury, Linux Enthusiast, Open Voting enthusiast
  138. Mark Yarborough, Open source groupie, former coder
  139. Alex Maier Fedora Ambassador
  140. Ruth Suehle editor-type geek, Red Hat Magazine
  141. Bryan J Smith, Senior Consultant, Red Hat GPS US Vertical/Financial (bumped by Continental Airlines, would not make it before Saturday 5pm)
  142. Jonathan Opp, writer, enthusiast
  143. T. Colin Dodd, Truth Happens, writer, enthusiast
  144. Luke Meyer, Gigolo
  145. Owen JH, Linux Geek, blogger, developer.
  146. Russ Dayan, Software Engineer and Fedora Enthusiast
  147. Cristóbal Palmer, student
  148. Ade Lee, user/developer
  149. Matthew S. Wilson, Fedora co-creator, past developer, Anaconda hacker
  150. Cristian Gafton, Past Fedora Leader
  151. Og Maciel, Foresight Linux Developer, GNOME Member
  152. Jitendra Kumar, Student, NCSU.



Got an idea for a session? Don't be shy... add it here.

(If you are interested in leading a session add your name afterwards).


Session Proposals with Owners

  • Annual Fedora State of the Union talk -- Max Spevack
  • Running Fedora from a USB key -- Max Spevack
  • Mass-Deploying Fedora with Cobbler -- Michael DeHaan
  • Func, the Fedora Unified Network Controller -- Michael DeHaan, Adrian Likins (&others?)
  • From code to an RPM -- simple packaging tutorial for dummies -- Tom "spot" Callaway
  • Perl direction (5.10 and beyond) -- Tom "spot" Callaway and Robin Norwood (and others (add your name here)?)
  • Secondary Architectures in F-9 -- Tom "spot" Callaway and Dennis Gilmore (and others(add your name here)?)
  • Developer Guide Reboot -- Paul W. Frields
  • MirrorManager: Getting the bits out -- Matt Domsch
  • Inaugural meeting of the Fedora Mirror Wranglers -- Matt Domsch
  • Integrating DNSSEC -- Proposal and Demonstration of DNSSEC aware software -- Paul Wouters
  • Customizing Fedora Installation Media -- Jeroen van Meeuwen
  • Jigdo/pyJigdo releases -- Jeroen van Meeuwen
  • Anaconda updates during release cycles -- Jeroen van Meeuwen
  • Expiring Updates, Distributing Sources -- Jeroen van Meeuwen
  • Planning Fedora's Summer Coding Projects - Karsten Wade
  • Open Source Development Courses -- Will Cohen
  • Asterisk: What is it, and what can it do for me -- Jared Smith
  • You Too Can Write a Book in XML: An Introduction to Docbook -- Paul W. Frields and Jared Smith
  • GPG Keysigning - see below -- Matt Domsch
  • PackageKit -- Robin Norwood
  • Vaniv -- Kevin Sonney, GDK, and James McDermott
  • Plugging Students into Open Source Communities -- Chris Tyler
  • Fedora Account System 2 -- Mike McGrath and Ricky Zhou


  • K12Linux:Thin Client Support in Fedora -- Warren Togami and Eric Harrison
  • Firmware-Tools: Updating your BIOS and Firmware in Fedora -- Matt Domsch
  • Fedora Infrastructure: What we're about and why you can't have a pony -- Mike McGrath
  • Dr. Transifex: How I Learned to Stop Worrying and Love the Translators -- Dimitris Glezos
  • Open Source Legal Q&A -- Mark Webbink
  • OLPC/XO (or maybe other ultramobiles like the Eee PC) owner meetup? - Adrian Likins
  • Making Fedora Developers More Productive: Step 1, Fedora Infrastructure Unification...Step n, world domination -- John (J5) Palmieri
  • Maintainer Karma: Using karma points to promote maintainers -- Jesse Keating
  • Open Source Geographic Information Systems -- Doug Newcomb
  • Bodhi: The Fedora update system -- Luke Macken
  • TurboGears -- Luke Macken, Toshio Kuratomi, anyone who wants to share TG knowledge
  • Something handwavy about the current state of the Fedora kernel -- Dave Jones
  • Catalyzing the Creative Commons with Sessions@KNC -- Steve Salevan
  • Designing An Open Package Management Solution For Fedora -- Michael DeHaan
  • Fedora Bug Triage/Burried in Bugs - what's wrong and how to fix it (VERY interactive) -- Jon Stanley and John Poelstra
  • Writing simple utilities using the yum python modules -- Seth Vidal
  • Init system town hall: The final word -- Casey Dahlin
  • AJAX Offline: Zimbra Desktop -- John Holder
  • Should companies adopt Fedora as their own home for corp development projects? -- Michael Tiemann
  • State of Linux wireless -- John W. Linville



  • Others? Don't be shy -- put them here.


Sessions that Would Be Nice, but need owners. Claim one, and move it up!



GPG Keysigning


Meet Fedora people face-to-face. Taunt each other over their passport/driver's license photos. Add yourself to the Web of Trust or increase your ranking.


Pre-registration for the keysigning is now over. However, you can still participate.


  • Mandatory: Create a GPG keypair for yourself (if you haven't already)
  • Optional: add your user@fedoraproject.org uid to your keypair
  • Mandatory: Send your key before the event to the subkeys.pgp.net keyserver. Get your KEYID from your keyring as the part following the 1024D/ as follows:


gpg --list-secret-keys | grep ^sec


For Matt, this is 92F0FC09. Yours will be different.


Then send your key to the keyserver with:


gpg --keyserver subkeys.pgp.net --send-keys KEYID


  • Mandatory: If you pre-registered for the keysigning, print out your key fingerprint once and bring it. If you didn't pre-register, print out your key fingerprint 20-50 times, and bring it with you. You'll hand one of these out to each other person at the keysigning, so bring enough. The program 'gpg-key2ps' in the pgp-tools RPM can do this for you quite nicely.
  • Mandatory: run md5sum and sha1sum on the fudcon-keysigning-fingerprints.txt file, print at the results, and bring them to the meeting. It should match the corresponding files on the web site.
  • Mandatory: Bring a government-issued picture ID of yourself


Note: this means you will have at least 2 pieces of paper (your key fingerprint and the sha1sum and md5sum results) that you bring.


At the Keysigning


For those who pre-registered, you can find the keyring, the fingerprint file we'll use, and the md5sum and sha1sum hash of the fingerprint file, all at http://domsch.com/linux/fedora/fudcon2008/. We will read these values, for everyone to confirm they all match.




After the Keysigning

Following the keysigning, you'll need to actually sign people's keys. The easiest way to do this is to use caff which is conveniently packaged in the Fedora pgp-tools package. caff lets you sign a number of keys at once, and will then email each recepient their signed key, encrypted with their key (actually, it sends one email per UID on the target key, so those people with 10 UIDs on their key will get 10 emails from caff, but that's OK - it makes sure they control that email address too). They must know their own passphrase to retrieve their signed key, which they can then import into their gpg keyring and upload to the keyserver subkeys.pgp.net.





We are meeting at the Alumni Club on NCSU Centennial Campus at 9:30 on Friday morning. Map


Hackfest sessions


WE CURRENTLY NEED PEOPLE TO PLAN HACKFEST SESSIONS. Last year we had sessions on packaging, infrastructure, yum, OLPC, QA, and Live CD.


For those who are able to stay over the weekend, we will be running hackfest sessions on Friday and Sunday. Please, if you intend to participate, contact the leader of each session for more information about how you can help.


Core/Extras Merge Package Review

  • Session Leader: TBD
  • General Plan: finish the package review from all packages previously in Core


Package review process brainstorm

  • Session Leader: Jason Tibbitts
  • General Plan: try to come up with ideas for streamlining the package review process. What we put together quickly with the onset of the merge review tide has worked but to many is excessively baroque. Please bring your ideas.


Vaniv hackfest

  • Session Leader: Greg DeKoenigsberg
  • General Plan: Work out remaining details with newly-open-sourced Vaniv (formerly vidpress) codebase before presentation on FUDCon Saturday. Know the wordpress codebase? You are more than welcome to attend and help us out!


Fedora Infrastructure Unification

  • Session Leader: John (J5) Palmieri
  • General Plan: Get a basic framework in place for integrating package views and other infrastructure bits into one place. This includes defining common API's, guidelines and technologies to be used.


Automated MIA Detection

  • Session Leader: Jesse Keating
  • General Plan: Work out methods to auto file bugs so that they can be found later, avoiding duplicate filings, and determine maintainer responsiveness. See where we get to from there.


Func modules

  • Session Leader: Michael DeHaan
  • General Plan: Hammer out a lot of killer Func modules and/or scripts for controlling your favorite apps and admin tools, and then blog the heck out of it. Work on the Func core is fair game too. Bring your ideas! See https://hosted.fedoraproject.org/func/ .


Smolt and Smoon

  • Session Leaders: Mike Mcgrath and Yaakov Nemoy [anyone else?]
  • General Plan: Hack some of the features into Smolt we've been talking about, optimize the database, do peer coding, help write unit tests, any others? See https://fedorahosted.org/smolt/
  • Fill in the wiki with useful information. Does not require any turbogears experience.



  • Session Leaders: Luke Macken & Robin Norwood
  • General Plan: Get PackageKit polished up, integrated, and optimized for Fedora 9. This will most likely entail hacking on the Yum backend (Python) the Gtk frontend (C). Usability / design people needed as well, along with documentation writers.


Wiki Gardening

  • Session Leader: Karsten Wade
  • General Plan: As detailed here, this session is to prune, feed, shred, compost, and replant the wiki. Goals include creating a lightweight information architecture for the Fedora Project to adopt for (in)formal content, define a method to steward and watch pages for sub-projects, and get our hands dirty re-organizing the wiki.


Random kernel hacking.

  • Session Leader: Dave Jones
  • General plan: Myself and Kyle and whoever else is dumb enough to join us will be hacking on 'stuff'. I'm going to bring a bunch of toys, we'll see what happens.


Making F9 on the Eee rock.

  • Session Leader: Dave Jones
  • General plan: F9 should install on this 'out of the box' effortlessly. Lets make it happen.


Designing An Open Package Management Solution

  • Session Leader: Michael DeHaan
  • Contact info: mdehaan AT redhat DOT com , actual mailing list pending
  • General plan: an in-depth group discussion of what needs to go into a general purpose Web based package management tools, what sucks about package management for large install bases today (like, say, colleges, datacenters), and discussion about Pulp (new project on Fedora Hosted Projects), and possibly the start of hacking on a backend for it. Let's design/create something really nice for managing a lot of Fedora machines, all the way up to data center level environments. See also: https://fedorahosted.org/pulp


OLPC/XO exploring/hacking

  • Session Leader: Gavin Romig-Koch
  • Contact info: gavin AT redhat DOT com
  • General Plan: I've just gotten two of these cuties for my kids (and two deserving kids elsewhere in the world), and have I've just started exploring/hacking the software. If there are others who would be interested hacking/exploring with me that would be very cool. If there is interest, I can provide two actual machines, and some "getting started hacking" help. Where we go from there will depend on the who shows and what they want to do. If you want to get some experience, or have some experience with the XO's software that you are willing to share, please contact me as soon as you can.
  • note from Dennis Gilmore I will bring with me my XO's as I work for OLPC i have some insight. I would love to see a fedora 9 XFCE spin for the XO :)


Preupgrade/yum/createrepo hacking

  • Session Leader: Seth Vidal, Will Woods, others
  • Contact Info: skvidal AT fedoraproject.org
  • General Plan: Work on reimplementing preupgrade and writing the gtk interface to it for fedora9. Working on outstanding yum/yum-util features and cleaning up the recent yum-based createrepo.

Info on preupgrade here: http://fedoraproject.org/wiki/Features/PreUpgrade


rrn: Parallel init system

  • Session Leader: Casey Dahlin
  • Contact info: cdahlin@redhat.com
  • General Plan: I've been working on a Prcsys replacement for Fedora that will allow LSB-compliant init scripts to be launched in parallel, with dependency solving and DBus integration. The code is in need of some peer review and a little love, so let's get together and polish it off.


Secondary Archs

  • Session Leader: Dennis Gilmore
  • Contact info: ausil@fedoraproject.org
  • General Plan: finalise writing code and have the first secondary arch deployed


Bug Triage

  • Session Leader: Jon Stanley and John Poelstra
  • Contact info: jstanley@fedoraproject.org
  • General Plan: Begin triaging bugs using the process that we come up with on Saturday
  • Notes: This has to be a Sunday session as policy will not be decided until Saturday.


Fedora 9: Installation Testing

  • Session Leader: James Laska
  • Contact info: jlaska AT fedoraproject DOT org
  • General Plan: Interested in contributing to the stability of the fedora installation process? Come by and discuss your thoughts/concerns about a Fedora 9 Installation test plan. A related topic will be SNAKE, a python based installation tool we're exploring to aid in testing anaconda.


Developer Guide Essentials

  • Session Leader: Paul W. Frields
  • Contact info: stickster AT gmail DOT com
  • General Plan: We want to create a better resource for developers getting started in FOSS using Fedora. These people are the next generation of contributors to our community and they need a centralized, thorough, and informative guide to getting started in our project. What material is stable enough to be moved to an official doc? Please stop by and lend us your thoughts. You need not commit to actually writing anything, but we would LOVE developers to think about the general things they know that need to be passed on.


Hackfest Session

  • Session Leader: YOUR NAME
  • Contact info: YOUR INFO
  • General Plan: link to a page somewhere with the hackfest plan



FUDCon Raleigh 2008


  • Date and time, FUDCon: Saturday 12 January, 8:30 AM-6PM, Hackfest: Fri 11 (9AM-6PM), Sun 13 (9AM-2PM).
  • Location: Red Hat headquarters in Raleigh, NC, on NC State University Centennial Campus
  • Food: Breakfast and box lunches provided on Saturday.


January 12th: FUDPub Raleigh 2008


  • Please join us for drinks after the final session on Saturday. Location, Flying Saucer (328 W Morgan St, Raleigh NC 27601) Time, 6:30PM.
  • Please be aware that the legal drinking age in North Carolina is 21.



What We Need

  • Power strips and extension cords. If you have them, bring them.
  • Video recording equipment. We'd like lots of footage, and we'd like to see it on YouTube.


Wireless Network Information

  • This will be configured to be open and generally completely unsecured for the areas we'll be in for the duration of the event.




Preliminary Schedule for FUDCon Saturday


8:30-9:00Registration and Breakfast, Coffee
9:00-9:30Fedora State of the Union
9:30-10:15Hackfest planning, Session pitches, Social time
10:15-11:10Session 1
11:15-12:00Session 2
1:30-2:25Session 3
2:30-3:25Session 4
3:30-4:25Session 5
4:30-5:25Session 6
5:45-6:00Clean up



Air Travel


Hotel Accommodations

  • We have a group rate at the Brownstone Hotel -- http://www.brownstonehotel.com
  • On their reservations page, click on the "corporate, group, and IATA identification" section and enter the code RED (in capital letters).
  • It is possible to get either single or double rooms. We have a block of 20 rooms reserved for Thursday - Saturday night. If there are a few people who need different nights, that is not a problem.