Given the info in the appdata might be the first and only thing
especially newcomers to the world of (FLOSS)/linux software might see,
let's be more detailed here, to catch them when they are young ;)
Details
- Reviewers
apol kfunk - Group Reviewers
KDevelop - Commits
- R32:2a6de7818d11: Add more content to <description> part of appdata
Diff Detail
- Repository
- R32 KDevelop
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Ideally the content of <summary> and <description> would be brushed up to something that then can also be pushed downstream to the non-appdata package metadata, which currently are not really reflecting the power of kdevelop5, and thus might also miss out to have more people discover KDevelop as their problem solver, e.g. those:
https://software.opensuse.org/package/kdevelop5
https://apps.fedoraproject.org/packages/kdevelop
https://packages.debian.org/sid/kdevelop
http://packages.ubuntu.com/zesty/kdevelop
Maybe you could extend the guidelines? https://community.kde.org/Guidelines_and_HOWTOs/AppStream
Thanks, that's great (and important) detail work!
org.kde.kdevelop.appdata.xml | ||
---|---|---|
46 | ... several programming languages, integration ... |
org.kde.kdevelop.appdata.xml | ||
---|---|---|
46 | This should be "provides X, and (A and B)" (actually inspired by https://en.wikipedia.org/wiki/KDevelop, second sentence ;) ). |
org.kde.kdevelop.appdata.xml | ||
---|---|---|
46 | +1. Much better. |