The Incredibly Fine Balance between Open Source Projects & Open Source Products Harish Pillay Head, Community Architecture and Leadership @harishpillay • [email protected] • [email protected] 

What is an Open Source Project? 

● Idealism to solve a problem Some characteristics of a Project 

● Idealism to solve a problem ● No constraints – should it have a product roadmap? Some characteristics of a Project 

● Idealism to solve a problem ● No constraints – should it have a product roadmap? ● No pain, no gain Some characteristics of a Project 

● Idealism to solve a problem ● No constraints – should it have a product roadmap? ● No pain, no gain ● Ask forgiveness, not permission Some characteristics of a Project 

● Idealism to solve a problem ● No constraints – should it have a product roadmap? ● No pain, no gain ● Ask forgiveness, not permission ● Permissionless innovation Some characteristics of a Project 

● Idealism to solve a problem ● No constraints – should it have a product roadmap? ● No pain, no gain ● Ask forgiveness, not permission ● Permissionless innovation ● Risk taking – no Product Requirements Document Some characteristics of a Project 

● Idealism to solve a problem ● No constraints – should it have a product roadmap? ● No pain, no gain ● Ask forgiveness, not permission ● Permissionless innovation ● Risk taking – no Product Requirements Document ● Fail fast, fail early – learn, grow and evolve Some characteristics of a Project 

What is an Open Source Product? 

Characteristics of Products ● Reduce risk – both yours and your customers 

Characteristics of Products ● Reduce risk – both yours and your customers ● Constrained in that it needs to meet the customer requirements 

Characteristics of Products ● Reduce risk – both yours and your customers ● Constrained in that it needs to meet the customer requirements ● UX/UI finesse 

Characteristics of Products ● Reduce risk – both yours and your customers ● Constrained in that it needs to meet the customer requirements ● UX/UI finesse ● Scalability is important: how would you help the evolution of the product? 

Characteristics of Products ● Reduce risk – both yours and your customers ● Constrained in that it needs to meet the customer requirements ● UX/UI finesse ● Scalability is important: how would you help the evolution of the product? ● Branding: project name <> product name 

Projects and Products Need People 

What about People ● Project people have a different motivations compared with Product people 

What about People ● Project people have a different motivations compared with Product people ● The motivations of being in a project team is significantly different than being a product team 

What about People ● Project people have a different motivations compared with Product people ● The motivations of being in a project team is significantly different than being a product team ● There may be overlaps, but it is few and far between 

What about Licensing? ● Licensing lays the ground rules of how the community can collaborate – sort of a “constitution” 

What about Licensing? ● Licensing lays the ground rules of how the community can collaborate – sort of a “constitution” ● It states the expectations, rules of engagement of all involved in the project 

● Licensing lays the ground rules of how the community can collaborate – sort of a “constitution” ● It states the expectations, rules of engagement of all involved in the project ● Can a project not have a license? What about Licensing? 

● Licensing lays the ground rules of how the community can collaborate – sort of a “constitution” ● It states the expectations, rules of engagement of all involved in the project ● Can a project not have a license? - You could, but not advisable What about Licensing? 

Source Code License Community Free and Open Source Software 

No content

No content

Comments? Harish Pillay [email protected] [email protected] @harishpillay, 9V1HP Open Unlocks The World’s Potential Photo taken 22 Oct 2018 at Red Hat Singapore pantry