Thanks JB, Regards, Serge...
On Sat, Mar 14, 2026 at 6:32 AM Jean-Baptiste Onofré <[email protected]> wrote: > > Hi Serge > > It looks good to me. > > Thanks ! > > Regards > JB > > On Mon, Mar 9, 2026 at 10:06 AM Serge Huber <[email protected]> wrote: > > > Hi all, > > > > I have prepared the board report draft for Apache Unomi, please find > > it below and let me know what you think asap, as the delay for > > submission is in 3 days. > > > > Thanks, > > Serge... > > > > ## Description: > > The mission of Apache Unomi is the creation and maintenance of software > > related > > to providing a reference implementation of the OASIS Customer Data Platform > > specification currently being worked on by the OASIS Context Server > > Technical > > Committee > > > > ## Project Status: > > Current project status: Ongoing, moderate activity > > Issues for the board: none > > > > ## Membership Data: > > Apache Unomi was founded 2019-02-20 (7 years ago) > > There are currently 17 committers and 8 PMC members in this project. > > The Committer-to-PMC ratio is roughly 9:4. > > > > Community changes, past quarter: > > - No new PMC members. Last addition was Jonathan Sinovassin-Naïk on > > 2024-11-25. > > - No new committers. Last addition was Jerome Blanchard on 2025-09-13. > > > > ## Project Activity: > > Work this quarter focused on a mix of user-facing improvements and core > > reliability hardening. The project website was significantly modernized in > > unomi-site, with improved structure, accessibility/SEO, and ASF compliance > > follow-up. On the core unomi codebase, recent changes targeted operational > > quality: startup/logging fixes, healthcheck behavior, REST API error > > handling, > > and test/build reliability improvements. JIRA activity also reflects a > > practical stabilization cycle: several reports around invalid payload > > handling, rule/segment validation, and startup/runtime behavior were raised > > and actively worked on. In parallel, the team continues the staged > > integration > > of the 3.x workstream by splitting a large body of changes into smaller, > > reviewable PRs, with tooling support to keep the process manageable. > > > > ## Community Health: > > The community remains engaged and responsive. Most visible mailing-list > > traffic is development workflow traffic (commits/PR/JIRA notifications), > > while > > substantive discussion threads this quarter centered on the website > > modernization proposal and regular project sync/reporting topics. > > User/support > > interaction continues to happen more through JIRA and Slack than through > > the > > users mailing list, with new reports and feedback still arriving and being > > handled. Overall, collaboration and throughput remain healthy, with no > > governance or community risk requiring board attention. > >
