Hello, Thank you for the work that has gone into this.
To me, the document is clearly worded. I would appreciate elaboration on the sentence "Humour is not a mitigating factor here" in section 2.3. An additional suggestions is to add a reminder that we do not all share a common cultural background or even a native language and that this can easily introduce confusion of tongues. To what extent will this document, once adopted, be not only applicable to all of the XSF's Activities, but also be the singular source of policy? Does that need to be specified? As for the applicability: much (all?) of the violations that I witnessed are simple spamming or abusive behaviours in MUC rooms. The definition of desired vs undesirable behaviour that's in this document can help in those cases, but the process on section 5 is less applicable. I doubt that this document intends to make moderators of a room go through a procedure of Reporting to the Conduct Team, prior to issuing a ban. Should this document more explicitly allow for action to be taken outside of the procedure defined in section 5? Kind regards, Guus Op di 31 okt 2023 19:09 schreef Peter Saint-Andre <[email protected]>: > This message constitutes notice of a Last Call for comments on XEP-0458, > a Procedural XEP that the XSF Board of Directors is considering for > advancement to a status of Active. > > Title: Community Code of Conduct > > Abstract: This document describes the XMPP Standard Foundation's Code of > Conduct. > > URL: https://xmpp.org/extensions/xep-0458.html > > This Last Call begins today and shall end at the close of business on > 2023-11-30. > > Please consider the following questions during this Last Call and send > your feedback to the [email protected] discussion list: > > 1. Is this document needed to fill gaps in the XSF's policies and > procedures? > > 2. Does the document address the goals stated in the introduction? > > 3. If code of conduct defined in this document applied to an interaction > in which you participated (e.g., if you witnessed a violation of the > code), would you follow the procedures defined in the document? > > 4. Do you have any privacy or security concerns related to this > specification? > > 5. Is the document clearly written and does it avoid unnecessary or > potentially damaging ambiguity? > > Your feedback is appreciated! > > Peter > (on behalf of the XSF Board of Directors) > > _______________________________________________ > Standards mailing list -- [email protected] > Info: Unsubscribe: %(real_name)s-unsubscribe@%(host_name)s > _______________________________________________ >
_______________________________________________ Standards mailing list -- [email protected] Info: Unsubscribe: %(real_name)s-unsubscribe@%(host_name)s _______________________________________________
