WIP: cherry pick some from 240 task

.appveyor/after_build.ps1

@@ -0,0 +1,36 @@
+param (
+    $VcpkgPath = 'c:\tools\vcpkg\',
+    $VcpkgPlatform = 'x64-windows'
+)
+
+$ErrorActionPreference = 'Stop'
+
+function Pack-Files($ext, $includeExe, $targetPath, $archiveName) {
+    New-Item $targetPath\imageformats -Type Directory -Force | Out-Null
+    New-Item $targetPath\platforms -Type Directory -Force | Out-Null
+
+    foreach ($name in @('Qt5Core', 'Qt5Gui', 'Qt5Network', 'Qt5Widgets')) {
+        Copy-Item $env:QT_DIR\bin\$name.$ext $targetPath\
+    }
+
+    Copy-Item $env:QT_DIR\plugins\imageformats\qwebp.$ext $targetPath\imageformats\
+    Copy-Item $env:QT_DIR\plugins\imageformats\qjpeg.$ext $targetPath\imageformats\
+    Copy-Item $env:QT_DIR\plugins\platforms\qwindows.$ext $targetPath\platforms\
+    Copy-Item $VcpkgPath\installed\$VcpkgPlatform\bin\ssleay32.$ext $targetPath\
+    Copy-Item $VcpkgPath\installed\$VcpkgPlatform\bin\libeay32.$ext $targetPath\
+
+    $itemsToPack = @("$targetPath\*.$ext", "$targetPath\platforms\*.$ext", "$targetPath\imageformats\*.$ext")
+    if ($includeExe) {
+        $itemsToPack += @("$targetPath\kepka.exe")
+    }
+
+    7z a -mmt $archiveName @itemsToPack
+}
+
+Push-Location "$PSScriptRoot\..\build"
+try {
+    Pack-Files dll $true Telegram kepka.zip
+    Pack-Files pdb $false Telegram pdb.zip
+} finally {
+    Pop-Location
+}

.appveyor/before_build.cmd

@@ -0,0 +1,2 @@
+set PATH=C:\Python35;%QT_DIR%\bin;%PATH%
+call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat"

.appveyor/build.ps1

@@ -0,0 +1,23 @@
+$ErrorActionPreference = 'Stop'
+
+Push-Location "$env:APPVEYOR_BUILD_FOLDER\build"
+
+function execute-cmake {
+    # We have to merge the stderr and stdout here because otherwise the build will fail on any random warning
+    cmd /c 'cmake 2>&1' @args
+    if ($LASTEXITCODE -ne 0) {
+        throw "CMake execution error: $LASTEXITCODE"
+    }
+}
+
+try {
+    execute-cmake '-GNinja' `
+        '-DCMAKE_TOOLCHAIN_FILE=c:/tools/vcpkg/scripts/buildsystems/vcpkg.cmake' `
+        '-DCMAKE_BUILD_TYPE=RelWithDebInfo' `
+        ..
+    execute-cmake --build . --config RelWithDebInfo
+    ctest .
+    if (!$?) { throw 'ctest execution error' }
+} finally {
+    Pop-Location
+}

.appveyor/install.cmd

@@ -0,0 +1,4 @@
+vcpkg install --triplet x64-windows openal-soft openssl opus zlib ffmpeg
+appveyor DownloadFile https://github.com/ninja-build/ninja/releases/download/v1.8.2/ninja-win.zip
+mkdir %APPVEYOR_BUILD_FOLDER%\build
+7z x ninja-win.zip -o%APPVEYOR_BUILD_FOLDER%\build > nul

.clang-format

@@ -0,0 +1,43 @@
+---
+AccessModifierOffset: -4
+AlignAfterOpenBracket: Align
+AlignConsecutiveAssignments: false
+AlignConsecutiveDeclarations: false
+AlignEscapedNewlinesLeft: false
+AlignEscapedNewlines: false
+AlignOperands: true
+AlignTrailingComments: false
+AllowShortBlocksOnASingleLine: false
+AllowShortCaseLabelsOnASingleLine: true
+AllowShortFunctionsOnASingleLine: Empty
+AllowShortIfStatementsOnASingleLine: true
+AllowShortLoopsOnASingleLine: true
+AlwaysBreakAfterDefinitionReturnType: None
+AlwaysBreakAfterReturnType: None
+AlwaysBreakBeforeMultilineStrings: true
+BinPackArguments: true
+BinPackParameters: true
+BreakBeforeBraces: Attach
+BreakBeforeTernaryOperators: false
+BreakConstructorInitializers: BeforeComma
+BreakStringLiterals: true
+ColumnLimit: 120
+ConstructorInitializerAllOnOneLineOrOnePerLine: false
+Cpp11BracedListStyle: true
+DerivePointerAlignment: true
+IndentCaseLabels: false
+IndentWidth: 4
+KeepEmptyLinesAtTheStartOfBlocks: false
+MaxEmptyLinesToKeep: 2
+NamespaceIndentation: None
+PointerAlignment: Right
+SortIncludes: false
+SpaceAfterCStyleCast: false
+SpaceBeforeAssignmentOperators: true
+SpaceBeforeParens: ControlStatements
+SpaceInEmptyParentheses: false
+Standard: Cpp11
+TabWidth: 4
+UseTab: ForIndentation
+ForEachMacros: [ for_const, foreach, Q_FOREACH, BOOST_FOREACH ]
+...

.github/CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing
 
-This document describes how you can contribute to Telegram Desktop. Please read it carefully.
+This document describes how you can contribute to Kepka. Please read it carefully.
 
 **Table of Contents**
 
@@ -17,14 +17,14 @@ This document describes how you can contribute to Telegram Desktop. Please read
 
 ## What contributions are accepted
 
-We highly appreciate your contributions in the matter of fixing bugs and optimizing the Telegram Desktop source code and its documentation. In case of fixing the existing user experience please push to your fork and [submit a pull request][pr].
+We highly appreciate your contributions in the matter of fixing bugs and optimizing the Kepka source code and its documentation. In case of fixing the existing user experience please push to your fork and [submit a pull request][pr].
 
 Wait for us. We try to review your pull requests as fast as possible.
 If we find issues with your pull request, we may suggest some changes and improvements.
 
-Unfortunately we **do not merge** any pull requests that have new feature implementations, translations to new languages and those which introduce any new user interface elements.
+Unfortunately we **do not merge** any pull requests that have not comply with [Telegram API Terms of Use][api-tos].
 
-Telegram Desktop is not a standalone application but a part of [Telegram project][telegram], so all the decisions about the features, languages, user experience, user interface and the design are made inside Telegram team, often according to some roadmap which is not public.
+Kepka is a fork of a Telegram Desktop which a part of [Telegram project][telegram], so all the decisions about the features, languages, user experience, user interface and the design *in upstream* are made inside Telegram team, often according to some roadmap which is not public.
 
 ## Build instructions
 
@@ -33,11 +33,11 @@ environments.
 
 ## Pull upstream changes into your fork regularly
 
-Telegram Desktop is advancing quickly. It is therefore critical that you pull upstream changes into your fork on a regular basis. Nothing is worse than putting in a days of hard work into a pull request only to have it rejected because it has diverged too far from upstram.
+Kepka is advancing quickly. It is therefore critical that you pull upstream changes into your fork on a regular basis. Nothing is worse than putting in a days of hard work into a pull request only to have it rejected because it has diverged too far from upstram.
 
 To pull in upstream changes:
 
-    git remote add upstream https://github.com/telegramdesktop/tdesktop.git
+    git remote add upstream https://github.com/procxx/kepka.git
     git fetch upstream master
 
 Check the log to be sure that you actually want the changes, before merging:
@@ -56,7 +56,7 @@ For more info, see [GitHub Help][help_fork_repo].
 
 ## How to get your pull request accepted
 
-We want to improve Telegram Desktop with your contributions. But we also want to provide a stable experience for our users and the community. Follow these rules and you should succeed without a problem!
+We want to improve Kepka with your contributions. But we also want to provide a stable experience for our users and the community. Follow these rules and you should succeed without a problem!
 
 ### Keep your pull requests limited to a single issue
 
@@ -95,7 +95,7 @@ Furthermore, the pixel shortage is over. We want to see:
 
 ### Test your changes!
 
-Before you submit a pull request, please test your changes. Verify that Telegram Desktop still works and your changes don't cause other issue or crashes.
+Before you submit a pull request, please test your changes. Verify that Kepka still works and your changes don't cause other issue or crashes.
 
 ### Write a good commit message
 
@@ -105,11 +105,52 @@ Before you submit a pull request, please test your changes. Verify that Telegram
 
   For example: `Fix #545`
 
+* For documentation commits add `[ci skip]` (or `[skip ci]`) at the end of the commit message.
+
+#### Commit Message Example
+
+```
+Summarize changes in around 50 characters or less
+
+More detailed explanatory text, if necessary. Wrap it to about 72
+characters or so. In some contexts, the first line is treated as the
+subject of the commit and the rest of the text as the body. The
+blank line separating the summary from the body is critical (unless
+you omit the body entirely); various tools like `log`, `shortlog`
+and `rebase` can get confused if you run the two together.
+
+Explain the problem that this commit is solving. Focus on why you
+are making this change as opposed to how (the code explains that).
+Are there side effects or other unintuitive consequences of this
+change? Here's the place to explain them.
+
+Further paragraphs come after blank lines.
+
+ - Bullet points are okay, too
+
+ - Typically a hyphen or asterisk is used for the bullet, preceded
+   by a single space, with blank lines in between, but conventions
+   vary here
+
+If you use an issue tracker, put references to them at the bottom,
+like this:
+
+Resolves: #123
+See also: #456, #789
+[ci skip]
+```
+
+(Example taken from [this source][commit_message_2])
+
+
 [//]: # (LINKS)
+[procxx]: https://procxx.github.io/
 [telegram]: https://telegram.org/
 [help_fork_repo]: https://help.github.com/articles/fork-a-repo/
 [help_change_commit_message]: https://help.github.com/articles/changing-a-commit-message/
 [commit_message]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
-[pr]: https://github.com/telegramdesktop/tdesktop/compare
-[build_instructions]: https://github.com/telegramdesktop/tdesktop/blob/master/README.md#build-instructions
+[commit_message_2]: https://chris.beams.io/posts/git-commit/
+[pr]: https://github.com/procxx/kepka/compare
+[build_instructions]: https://github.com/procxx/kepka/blob/dev/README.md#build-instructions
 [closing-issues-via-commit-messages]: https://help.github.com/articles/closing-issues-via-commit-messages/
+[api-tos]: https://core.telegram.org/api/terms

.github/ISSUE_TEMPLATE.md → .github/ISSUE_TEMPLATE/bug_report.md

@@ -1,5 +1,10 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
 <!--
-Thanks for reporting issues of Telegram Desktop!
+Thanks for reporting issues of Kepka!
 
 To make it easier for us to help you please enter detailed information below.
 --> 
@@ -17,13 +22,13 @@ Tell us what happens instead
 ### Configuration
 **Operating system:**
 
-**Version of Telegram Desktop:**
+**Version of Kepka:**
 
 **Used theme**:
 
 <details><summary><b>Logs</b>:</summary>
 Insert logs here (if necessary)
 
-<!-- You can type `debugmode` in settings and then see ~/.TelegramDesktop/DebugLogs/log_...txt for log files.
+<!-- You can type `debugmode` in settings and then see ~/.local/share/Kepka/DebugLogs/log_...txt for log files.
 Type `debugmode` in settings again to disable logs. -->
 </details>

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,13 @@
+---
+name: Feature Request
+about: New feature that you want to see in Kepka
+---
+
+## Feature description
+<!-- please describe your feature in simple English. -->
+
+
+## Feature check-list
+ - [ ] This feature has been implemented by <!-- Telegram Desktop / another fork. Required to fill if flag is set. Also please paste a link to repo with commit(s) implementing this feature -->
+ - [ ] This feature doesn't violate the Telegram [Terms of Service](https://telegram.org/tos)
+

.gitignore

@@ -55,3 +55,19 @@ xcuserdata
 /Linux/
 /Telegram/Makefile
 *.*~
+
+### Vim service files ##
+# swap
+.sw[a-p]
+.*.sw[a-p]
+# session
+Session.vim
+# temporary
+.netrwhist
+*~
+
+_build_
+_conan_build_
+
+.idea/
+cmake-build-debug/