On Wed, Aug 5, 2020 at 8:49 AM Uli Heilmeier <zeugs@xxxxxxxxxxxx> 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 (reports@xxxxxxxxxxxxx).
> 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 <wireshark-dev@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
