Re: Code Of Conduct

--===============6009966079364294111==
Content-Type: multipart/alternative; boundary="94eb2c000d5868623f055cbd22cf"

--94eb2c000d5868623f055cbd22cf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

That sounds like a good idea. Although if the CoC is in place that means
everyone should feel free to talk in this space even if it's not in other
places. Which IMO is a bonus to have people talk together when they
wouldn't be otherwise.
On Sun 29 Oct 2017 at 18:39, Jerome Martinez <[email protected]> wrote:

> On 29/10/2017 16:32, Steve Lhomme wrote:
> > [...]
> >
> > Changing the rules once they are set can be tricky. It can be
> > perceived as a way to block certain people at the time they are
> > changed. So it's important to get them right from the start.
>
> On our side, we saw that the Contributor Covenant is becoming popular so
> we didn't want to reinvent the wheel, but we also liked the Scope part
> of the Django CoC. I especially like the line "In addition, violations
> of this code outside these spaces may affect a person's ability to
> participate within them" in the Django CoC, in order to be clear that we
> don't accept people being nice with us because they have an agenda and
> at the same time being less nice in other spaces because they don't care
> of consequences. From my point of view, the Contributor Covenant was not
> dealing with this case and it could have created difficulties like how
> to deal with a person who does not violate our rules with us but prevent
> other people to come in physical spaces because they are afraid (with
> reason) to meet such person.
> So we took the Scope part from the Django project in order to include
> this "corner case" (ok, we were not trying to reinvent the wheel, but we
> mixed 2 CoC for fitting our needs)
> You may consider to do same if you want to have such larger scope from
> the beginning.
>
> Our CoC: https://mediaarea.net/Conduct
> Django CoC: https://www.djangoproject.com/conduct/
>
> J=C3=A9r=C3=B4me
> _______________________________________________
> Matroska-devel mailing list
> [email protected]
> https://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-devel
> Read Matroska-Devel on GMane:
> http://dir.gmane.org/gmane.comp.multimedia.matroska.devel

--94eb2c000d5868623f055cbd22cf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

That sounds like a good idea. Although if the CoC is in place that means ev=
eryone should feel free to talk in this space even if it&#39;s not in other=
 places. Which IMO is a bonus to have people talk together when they wouldn=
&#39;t be otherwise.<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sun =
29 Oct 2017 at 18:39, Jerome Martinez &lt;<a href=3D"mailto:jerome@mediaare=
a.net">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">On 29/10/2017 16:32, Steve Lhomme wrote:<br>
&gt; [...]<br>
&gt;<br>
&gt; Changing the rules once they are set can be tricky. It can be<br>
&gt; perceived as a way to block certain people at the time they are<br>
&gt; changed. So it&#39;s important to get them right from the start.<br>
<br>
On our side, we saw that the Contributor Covenant is becoming popular so<br=
>
we didn&#39;t want to reinvent the wheel, but we also liked the Scope part<=
br>
of the Django CoC. I especially like the line &quot;In addition, violations=
<br>
of this code outside these spaces may affect a person&#39;s ability to<br>
participate within them&quot; in the Django CoC, in order to be clear that =
we<br>
don&#39;t accept people being nice with us because they have an agenda and<=
br>
at the same time being less nice in other spaces because they don&#39;t car=
e<br>
of consequences. From my point of view, the Contributor Covenant was not<br=
>
dealing with this case and it could have created difficulties like how<br>
to deal with a person who does not violate our rules with us but prevent<br=
>
other people to come in physical spaces because they are afraid (with<br>
reason) to meet such person.<br>
So we took the Scope part from the Django project in order to include<br>
this &quot;corner case&quot; (ok, we were not trying to reinvent the wheel,=
 but we<br>
mixed 2 CoC for fitting our needs)<br>
You may consider to do same if you want to have such larger scope from<br>
the beginning.<br>
<br>
Our CoC: <a href=3D"https://mediaarea.net/Conduct" rel=3D"noreferrer" targe=
t=3D"_blank">https://mediaarea.net/Conduct</a><br>
Django CoC: <a href=3D"https://www.djangoproject.com/conduct/" rel=3D"noref=
errer" target=3D"_blank">https://www.djangoproject.com/conduct/</a><br>
<br>
J=C3=A9r=C3=B4me<br>
_______________________________________________<br>
Matroska-devel mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Matr=
[email protected]</a><br>
<a href=3D"https://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-dev=
el" rel=3D"noreferrer" target=3D"_blank">https://lists.matroska.org/cgi-bin=
/mailman/listinfo/matroska-devel</a><br>
Read Matroska-Devel on GMane: <a href=3D"http://dir.gmane.org/gmane.comp.mu=
ltimedia.matroska.devel" rel=3D"noreferrer" target=3D"_blank">http://dir.gm=
ane.org/gmane.comp.multimedia.matroska.devel</a></blockquote></div>

--94eb2c000d5868623f055cbd22cf--

--===============6009966079364294111==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Matroska-devel mailing list
[email protected]
https://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-devel
Read Matroska-Devel on GMane: http://dir.gmane.org/gmane.comp.multimedia.matroska.devel
--===============6009966079364294111==--