**Problem**
Krita contains a large number of tools for painters, a large number of settings and features. Their number increases every year, but not all of them are popular. More precisely, the critics want to know which of the options are popular. Based on this information, you can determine the vector of further work, finalize popular, but not too well-implemented features, remove old, useless functions. Use of clickstream analytics will help to learn the popularity of features.
Full version of proposal you can read [[ https://docs.google.com/document/d/1xxf6hONNDCnCWuG3vfo9Tjui87yBF86T1rRlKr8ptLA/edit?usp=sharing | here. ]]
**Сurrent status**
[13.05.2017] Was created [[ https://akapust1n.wordpress.com/2017/05/06/choice-of-library-for-selection/ | blog ]] on planet.kde.org. The blog offered changes to the used libraries in the project. The creator of the library kuserfedbachk was attracted to this record for to discuss technical nuances :)
A site for temporary telemetry mapping has been created([[ http://akapustin.me | akapustin.me ]]). Site isn't ready now. [[ https://github.com/akapust1n/kritaServers | Sources of site.]]
[4.06.2017]
The library kuserfeedback was built in as a plugin. Created server-prototype. Server can accept information from Krita.
You can load my branch and load info about your system on site.
[6.06.2017]
I have written backend server which can
- Take statistics
- Show last request on site
- parse json request and write it in database
[24.06.17]
[[ https://akapust1n.github.io/2017-06-15-secong-blog-gsoc-2017/ | Blog #2 ]] . [[ https://akapust1n.github.io/2017-06-15-third-blog-gsoc-2017/ | Blog #3 ]]
**Plan**
[ok]Deploy kuserfeedback backend server and try to sent basic information(like version of QT) to this server.
[ok] Refactor server code. Divide server on frontend and backend.