|
| 1 | +<?xml version="1.0" encoding="UTF-8"?> |
| 2 | +<component type="desktop-application"> |
| 3 | + <id>code.leech.pytimer</id> |
| 4 | + <metadata_license>CC0-1.0</metadata_license> |
| 5 | + <project_license>GPL-3.0-or-later</project_license> |
| 6 | + |
| 7 | + <name>PyTimer</name> |
| 8 | + <summary>Keep the summary shorter, between 10 and 35 characters</summary> |
| 9 | + <description> |
| 10 | + <p>No description</p> |
| 11 | + </description> |
| 12 | + |
| 13 | + <developer id="tld.vendor"> |
| 14 | + <name>Developer name</name> |
| 15 | + </developer> |
| 16 | + |
| 17 | + <!-- Requered: Should be a link to the upstream homepage for the component --> |
| 18 | + <url type="homepage">https://example.org/</url> |
| 19 | + <!-- Recommended: It is highly recommended for open-source projects to display the source code repository --> |
| 20 | + <url type="vcs-browser">https://example.org/repository</url> |
| 21 | + <!-- Should point to the software's bug tracking system, for users to report new bugs --> |
| 22 | + <url type="bugtracker">https://example.org/issues</url> |
| 23 | + <!-- Should link a FAQ page for this software, to answer some of the most-asked questions in detail --> |
| 24 | + <!-- URLs of this type should point to a webpage where users can submit or modify translations of the upstream project --> |
| 25 | + <url type="translate">https://example.org/translate</url> |
| 26 | + <url type="faq">https://example.org/faq</url> |
| 27 | + <!--Sould provide a web link to an online user's reference, a software manual or help page --> |
| 28 | + <url type="help">https://example.org/help</url> |
| 29 | + <!-- URLs of this type should point to a webpage showing information on how to donate to the described software project --> |
| 30 | + <url type="donation">https://example.org/donate</url> |
| 31 | + <!--This could for example be an HTTPS URL to an online form or a page describing how to contact the developer --> |
| 32 | + <url type="contact">https://example.org/contact</url> |
| 33 | + <!--URLs of this type should point to a webpage showing information on how to contribute to the described software project --> |
| 34 | + <url type="contribute">https://example.org/contribute</url> |
| 35 | + |
| 36 | + <translation type="gettext">pytimer</translation> |
| 37 | + <!-- All graphical applications having a desktop file must have this tag in the MetaInfo. |
| 38 | + If this is present, appstreamcli compose will pull icons, keywords and categories from the desktop file. --> |
| 39 | + <launchable type="desktop-id">code.leech.pytimer.desktop</launchable> |
| 40 | + <!-- Use the OARS website (https://hughsie.github.io/oars/generate.html) to generate these and make sure to use oars-1.1 --> |
| 41 | + <content_rating type="oars-1.1" /> |
| 42 | + |
| 43 | + <!-- Applications should set a brand color in both light and dark variants like so --> |
| 44 | + <branding> |
| 45 | + <color type="primary" scheme_preference="light">#ff00ff</color> |
| 46 | + <color type="primary" scheme_preference="dark">#993d3d</color> |
| 47 | + </branding> |
| 48 | + |
| 49 | + <screenshots> |
| 50 | + <screenshot type="default"> |
| 51 | + <image>https://example.org/example1.png</image> |
| 52 | + <caption>A caption</caption> |
| 53 | + </screenshot> |
| 54 | + <screenshot> |
| 55 | + <image>https://example.org/example2.png</image> |
| 56 | + <caption>A caption</caption> |
| 57 | + </screenshot> |
| 58 | + </screenshots> |
| 59 | + |
| 60 | + <releases> |
| 61 | + <release version="1.0.1" date="2024-01-18"> |
| 62 | + <url type="details">https://example.org/changelog.html#version_1.0.1</url> |
| 63 | + <description translate="no"> |
| 64 | + <p>Release description</p> |
| 65 | + <ul> |
| 66 | + <li>List of changes</li> |
| 67 | + <li>List of changes</li> |
| 68 | + </ul> |
| 69 | + </description> |
| 70 | + </release> |
| 71 | + </releases> |
| 72 | + |
| 73 | +</component> |
0 commit comments