Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add rules for jdev #1290

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Add rules for jdev #1290

wants to merge 1 commit into from

Conversation

horazont
Copy link
Contributor

This is mostly a clone of the operators rules.

This PR is to be seen as a proposal and has not been vetted or proof-read by anyone.


Like any growing community, the XMPP Developers Channel has a set of rules to govern the interactions, in order to make as many people as possible feel safe and welcome.

Above all, the [Community Code of Conduct of the XMPP Standards Foundation](https://xmpp.org/extensions/xep-0458.html) (still under discussion, but unless stated otherwise in *this* document, the current experimental version applies nontheless) applies, called CoC hereafter. That means that behaviour which goes against the CoC is automatically not accepted.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nontheless -> nonetheless


## On-Topicness

The channel started out as a place for developers to work together to improve the state of XMPP software in general, encompassing topics such as software interoperability (as opposed to deployment interoperability; for the latter, the [Operators channel](operators-rules.md) is the better a place), reliability, security and standards edge cases. It can provide valuable information when just reading passively, but also when actively asking.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the better a place
is a better place?

Maybe it's an English idiom I don't know though.

@Echolon Echolon added enhancement Website 🖱️ Issue is related to Website changes or problems labels Aug 4, 2023
@Echolon
Copy link
Member

Echolon commented Aug 4, 2023

@horazont can you also establish a link from this this page: https://xmpp.org/community/chat/

@Echolon
Copy link
Member

Echolon commented Aug 4, 2023

Are there dedicated admins for jdev?

@Echolon
Copy link
Member

Echolon commented Oct 3, 2023

Hi @horazont,

a kind reminder on this PR and change requests.


## About the XMPP Developers Channel ("jdev")

The XMPP Developers Channel is located at [[email protected]](xmpp:[email protected]?join). It is a place primarily for developers of software following or aiming to follow XMPP standards (RFC 6120--6122, as well as XMPP Extension Proposals, and updated versions of the RFCs), to have civil and low-bar knowledge transfer, learning and support in the task of implementing the various pieces of the XMPP standard compendium.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The XMPP Developers Channel is located at [[email protected]](xmpp:[email protected]?join). It is a place primarily for developers of software following or aiming to follow XMPP standards (RFC 6120--6122, as well as XMPP Extension Proposals, and updated versions of the RFCs), to have civil and low-bar knowledge transfer, learning and support in the task of implementing the various pieces of the XMPP standard compendium.
The XMPP Developers Channel is located at [[email protected]](xmpp:[email protected]?join). It is a place primarily for developers of software following or aiming to follow XMPP standards (RFC 6120--6122, as well as [XMPP Extension Proposals](/extensions), and updated versions of the [RFCs](/rfcs)), to have civil and low-bar knowledge transfer, learning and support in the task of implementing the various pieces of the XMPP standard compendium.


For transgressions solely happening within the XMPP Developers channel, the channel admins are an acceptable first point of contact.

**Note**: The CoC only applies to XMPP Standards Foundation (XSF) members and venues. It does not automatically apply to all members of all XMPP channels. Do not report misconduct in venues outside of the control of the XSF to this room or the XSF Conduct Team, unless an XSF member is involved.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Note**: The CoC only applies to XMPP Standards Foundation (XSF) members and venues. It does not automatically apply to all members of all XMPP channels. Do not report misconduct in venues outside of the control of the XSF to this room or the XSF Conduct Team, unless an XSF member is involved.
**Note**: The CoC only applies to XMPP Standards Foundation (XSF) [members](/community/membership) and venues. It does not automatically apply to all members of all XMPP channels. Do not report misconduct in venues outside of the control of the XSF to this room or the XSF Conduct Team, unless an XSF member is involved.


## On-Topicness

The channel started out as a place for developers to work together to improve the state of XMPP software in general, encompassing topics such as software interoperability (as opposed to deployment interoperability; for the latter, the [Operators channel](operators-rules.md) is the better a place), reliability, security and standards edge cases. It can provide valuable information when just reading passively, but also when actively asking.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The channel started out as a place for developers to work together to improve the state of XMPP software in general, encompassing topics such as software interoperability (as opposed to deployment interoperability; for the latter, the [Operators channel](operators-rules.md) is the better a place), reliability, security and standards edge cases. It can provide valuable information when just reading passively, but also when actively asking.
The channel started out as a place for developers to work together to improve the state of XMPP software in general, encompassing topics such as software interoperability (as opposed to deployment interoperability; for the latter, the [Operators channel](/community/channels/operators) is a better place), reliability, security and standards edge cases. It can provide valuable information when just reading passively, but also when actively asking.


### On-Topic induced Off-Topic

Since some of the on-topic cases can quickly derail into off-topic when debates become ad-hominem. When debating controversial topics, the difference between an insult or judgement and a discussion is in the rationale.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First sentence sounds incomplete to me. Maybe better without starting with "Since"?


### I want to discuss something that is considered off-topic in this channel, where can I go?

To discuss operating XMPP server software as well as deployment interoperability, there exists the [XMPP Operators channel](operators-rules.md) at [[email protected]](xmpp:[email protected]?join). Discussion of XMPP Extension Proposals as well as the XMPP standard itself and matters concerning the XMPP Standards Foundation takes place in [[email protected]](xmpp:[email protected]?join).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To discuss operating XMPP server software as well as deployment interoperability, there exists the [XMPP Operators channel](operators-rules.md) at [[email protected]](xmpp:[email protected]?join). Discussion of XMPP Extension Proposals as well as the XMPP standard itself and matters concerning the XMPP Standards Foundation takes place in [[email protected]](xmpp:[email protected]?join).
To discuss operating XMPP server software as well as deployment interoperability, there exists the [XMPP Operators channel](/community/channels/operators) at [[email protected]](xmpp:[email protected]?join). Discussion of XMPP Extension Proposals as well as the XMPP standard itself and matters concerning the XMPP Standards Foundation takes place in [[email protected]](xmpp:[email protected]?join).

@@ -99,7 +99,7 @@ Finally, note that channel membership does not imply any kind of immunity from t

### I want to discuss something that is considered off-topic in this channel, where can I go?

To discuss software development related to XMPP, there exists [[email protected]](xmpp:[email protected]?join). Discussion of XMPP Extension Proposals as well as the XMPP standard itself and matters concerning the XMPP Standards Foundation takes place in [[email protected]](xmpp:[email protected]?join).
To discuss software development related to XMPP, there exists the [XMPP Developers channel](jdev-rules.md) at [[email protected]](xmpp:[email protected]?join). Discussion of XMPP Extension Proposals as well as the XMPP standard itself and matters concerning the XMPP Standards Foundation takes place in [[email protected]](xmpp:[email protected]?join).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To discuss software development related to XMPP, there exists the [XMPP Developers channel](jdev-rules.md) at [[email protected]](xmpp:[email protected]?join). Discussion of XMPP Extension Proposals as well as the XMPP standard itself and matters concerning the XMPP Standards Foundation takes place in [[email protected]](xmpp:[email protected]?join).
To discuss software development related to XMPP, there exists the [XMPP Developers channel](/community/channels/jdev) at [[email protected]](xmpp:[email protected]?join). Discussion of XMPP Extension Proposals as well as the XMPP standard itself and matters concerning the XMPP Standards Foundation takes place in [[email protected]](xmpp:[email protected]?join).


For transgressions solely happening within the XMPP Developers channel, the channel admins are an acceptable first point of contact.

**Note**: The CoC only applies to XMPP Standards Foundation (XSF) members and venues. It does not automatically apply to all members of all XMPP channels. Do not report misconduct in venues outside of the control of the XSF to this room or the XSF Conduct Team, unless an XSF member is involved.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe a topic to explore elsewhere, but does the CoC apply to any XSF member anywhere? Or just when they act in quality of XSF member?

@Echolon
Copy link
Member

Echolon commented Mar 2, 2024

@mwild1 do you have comments on this or can you approve change suggestions?

@mwild1
Copy link
Contributor

mwild1 commented Mar 2, 2024

I support it in principle, but it looks like there is a bunch of feedback already that hasn't been incorporated, so I think approval is not an option at this time.

@cal0pteryx
Copy link
Member

@horazont are you still interested in working on this?

@cal0pteryx cal0pteryx marked this pull request as draft March 24, 2024 22:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Website 🖱️ Issue is related to Website changes or problems
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants