Skip to content
The title slide and first slides of the Inner Source Launch Deck template

Inner Source Launch Deck

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
12
Difficulty
Beginner
Updated
November 6, 2026

Every slide (12)

Overview

Inner source applies open source habits inside one company, so engineers can read, reuse and improve each other's code. Without clear rules, teams copy the same tools in silos and wait weeks for review. This open source contribution guide template, in slide form, launches the programme in order: why it matters, the principles, the first projects, how to contribute and where to get support.

The sample is for Driftwood Labs, a fictional company, launching with three pilot projects, four principles and a review turnaround of 3 working days for a first response. Replace the project names, the figures and the people with your own, and check the set-up steps on a fresh machine before you invite anyone to contribute. Remove any principle your teams cannot keep.

Useful for

  • A launch plan for sharing libraries across product engineering teams
  • An onboarding talk for new engineers joining a platform team
  • A quarterly review of which shared projects are ready to grow

What's included

  • Why slide on duplicated work, siloed fixes and the case for sharing code
  • Principles cards with the four rules every project follows
  • First projects with three pilots, their owners and success tests
  • How to contribute steps from cloning the repository to opening a pull request
  • Support slide with review turnaround, decision makers and contacts
  • Make-it-yours guide and a closing slide with questions and contacts

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Swap in your project name, licence and repository links on the cover.

  3. 3

    Run the set-up steps on a fresh machine, then update the timings on slide 8.

  4. 4

    Name your real maintainers and enforcement contact before the launch date.

  5. 5

    Delete the guide slide, then share the deck with contributors or present it.

What you need

Requirements

  • A Google account with access to Google Slides

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)

Questions

Are Driftwood Labs, its people and the figures real?

No. Driftwood Labs, its people, the pilot projects, the review turnaround and the contributor numbers are fictional sample data. Replace them with your own facts before you invite contributors. A code of conduct template needs a real enforcement contact.

How long should a first response take?

A first response in 3 working days is a fair target for most teams. Say it openly on the page, then meet it, because people plan around the number you publish and drop contributions when silence lasts.

Who decides when maintainers disagree?

Name the owning team for each project and agree a tie-break rule in writing, as a short governance document, before the first dispute. Governance left implicit causes the most trouble at the first disagreement.

  • #inner-source
  • #contributing-guide
  • #open-source-governance
  • #code-of-conduct
  • #engineering-leaders
  • #developer-workflows

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…