Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

appdata.xml metadata file for inclusion in Software Center #6490

Closed
DorpsGek opened this issue Jul 18, 2016 · 15 comments
Closed

appdata.xml metadata file for inclusion in Software Center #6490

DorpsGek opened this issue Jul 18, 2016 · 15 comments

Comments

@DorpsGek
Copy link

@DorpsGek DorpsGek commented Jul 18, 2016

Mailaender opened the ticket and wrote:

http://pkgs.fedoraproject.org/cgit/rpms/openttd.git/tree/openttd.spec?id=763604381fa252e7f8fbe3f54db33699d90d3dc9;id2=HEAD# n77 contains such a file. It was sent to you 2 years ago for inclusion. I don't want to manually patch it into the openSUSE rpm package. This is something you should maintain for every distribution.

Reported version: Version?
Operating system: Linux


This issue was imported from FlySpray: https://bugs.openttd.org/task/6490
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Jul 30, 2016

Mailaender wrote:

Updated the file with slightly more suitable screenshots.

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14247
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Aug 11, 2016

frosch wrote:

Some dude via mail:

We've been busy building an awesome software center, and we've been adding more and more metadata fields that upstream authors can set. The software center is now being used in Fedora, Opensuse, Ubuntu, Debian and Arch, with many millions of happy users.

Some of the newest features include a way to make it easy for translators to contribute new translations of your applications by specifying a URL in the openttd.appdata.xml AppData file that tells them where to start looking. This can be specified by adding:

http://the-web-site-with-translation-instructions/

Another useful tag to add is to tell end-users where to donate, for instance:

http://www.gnome.org/friends/

If it's been some time since you updated the AppData file (and hey, you've got an app to write!) you can get add the latest metadata fields by doing `appstream-util upgrade openttd.appdata.xml` and then replacing any FIXMEs in the file with actual data. We'll be putting more functionality into the software center in the future that uses this extra data, but we need more upstream software to opt-in before we can enable features, for instance, providing a button for users to donate to specific apps.

You can also use `appstream-util validate-relax` on your AppData file to check the various fields meet our style guidelines. If you disagree with any of the validation warnings, please let me know!


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14251
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Sep 17, 2016

frosch wrote:

Same dude via mail:

The latest feature we want to support is age classifications for games. As your application is listed in the games category we wanted to ask if you could generate some OARS metadata and add it to the openttd.appdata.xml file. It's really as simple as visiting http://apps-xdgapp.rhcloud.com/oars then answering about 20 questions with multiple choice answers, then pasting the output inside the tag.

Using the <content_rating> tag means we can show your game with an appropriate age rating depending on the country of the end user. If you have any comments about the questions on the OARS page please do let me know.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14271
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Mar 13, 2017

peter1138 wrote:

Which package managers should we support today? Which in 5 years?


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14366
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Mar 13, 2017

Mailaender wrote:

The appdata.xml file is independent from the package manager used.

For the Open Age Ratings Service you can take OpenRA/OpenRA#12044 for reference where I did this for OpenRA. I am not sure where this is exposed though.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14370
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Mar 15, 2017

peter1138 wrote:

And what needs to happen with the file? Does it need to go somewhere specific? Is it just part of the source or does it need to be installed?


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14388
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Mar 15, 2017

Mailaender wrote:

It needs to go to /usr/share/appdata

See https://build.opensuse.org/request/show/416036 for an integration test of this file.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14391
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Sep 9, 2017

Alberth wrote:

It's great you're adding meta-information to all applications for your users. It is even more great that this is done across distributions.
However, you're only doing Linux, not windows, not osx, not .

So why do you want application developers to make only your users happy?

The better solution would be imho to make a cross-Linux-distribution repo with this stuff for all applications that your OS(es) support. You can add whatever you want in whatever speed you want. Frankly, we have more than enough problems with just the application, we don't need more work.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14762
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Sep 10, 2017

Mailaender wrote:

Copying it into your repository shouldn't be that much of an effort. If your attitude would be more friendly and your source code repository more accessible, I might have even setup a patch for the Makefile install rules or l10n support.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14765
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Sep 11, 2017

peter1138 wrote:

I guess it would go in the os/rpm/ directory and then however that stuff works would put the file into the package that gets built. None of my non-RPM systems have a /usr/share/appdata to care about.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14769
@DorpsGek

This comment has been minimized.

Copy link
Author

@DorpsGek DorpsGek commented Sep 11, 2017

Mailaender wrote:

Ubuntu 16.04 should come with GNOME Software which also displays these by default.


This comment was imported from FlySpray: https://bugs.openttd.org/task/6490#comment14770
@TrueBrain

This comment has been minimized.

Copy link
Member

@TrueBrain TrueBrain commented Apr 10, 2018

Good idea! We also do the same for OSX, so why not for Linux. Enough stuff supports this to be worth our while!

@ghisvail

This comment has been minimized.

Copy link

@ghisvail ghisvail commented Apr 23, 2018

I submitted some AppStream metadata for the Flatpak package. Might be worth including upstream once the review is completed by the Flathub community?

@andythenorth andythenorth added the stale label Jan 5, 2019
@andythenorth

This comment has been minimized.

Copy link
Contributor

@andythenorth andythenorth commented Jan 5, 2019

This specific issue might be dead. However there is discussion about more support for Flatpak, Steam etc.

@andythenorth

This comment has been minimized.

Copy link
Contributor

@andythenorth andythenorth commented Jan 12, 2019

Thanks for this. There's been no activity on this for some time, and as it stands, it doesn't look likely that it will go any further. I'm closing it as we try to keep the issue count low for OpenTTD, it helps us focus on things that are important and fun. Feel free to discuss in irc or request re-opening if you disagree. Thanks for contributing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.