Community Architecture ideas

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Check this out -- you are supposed to do links in MediaWiki with spaces in brackets Like this; MW adds the '_' itself. Makes nicer pages easier to obtain, eh?)
Line 22: Line 22:
  
 
'''METRICS'''
 
'''METRICS'''
* [[Community_participation_metrics|Community participation metrics]]
+
* [[Community participation metrics]]
 
* who is participating, project by project?
 
* who is participating, project by project?
 
* how do we drive those numbers?
 
* how do we drive those numbers?

Revision as of 15:56, 16 February 2009

Random ideas that we don't want to forget

IDEAS

STUFF THAT AN APAC COMMUNITY ARCHITECT COULD DO

  • japan intelligence
  • china intelligence
  • apac university tour (interns/contributors)
  • local events
  • knowing which ones matter
  • creating them if necessary
  • apac ambassador summit -- lca 2009??

BIG SHOWS IN APAC

  • india -- foss.in, linux asia
  • japan -- ? (warren, harish)
  • china -- linux foundation event (eugene?)
  • apac -- AOSSS (funded by japanese government)
  • singapore -- singapore linux conf (99,00,01,03, now dead)

METRICS

  • Community participation metrics
  • who is participating, project by project?
  • how do we drive those numbers?
  • what does it mean to participate?
  • patches from outside, bugzilla/trac usage?

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
  • ambassador business cards

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