Hi All, Here is the report I posted to board. If this report strikes and interest or topics that merit further discussion, please don’t hesitate to raise a thread.
Having had some discussions with PMC/Committers, I think the next quarter will bring with it some new feature requirements for Flagon, Distill and back end integrations. That means there will be some spirited discussion and roadmapping coming to dev soon :) Complete Report Follows: ## Description: The mission of Apache Flagon is the creation and maintenance of software related to thin-client behavioral logging capability useful for business analytics, usage analytics, usability and user testing ## Project Status: Current project status: Ongoing with healthy community participation Issues for the board: No issues at this time ## Membership Data: Apache Flagon was founded 2023-03-21 (2 years ago) There are currently 19 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Evan Jones on 2024-07-10. - No new committers. Last addition was Ryan Thenhaus on 2025-02-08. ## Project Activity: Project activity has been healthy in that the community has been steadily working together on maintenance or new features. Newer PMC members have done well in recruiting new contributors during this time. They have invested their time in supporting projects that both maintain the projects and bolster the community. First, the community discussed and completed a major migration to a monorepo structure, which has been useful for expediting new onboarding for contributors. Second, community members have taken it upon themselves to address and updating our website, which is still underway. Finally, current PMC members and new contributors addressed modernizing elements of UserALE's browser plugin deployment methodology, migrating to Manifest v 3. ## Community Health: Getting organic communication to occur within Apache lists remains challenging, although some members of the community started running a weekly synch earlier in the year. This did set some objectives that the community started organizing around from a development standpoint. I also find that for larger decisions (e.g., monorepo) about product direction, those discussions are at least raised on lists before initiative is taken. For straightforward maintenance issues, we see more individual or small group initiative to address issues (e.g., Mv3 and Website). Notwithstanding, we are seeing some new growth in that two contributors have shown interest in becoming committers--there are VOTEs ongoing on private as of the date of this report. In the next two quarters, I suspect PMC will open discussions on other functional areas of the project, including additional back-end examples and examples for integration with other instrumentation and telemetry packages, as well as a push toward adopting firmer standards in logging that are consistent with other communities (e.g., OpenTelemetry).
