metadata.yaml for Plasma projects?

[Martin Graesslin]

On Friday, April 8, 2016 3:09:13 AM CEST Matthias Klumpp wrote:
> 2016-04-07 13:55 GMT+02:00 Martin Graesslin <mgraesslin at kde.org>:
> > On Thursday, April 7, 2016 1:21:55 PM CEST Aleix Pol wrote:
> >> On Thu, Apr 7, 2016 at 11:41 AM, Martin Graesslin <mgraesslin at kde.org>
> > 
> > wrote:
> >> > Hi Plasmates,
> >> > 
> >> > an idea for better documentation is to introduce some metadata similar
> >> > like
> >> > what frameworks have. This could be useful for potential devs who want
> >> > to
> >> > contribute, but also for distributions as in that way:
> >> > * we can specify whether it's experimental, released, obsoleted, etc.
> >> > * what other Plasma projects it depends on
> >> > * who is maintaining it and where to reach us
> >> > 
> >> > Below I have an example how this could look like (in the case of KWin).
> >> > 
> >> > What do you think?
> >> > 
> >> > Cheers
> >> > Martin
> >> > 
> >> > # The maintainer of the project
> >> > maintainer: graesslin
> >> 
> >> I'd suggest offering an appstream appdata file instead of this.
> > 
> > We have projects for which appstream doesn't make sense. Example is KWin,
> > kdecoration, kscreenlocker, kwayland, etc. etc. In fact I think we have
> > more projects in Plasma which do not need an appdata file than projects
> > which actually benefit from it.
> 
> That's actually not true - AppStream is a generic metadata format, and
> instead of writing an appdata file, you can just as well write a
> generic metainfo file to add metadata (and a unique ID!) to any
> software component.
> Just omit the type= attribute in the <component/> root tag, or set it
> to "generic". Those components won't show up in software centers, but
> the metadata will still be available in distributions via more
> advanced tools.
> 
> So, your metadata file ideally only contains stuff that isn't in the
> metainfo XML already - or you add your own, non-standard tag to the
> metainfo file.

is there a high level visual editor for such appstream metadata? I'm not going 
to write XML and don't want to get my fellow developers to have to write xml. 
It's the path to outdated metadata if we need to write xml.

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160408/639408c8/attachment.sig>