Skip to content
The title slide and first slides of the Open Source Community Update template

Open Source Community Update

Presentation template for Google Slides and PowerPoint

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

Every slide (12)

Overview

Maintainers repeat the same answers on every call: what shipped, who helped and how a newcomer can join in. This Google Slides deck gives the call a fixed shape, moving from releases and contributors through issues and the roadmap to specific calls for help. Each slide makes one claim, such as a release date or a triage turnaround, so the room can follow without a script and the questions can go to the people who own each item.

The sample reports on a fictional project run by Fallowfield Software, with release dates, issue counts, triage rules and roadmap lanes all shown as sample data. Replace the project name, the release history and the maintainers first, then check the set-up and test figures against a fresh run of your own project. Keep each call for help specific, because a named task gets a faster reply than a general request.

Useful for

  • A monthly community call where maintainers report releases and open calls for help
  • A quarterly roadmap update for contributors and the companies that sponsor the work
  • A release review that thanks contributors and sets the next triage priorities

What's included

  • Cover slide with the call title, subtitle and presenter credit
  • Timeline of releases, with shipped and planned versions by month
  • Roadmap with four lanes across the next four quarters
  • Team slide and cards that explain how a change reaches merge
  • Issues table with open counts and median time to close
  • Triage rules, a split photo slide and a closing set of calls for help

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

    Replace the project name, licence and repository links on the first slide.

  3. 3

    Update the timeline and roadmap with your real release dates and owners.

  4. 4

    Check the issue table against your tracker and note the date the data was taken.

  5. 5

    Delete the guide slide, then share the deck or present it on the call.

What you need

Requirements

  • A Google account with access to Google Slides

Works with

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

Questions

Are the project, people and figures real?

No. Fallowfield Software, the maintainers named, the .example email addresses, the release dates, issue counts and roadmap items are fictional sample data. Replace them with your own before the call.

How do I keep the roadmap from going stale?

Review the roadmap lanes at each call, moving finished bars out and adding new ones with a named owner. A roadmap with no date or owner is a wish list, so date each bar or remove it.

Can I use this for a community that is not a software project?

Yes. Keep the order of releases, contributors, issues, roadmap and asks, then swap the terms for your group's work, such as events, papers or grants. Tie each figure to a source and a date.

  • #contributing-guide
  • #community-call
  • #maintainers
  • #open-source-updates
  • #google-slides
  • #release-update-deck

More contributing guide templates

See all 8

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…