XSF Discussion - 2022-05-09

hi folks! in light of this PR https://github.com/xsf/xmpp.org/pull/986 where I'm processing client DOAP files for rendering a nice overview, I'm asking myself if we want to keep maintaining OSes in our clients.json file. at the moment, there are five keys per client: "doap", "last_renewed", "name", "platforms", and "url". I'd like to keep the amount of infos maintained at our clients.json down to a bare minimum. DOAP files offer OS/platform infos as well, so this would be duplicated info here. I'm inclined to remove the "platforms" key, and rely on DOAP files only. this means clients without a DOAP file would be listed under "Other" on the website though. what do you think?

Bad idea, not everyone will have a doap file and we need to stop adding complexity for client authors.

If we want to have a "defer to doap" field, that's fine, but don't get rid of it entirely.

remove the requirement for the extra fields, prefer DOAP data if available?

that

require DOAP, it's easier (especially with XSF's limited resources), and if someone else wants to maintain a different index not requiring DOAP they are free to do so

Let's not start that one again :)

If it's easy enough, we can just make the fields optional for projects with DOAP

Alright, I went with "prefer DOAP data if available". I think this is a good first step! A review would be appreciated before it's merged :) https://github.com/xsf/xmpp.org/pull/986

wurstsalat: thanks for your great work again

wurstsalat: can you post a screenshot?

there is one in the PR ✏

is it still up to date?

yes

I updated it

ok!