Jump to content

GSoC/2017/StatusReports/AlexeyKapustin: Difference between revisions

From KDE Community Wiki
Akapustin (talk | contribs)
Akapustin (talk | contribs)
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Krita telemetry==
== 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.
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(Apache), a back-end server(with database MongoDb), a front-end server(Django). The collection of statistics help us  to improve Krita in future.
Details about your project


== Work report ==
== Work report ==
*1 Phabricator task https://phabricator.kde.org/T6102
*1 Phabricator task https://phabricator.kde.org/T6102
*2 Site with the current frontend(may not be available)  http://akapustin.me/
*2 Site with the current frontend(may not be available)  http://akapustin.me:8000
*3 Test build https://krita.org/en/item/google-summer-of-code-help-alexey-kapustin-by-testing-his-work/


== Blogs ==
== Blogs ==
*1 [https://akapust1n.github.io/2017-06-15-secong-blog-gsoc-2017/ Blog #1 ]
*1 [https://akapust1n.github.io/2017-06-15-secong-blog-gsoc-2017/ Blog #1 ]
*2 [https://akapust1n.github.io/2017-06-15-third-blog-gsoc-2017/ Blog #2 ]
*2 [https://akapust1n.github.io/2017-06-15-third-blog-gsoc-2017/ Blog #2 ]
*3  [https://akapust1n.github.io/2017-06-15-fourth-blog-gsoc-2017/ Blog #4 ]
*3  [https://akapust1n.github.io/2017-07-09-fourth-blog-gsoc-2017/ Blog #4 ]
*4  [https://akapust1n.github.io/2017-06-15-fifth-blog-gsoc-2017/ Blog #5 ]
*4  [https://akapust1n.github.io/2017-07-24-fifth-blog-gsoc-2017/ Blog #5 ]
*5  [https://akapust1n.github.io/2017-08-26-final-blog-gsoc-2017/ Final blog]


== Problems ==
== 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]
*2 Private policy [https://akapust1n.github.io/2017-08-15-sixth-blog-gsoc-2017/  Blog #6 ]
== Repositories ==
== Repositories ==
*1 Branch in Krita [https://github.com/KDE/krita/tree/akapustin/T6102-telemetry mirror]
*1 Branch in Krita [https://github.com/KDE/krita/tree/akapustin/T6102-telemetry mirror] [https://github.com/KDE/krita/commits/akapustin/T6102-telemetry?author=akapust1n only my commits(from May 2017)]
*2 [https://cgit.kde.org/websites/telemetry-krita-org.git/ Server-side]
*2 [https://cgit.kde.org/websites/telemetry-krita-org.git/ Server-side]

Latest revision as of 20:15, 28 August 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(Apache), a back-end server(with database MongoDb), a front-end server(Django). The collection of statistics help us to improve Krita in future.

Work report

Blogs

Problems

Repositories