An Open Source Approach To
Community Culture
The Road Is The Destination
ben van 't ende
@benvantende
@srijan #SrijanWW
What is InnerSource?
Common open-source development practices
● universal access to development artefacts
● transparent fish-bowl development environment
● peer-review of contributions through organization-wide scrutiny of
contributions
● informal communication channels (e.g., mailing lists, Internet
Relay Chat (IRC) channels)
● self-selection of motivated contributors
● frequent releases and early feedback
● “around the clock” development
@srijan #SrijanWW
Why InnerSource?
@srijan #SrijanWW
Why InnerSource?
@srijan #SrijanWW
Why InnerSource?
@srijan #SrijanWW
Why InnerSource?
@srijan #SrijanWW
Collaboration
● Make collaboration part of the process. Organisation-wide
collaboration and reducing duplicated effort
● Collaboration needs to get into the culture
● Helping other people understand
● Self-healing environment
● The health of the community depends on collaboration
● Base collaboration on standards
@srijan #SrijanWW
Sharing / Transparency
● Require everything to be documented
● Communicating
● Educating
@srijan #SrijanWW
Meritocracy
The open source community values and provides public
feedback, both positive and negative, on contributions and
contributors.
@srijan #SrijanWW
Behavior
● Assholes are Ruining Your Project
● Respect
● Assume best intent
@srijan #SrijanWW
Evolution
The evolution into an “InnerSource” community:
1) Reduce the risks associated with in-house software development and improve
IT security.
2) Foster greater accountability and a culture of meritocracy amongst the in-
house software developers.
3) Identify and target in-house developer talent faster and more effectively.
4) Create more of an internal market for IT skills, which is focused on problem
solving.
5) Provide metrics for remuneration and bonuses to become far more result
driven.
6) Promote more effective cross-organisational learning, and greater transfer of
knowledge and skills.
7) Support innovation in core practice.
@srijan #SrijanWW
Challenges
● Mindset
● Long term versus short term
● Workplace ethos
● Social responsibility
ben van 't ende
@benvantende
Thank You!
Take this conversation online by tweeting using the hashtag #SrijanWW

[Srijan Wednesday Webinars] InnerSource: An Open Source Approach to Community Culture

  • 1.
    An Open SourceApproach To Community Culture The Road Is The Destination ben van 't ende @benvantende
  • 7.
    @srijan #SrijanWW What isInnerSource? Common open-source development practices ● universal access to development artefacts ● transparent fish-bowl development environment ● peer-review of contributions through organization-wide scrutiny of contributions ● informal communication channels (e.g., mailing lists, Internet Relay Chat (IRC) channels) ● self-selection of motivated contributors ● frequent releases and early feedback ● “around the clock” development
  • 8.
  • 9.
  • 10.
  • 11.
  • 12.
    @srijan #SrijanWW Collaboration ● Makecollaboration part of the process. Organisation-wide collaboration and reducing duplicated effort ● Collaboration needs to get into the culture ● Helping other people understand ● Self-healing environment ● The health of the community depends on collaboration ● Base collaboration on standards
  • 13.
    @srijan #SrijanWW Sharing /Transparency ● Require everything to be documented ● Communicating ● Educating
  • 14.
    @srijan #SrijanWW Meritocracy The opensource community values and provides public feedback, both positive and negative, on contributions and contributors.
  • 15.
    @srijan #SrijanWW Behavior ● Assholesare Ruining Your Project ● Respect ● Assume best intent
  • 16.
    @srijan #SrijanWW Evolution The evolutioninto an “InnerSource” community: 1) Reduce the risks associated with in-house software development and improve IT security. 2) Foster greater accountability and a culture of meritocracy amongst the in- house software developers. 3) Identify and target in-house developer talent faster and more effectively. 4) Create more of an internal market for IT skills, which is focused on problem solving. 5) Provide metrics for remuneration and bonuses to become far more result driven. 6) Promote more effective cross-organisational learning, and greater transfer of knowledge and skills. 7) Support innovation in core practice.
  • 17.
    @srijan #SrijanWW Challenges ● Mindset ●Long term versus short term ● Workplace ethos ● Social responsibility
  • 18.
    ben van 'tende @benvantende Thank You! Take this conversation online by tweeting using the hashtag #SrijanWW