[AppStream] Additional markup support in descriptions

Matthias Klumpp matthias at tenstral.net
Thu Aug 1 12:10:09 UTC 2019


Am Mi., 31. Juli 2019 um 22:31 Uhr schrieb Robert Ancell
<robert.ancell at canonical.com>:
> [...]
> What's the next step here; should I make an MR for <code/> to be added to the specification?

That would be nice, however I only merge specification changes if they
also have a corresponding implementation in libappstream (and ideally
validator adjustments). So, just submitting a PR for the spec change
is fine, but that may sit in the queue then until I can fully
implemented the feature (and merge it then).

> I figure this discussion would have worked better as a GitHub issue? It might be worth opening issues for <strong/> and <pre/> so we have a better record of the reasoning for/against.

While initially I didn't want that (we have a mailinglist afterall, so
that should be used for discussions...) it turned out that Github
issues are actually far more effective and efficient for managing
these feature requests than a mailinglist, so yes, please report them
as issues at https://github.com/ximion/appstream - I also regularly go
through the open feature requests, issues and PRs to see what is still
requested and could be addressed or whether discussion is stalled and
needs to move further. Github issues are also highly visible, so other
people who want a feature can chime in easily.

Cheers,
    Matthias

---
I welcome VSRE emails. See http://vsre.info/


More information about the AppStream mailing list