Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Connected Community Model: Research Finding...

The Connected Community Model: Research Findings and Lessons Learned

Conference: OSCON 2019
Speakers: Diane Mueller and Daniel Izquierdo

The interdependency of open source projects such as OpenShift (OKD) with upstream projects (Kubernetes, OpenStack), downstream services, and related initiatives (operator framework) has changed nature of open source community development. As communities converge and release schedules and priorities collide, project leaders need to adjust OS models, rethink interactions with multiple release cycles, and juggle the divergent agendas.

Diane Mueller and Daniel Izquierdo examine joint research findings from Bitergia and share lessons learned at Red Hat on the interrelatedness of Kubernetes, OpenShift and OKD, OpenStack, and CNCF communities developing around distributions. They also detail new approaches to open source community development as well as new tools and practices.

What you'll learn

Learn lessons from practitioners in the industry and the new realities of open source community development
Gain a better understanding of new tools and practices to do effective open source community development in the era of emerging connected communities models

Bitergia

July 17, 2019
Tweet

More Decks by Bitergia

Other Decks in Technology

Transcript

  1. The Connected Community Model: Research Findings and Lessons Learned Diane

    Mueller Director, Community Development Red Hat Cloud Platform [email protected] @openshiftcommon July 17, 2019 - OSCON Daniel Izquierdo Chief Data Officer Bitergia [email protected] @dizquierdo / @bitergia
  2. • Origin to OKD - how the Project Shifted ◦

    OKD = f(Kubernetes++) • Reality Check ◦ A Short History Lesson • Dynamic Community Personas • Adapting the Model and the Tools ◦ OpenShift Commons Model Agenda
  3. OPEN SOURCE IS THE SOURCE OF TECHNOLOGICAL INNOVATION 1M+ projects

    KVM GNOME Apache Project OpenShift Origin OpenStack® Linux® kernel node.js Kubernetes Fedora OpenJDK TensorFlow Hyperledger 96M* REPOSITORIES 31M* DEVELOPERS 2.1M* BUSINESSES *GitHub Oct 2018
  4. KUBERNETES SIGs & WGs- ENGINEERING LEADERSHIP API MACHINERY AZURE DOCS

    OPENSTACK STORAGE CONTAINER IDENTITY AWS BIG DATA INSTRUMENTATION PRODUCT MANAGEMENT TESTING KUBEADM ADOPTION APPS CLI MULTI CLUSTER RELEASE UI RESOURCE MANAGEMENT ARCHITECTURE CLUSTER LIFECYCLE NETWORK SCALABILITY WINDOWS AUTH CLUSTER OPS NODE SCHEDULING APP DEF AUTO SCALING CONTRIBUTOR EXPERIENCE ON-PREM SERVICE CATALOG CLUSTER API 17 of 40 GROUPS RED HAT LEAD or CO-LEAD This slide is General Distribution/customer facing IOT EDGE POLICY *
  5. Chart Details Example • Dots are contributors • Blue Rectangles

    are projects or repositories • Dot size = # repos • Edge thick = # commits • Coloured dots are organizations
  6. OKD Project Atomic Prometheus Knative Project Lead Persona: SmarterClayton Kubernetes

    How he shows up: Kubernetes, OKD, Prometheus, Knative, Project Atomic, Solum (OpenStack) OpenStack (Solum)
  7. OpenStack Kubernetes OKD Organizational Persona: CERN How they show up:

    OKD, Kubernetes, OpenStack and more contributors
  8. Jaeger OpenStack Kubernetes OKD Individual Persona: Rackspace’s Greg Swift How

    they show up: OKD, Kubernetes, OpenStack contributors plus Slack, Commons, and more
  9. m3db Jaeger Kubernetes Operator Framework Tangential Persona: Uber’s Yuri Shkuro

    OKD Community Contribution: https://youtu.be/fjYAU3jayVo How they show up: Jaeger, OpenTracing, Operators, M3DB contributors OpenStack
  10. OpenStack Kubernetes OKD Corporate Persona: Amadeus’ Lénaïc Huard How they

    show up: Kubernetes, OKD, OCP on Azure, OCP on OpenStack
  11. OpenStack OpenStack OKD Upstream Persona: Alipay’s Kim Min Kubernetes How

    they show up: Kubernetes, OKD, Saltstack, Spinaker
  12. Commons Model for Cross-Community Collaboration New Community Model Commons Briefings

    & Gatherings Code Contributions Mailing Lists SIGs Promote Peer-to-Peer Interactions https://commons.openshift.org/#join
  13. • No Company is Working on ‘Just One’ Thing •

    Upstream Coordination is Essential • Relationships Matter • Domain knowledge • Community Development vs. Community Management • Data Matters (clean, curated data and good tools!) • Anonymity is Dead What’s Up Next? Predictive Analysis (perhaps using IBM Watson ;-) Convergence of Conclusions