<?xml version="1.0" encoding="UTF-8"?>
<proposals type="array">
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-02-18T12:08:39-08:00</created-at>
    <description>Large data centers are growing, and soon some will consume 50MW or more of electrical energy.  The EPA estimated US data center power consumption in 2006 at 60 billion kilowatt hours, or 1.5% of total US power consumption, and predicts a doubling by 2011.   Our efforts as programmers and technologists  will continue this exponential growth.  This will have huge environmental, social, and economic consequences unless we find alternative ways to power our digital economy.

Server sky is a proposal to use the capabilities of Oregon companies such as Solar World, Intel, and Triquint to build large dispersed arrays of ultralight solar powered server satellites and launch them into 6000km earth orbit, between the inner and outer Van Allen belts.

A 50 gram server-sat consists of a thinned 12 inch solar cell, with an efficient  2GIPs processor, terabit solid state disk, and microwave transmitter bonded to the back.  Thousands of server-sats position themselves into dozens of  dispersed three dimensional clouds  (kilometers on a side) using light pressure for thrust and liquid-crystal shutters for trimtab steering.   A server-sat array acts as a large phased array antenna, permitting it to steer thousands of communication beams at receiving stations and communities under its position in orbit, handing off communication and control to the server-sat clouds that follow it in orbit as it passes overhead.

A Russian Dnepr rocket  could place a cylindrical stack of 50,000 server-sats into orbit for $15,000,000, or $300 per server-sat.  If each server-sat displaces 100 watts of ground-based electrical generation, cooling, and power conversion,  it will pay for itself in electrical savings alone in just a few years.  A server-sat will cost more to manufacture than a white-box PC, but it will not need the cases, racks,  cabling, power converters, land, buildings, power lines, and other materials needed to build a ground-based server farm.  Total resource usage is reduced, and the total manufacturing cost may become less than traditional approaches.  A server-sat array provides its own communication infrastructure and can reach the entire inhabited globe.  

Since server-sat arrays operate outside the biosphere, the environmental impact of power generation and heat disposal is close to zero.  Server-sat arrays can grow to practically unlimited size - space is big, and filled with unused solar energy.  In time, new launch techniques, and solar cells made from lunar rock, can greatly reduce the environmental and economic costs of manufacturing and launch.  There is room for 1 trillion server-sats within a 100 millisecond ping time distance from earth. Someday, quintillions of server-sats scattered around the solar system  will perform cluster computation.  

Of course, it will be built on open source technologies with best-of-breed security.  Hopefully, OSbridge participants will have many ideas for protecting the system from criminals.

Earth can return to what it is good at - green and growing things - while space can be filled with gray and computing things.</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>Solar powered server and communication arrays in Earth orbit .

Manufacturing, costs, environmental benefits, security, maintenance, and survivability will be discussed.</excerpt>
    <id type="integer">15</id>
    <note-to-organizers>Wacky - sure.  But the calculations I've done so far are surprising.   And sometimes we need grand visions to help us get out of bed in the morning.

Note - there will probably be 20 people that want to talk about this for hours afterwards, so schedule this before a long meal break.</note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">4</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-18T17:00:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-02-18T12:08:39-08:00</submitted-at>
    <title>Server Sky</title>
    <track-id type="integer">3</track-id>
    <updated-at type="datetime">2009-06-04T15:42:53-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-03-24T10:43:56-07:00</created-at>
    <description>Update: The device isn't completely working but the talk will cover debugging, setting up a build environment, Beagleboard I/O and basics of Linux network drivers.

I will show how I built an embedded system to monitor machines on a small development network using an ARM based Linux machine with a SPI attached network adapter.

The embedded ARM device is a &quot;BeagleBoard&quot;:http://beagleboard.org/ that records the syslogs coming from my development systems and communicates with my &quot;power distribution unit&quot;:http://www.apc.com/resource/include/techspec_index.cfm?base_sku=AP9212 to reboot them automatically if it detects a system oops. My talk will discuss building software for the ARM architecture, writing a Kernel driver for a simple network device and the automation of the system.</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>As a Kernel developer I spend alot of my day looking at syslogs and rebooting systems. So, I set off to automate the process and you, the audience, will get an introduction to building ARM software and network device drivers.</excerpt>
    <id type="integer">61</id>
    <note-to-organizers>This may make for a good tutorial. I could just change the focus to writing a device driver and request everyone brings the requisite hardware.

Thoughts? </note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">3</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-17T15:50:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-03-24T10:43:56-07:00</submitted-at>
    <title>Building an embedded Linux system monitoring device</title>
    <track-id type="integer">3</track-id>
    <updated-at type="datetime">2009-06-16T09:29:12-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-03-30T17:08:38-07:00</created-at>
    <description>The idea for Code-n-Splode grew out of the Women in Open Source BOF at OSCON 2007.  Leading a women-friendly tech group continues to be an exciting ride, and I'm going to share it with you!  The talk will be a &quot;case study&quot;-type format, featuring the following:
- why I felt a woman-focused group was necessary
- how the name came about, if it's not completely obvious
- what belonging to the group has done (or in some cases, not done) for its members
- touchy subjects, such as issues we encountered with having men in the group
- how my reasons for continuing the group have changed over time

There will be a BOF-type get-together to go with this talk for an even less-formal discussion period/recruiting session.  (Free toaster!*)

*joke</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>The idea for Code-n-Splode grew out of the Women in Open Source BOF at OSCON 2007.  I'll talk about my original reasons for starting a women-friendly tech group, how the group is evolving, and what I've learned.</excerpt>
    <id type="integer">115</id>
    <note-to-organizers></note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">5</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-17T11:20:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-03-30T17:08:38-07:00</submitted-at>
    <title>My Grand Experiment:  A Portland Women-focused Tech Group.</title>
    <track-id type="integer">5</track-id>
    <updated-at type="datetime">2009-06-04T15:42:54-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-03-30T17:40:04-07:00</created-at>
    <description>After nearly two years of full-time freelancing, I have learned a lot about maintaining my own website, making backups, managing version control, keeping track of time spent on projects, and invoicing tools. Come to this session where I will share much of what I've learned and present open source tools I have found essential for successful freelancing.

Topics covered:

* How to choose among shared/virtual/dedicated/cloud hosting options.
* Simple, effective options for making regular, local and off-site backups.
* Painless ways to utilize version control.
* Simple time-tracking and invoicing tools.</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>As a freelancer, you must be your own IT department. You are responsible for website hosting, backups, version control, project/time-tracking and invoicing. Finding inexpensive and maintainable solutions for these needs can be quite daunting. In this session, I will present an overview open-source solutions for these needs.</excerpt>
    <id type="integer">116</id>
    <note-to-organizers></note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">4</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-17T11:20:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-03-30T17:40:04-07:00</submitted-at>
    <title>Open Source Tools for Freelancers</title>
    <track-id type="integer">4</track-id>
    <updated-at type="datetime">2009-06-04T15:42:54-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-03-31T14:22:35-07:00</created-at>
    <description>The GNU Compiler Collection includes compilers for seven languages and supports dozens of architectures and operating systems.  Hundreds of developers are constantly improving GCC by implementing new language features, porting to new processors, and adding new optimizations to make your application run faster.  The last few releases have included many interesting changes, with many more new developments in the works for upcoming releases.</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>The GNU Compiler Collection keeps getting better.  Learn about new functionality and nifty optimizations that have been added in the last couple of years and hear about what's on the horizon.</excerpt>
    <id type="integer">138</id>
    <note-to-organizers></note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">8</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-17T15:50:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-03-31T14:22:35-07:00</submitted-at>
    <title>What's New in GCC</title>
    <track-id type="integer">1</track-id>
    <updated-at type="datetime">2009-06-16T16:14:12-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-04-10T12:37:19-07:00</created-at>
    <description>This is a three-part presentation, beginning with an introduction of my personal experiences with open source:

- early exploration of open source software
- technical journey, from sales to support, administration and finally, engineering
- the danger of &quot;laying low&quot;
- challenges and successes
- how failure led to the need for inspiration
- how inspiration led to community

The second section will explore the community I've discovered:

- local groups for women in tech
- vast resources on the web
- support and recognition within the sub-community of women in tech
- what's next?

The last section invites the attendees to participate:

- Q &amp; A
- Invitation to share women-in-tech events
- Invitation to share additional experiences
- Comments and suggestions

The entire presentation gives voice to my own experience but more precisely how I believe it parallels that of many women in technology: we think ourselves on the fringe, but in fact, we are active participants in an ever-growing community.</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>As a long-time user of open source software, I've often considered myself an advocate but not necessarily a participant. Over the last year and a half, my own search for technical inspiration has led me full-circle to the realization that I'm an active member of a vibrant community of technical women.</excerpt>
    <id type="integer">213</id>
    <note-to-organizers>While I think I'm more than capable of leading a 45 min session, it might be great if this proposal is pieced together with other presentations as part of a panel, and I could trim it back a bit to fit such a framework if there's need.</note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">4</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-18T15:50:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-04-10T12:37:19-07:00</submitted-at>
    <title>Faking It Til I Make It: A Woman On The Fringe Of Open Source</title>
    <track-id type="integer">5</track-id>
    <updated-at type="datetime">2009-06-04T15:42:55-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-04-10T13:25:50-07:00</created-at>
    <description>The strength of your community is the best predictor of your project's long-term viability. What happens when your community is gradually infiltrated by assholes, who infect everyone else with their constant negativity and personal attacks? Although one person may be a valuable technical contributor, that one person will never contribute as much to the project as the many people who are scared away and demotivated.

How can you defuse these time bombs and prevent your project's destruction? The level of closeness of personal connections between members of your community has a huge impact on the likelihood a conversation will descend into the kinds of personal attacks that send people running from your project. Another key realization is that technical ability and social ability are orthogonal concepts, and both are a requirement for a competent contributor. You can't just have one or the other, and more of one never balances out less of the other.

This talk will teach you about the dramatic impact assholes are having on your organization today and will show you how you can begin to repair it.</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>The strength of your community is the best predictor of your project's long-term viability. What happens when your community is gradually infiltrated by assholes, who infect everyone else with their constant negativity and personal attacks? This talk will teach you about the dramatic impact assholes are having on your organization today and will show you how you can begin to repair it.</excerpt>
    <id type="integer">216</id>
    <note-to-organizers>Audience: everyone involved with a community who cares about it.

I've led discussions on this topic at the Google Summer of Code's mentor summit and for 2 years at BarCamp Portland, </note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">7</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-17T15:50:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-04-10T13:25:50-07:00</submitted-at>
    <title>Assholes are killing your project</title>
    <track-id type="integer">5</track-id>
    <updated-at type="datetime">2009-06-04T15:42:55-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-04-10T15:11:07-07:00</created-at>
    <description>Do you love the idea of an Open Source Development community but frequently find yourself battling:

* Application components that require chmod 777 to work correctly
* The need for a law degree to understand implications of OSI licenses and how they mix and match
* Scattered documentation
* OS Distros that divide up your configuration files
* Cargo Cult mentalities
* Learning to use five different source control systems
* Dealing with communities where developers are highly specialized and not technologists
* Smack talk on the development mailing list and in irc channels
* Meritocracies that aren't
* Benevolent Dictators that aren't so benevolent or competent
* Upgrade paths that require the correct astronomical alignment, a sirocco, and twin albino goats to successfully complete with no data-loss
* And more!

Jennifer Redman, a veteran user of and occasional attempted contributor to Open Source software explores the labyrinth of the community development model and the trials and tribulations of mixing with technically diverse &quot;open&quot;-communities, from a primarily end-user perspective. </description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>Navigating the Darkside of the Open Source Development Community.  A decidedly sarcastic and hopefully humorous look at the dark under-belly of the Open Source Development Culture.</excerpt>
    <id type="integer">223</id>
    <note-to-organizers></note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">5</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-17T17:00:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-04-10T15:11:07-07:00</submitted-at>
    <title>Open Source Development - The Dark Side</title>
    <track-id type="integer">5</track-id>
    <updated-at type="datetime">2009-06-04T15:42:55-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-04-10T16:19:34-07:00</created-at>
    <description>Many software projects suffer from long release schedules, feature freezes, painful QA processes, awkward merges, version number debates, backwards compatibility paralysis -- oh, and customers who aren't completely delighted.

Project management doesn't have to be this way.

Several real-world projects have solved these problems with a combination of iteration, refactoring, continual improvement, reflection, and low-ceremony processes.  The solutions aren't all simple or easy, but they're easy to understand, and they're within your grasp.  This talk will tell you what's possible and recommend concrete steps to improve your project management.</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>Many people see project management as the art of trying to please everyone and pleasing no one, while trying not to go too far over deadline and too far over budget.  It doesn't have to be that way.  Good project management can be so predictable and reliable that it's almost boring.  Here's what works in real projects.</excerpt>
    <id type="integer">229</id>
    <note-to-organizers>This is a variant of my &quot;Failure!&quot; talk from last year (given at PDX.pm, OSCON, and YAPC), with a different focus.  In particular, I want to talk about what to do instead of what not to do.  It also applies to community-driven and internal projects, though I'm not sure how to describe that in the description.  Perhaps an &quot;intended audience&quot; blurb would help.</note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">8</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-18T15:50:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-04-10T16:19:34-07:00</submitted-at>
    <title>Project Management Should be Boring!</title>
    <track-id type="integer">1</track-id>
    <updated-at type="datetime">2009-06-04T15:42:55-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-05-08T08:16:40-07:00</created-at>
    <description>Welcome to Open Source Bridge!

Amber Case will be speaking about being a cyborg citizen.

Kurt Von Fink will speak about the hacker business model.</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>Featuring Amber Case, Cyborg Anthropologist, and Kurt von Finck of Monty Program AB.</excerpt>
    <id type="integer">271</id>
    <note-to-organizers></note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">2</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-17T09:00:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-05-08T08:16:40-07:00</submitted-at>
    <title>Wednesday Welcome and Keynotes</title>
    <track-id type="integer">5</track-id>
    <updated-at type="datetime">2009-06-06T15:18:56-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
  <proposal>
    <affiliation nil="true"></affiliation>
    <agreement type="boolean">true</agreement>
    <biography nil="true"></biography>
    <created-at type="datetime">2009-05-08T08:23:12-07:00</created-at>
    <description>A short introduction to unconferences, and session scheduling.</description>
    <email nil="true"></email>
    <event-id type="integer">2009</event-id>
    <excerpt>Welcome to the unconference day.</excerpt>
    <id type="integer">273</id>
    <note-to-organizers></note-to-organizers>
    <presenter nil="true"></presenter>
    <room-id type="integer">2</room-id>
    <session-type-id type="integer">2</session-type-id>
    <start-time type="datetime">2009-06-19T09:00:00-07:00</start-time>
    <status>confirmed</status>
    <submitted-at type="datetime">2009-05-08T08:23:12-07:00</submitted-at>
    <title>Friday Unconference Kickoff &amp; Scheduling</title>
    <track-id type="integer">5</track-id>
    <updated-at type="datetime">2009-06-11T17:11:40-07:00</updated-at>
    <user-id type="integer" nil="true"></user-id>
    <website nil="true"></website>
  </proposal>
</proposals>
