* definition of open community infra of participation
* what we're looking for: win-win
** satisfy what the contributor is looking for and find a way to make
   that benefit the project
* What the project is looking for
** content and data ownership
** control so you are not locked in
** ability to control infra that is core to devel mission
** ability to parse out management of non-core items while maintaining
   first principles of freedom
** pragmatic without giving up values
* What a contributor is looking for
** support a favorite project/technology
** play with new, cool technology
** gain skills that affect career
** potential for new employment - mmcgrath example
** operate nimbly in ways a start-up can only dream about
** put in sweat/blood in support of freedom values
* How to do it
** figure out what is core-essential, core-non-essential, non-core
*** own your core to the bare metal, core-non-essential to the service
    level so you can tweak, non-core put on PaaS-equivalent
** operate like a freaking open source team - practice TOSW
*** merit
*** default to open
**** only passwords are secret, forget security-through-obscurity
** how to create trust when you may never meet face-to-face?
*** work done
*** talk done
*** remember the critical mission portfolio - no babies are at risk
** segmentize
*** use sudo, groups
*** host things differently to give out access most easily
*** make the admin web interface use available
** Start with bare-minimum
*** Many projects can start with e.g. a DreamHost shared server- you
    can share shell access to many people, menu of things to install,
    inexpensive.
*** Scale up as you need - go from shared to VM/VPS, then upward; let
    people pay-for or donate rev'd up servers. (IFedora example of how
    they identify sponsors.)
** Sponsors
*** People want to donate, find a way they can support your existing
    hosting, supplement, or replace
*** Use this as a way to diversify so the disappearance of one sponsor
    doesn't put the project at risk.
*** E.g. what Fedora, oVirt do
* Examples
** Fedora - core services; CSI; mmcgrath
** oVirt - just start and grow; attract sponsors
* Resources
** tosw.org
** csi
** what do we need here?
* Q&A




Does every open source project need an open infrastructure? Should
root be potentially available to any community member? If you think
"Maybe, yes," come learn how-to and why-to with lessons from Fedora,
oVirt, and other projects.

First, you get the same assurance about data, community support, and ownership of the code that you get using open source in other ways.

Second, it's the best way to build an infrastructure team from the community. Many existing and up-coming sysadmin and devops people want to contribute to open source, but are blocked by the effort of contributing code. An open community infrastructure team is a way to play with the latest technology, earn root via merit, and participate in a global IT team in ways that are even more agile and advanced than many companies can offer, even start-ups.

Third, it provides an assurance to your open source developers and community that the lights will stay on regardless of who are the corporate sponsors. It's clear how they can participate and even provide infrastructure components that continue making the project self-sufficient.


== s1 ==

How to build an open community infrastructure of participation

Karsten Wade, Red Hat

=== s1 notes ===

Introduce myself, topic of presentation.

== s2 ==

Most assurance you can get when your job is keeping the lights on.

{picture}

=== s2 notes ===


== s3 ==

One of the best ways to enable the community to help the project.

{picture}

=== s3 notes ===


== s4 ==

Most assurance you can give that the lights will stay on.

{picture}

=== s4 notes ===


== s5 ==

{picture}

=== s5 notes ===


== s6 ==

{picture}

=== s6 notes ===


== s7 ==

{picture}

=== s7 notes ===


== s8 ==

{picture}

=== s8 notes ===


== s9 ==

{picture}

=== s9 notes ===


== s10 ==

{picture}

=== s10 notes ===




	
== Image notes ==

Slide 1 - http://www.flickr.com/photos/infomatique/5006263970/
Slide 2 - http://www.flickr.com/photos/artefatica/4630519515/
Slide 3 - http://www.flickr.com/photos/puuikibeach/5106738876/
Slide 4 - http://www.flickr.com/photos/sacramentodistrict/5865261080/
Slide 5 - http://www.flickr.com/photos/sarahmworthy/7054636507/
Slide 6 - http://www.flickr.com/photos/madmarv/6194763518/
Slide 7 - http://www.flickr.com/photos/11304375@N07/2818891443/
Slide 8 - http://www.flickr.com/photos/opensourceway/4371000464/
Slide 9 - http://www.flickr.com/photos/artefatica/4827925602/
Slide 10 - http://www.flickr.com/photos/94999676@N00/1217058480/
Slide 11 - http://www.flickr.com/photos/calliope/104603315/
Slide 12 - http://www.flickr.com/photos/alphaxion/2691964551/
Slide 13 - http://www.flickr.com/photos/jonnybrownbill/100388999/
Slide 14 - http://fedoraproject.org/sponsors (screenshot)
Slide 17 - http://apps.fedoraproject.org (screenshot)
Slide 18 - http://theopensourceway.org (screenshot)
Slide 19 - http://www.flickr.com/photos/hyku/920925628/