
Contributing Guide
Docs + Word8 pages
Free
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.
Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.
Swap in your project name, licence and repository links on the cover.
Run the set-up steps on a fresh machine, then update the timings on slide 8.
Name your real maintainers and enforcement contact before the launch date.
Delete the guide slide, then share the deck with contributors or present it.
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.
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.
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.
More Google Slides templatesMore developer workflows templates

Docs + Word8 pages
Free
Docs + Word7 pages
Free
Slides + PowerPoint11 slides
Free