How to deal with less maintained plugins wrt KF5?

[Milian Wolff]

On Tuesday 18 November 2014 22:46:48 Kevin Funk wrote:
> Hey,
> 
> I'm wondering how we want to deal with plugins which don't get as much as
> they should wrt KF5.
> 
> Speaking of plugins such as kdev-valgrind, kdev-cppcheck, etc. Of course
> we'd like to have them ported to KF5. So how do we want to proceed here?
> 
> Proposal:
> For each of them (which don't have any branches yet):
> - Create a 1.7 branch, make sure it compiles with kdevplatform/kdevelop
> - Port to KF5 in master branch

I'd also prefer this than waiting for $someone to step up. Having to port to 
both, Qt5 and our internal API changes is just too much for most newcomers. 
And for us it's rather trivial nowadays, no?

I'll try to do the above for anything I deem useful at least.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de