There are different types of XEPs as outlined in XEP-0001:
https://xmpp.org/extensions/xep-0001.html#types
You are talking about Standards Track XEPs which, as the name suggests, define
the standard for the protocol ("protocol extensions") and thus are typically
rather technical.
This is a
On 04.02.22 11:43, Andrew Nenakhov wrote:
Just agree to change a set of documents using
a "community-driven governance". Protocol extensions should contain
protocol extensions, and nothing but them. It is a technical
documentation, but such things turn it into a political manifest.
Ah yes,
Just agree to change a set of documents using
a "community-driven governance". Protocol extensions should contain
protocol extensions, and nothing but them. It is a technical documentation,
but such things turn it into a political manifest.
On Fri, 4 Feb 2022, 15:39 JC Brand, wrote:
>
>
> On
On 04.02.22 11:20, Andrew Nenakhov wrote:
1. From what I've seen, CoCs are used so silence or scare into silence
people with differing political opinions (so much for tolerance). The
language of this CoC, too, is too broad and allows for such misuse.
2. XEPs are not the place for such
1. From what I've seen, CoCs are used so silence or scare into silence
people with differing political opinions (so much for tolerance). The
language of this CoC, too, is too broad and allows for such misuse.
2. XEPs are not the place for such documents. If XSF wants to have a code
of conduct, it
Dear list
The community code of conduct (xep-0458) came up for an approval vote in
a recent board meeting.
I've gone through the document and am writing down my thoughts and
feedback here.
Quoted parts are directly from the document.
> The examples in this document of what not to do are
