What about maintenance on the existing projects? Open issues on Github:
Grafana: 2.6k issues, 275 PRs
Loki: 531 issues, 113 PRs
Mimir: 305 issues, 40 PRs
Tempo: 159 issues, 19 PRs
Grafana: 2.6k issues, 275 PRs
Loki: 531 issues, 113 PRs
Mimir: 305 issues, 40 PRs
Tempo: 159 issues, 19 PRs
For example, I created an issue requesting a flamegraph visualization in grafana[1] and now it makes sense that they didn't initially respond because they were building it internally in secret and didn't want to spoil the big reveal (when they did respond they did mention that it was a secret).
They're also less incentivized now to tend to issues and PRs that help others outside of their ecosystem (i.e. competing logs, metrics, tracing, profiling, etc products).
Secrets kinda conflict with the whole Open part of OSS.
By the OSI definition, most of android is in fact open source. However, much of it is thrown over the wall after a release. Don’t conflate the two.
That's in direct contract with Grafana's own messaging. The following is from their OSS marketing page.
>Open Source is at the heart of what we do at Grafana Labs. We believe building software in the open, with thriving communities, helps leave the world a little better than we found it. https://grafana.com/oss/
Secrets kinda conflict with the whole Open part of OSS.
As I said, please stop conflating open source software with open communities. They’re part of a thriving and healthy project, but are not the same thing.
The thing with the core Grafana product being open source is that there's not that much dissimilarity between paying/enterprise Grafana users, and open-source users. Feedback from one set will almost always work in favor for the other.
Also it's a bit hard to judge what the number of open issues means right now, because we use github issues also to track internal tasks (for better visibility). So as we have more engineers and more users there will inevitably be more open issues/PRs at any given moment.