Tweet
Tweet

Slide 1

Slide 1 text

Establishing an InnerSource Development Model Christian Weber, Senior Solutions Engineer
 github.com/webdog [email protected] classicwebdog

Slide 2

Slide 2 text

1960 Simple Few 100K Few 400K Many Global 10M Team 2.5M 50M Connected 2020 2B Autonomous Today Complex Global 150M Assisted A brief history of time

Slide 3

Slide 3 text

Source: https://www.flickr.com/photos/hades2k/7001927337

Slide 4

Slide 4 text

Collaboration SCM Automation InnerSourcing Mindset

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

So what is InnerSource then? • Takes the best of the Open Source Community • A different way of thinking about Software Development • Empowering People

Slide 7

Slide 7 text

What does it mean to be ‘Inner Source?’ • Open Collaboration • Open Communication • Separating Contributions from Integration

Slide 8

Slide 8 text

Core Tenets of Inner Source • Open by Default Access to Source Code • Transparent development environments • Peer Review • Informal communication channels • Self-Selection • Frequent Releases • “24/7” Development

Slide 9

Slide 9 text

Using GitHub with InnerSource

Slide 10

Slide 10 text

Using GitHub with InnerSource

Slide 11

Slide 11 text

Using GitHub with InnerSource

Slide 12

Slide 12 text

Using GitHub with InnerSource

Slide 13

Slide 13 text

Decrease time to market by leveraging labels, projects and project automation capabilities

Slide 14

Slide 14 text

Improve community collaboration with repository based issues, pull requests, wikis and project boards. Allow community members to vote on features with reactions

Slide 15

Slide 15 text

Unified search across your repositories to leverage the knowledge of your community members and improving reuse

Slide 16

Slide 16 text

Increase knowledge worker efficiency leveraging a pull request workflow with integrated reviewers and assignees

Slide 17

Slide 17 text

Enforce compliance policies with branch statuses, branch protection, required reviews and inline conflict resolution

Slide 18

Slide 18 text

Collaboration By adopting social collaboration tools, companies can raise productivity by 20-25% McKinsey and Co. Study

Slide 19

Slide 19 text

Collaboration statistics PRODUCTIVITY By adopting social collaboration tools, companies can raise productivity by 20-25% FAILURE 96% of execs cite lack of collaboration or ineffective communication as the main source for workplace failures. RETENTION Poor communication and unsupportive company culture is an employee-retention issue for between 20%-30% of organizations. - McKinsey and Co. Study

Slide 20

Slide 20 text

Automation

Slide 21

Slide 21 text

Quality & Security

Slide 22

Slide 22 text

Accelerating the SDLC Workflow to boost Developer Productivity Integrations to Boost Developer Productivity • Developers use their favorite tools • CI/CD automate build and delivery • Give insight to the entire lifecycle • “Best of Breed” vs Opinionated workflow

Slide 23

Slide 23 text

Right Brain Left Brain

Slide 24

Slide 24 text

Collaboration + SCM + Automation =