-
flow
well, a lot of the same technical and social discussions/issues surface in multiple communities, like the discourse discussion ;)
-
emus
Great discussion and I think the solution is great too, incl. no renewals anymore
-
wurstsalat
My first proposal would be: remove all entries in {clients,servers,libraries}.json for which last_updated is "null". These entries haven't been shown anyway since 2017.
-
wurstsalat
Then I'd check entries for which "last_renewed" is set, and if they don't provide a DOAP file themselves, add a bare-minimum DOAP file to host on xmpp.org
-
flow
what's the advantage of removing them, it only seems to make it harder to re-add them✎ -
flow
what's the advantage of removing them? it only seems to make it harder to re-add them ✏
-
MattJ
Yeah, I'm not sure about removing them either, if links still work, etc.
-
MattJ
By all means bury them as inactive
-
wurstsalat
flow, less DOAP files to write. But yes, in the end they could be displayed in a separate "Inactive" section
-
flow
if they are hidden anyways, then you don't have to write DOAP files for them, no?
-
wurstsalat
flow, but I want to get rid of the "platforms" and "url" keys in the long run. this info would be lost, if not transferred to a DOAP file
-
flow
hmm, I do not have immediate plans to write a DOAP for Smack but would like to keep it listed, and ideally with a URL to the project's homepage and mentioned the supported platforms.
-
flow
Not because I don't like DOAPs, I find the idea appealing, but because I just don't have time, and writing DOAPs is currently a category C todo item for me
-
wurstsalat
flow, that's why we want to host bare-minimum DOAP files for projects which don't provide one. That lets us simplify the processing
-
wurstsalat
this includes name, shortdesc, website, os, (logo)
-
flow
ahh ok, so the status-quo for smack remains the same without me having to lift a finger? I think I *could* life with that :)
-
wurstsalat
yeah, that's the plan
-
Menel
Wherr on xmpp.org can I even see the benefits of the fancy DOAP data? From the main page I can only find https://xmpp.org/software/clients/ But that's only a name, logo and link to project.
-
wurstsalat
Menel, atm, logo and short description are the only benefits. but that'll be extended soon
-
Menel
I see, thanks
-
Zash
I imagined a boring list at the bottom of the page for all the other items. Maybe hidden behind a <details>
-
emus
flow: I still think your project should have a doap - cmon its smack!
-
emus
> Zash wrote: > I imagined a boring list at the bottom of the page for all the other items. Maybe hidden behind a <details> *roll eyes*
-
emus
compliance Badges!
-
Guus
> flow: I still think your project should have a doap - cmon its smack! We welcome your contribution? 😉
-
emus
😃 do you actually list supported xeps somewhere at all?
-
flow
we do
-
emus
flow: where?
-
flow
https://github.com/igniterealtime/Smack/blob/master/documentation/extensions/index.md
-
vanitasvitae
flow, emus: I think I have a Smack branch somewhere where I started writing a DOAP file, but that branch is probably horribly outdated.
-
singpolyma
"supported xeps" is such an interesting concept. I guess with a library it is probably more clear, but with a client it is often borderline meaningless
-
emus
is fine but then send it to me :-)
-
emus
singpolyma: how else should you review compliance?
-
singpolyma
emus: not sure what you mean?
-
emus
based on the listed client xeps you can elaborate ita compliance
-
singpolyma
Can you though? It depends on several people's interpretation of "supporting a xep" and "compliance"
-
Menel
I think one can construct meaningless examples. But in reality its quite clear. Can it do http upload or not.. Etc
-
singpolyma
Menel: some are clearer that others for sure. Http upload is a great example of a pretty clear one
-
Kev
HTTP's a great example of one that's very muddy.✎ -
Kev
HTTP upload's a great example of one that's very muddy. ✏
-
singpolyma
Though even there... What does the client use http upload *for*? You can probably guess by what is common, but...
-
Kev
Because the XEP requires being able to set cookies on a per-request basis, which is ... not straightforward in a web client.
-
Kev
So people will very reasonably skip that bit. And then some day someone needs it, finds out the client that claimed to support HTTP Upload doesn't, and ... muddy.
-
singpolyma
Kev: right partial compliance is common. For example, everyone claims to support data forms just because they have a parser for it, maybe use it in ibr. But the xep allows for data forms being send in messages and tracked by thread ID... I've not found a client that supports that will yet. So do they "support" data forms or not?✎ -
singpolyma
Kev: right partial compliance is common. For example, everyone claims to support data forms just because they have a parser for it, maybe use it in ibr. But the xep allows for data forms being send in messages and tracked by thread ID... I've not found a client that supports that well yet. So do they "support" data forms or not? ✏
-
emus
I know its not perfect but I believe its the best step in the right direction.
-
MSavoritias (fae,ve)
I agree we need some ways to show it to whoever ends up on the page. People still install pidgin because they are not "in the know" for example
-
emus
One thing I try to improve in general in XMPP is central communication, thats why I support this.