Preparing mass-packaging of 170 KDE application - hwo to do?

[Hartmut Goebel <h.goebel@crazy-compilers.com>]

Hi,

I'm currently working on a script to mass-generate *draft* packages for
KDE applications. Ca. 170 of them :-) These are the ones listed at
<https://www.kde.org/applications/>

The idea is to have a draft which can easily be taken and adopted.
Inputs will be lists at best knowledge (taken from the CMakeLists.txt
file). Synopsis and description are pre-filled from Debian and Mageia.

Nevertheless 170 packages are a lot of work, which I would like to
distribute. Esp. checking the licenses and linting is quite some effort.

Questions:

  * To distribute the workload, I'd like to put the drafts somewhere.
    Should I push this into a wip-branch? Or hat else would be an option?

  * Should these apps be sorted alphabetically of being grouped
    (development, office, system, education, utilis, …)?

  * Any other hints for managing this mass of patches and changes?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |