Thank you very much for the meeting minutes, I'll try to reply to some of the open questions here:
On Thu, Jun 13, 2024 at 5:08 PM Francois Gerthoffert < franc...@gerthoffert.net> wrote: > > ## Roadmap and backlog > > Some work was done recently to upgrade dependencies (UNOMI-829). > Dedicated issues were created for those dependencies that couldn’t be > updated without significant changes in the codebase. Pull Requests > opened by dependabot were not re-reviewed after that effort, Jonathan > S. (assignee on UNOMI-829) will do a pass on those that were made > outdated by the ticket and will close them. For the other dependabot > pull requests, this will be tracked with UNOMI-693, by looking at > their age, quite a few of them are likely outdated. > Thanks for doing this work, it's much appreciated. > > Work was carried out on the Graphql API, but was blocked by > dependencies to graphql-java / graphql-java-annotations. A release is > currently being worked on for graphql-java-annotations (expected in > the next 2 weeks), which would allow the work to resume on UNOMI-680 > and its subtasks. > That's good news thank you. > ## General discussion items > Thomas mentioned that the lack of UI / admin view on Unomi is creating > challenges to adoption. It was mentioned that some work might > currently be carried out on this topic by project/community members > but participants of the call were not directly involved and cannot > comment (individual (s) involved are welcome to comment). > Yes I had initially mentioned work on a UI but before that I believe some things can be improved in terms of on-board using documentation, as recent interactions in the Slack channel showed that newcomers struggle with quite basic stuff (like form and login handling). > > A ticket was created to implement OpenSearch support for Unomi > (UNOMI-828), this raises interests but participants on the call were > unclear about the status and plans, in particular when it comes to > current and future (8+) compatibility with Elasticsearch (see the > question in the ticket itself). > This came from an external request to support OpenSearch and the Apache Board also raised concerns about the fact that sole dependency on a commercial product is not a good thing for an Apache project. I started some initial work on OpenSearch support as I believe JB did as well, and this ticket was created to track discussions on this topic. > A question was raised about the use of sessions in REST vs GraphQL, > sessions are still used and necessary for the REST API but are not > implemented in the GraphQL API. > Yes I was wondering this myself as well, it might be interesting to see what the different needs are. Best regards, Serge Huber.
