Ping ? On Sat, Mar 1, 2025 at 8:35 AM Serge Huber <shu...@apache.org> wrote:
> Hi all, > > I have prepared the board report for March 2025. Please find it below. As > usual, please don't hesitate if you have feedback, questions or any other > topics you want to add/modify. > > At a minimum a +1 would be appreciated :) > > Best regards, > 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: On-going, with high development activity > Issues for the board: none > > ## Membership Data: > Apache Unomi was founded 2019-02-20 (6 years ago) > There are currently 16 committers and 8 PMC members in this project. > The Committer-to-PMC ratio is 2:1. > > 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 Francois Gerthoffert on 2022-09-15. > > ## Project Activity: > Major activity on the development side is currently on-going, with a focus > on > the next major version 3.0. Alongside with that a new support for > OpenSearch > has been developed and is in review that will now make it possible to no > longer just have a requirement for Elasticsearch. > > Version 3.0 will include: > - Support for multi-tenancy at a data level to reduce the need for > containerization to support multiple (true) tenants. > - A brand new scheduler with support for task persistence and cluster > distribution > - A new unit test framework, maybe it a lot easier to test and refactoring > code modifications > - Improved documentation with support for PlantUML diagrams > - Better developer experiences including an explain system for > understanding > request execution > - Lots of new Karaf Shell commands > - And a lot more to come > - Replaced the Karaf Cellar use with a custom persistence based > communication > system > > Alongside with that bugfix releases are still being done on the > stable (2.x) version. > > ## Community Health: > The community is healthy and the new monthly meeting has been a great way > to > exchange ideas and improve collaboration between developers. Meeting notes > are > always produced and the meeting is being held at two alternating times to > give > users across the world a change to participate. All decisions remain done > through mailing lists of course. Slack is still the most active > asynchronous > communication. Activity will probably increase in the Github once the major > contributions for 3.0 are being reviewed but for the moment the focus is on > finishing the planned feature set. >
