Re: [Wireshark-dev] Code of Conduct for our community
On Mon, Aug 24, 2020 at 2:15 AM Uli Heilmeier wrote: > Am 05.08.20 um 19:06 schrieb Richard Sharpe: > >> As discussed in the last Remote Developer Den meeting I see a Code of > Conduct (CoC) as helpful for our community. > > > > Why? Nothing is broken at the moment, so nothing needs fixing, AFAICT. > > For me this is about improving and not about fixing. > Indeed. When nothing is visibly broken is the easiest time to add a Code of Conduct. I say "visibly broken" because we can't know how many people have walked away silently after seeing that we have no rules and no consequences for bad behavior. The norm is increasingly to have a Code of Conduct. Not having one is becoming a red flag. > > I would suggest the following alternative approach that the Samba team > > seems to have adopted: > > > > https://wiki.samba.org/index.php/How_to_do_Samba:_Nicely > > The Samba CoC can also be a starting point. I'm missing here a clear > encouragement for diversity and openness. > The Samba document is not really a Code of Conduct, because it doesn't address safety/diversity issues and because it doesn't impose consequences. Adopting it would be a half measure. There are many better examples to choose from. -Paul ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Code of Conduct for our community
Am 05.08.20 um 19:06 schrieb Richard Sharpe: > On Wed, Aug 5, 2020 at 8:49 AM Uli Heilmeier wrote: Thanks for your feedback Richard! >> As discussed in the last Remote Developer Den meeting I see a Code of >> Conduct (CoC) as helpful for our community. > > Why? Nothing is broken at the moment, so nothing needs fixing, AFAICT. For me this is about improving and not about fixing. > I would suggest the following alternative approach that the Samba team > seems to have adopted: > > https://wiki.samba.org/index.php/How_to_do_Samba:_Nicely The Samba CoC can also be a starting point. I'm missing here a clear encouragement for diversity and openness. The scope should also be a broader (we have ask.wireshark.org and Sharkfest etc.). > As far as I can recall, there have been no instances of the behavior > the Contributor Covenant seems to protect against, so what is the > point here? It defines clear expectations and rules. Of course it can't protect against violating the rules (like it is with all kind of rules and laws). Cheers Uli ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Code of Conduct for our community
I agree, The samba one is much more comfortable. On Thu, Aug 6, 2020 at 3:07 AM Richard Sharpe wrote: > > On Wed, Aug 5, 2020 at 8:49 AM Uli Heilmeier wrote: > > > > All, > > > > As discussed in the last Remote Developer Den meeting I see a Code of > > Conduct (CoC) as helpful for our community. > > Why? Nothing is broken at the moment, so nothing needs fixing, AFAICT. > > I would suggest the following alternative approach that the Samba team > seems to have adopted: > > https://wiki.samba.org/index.php/How_to_do_Samba:_Nicely > > As far as I can recall, there have been no instances of the behavior > the Contributor Covenant seems to protect against, so what is the > point here? > > Is someone saying that Wireshark is bad because of harassment on the lists? > > > I propose that we adopt the "Contributor Covenant" version 2 [1] for our > > community. > > This is a well established CoC with a good scope (including code review, > > mailing lists, ask.wireshark.org, Sharkfest). > > > > The instance to handel reports should be a team consisting of 3 or 5 well > > accepted community members (not only core > > devs). The email address to reach them should be an alias or so > > (repo...@wireshark.org). > > We should have a wiki page where the team members are listed (similar to > > node.js [2]). > > > > [3] gives a nice overview of CoC and is a good starting point to read. [4] > > is a scientific paper discussing some aspects > > of different CoC. > > > > So, what's your opinion? Any concerns? Any suggestions? > > > > Cheers > > Uli > > > > [1] https://www.contributor-covenant.org/version/2/0/code_of_conduct.html > > [2] https://github.com/nodejs/admin/blob/master/CODE_OF_CONDUCT.md > > [3] https://opensource.guide/code-of-conduct/ > > [4] https://www.win.tue.nl/~aserebre/SANER2017.pdf > > > > > > ___ > > Sent via:Wireshark-dev mailing list > > Archives:https://www.wireshark.org/lists/wireshark-dev > > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > > > -- > Regards, > Richard Sharpe > (何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者) > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Code of Conduct for our community
On Wed, Aug 5, 2020 at 8:49 AM Uli Heilmeier wrote: > > All, > > As discussed in the last Remote Developer Den meeting I see a Code of Conduct > (CoC) as helpful for our community. Why? Nothing is broken at the moment, so nothing needs fixing, AFAICT. I would suggest the following alternative approach that the Samba team seems to have adopted: https://wiki.samba.org/index.php/How_to_do_Samba:_Nicely As far as I can recall, there have been no instances of the behavior the Contributor Covenant seems to protect against, so what is the point here? Is someone saying that Wireshark is bad because of harassment on the lists? > I propose that we adopt the "Contributor Covenant" version 2 [1] for our > community. > This is a well established CoC with a good scope (including code review, > mailing lists, ask.wireshark.org, Sharkfest). > > The instance to handel reports should be a team consisting of 3 or 5 well > accepted community members (not only core > devs). The email address to reach them should be an alias or so > (repo...@wireshark.org). > We should have a wiki page where the team members are listed (similar to > node.js [2]). > > [3] gives a nice overview of CoC and is a good starting point to read. [4] is > a scientific paper discussing some aspects > of different CoC. > > So, what's your opinion? Any concerns? Any suggestions? > > Cheers > Uli > > [1] https://www.contributor-covenant.org/version/2/0/code_of_conduct.html > [2] https://github.com/nodejs/admin/blob/master/CODE_OF_CONDUCT.md > [3] https://opensource.guide/code-of-conduct/ > [4] https://www.win.tue.nl/~aserebre/SANER2017.pdf > > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者) ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Code of Conduct for our community
All, As discussed in the last Remote Developer Den meeting I see a Code of Conduct (CoC) as helpful for our community. I've always felt comfortable and welcome in the Wireshark community. But I'm a white old man so my view may have some bias. I propose that we adopt the "Contributor Covenant" version 2 [1] for our community. This is a well established CoC with a good scope (including code review, mailing lists, ask.wireshark.org, Sharkfest). The instance to handel reports should be a team consisting of 3 or 5 well accepted community members (not only core devs). The email address to reach them should be an alias or so (repo...@wireshark.org). We should have a wiki page where the team members are listed (similar to node.js [2]). [3] gives a nice overview of CoC and is a good starting point to read. [4] is a scientific paper discussing some aspects of different CoC. So, what's your opinion? Any concerns? Any suggestions? Cheers Uli [1] https://www.contributor-covenant.org/version/2/0/code_of_conduct.html [2] https://github.com/nodejs/admin/blob/master/CODE_OF_CONDUCT.md [3] https://opensource.guide/code-of-conduct/ [4] https://www.win.tue.nl/~aserebre/SANER2017.pdf ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
