Albert Astals Cid
aacid at kde.org
Tue Apr 19 23:49:47 BST 2016
El dijous, 14 d’abril de 2016, a les 20:40:26 CEST, Olivier Churlaud va
> First of all, I'm not part of the ML, so please answer me in copy :)
I'd suggest the kde-frameworks-devel at kde.org mailing list since this email
seems to be about frameworks (or at least metainfo.yml is frameworks specefic
Also I'd be a bit more specific, i read the email and didn't understand what
you actualyl want to do, sure add more fields, but which and why.
> Following the CERN script about reorganizing techbase, I began to work
> on extending kapidox.
> The observation is the following: developers don't have time to document
> and update their codes and the wikis, so the wikis are not up-to-date
> and users don't know where to find the information that is sometimes in
> a /doc or /examples folder in the git repository.
> To correct this, we came up with the solution to follow the Qt way: all
> the documentation would be generated by kapidox. This is almost done.
> Here is my question
> Can we use metainfo.yml and extend it to fill the missing information?
> We were thinking of creating supplementary files like 'config.kapidox'
> but while writing the code, I realized that most of the basic projects
> wouldn't need that..
> You can find the current state of the project under my branch
> Thank you for your advices.
More information about the kde-core-devel