From Fedora Project Wiki

Line 40: Line 40:
 
* user driven innovation
 
* user driven innovation
 
* fedora, firefox
 
* fedora, firefox
 +
 +
'''COMMUNITY CONSULTING ENGAGEMENT MODEL'''
 +
* What we do
 +
* Who we serve
 +
* How we get value
 +
* How that value is useful to the rest of the company
 +
 +
  
 
[[Category:Community Architecture]]
 
[[Category:Community Architecture]]

Revision as of 17:05, 22 July 2009

Random ideas that we don't want to forget

IDEAS

  • Reward the true open source partners
  • Information should be relevent, standardized, transparent.

TIEMANN

  • development -> test -> production.
  • make d -> t faster, better.
  • make p have fewer problems, supportable and scalable.
  • community consulting in d, t drives value and makes revenue in p acceptable.
  • otherwise, p is a commodity and we lose.
  • leverage open source in non-differentiating areas.

OTHER

  • podcasts/tv/etc in local languages
  • localized spins at every show
  • publications (again localized)
  • ambassadors newsletter
  • local language portals for ambassadors

SALES STUFF

  • revenue vs. bookings
  • gross margin
  • single year bookings
  • gross margins -- software vs. services

RANDOM WISDOM

  • knock down barriers
  • infrastructure of participation
  • weekend projects
  • sustainability of models
  • Fedora = Get There, RHEL = Stay There
  • For any sufficiently advanced computer problem, Linux always provides greatest option value.

OPEN SOURCE FUNDAMENTALS

  • option value and modularity
  • strong community
  • overlap of user and developer
  • user driven innovation
  • fedora, firefox

COMMUNITY CONSULTING ENGAGEMENT MODEL

  • What we do
  • Who we serve
  • How we get value
  • How that value is useful to the rest of the company