chore: add appdata metainfo#1347
Conversation
- add metainfo.xml file - add screenshot files - update CMakeLists.txt to install metainfo - note: screenshot URLs should be changed once this PR is merged and images are available in the github repository Signed-off-by: letsfindaway <me@letsfindaway.de>
| <name>Département de l'Instruction Publique (DIP-SEM)</name> | ||
| </developer> | ||
| <description> | ||
| <p>OpenBoard is an open source cross-platform teaching software for interactive whiteboard designed primarily for use in schools and universities. It can be used both with interactive whiteboards or in a dual-screen setup with a pen-tablet display and a beamer.</p> |
There was a problem hiding this comment.
In OpenBoard.ch, I'm about to add that it can also be used with a simple computer, because I find the sentence confusing a bit.
In English, at the end of the sentence : "... beamer. It can also be used on your computer without any additional hardware."
In French : ". Il peut aussi être utilisé sur votre ordinateur, sans aucun matériel supplémentaire."
Can you adapt the sentences here accordingly ? Thanks !
| </screenshot> | ||
| </screenshots> | ||
| <releases> | ||
| <release version="1.7.3" date="2024-12-17"> |
There was a problem hiding this comment.
Need to be updated to 1.7.4. Is it necessary to have the changelog here, because it will imply to change it also there, for every release, where I was more in the way of removing them from openboard.ch to only have them in releases page of GitHub (and links to it for the other places where one wants to find them)...
What do you think ?
There was a problem hiding this comment.
You do not have to add the changelog here, the release tag can also be empty.
It however makes graphical updaters show the user what the update changes, so it is useful.
There was a problem hiding this comment.
Can we also have a link to the Github change log in the metadata? If yes, then we could easily update metainfo.xml automatically in a release script, which adds the entry for a new version.
People would then see something like:
Changes in version 1.7.5: See changelog.
There was a problem hiding this comment.
- add description for 1.7.4 - add description for 1.7.5 Signed-off-by: letsfindaway <me@letsfindaway.de>
letsfindaway
force-pushed
the
chore-appdata
branch
from
b05d9cc to
a25a925
Compare
|
Superseded by #1446 |
3 participants
This PR adds the necessary metainfo to make OpenBoard visible in software managers like KDE Discover or GNOME Software.
You can see how this would look like in the Flathub entry for OpenBoard. You have screenshots, a changelog, links to the project website and other useful information.
Distribution packagers can easily pick up this information to include OpenBoard in their software repositories not only as a package, but as an application.
This PR provides the following:
metainfo.xmlfileCMakeLists.txtto install metainfoNote that it will be necessary to update this information before creating a new release, so that it is already included in the release. This would require an additional step in the release process, which must not be skipped. It would be counter-intuitive if e.g. the tagged version 1.7.4 of OpenBoard would still contain the metainfo for 1.7.3.
Updating this information requires to add the changelog for the new release in the
ch,openBoard.OpenBoard.metainfo.xmlfile.Thanks to @jbruechert for providing the metainfo from the Flathub build.