Hi,
Sorry for not having being so clear :S
I sent a "maybe clearer" email to kde-devel [1]. The idea is to
generalize the metainfo.yml to all projects and extend the available
keys in order to build a api.kde.org with all projects. Please refer to
this email. According to Martin Gräßlin, I should come with a full
proposition that works and then say to people "this is what you need to
put in your libs so that they appear on api.kde.org"
I'll do such a proposition in the upcoming weeks.
Cheers
Olivier
[1] http://marc.info/?l=kde-devel&m=146081804706196&w=2
Le 20/04/2016 00:49, Albert Astals Cid a écrit :
El dijous, 14 d’abril de 2016, a les 20:40:26 CEST, Olivier Churlaud va
escriure:
Hello,
First of all, I'm not part of the ML, so please answer me in copy :)
I'd suggest the kde-frameworks-de...@kde.org mailing list since this email
seems to be about frameworks (or at least metainfo.yml is frameworks specefic
i think).
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.
Cheers,
Albert
Context
=====
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
olivier/generate_all
Thank you for your advices.
Cheers
Olivier
