flathub now supports <developer> tag, but which id to use for KDE? (was: Re: Defining a developer name for our applications metadata)

[Friedrich W. H. Kossebau]

Am Dienstag, 30. Januar 2024, 18:34:46 CET schrieb Timothée Ravier:
> Hi folks,
> 
> Flathub is now requiring that applications define a "developer_name" tag in
> their metadata (see [1], [2]).
> 
> What do folks think would be a good value for our application there?
> 
> Based on the suggestion in the documentation [3], I started making PRs [4]
> [5] [6] [7] for our KDE Apps with "The KDE Community" as the
> "developer_name" tag.

Seems meanwhile flathub maintainers have resolved that on their side, and now 
also support the non-deprecatd <developer> tag, by what I learned in MR 
https://invent.kde.org/utilities/okteta/-/merge_requests/22

The proposed patch there raises another question here though and some tasks:
--- 8< ---
  <developer id="org.kde">
    <name translate="no">KDE</name>
  </developer>
--- 8< ---

Is "org.kde" (reverse-DNS) to be the official id, and is/could that be 
documented somewhere? accessibility-inspector currently uses even "https://
kde.org", while others use "kde.org" (non-reverse DNS).

Given the purpose of the id is to be unique per group, this should be 
standardized, no? :)

Confusingly enough one doc talks about "tld.domain" as pattern of the id 
(flathub), while the other talks about "gnome.org" as example (appstream):

https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/#name-summary-and-developer-name
vs.
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-developer


Tasks for people into this, please:

a) decide on an id here

b) document that id somewhere
(e.g. https://develop.kde.org/docs/packaging/flatpak/ ?)

c) ask upstream to change the docs to not use "The KDE Community" as example, 
but "KDE" (and with no-translate attribute) in the respective docs:
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-developer

Cheers
Friedrich