Progress Tracking

This document outlines how to track project progress. The objective is to provide clear, standardized visibility into active work, delivery status, and milestone progress so that the community can evaluate execution at a glance.

Written By Mehrdad Sadeghi

Last updated About 1 month ago

Context

Consistent GitHub tracking ensures that ecosystem progress remains transparent, verifiable, and easy to reference in monthly updates, retrospectives and governance discussions. When tasks are structured under milestones, contributors and community members can quickly understand what is planned, what is in progress, and what has been delivered without needing additional reporting layers.

This approach reduces reporting overhead while improving accountability and visibility across the ecosystem.

Requirements & Expectations

Each project must maintain a GitHub tracking structure that includes the following:

  • GitHub Project Board containing all active tasks and issues

  • Clearly defined Milestones representing delivery checkpoints

  • All issues and tasks assigned to the appropriate milestone

  • Regular status updates reflecting the current state of each task

Milestones must have due dates and reflect meaningful delivery units such as proposal phases, milestone deliverables, or quarterly execution checkpoints

Reference Example

For example check the milestones from the Explorer RFP and Cloud SPE