Project Reporting
- Andrew Wilkinson
- Jeff Brower
Akraino project reporting provides visibility of the each BP validation project (MBx1, MBx2 etc) and feature project (MF1, MF2 etc) by means of a set of defined milestones.
The milestones are defined by the Documentation subcommittee.
Blueprint Validation Project reporting
BP validation projects milestones will be different in the 'Incubation' and 'Mature' stages since the graduation criteria from these two stages are different.
A single table shall be maintained for all projects in Incubation (i.e. tracking the progress towards graduating from Incubation to Mature)
A single table shall be maintained for all project in Mature stage (i.e. tracking the progress towards graduating Mature to Core)
Each BP validation project's PTL is responsibility for updating the Incubation or Mature BP tracking tables for their BP validation project so that the TSC can easily track all BP validation projects' status.
In addition to the PTLs reporting the actual dates each milestone is achieved, the PTLs are encouraged in their planning stage to enter their target date for each milestone in the same table.
Feature Project reporting
Each feature project's PTL is responsibility for the updating feature project tracking table for their feature project so that the TSC can easily track all feature projects' status.
Blueprint Projects R4 API Information Reporting Requirements
Starting with R4, all blueprint projects are required to report significant edge computing APIs they both expose and consume. The API Subcommittee page has instructions.