Your SlideShare is downloading. ×
0
Training workinggroupupdatejan28 2013
Training workinggroupupdatejan28 2013
Training workinggroupupdatejan28 2013
Training workinggroupupdatejan28 2013
Training workinggroupupdatejan28 2013
Training workinggroupupdatejan28 2013
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Training workinggroupupdatejan28 2013

95

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
95
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 10/04/12
  • 10/04/12
  • 10/04/12
  • 10/04/12
  • 10/04/12
  • Transcript

    1. Working Group Background‣ Board established working group in November 2012 meeting ‣ http://wiki.openstack.org/Governance/Foundation/02Nov2012BoardMinutes“Mr. Goode led a discussion of the Foundation’s involvement in standards for training. To avoid potential conflicts of interest, the discussion was limited to the formation of a working group to address the issue. The Board agreed to the formation of a working group led by Mr. Collier. The working group will create a proposal on the Board’s involvement in standards for training and present to the Board at a later date.”
    2. January 31s, 2013 Board Update‣ The working group is drafting a proposal for the Board’s review. To ensure the proposal is consistent with the Board’s goals, the framework will be discussed at the February 12th face-to-face Board Meeting in San Francisco.‣ General Direction: Create a new “OpenStack Training” licensing & co- marketing program for training businesses, to supersede the current “Built for OpenStack” program in the training context‣ Biggest unanswered question is whether or not “certifications” should be part of the scope of the new program, and if so, how to implement. Board input needed.
    3. New Licensing Program ApproachProgram Goals & Approach ‣ Generate awareness of the many OpenStack Training options in the ecosystem by creating a targeted co-marketing/licensing program ‣ Empower 3rd parties to promote OpenStack and spread OpenStack knowledge globally by licensing the marks for their use, and by making the program as frictionless as possible. ‣ Protect the OpenStack Brand by implementing quality control measuresProposed Approach to Quality Control (under discussion)1.Require courses cover certain key topics/messages2.Foundation administered post-training student surveys3.Testing for trainers employed by the licensees (still being debated)
    4. Biggest Challenge: Certification / CredentialsMarket Dynamics & Opportunity•There is market demand for “Certification” or “Credential” programs•Analysts have told us a certification program would accelerate adoption•Rackspace has launched “Rackspace Certified Technician for OpenStack”offering under the “Built for OpenStack” licenseComplications•The “Built for OpenStack” program was not optimized for this use case•If the market is flooded with many “certifications for OpenStack”, the meaningmay be lost and the OpenStack brand may be tarnished•If the new “OpenStack Training” licensing program covers “Certified” offerings,creating standards will be challenging and likely require a large resourcecommitment from the Foundation.•The word “Certified” has special meaning in the trademark world
    5. Biggest Challenge: Certification / CredentialsMarket Dynamics & Opportunity•There is market demand for “Certification” or “Credential” programs•Analysts have told us a certification program would accelerate adoption•Rackspace has launched “Rackspace Certified Technician for OpenStack”offering under the “Built for OpenStack” licenseComplications•The “Built for OpenStack” program was not optimized for this use case•If the market is flooded with many “certifications for OpenStack”, the meaningmay be lost and the OpenStack brand may be tarnished•If the new “OpenStack Training” licensing program covers “Certified” offerings,creating standards will be challenging and likely require a large resourcecommitment from the Foundation.•The word “Certified” has special meaning in the trademark world

    ×