Top Banner
Making Open Core Product Decisions OW2con’13 Yves de Montcheuil @ydemontcheuil
15

Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

Jan 15, 2015

Download

Technology

OW2 Consortium

Open core has become a nasty phrase in some circles. Perched high on the fence that separates open source and proprietary software, the open core model has caused debate ever since it first emerged. Open core companies that enter the market with the best of intentions all too often prioritize their enterprise products (or, more to the point, the financial opportunities that they create) and allowing their communities to slowly decay. The open core model has worked, though…and when it does work, it creates explosive growth for the business, the technology, and its community. With the right leaders and priorities, it is possible to consistently make product decisions that are both profitable and community-friendly. In this session, Yves de Montcheuil from Talend talks about how his company approaches the open core model, where it’s worked, where it’s been surprisingly difficult, and how to maintain community values when divisive commercial opportunities become increasingly hard to resist.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

1  ©  Talend  2013  

Making Open Core Product Decisions OW2con’13  

Yves  de  Montcheuil  @ydemontcheuil  

Page 2: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

2  ©  Talend  2013  

Open Core and Open Source

➜  Open  Source  is  not  a  business  model…  •  Open  Core  is  not  Open  Source,  and  vice  versa  

➜  Open  Source  is  •  A  way  of  developing  soHware  •  A  way  of  providing  soHware  •  A  collaboraIon  philosophy  •  The  “3  (or  4)  fundamental    freedoms”  of  open  source  

➜  No  such  thing  as    “Open  Source  Vendor”  

•  Freedom  0:  The  freedom  to  run  the  program  for  any  purpose.  

•  Freedom  1:  The  freedom  to  study  how  the  program  works,  and  change  it  to  make  it  do  what  you  wish.  

•  Freedom  2:  The  freedom  to  redistribute  copies.  

•  Freedom  3:  The  freedom  to  improve  the  program,  and  release  your  improvements  (and  modified  versions  in  general).  

Page 3: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

3  ©  Talend  2013  

Defining Open Core

➜  Spectrum  of  business  models  •  (No  business  model  –  community  only,  foundaIons)  •  Services  •  Dual  licensing  •  Open  core  •  Proprietary  extensions  •  (Full  proprietary)  

➜  The  first  Open  Core  definiIon  •  JaspersoH’s  then  Director  of    Biz  Dev  Andrew  Lampi[    in  an  August  2009  post    •  GPL  or  not  GPL?  That  is  the    quesIon    

•  Core  is  GPL:  if  you  embed  the  GPL  in  closed  source,  you  pay  a  fee  

•  Technical  support  of  GPL  product  may  be  offered  for  a  fee  

•  Annual  commercial  subscripJon  includes:  indemnity,  technical  support,  and  addiJonal  features  and/or  plaLorm  support  

•  Professional  services  and  training  are  for  a  fee  

Page 4: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

4  ©  Talend  2013  

Benefits of Open Core for User

➜  Freely  usable  enterprise  grade  soHware  •  Bells  &  whistles  •  Including  “non  graIfying”  features,  such  as  UI/wizard  work  

•  Usability  •  UI  consistency,  wizards,  online  help  

•  AdopIon  materials  •  Tutorials,  documentaIon,  etc.  

➜  Supported  and  maintained  by  vendor  •  No  SLA  does  not  mean  no  commitment  

➜  “Upgrade”  path  •  Including  IndemnificaIon  

Page 5: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

5  ©  Talend  2013  

Benefits of Open Core for Vendor

➜  Viral  adopIon  •  Freely  downloadable  soHware  • Word  of  mouth  •  Blogs,  forums,  Twi[er,  etc.  

➜  Community,  contribuIons  •  Community-­‐centric  process  •  Orchestrated  by  vendor  

•  Engaged  users  are  likely  to  donate  back  •  Intangible  contribuIons:  help  others,  test/review  soHware,  etc.    •  Tangible  contribuIons:  code,  extensions,  doc,  tutorials,  features  requests,  etc.    

•  A  strong  community  is  a  must-­‐have  for  any  open  source  project  

Page 6: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

6  ©  Talend  2013  

Beware of Subterfuge

➜ What  Open  Core  is  not  

Page 7: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

7  ©  Talend  2013  

Example of an Open Core Stack

TALEND ENTERPRISE

Big  Data   Data  IntegraIon   ESB  

TALEND OPEN STUDIO for

Big  Data   Data  Quality  

Data  IntegraIon  

MDM            ESB            BPM  

Data    Management  

Big  Data   MDM   Enterprise  IntegraIon  

Data    Services  

TALEND PLATFORMS ➜  Bundles  of  Enterprise  products  ➜  Advanced  features  ➜  PlaInum  support  

➜  Commercial  license  ➜  SubscripIon  model  ➜  Support  included  

➜  Open  source  license  ➜  Free  of  charge  ➜  OpIonal  support  

Page 8: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

8  ©  Talend  2013  

Zooming Inside the Stack

Talend  Plaoorm  for  Data  Management  

SubscripIon,  commercial    

All  of  below,  +    •  Data  quality  &  profiling  •  High  availability    

Talend  Enterprise  Data  IntegraIon  

SubscripIon,  commercial    

All  of  below,  +    •  Deployment  environment  •  CollaboraIve  repository  •  ProducIvity  features  

Talend  Open  Studio  for  Data  IntegraIon  

GPL    

•  Development  environment  •  Graphical  studio  •  All  connectors  &  components  •  Metadata  management  

Page 9: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

9  ©  Talend  2013  

The Trade Offs

➜  “Community”  EdiIon(s)  vs.  “SubscripIon”  EdiIon(s)  •  Terms  may  vary…  need  a  way  to  express  clearly  what  is  each  

➜  Careful  arbitrage  • Weigh  each  feature  •  Contribute  equally  to  both  

➜ Must  maintain  the  balance  •  Fork  as  way  for  community  to  react  

Page 10: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

10  ©  Talend  2013  

Standing on a Narrow Ridge

➜  Permanent  balancing  act  •  Add  too  much  to  Community  EdiIon/too  li[le  to  Enterprise  EdiIon  •  AdopIon  up  •  Conversion  down  

•  Add  too  much  to  Enterprise  EdiIon/too  much  to  Enterprise  EdiIon  •  AdopIon  down  •  Conversion  up  

•  The  key:  keep  the  balance  

Page 11: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

11  ©  Talend  2013  

Examples of Open Core Decisions

SAP  Support  Talend  Open  Studio  for  Data  IntegraJon  

Talend  Enterprise  Data  IntegraJon  

Connectors  included  Metadata  support  

Wizards  Direct  access  to  SAP  metadata  documentaIon  

Page 12: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

12  ©  Talend  2013  

Examples of Open Core Decisions

Teamwork  CapabiliIes  Talend  Open  Studio  for  Data  IntegraJon   Talend  Enterprise  Data  IntegraJon  

Single  user  environment  Export  &  import  capabiliIes  Versioning  

Shared  mulI-­‐user  repository  Lock  mechanisms  Access  rights  

Page 13: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

13  ©  Talend  2013  

Examples of Open Core Decisions

Joblets  Talend  Open  Studio  for  Data  IntegraJon  

Talend  Enterprise  Data  IntegraJon  

Copy/paste  of  job  elements  

Joblets  for  reusability  

Page 14: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

14  ©  Talend  2013  

Examples of Open Core Decisions

Event  Monitoring  in  ESB  Talend  Open  Studio  for  ESB  

Talend  Enterprise  ESB  

Published  database  structure  

Service  AcIvity    Monitoring    Dashboard  

Page 15: Making Tough Open Core Product Decisions. Yves de Montcheuil, Talend.

15  ©  Talend  2013  

Thank You!

Yves  de  Montcheuil  [email protected]    @ydemontcheuil