lu.arnoux.Oupis.metainfo.xml.in 3.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <component type="desktop-application">
  3. <id>lu.arnoux.Oupis</id>
  4. <metadata_license>CC0-1.0</metadata_license>
  5. <project_license>GPL-3.0-or-later</project_license>
  6. <name>Oupis</name>
  7. <summary>Trouver rapidement et consulter les procédures</summary>
  8. <description>
  9. <p>
  10. Oupis est un utilitaire permettant d'accéder rapidement au dossier d'enregistrement
  11. LRPGN ou aux pages Pulsar (Registre et MIS) d'une procédure à partir de son UNA.
  12. </p>
  13. <p>
  14. En tenant à jour un index de l'ensemble des fichiers enregistrés dans le dossier
  15. des procédures LRPGN, Oupis permet aussi de trouver presque instantanément
  16. n'importe quelle pièce de procédure à partir de son nom.
  17. </p>
  18. </description>
  19. <developer id="lu.arnoux">
  20. <name>Thomas Arnoux</name>
  21. </developer>
  22. <!-- Required: Should be a link to the upstream homepage for the component -->
  23. <url type="homepage">https://code.arnoux.lu/GN/Oupis/wiki</url>
  24. <!-- Recommended: It is highly recommended for open-source projects to display the source code repository -->
  25. <url type="vcs-browser">https://code.arnoux.lu/GN/Oupis</url>
  26. <!-- Should point to the software's bug tracking system, for users to report new bugs -->
  27. <url type="bugtracker">https://code.arnoux.lu/GN/Oupis/issues</url>
  28. <!-- URLs of this type should point to a webpage where users can submit or modify translations of the upstream project -->
  29. <!--<url type="translate">https://example.org/translate</url>-->
  30. <!-- Should link a FAQ page for this software, to answer some of the most-asked questions in detail -->
  31. <url type="faq">https://code.arnoux.lu/GN/wiki/FAQ</url>
  32. <!-- Should provide a web link to an online user's reference, a software manual or help page -->
  33. <!--<url type="help">https://example.org/help</url>-->
  34. <!-- URLs of this type should point to a webpage showing information on how to donate to the described software project -->
  35. <!--<url type="donation">https://example.org/donate</url>-->
  36. <!-- This could for example be an HTTPS URL to an online form or a page describing how to contact the developer -->
  37. <url type="contact">https://www.tchap.gouv.fr/#/room/!lshyxXUIGdiXnVCzDl:agent.interieur.tchap.gouv.fr</url>
  38. <!-- URLs of this type should point to a webpage showing information on how to contribute to the described software project -->
  39. <!--<url type="contribute">https://example.org/contribute</url>-->
  40. <translation type="gettext">oupis</translation>
  41. <!-- All graphical applications having a desktop file must have this tag in the MetaInfo.
  42. If this is present, appstreamcli compose will pull icons, keywords and categories from the desktop file. -->
  43. <launchable type="desktop-id">lu.arnoux.Oupis.desktop</launchable>
  44. <!-- Use the OARS website (https://hughsie.github.io/oars/generate.html) to generate these and make sure to use oars-1.1 -->
  45. <content_rating type="oars-1.1" />
  46. <!-- Applications should set a brand color in both light and dark variants like so -->
  47. <branding>
  48. <color type="primary" scheme_preference="light">#ff00ff</color>
  49. <color type="primary" scheme_preference="dark">#993d3d</color>
  50. </branding>
  51. <screenshots>
  52. <screenshot type="default">
  53. <image>https://example.org/example1.png</image>
  54. <caption>A caption</caption>
  55. </screenshot>
  56. <screenshot>
  57. <image>https://example.org/example2.png</image>
  58. <caption>A caption</caption>
  59. </screenshot>
  60. </screenshots>
  61. <releases>
  62. <release version="1.0.1" date="2024-01-18">
  63. <url type="details">https://example.org/changelog.html#version_1.0.1</url>
  64. <description translate="no">
  65. <p>Release description</p>
  66. <ul>
  67. <li>List of changes</li>
  68. <li>List of changes</li>
  69. </ul>
  70. </description>
  71. </release>
  72. </releases>
  73. </component>