-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a disclaimer/caveat to the ReadMe #336
Comments
It would be great if we added the following. This is a saved reply we have sent before from the Support email team:
|
Ugh. Given the mishaps in getting the container up for a quick assessment/demo + this issue informing me of "complete and full control of all dependencies and packages..." leads to my confidence in this project quickly waning. We expect project owners to not only offer containers, but also ensure integrity with their container offerings. My team is focused on delivering results rather than goose chase finger traps. No container or neglected container is so last century. We may revisit sometime next year. |
@ezekieldas thank you for your feedback. We will pass it onto the product team. In the meantime, you can browse the free demo on https://demo.matomo.cloud/ or quickly establish a free trial with all the premium features via https://matomo.org and https://matomo.org/lets-get-started/. |
We had another user today report that they use this matomo docker image "as is", without customizing it. |
Based on emails we get, folks treat this repo with a lot of trust -- more than we intend.
We should consider adding a stronger disclaimer, preferably on the readme page.
The text was updated successfully, but these errors were encountered: