On 4/22/19 4:13 PM, Matthew Ahrens wrote: > Team, we are putting together a code of conduct for OpenZFS. > > The OpenZFS Code of Conduct will apply to spaces associated with the > OpenZFS, ZFSonLinux, ZFSonOSX, and ZFSonWindows projects. > > The OpenZFS community values respectful, welcoming behavior towards > everyone. This enables our members to thrive and contribute, and > encourages new participants to join our community. > > Although most experiences within the community are positive, we all have > moments when we are unaware of our tone or are too busy to choose our words > carefully. The goal of this code of conduct is to set the tone for the > community, and provide a process to resolve conflicts when they occur. > > The proposed code of conduct is available here: > http://www.open-zfs.org/wiki/Code_of_Conduct_Summary > > The Code of Conduct was put together by myself, Karyn Ritter, and Brian > Behlendorf, with input from Jorgen Lundman, Allan Jude, Joshua Clulow, Rob > Mustacchi, Dan McDonald, Tom Caputi, Kirk McKusick, and Tim Chase. > > If you have comments or questions about the code of conduct, please let us > know. There is a 1-week community comment period before the Code of > Conduct takes effect, so please get in touch before March 29th. You can > reply on this thread or email any of us directly. > > --matt > > ------------------------------------------ > zfsonlinux: Discuss > Permalink: > https://zfsonlinux.topicbox.com/groups/zfs-discuss/T078229d4f26ba492-M9671f035f902af801b46107d > Delivery options: > https://zfsonlinux.topicbox.com/groups/zfs-discuss/subscription >
The following sentence is overly broad: "In addition, conduct outside these spaces may affect a person's ability to participate within them." It would be better if it said: "In addition, conduct in professional settings outside these spaces may affect a person's ability to participate within them." The way that it is presently worded risks creating different interpretations of what the scope of the CoC is. That could cause the project to be asked to police situations where the CoC is out of scope. Saying that a situation is out of scope in such situations would invite accusations of selective enforcement, which we don't need. If we later find that this change made the CoC too narrow, then we can always revise it to address the situation in an environment that is amicable. Wording the CoC in a way that we later find that it was too broad might not give us quite as amicable an environment for revision.
signature.asc
Description: OpenPGP digital signature
This is a multi-part message in MIME format... ------------=_1556065081-324260-1--
