GSoC/2017/StatusReports/AlexeyKapustin: Difference between revisions
mNo edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
== Work report == | == Work report == | ||
*1 Phabricator task https://phabricator.kde.org/T6102 | |||
*2 Site with the current frontend(may not be available) http://akapustin.me/ | |||
== Blogs == | |||
*1 [https://akapust1n.github.io/2017-06-15-secong-blog-gsoc-2017/ Blog #1 ] | |||
== Problems == | |||
*1 Blog about choice of library [https://akapust1n.wordpress.com/2017/05/06/choice-of-library-for-selection/ Short description] | *1 Blog about choice of library [https://akapust1n.wordpress.com/2017/05/06/choice-of-library-for-selection/ Short description] | ||
* | == Repositories == | ||
* | *1 Branch in Krita [https://github.com/KDE/krita/tree/akapustin/T6102-telemetry mirror] | ||
*2 [https://cgit.kde.org/websites/telemetry-krita-org.git/ Server-side] | |||
Revision as of 15:34, 24 June 2017
Krita telemetry
The creation of a telemetry system, which allows you to better understand what users of Krita are using. That is something similar to clickstream analytics for sites. It is supposed to create: a client part, a proxy server(nginx), a back-end server(with database ClickHouse), a front-end server(nodejs), separate Steam-version. The collection of statistics will help create a separate version of Krita for the Steam with the achievements. The system of achievements is a good marketing tool that will promote the popularization of the Krita. Details about your project
Work report
- 1 Phabricator task https://phabricator.kde.org/T6102
- 2 Site with the current frontend(may not be available) http://akapustin.me/
Blogs
- 1 Blog #1
Problems
- 1 Blog about choice of library Short description
Repositories
- 1 Branch in Krita mirror
- 2 Server-side