We should ship AppStream data with Picard. AppStream adds standardized descriptions of applications, that can be used by different application stores / installers. E.h. GNOME Software and KDE Discover make use of it. It is also required for Flatpak packages.

      See https://www.freedesktop.org/wiki/Distributions/AppStream/ for details.

      Tasks:

      1. Add an appdata XML file, use https://github.com/flathub/org.musicbrainz.Picard/blob/master/org.musicbrainz.Picard.appdata.xml as a starting point and extend it with a proper description, more URLs and other suitable data (see AppStream specs)

      2. Make proper screenshots (2-3, main window, maybe options), host them on MusicBrainz FTP and link them

      3. Make sure the AppData XML gets installed to /usr/share/metainfo

          [PICARD-1384] Add AppStream data

          Philipp Wolfer made changes -
          Fix Version/s New: 2.1.0 [ 11126 ]
          Fix Version/s Original: 2.1.0dev2 [ 11113 ]
          Philipp Wolfer made changes -
          Component/s New: Packaging & Deployment [ 11094 ]
          Philipp Wolfer made changes -
          Link New: This issue is a dependency of PICARD-1424 [ PICARD-1424 ]
          Philipp Wolfer made changes -
          Issue Type Original: Improvement [ 4 ] New: New Feature [ 2 ]
          Philipp Wolfer made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Release Pending [ 10006 ] New: Closed [ 6 ]
          Philipp Wolfer made changes -
          Status Original: Review Submitted [ 5 ] New: Release Pending [ 10006 ]
          Philipp Wolfer made changes -
          Link New: This issue has related issue PICARD-1393 [ PICARD-1393 ]

          You actually would not need to translate it, but provide the necessary changes to Picard and the build system to allow for translation of the app data file. But you could if course translate to your native language as a test to show that the approach works

          I actually have a pretty good idea how we should implement this in Picard, I just have to write it down I to a proper task for GCI.

          Philipp Wolfer added a comment - You actually would not need to translate it, but provide the necessary changes to Picard and the build system to allow for translation of the app data file. But you could if course translate to your native language as a test to show that the approach works I actually have a pretty good idea how we should implement this in Picard, I just have to write it down I to a proper task for GCI.

          Abhinav Ohri added a comment -

          @outsidecontext I would like to do it. But I have a question, which language do I have to translate the file to if I take up the task?

          Abhinav Ohri added a comment - @outsidecontext I would like to do it. But I have a question, which language do I have to translate the file to if I take up the task?

          Agreed for the translation, but we will handle this in a separate task. It's a bit too much for a single Google Code-In task to do both. I'll probably add a GCI task for this. @abhi_ohri, maybe you are interested?

          Philipp Wolfer added a comment - Agreed for the translation, but we will handle this in a separate task. It's a bit too much for a single Google Code-In task to do both. I'll probably add a GCI task for this. @abhi_ohri, maybe you are interested?

            abhi_ohri Abhinav Ohri
            outsidecontext Philipp Wolfer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                2.1