Dear community members,
thank you to all people who found time to join us on the community calls, especially the ones who joined even during their vacation. All calls ended up being 2.5 hours long.
As promised, here is a summary of the calls, which we had last week.
As transparency and communication were meta-topics across the entire feedback, during the calls we spent time to give context, shed light into what happens behind the scenes: how our teams are structured, how our roadmap is being created, how we do quality assurance and other details.
Then, we discussed the five topics, which were the most prominent in the feedback:
- Roadmap
- Feature portal
- Quality
- Support
- Bug tracker
For each topic, we
- Reflected on the feedback we received previously in this thread
- Discussed proposed actions by tribe29
Some of the discussed actions are pretty straight-forward, e.g.
- Updating the roadmap section on our website
- Regularly giving updates on the roadmap and progress
- One of the proposed formats for this is having regular catch-up community calls
- Implementing requests from the feature portal for Checkmk 2.3.
- The context is important here: the feature portal was introduced after the 2.2 roadmap was defined, that’s why not so much has been implemented for Checkmk 2.2 – we planned anyway to have more features included from the portal in the future, but now we will put even more emphasis on that
- Communicating better and more around the feature portal.
- Fix inconsistencies and increase usability of the product.
- We have already started a series of surveys to collect feedback and improve the user experience – and we are committed to continue doing that.
Some are much more complex and need to be further refined, e.g.
- Adapting our support model to reflect current day user expectations
- Increasing test coverage for check plugins, agent plug-ins and agents
- Making Checkmk upgrades easier to manage
- Building a proper public bug tracker
It was very helpful for us to have in-person discussions to get your thoughts on how something like a bug tracker could actually be implemented. We are also glad that these calls gave way to more productive interaction with involved community members: some of the feedback is already being discussed additionally with the people who suggested it.
Our next step now is to come up with a detailed plan which we can commit to. We will share it publicly to the wider user base, once it is done.
This thread will be closed. If you have further feedback, please contact directly either @Sara, your tribe29 Account Executive, or join us in future community calls, where there will be ample room to discuss topics of concern in person – as the calls we had have shown, this is a good and productive way.