Community health tracking
Rationale
The topic of the community health tracking is important for any of the growing and extending open source project. The Oniro project is not different in that scope. In OSTC, we did some preleminary analysis in this area using commonly available tools like python, numpy, matplot etc for POC. Also, we used to have statistics taken directly from GitLab and other used systems. In the meantime also other projects & approacheds were considered like Chaoss, GrimoireLab etc.
Depending on the scope, pepople resources and the integrated modules, deployment may take from a few weeks to a few months. Thus, we believe it's vital to prepare to this and at least put some direction and spin into this process.
Additional considerations would be:
- infrastructure to host
- deployment scope
- data update mechanisms
- report & checkup cadence
- security
- others
Plan
Analysis
-
summarise the experience and expectations in terms of community health tracking within the WG -
document expections and prepare proposal -
assess capacity, work load and systems needed -
have the metrices chosen, data sources and a plan confirmed by the Oniro WG
Deployment
-
Prepare & reserve resources (infra check, equipment, people) -
Integration / preparation for deployment (systems configuration, adjustments, extra scripting etc) -
Deploy & launch!
Tests & review
-
Test the basic data feeds with accordance to earlier selected metrices -
Periodically report the health status in a form of a report / presentation etc