RFC/call for assistance: Merging kdev-clang-tidy into kdevelop repo

[Friedrich W. H. Kossebau]

Hi,

I would like to propose the merge of the Clang-Tidy integration plugin, kdev-
clang-tidy, into the kdevelop repo (master branch), as soon as it has been 
decided about. To join the static analyzer buddies kdev-clazy & kdev-cppcheck.

State:
* the current code of the plugin has seen some release already this year
* works for me (tm)
* builds clean on KDE CI
  https://build.kde.org/job/KDevelop/job/kdev-clang-tidy
* no bugs reported (but also no other users yet known :) )
  https://bugs.kde.org/buglist.cgi?component=Analyzer%3A%20Clang-Tidy&product=kdevelop

Get some more information about the plugin (incl. screenshots) on
https://frinring.wordpress.com/2018/08/30/improve-your-cpp-code-in-kdevelop-with-clang-tidy/


ARE WE OKAY WITH THAT?

So far it seems KDevelop contributors/maintainers are positive about such a 
merge. But let's make sure and get an explicit Yay/Nay here :)


EXECUTION

Given kdev-clang-tidy plugin code has seen multiple authors, a simple commit 
with a dump of the current working copy might lose too much info.
So semms best the git history of the kdev-clang-tidy gets completely merged?

Anyone experienced with that, who could tell what to do or do it themselves?
I will do what I can do, but need a helping hand with that nerge bit.


BUT WHAT ABOUT THE PLANS TO DO MORE INDEPENDENT RELEASES?

Doing an Autumn reevaluation of my maintained projects, I found the my old 
plan to continue independent development of kdev-clang-tidy with new feature 
releases parallel to stable KDevelop 5.3 and then merging in time for KDevelop 
5.4 lacks my motivation now, as the additional planned features are currently 
not needed by myself and I also never got any feedback on the plugin.

Given I use KDevelop from master myself, the source location of kdev-clang-
tidy makes no difference for me :)

Actually, having kdev-clang-tidy in master sooner might even help with fixing 
my current biggest bummer, having to manually enable  
CMAKE_EXPORT_COMPILE_COMMANDS with lots of steps, when that could be done 
code-wise (patch started somewhere in a branch).

Cheers
Friedrich