Mateusz Hawrus

hey @djetelina, I think for now the best way to move forward is with `oslo`. As of v0.11.0 it is a usable Go package, here's an example usage: https://github.com/OpenSLO/oslo/blob/main/examples/example.go, so...

https://github.com/OpenSLO/OpenSLO/issues/87 - pinning for reference. If you'd have the schema to work with @djetelina would you consider making the CRDs public and part of the OpenSLO?

hey @fourstepper thanks for chiming in! I'm torn on this one, mainly because I've had some decent JSON Schema exposure in the past, and It was pure pain. The main...

I'm currently picking up on what was initially done in https://github.com/OpenSLO/OpenSLO/pull/32, as a minimum I'd like to have a full working SLI schema defined in cue as it has the...

hey @CRThaze I wonder If you still have any interest left with that :) I'm leaning towards moving on with JSON Schema as it seems to be the most universal...

Admittedly though, JSON Schema is a cumbersome peace of work to craft the right way, there are a lot of caveats not only in regards to URI resolution, but defining...

I also want to highlight the main downside I see for this path, i.e. the projects providing means of native validation in Go are all seemingly abandoned: - https://github.com/xeipuuv/gojsonschema (almost...

On the [last community meeting](https://openslo.com/blog/openslo-project-meeting-february-2024/) (2024-02-21) we've decided to break the impasse and move on with Go structs as the source of truth. We'll go back to the JSON schema...

hey @kenfinnigan, we're planning OpenSLO community meeting between 05-09 of February. Feel free to vote in [this Slack survey](https://openslo.slack.com/archives/C0202J83M3R/p1706191817667639) or let me know which date suits you best here: -...

hey @kenfinnigan, we're planning OpenSLO community meeting between 05-09 (Monday-Friday) of February, 18:00 UTC. If you'd like to join and discuss your proposal, you can vote on the specific date...