From Fedora Project Wiki
No edit summary
 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
= FY09 Goals =
== FY09 Goals ==


These are my personal goals for FY09 (March 2008 - February 2009).  They are related to my [[CommunityArchitecture/Goals| team's goals]] .
These are a combination of my personal goals as well as ''some'' of my [[Community Architecture|team's]] goals for Red Hat's FY09 (March 2008 - February 2009).


A picture is worth 1,000 words.  [http://fedoraproject.org/maps/mirrorlist/f9.all.png Look at Fedora 9's usage in EMEA.]  It is time for us to invest strongly in having a full time community builder and leader over there.
=== EMEA Community ===


= Fedora Goals =
'''''Organize and lead a [[FUDCon:Brno_2008|FUDCon in the Czech Republic]] (Q3, September 2008).'''''
 
* Bring more of Red Hat's Czech Republic engineers into the Fedora community.
== Events and Ambassadors ==
 
'''''Have a large, multi-day FUDCon (hackfest + sessions) in Europe.'''''
* Organize FUDCon as a standalone event in Q3 (Sep - Nov 2008).
* METRICS: Was this event as good or better as the recent US-based FUDCons?  Do a survey similar to the FUDCon Raleigh 2008 survey and compare results.  How many people showed up?  What technical work was achieved?  How much did we spend, and what value did we generate for our money?
* METRICS: Was this event as good or better as the recent US-based FUDCons?  Do a survey similar to the FUDCon Raleigh 2008 survey and compare results.  How many people showed up?  What technical work was achieved?  How much did we spend, and what value did we generate for our money?


'''''Have a presence at the two largest Linux events in Europe.'''''
'''''Have a presence at important Linux events in Europe.'''''
* Fedora presence at [[FedoraEvents/LinuxTag/LinuxTag2008| LinuxTag]] in Q1 (May 2008).
* Fedora presence at [[LinuxTag_2008|LinuxTag]] (Q1, May 2008).
* Fedora presence at [[FedoraEvents/FOSDEM| FOSDEM]] in Q4 (February 2009).
* Fedora presence at [[FOSDEM_2009|FOSDEM]] (Q4, February 2009).
* METRICS: How many new contributors did we sign up at these events?  Were these the best !LinuxTag and FOSDEM shows that Fedora has been to yet?  How much did we spend, and what value did we generate for our money?
* Fedora presence at other important shows as necessary (Q1 - Q4).
* METRICS: How many events did we attend?  How many new contributors did we sign up at these events?  Were these the best LinuxTag and FOSDEM shows that Fedora has been to yet?  How much did we spend, and what value did we generate for our money?  Did we have speaking sessions?


'''''Make the Fedora Ambassadors as self-sufficient as possible.'''''
'''''Discover at least 1 Fedora in the enterprise success story.'''''
* Be the mentor, assistant, and primary point of contact within Red Hat for the [[Ambassadors/SteeringCommittee| Fedora Ambassadors Steering Committee]]  and for all Fedora Ambassadors in EMEA.
* Work with sales engineers and marketing folks to identify a large Red Hat customer who has interest in participating in Fedora.
* Maintain a global event calendar for all Ambassadors worldwide.
* Bring some of that customer's engineers into Fedora in a way that provides them with additional value that they would not otherwise get from their Red Hat subscriptions.
* Have a presence at all important events in Europe.
* Use Fedora to augment their pre-existing Red Hat customer experience.
* Set an example for Fedora Ambassadors about how to organize and run an event.
* Set up a template for an Event Report.
* Have local leaders coordinating every event, with me providing help and budget.
* Train Ambassadors to be Fedora spokesmodels.
* METRICS: Are we growing our contributor base?  How much did we spend, and what value did we generate for our money?  How many events did we attend?
 
== Marketing ==


'''''Contribute to the creation of a Fedora messaging index that can be used worldwide.'''''
'''''Integrate with Red Hat's European sales and marketing endeavors.  Have a Fedora presence at major Red Hat marketing events, when applicable.'''''
* Be accountable for the localization of that messaging index for all major European languages that Fedora supports.
* Attend the Red Hat EMEA Marketing meetings in Munich (Q2, June 2008).


'''''Find and report Fedora success stories throughout Europe.'''''
=== Fedora ===
* Turn these into Red Hat Magazine articles, and work with Corporate Marketing to figure out the best way to share these stories.


'''''Assist PaulFrields with the Fedora 9 go-to-market plan.'''''
'''''Assist [[User:Pfrields|Paul Frields]] in his role as [[FPL|Fedora Project Leader]].'''''
* Ensure that the Fedora 9 go-to-market plan is successfully created and executed.
* METRICS: Is Paul happy and successful in his new role?  Is he getting sufficient support from the [[Community Architecture]] team?


'''''Investigate opportunities to promote Linux, Open Source, and/or Fedora in classrooms and various education curricula.'''''
'''''Investigate opportunities to promote Linux, Open Source, and/or Fedora in classrooms and various education curricula.'''''
* Ensure that there is a Fedora intern program.
* Get the [[Scholarship|Fedora Scholarship]] program up and running.


== Technical ==
'''''Be a catalyst for community-led engineering efforts.'''''
 
'''''Have localized LiveCDs or LiveUSBs of Fedora at every event in Europe.'''''
* Get kickstart files created and approved, and with a local owner of each.
* Get the spins made.
* Mass-produce media when applicable.
 
'''''Be a catalyst for several community-led engineering efforts.'''''
* A [https://fedorahosted.org/liveusb-creator Live USB key tool] .
* A [https://fedorahosted.org/liveusb-creator Live USB key tool] .
* A web-based tool for generating a custom spin of Fedora.
* Investigate potential between Fedora and Amazon EC2.
* Creation of a Fedora/JBoss spin.
* Lead weekly meetings of the [[Websites| Fedora Websites]]  team.


= Red Hat Goals =
=== Leadership ===


'''''Generate at least 1 Fedora in the enterprise success story in Europe.'''''
'''''Make the Fedora [[Ambassadors]] as self-sufficient as possible.'''''
* Work with Europe's sales engineers and marketing folks to identify a large Red Hat customer who has interest in participating in Fedora.
* Be the mentor, consultant, and primary point of contact within Red Hat for the [[Fedora Ambassadors Steering Committee]] and for all Fedora Ambassadors in EMEA.
* Bring some of that customer's engineers into Fedora in a way that provides them with additional value that they would not otherwise get from their Red Hat subscriptions.
* Maintain a global event calendar for all Ambassadors worldwide.
* Use Fedora to augment their pre-existing Red Hat customer experience.
* Set an example for Fedora Ambassadors about how to organize and run an event.
 
* Set up a template for [[Event reports]].
'''''Integrate with Europe's marketing endeavors.  Have a Fedora presence at major Red Hat marketing events, when applicable.'''''
* Have local leaders coordinating every event, with me providing help and budget.
 
* Train Ambassadors to be Fedora spokesmodels.
'''''Bring Red Hat's Czech Republic engineers into the Fedora community.'''''
* METRICS: Are we growing our contributor base?  How much did we spend, and what value did we generate for our money?  How many events did we attend?
* METRICS: What percentage of Red Hat's engineers in Brno have Fedora accounts?  What kinds of things are they contributing to Fedora?
 
'''''Deliver [[CommunityArchitecture/Presentations| Community Strategy]] talk to Red Hat & JBoss folks in Europe.'''''
 
'''''Be the accountant for the CommunityArchitecture team's budget.'''''
* Keep track of total expenses, expenses per quarter, etc.
* METRICS: Did we stay under-budget for each quarter, and for the year?
 
'''''Work with the EMEA sales & marketing organizations in any capacity in which I can be useful.'''''
 
= Personal Goals =


'''''Relocate to Netherlands in Q1.'''''
'''''Provide leadership to various Fedora sub-projects.'''''
* Make sure all immigration, tax, etc. details are sorted out.
* Determine the critical path for success and community leadership in the future, and get the projects to that point.  Then, serve in an advisory role.
* Why the Netherlands?
* [[Marketing|Fedora Marketing]]
* Pretty centrally located in Europe.
* [[FWN|Fedora Weekly News]]
* Most of the events are in the Western part of Europe (France, Switzerland, Netherlands, Belgium, Germany).  From the Netherlands, much of this travel can be done via public transportation.
* [[Websites|Fedora Websites]]
* Some travel will be needed to the Czech Republic.  Not a far trip, and easy to get there 2 or 3 times per year.
* English is (comparatively) widely spoken in the Netherlands.  From a language perspective, the transition will be easy.
* Red Hat already has an office in the Netherlands, so I will not be totally alone.
* It is a short trip to see several of our more prominent European Fedora contributors.
* Laws for bringing a pet from US to EU are pretty easy.


'''''Start learning Dutch.'''''
'''''Lead the [[Community Architecture]] team.'''''
* Make sure we have team and individual goals & metrics, and that we are accountable to them.
* Keep track of [[Accounting|total expenses, expenses per quarter, etc.]]
* Make sure that we have [[Community Architecture meetings|weekly meetings]] that are useful.
* METRICS: Did we stay under-budget for each quarter, and for the year?  Do we have records of all our meetings from the year?

Latest revision as of 23:31, 6 April 2010

FY09 Goals

These are a combination of my personal goals as well as some of my team's goals for Red Hat's FY09 (March 2008 - February 2009).

EMEA Community

Organize and lead a FUDCon in the Czech Republic (Q3, September 2008).

  • Bring more of Red Hat's Czech Republic engineers into the Fedora community.
  • METRICS: Was this event as good or better as the recent US-based FUDCons? Do a survey similar to the FUDCon Raleigh 2008 survey and compare results. How many people showed up? What technical work was achieved? How much did we spend, and what value did we generate for our money?

Have a presence at important Linux events in Europe.

  • Fedora presence at LinuxTag (Q1, May 2008).
  • Fedora presence at FOSDEM (Q4, February 2009).
  • Fedora presence at other important shows as necessary (Q1 - Q4).
  • METRICS: How many events did we attend? How many new contributors did we sign up at these events? Were these the best LinuxTag and FOSDEM shows that Fedora has been to yet? How much did we spend, and what value did we generate for our money? Did we have speaking sessions?

Discover at least 1 Fedora in the enterprise success story.

  • Work with sales engineers and marketing folks to identify a large Red Hat customer who has interest in participating in Fedora.
  • Bring some of that customer's engineers into Fedora in a way that provides them with additional value that they would not otherwise get from their Red Hat subscriptions.
  • Use Fedora to augment their pre-existing Red Hat customer experience.

Integrate with Red Hat's European sales and marketing endeavors. Have a Fedora presence at major Red Hat marketing events, when applicable.

  • Attend the Red Hat EMEA Marketing meetings in Munich (Q2, June 2008).

Fedora

Assist Paul Frields in his role as Fedora Project Leader.

  • Ensure that the Fedora 9 go-to-market plan is successfully created and executed.
  • METRICS: Is Paul happy and successful in his new role? Is he getting sufficient support from the Community Architecture team?

Investigate opportunities to promote Linux, Open Source, and/or Fedora in classrooms and various education curricula.

  • Ensure that there is a Fedora intern program.
  • Get the Fedora Scholarship program up and running.

Be a catalyst for community-led engineering efforts.

Leadership

Make the Fedora Ambassadors as self-sufficient as possible.

  • Be the mentor, consultant, and primary point of contact within Red Hat for the Fedora Ambassadors Steering Committee and for all Fedora Ambassadors in EMEA.
  • Maintain a global event calendar for all Ambassadors worldwide.
  • Set an example for Fedora Ambassadors about how to organize and run an event.
  • Set up a template for Event reports.
  • Have local leaders coordinating every event, with me providing help and budget.
  • Train Ambassadors to be Fedora spokesmodels.
  • METRICS: Are we growing our contributor base? How much did we spend, and what value did we generate for our money? How many events did we attend?

Provide leadership to various Fedora sub-projects.

Lead the Community Architecture team.

  • Make sure we have team and individual goals & metrics, and that we are accountable to them.
  • Keep track of total expenses, expenses per quarter, etc.
  • Make sure that we have weekly meetings that are useful.
  • METRICS: Did we stay under-budget for each quarter, and for the year? Do we have records of all our meetings from the year?
Retrieved from "https://fedoraproject.org/w/index.php?title=MaxSpevack/FY09&oldid=164243"