[Development] QUIP 12: Code of Conduct

[Alexey Andreyev]

> We need the document to explain the complaint process and to establish
the committee for dealing with complaints.
If we have a committee, probably they should have some statements and
agreements about how to work (I'm okay if it should be discussed separately
from CoC)
> We are adults. Despite the apparent tolerance of the bad behavior of
Donald Trump, we all know what is bad behavior in this context
I'm afraid, provided example is not an exception of our behavior as adults

чт, 25 окт. 2018 г. в 17:02, Martin Smith <Martin.Smith at qt.io>:

> >Why do we need the document then?
>
> We need the document to explain the complaint process and to establish the
> committee for dealing with complaints.
>
> >CoC committee is just a people. They need some agreements how to make
> decisions.
>
> We are adults. Despite the apparent tolerance of the bad behavior of
> Donald Trump, we all know what is bad behavior in this context.
>
> ________________________________________
> From: Alexey Andreyev <yetanotherandreyev at gmail.com>
> Sent: Thursday, October 25, 2018 3:56:18 PM
> To: Martin Smith
> Cc: Ulf Hermann; Qt development mailing list
> Subject: Re: [Development] QUIP 12: Code of Conduct
>
> > I suspect that most if not all of the commenters here who object to the
> CoC object to the attempt to define unacceptable behavior. It really has to
> be decided on a case by case basis, so remove the examples of unacceptable
> behavior, and don't attempt to define it at all.
>
> I'm okay to develop the rules. I disagree though to leave an attempt to
> define unacceptable or acceptable behavior. What should we leave then?
> General recommendation about being conscious and think about future
> consequences? It could be written in one sentense. Why do we need the
> document then?
>
> > so remove the examples of unacceptable behavior
> I agree that just the examples are not helping
>
> > No one can object to the examples of positive behavior. No one can
> object to a CoC that simply promotes those positive examples and then
> establishes a complaint process and a CoC committee to rule on each
> complaint.
>
> CoC committee is just a people. They need some agreements how to make
> decisions.
>
> чт, 25 окт. 2018 г. в 16:17, Martin Smith <Martin.Smith at qt.io<mailto:
> Martin.Smith at qt.io>>:
> I suspect that most if not all of the commenters here who object to the
> CoC object to the attempt to define unacceptable behavior. It really has to
> be decided on a case by case basis, so remove the examples of unacceptable
> behavior, and don't attempt to define it at all.
>
> No one can object to the examples of positive behavior. No one can object
> to a CoC that simply promotes those positive examples and then establishes
> a complaint process and a CoC committee to rule on each complaint.
>
> martin
>
> ________________________________________
> From: Development <development-bounces+martin.smith=qt.io at qt-project.org
> <mailto:qt.io at qt-project.org>> on behalf of Ulf Hermann <ulf.hermann at qt.io
> <mailto:ulf.hermann at qt.io>>
> Sent: Wednesday, October 24, 2018 9:17:09 AM
> To: development at qt-project.org<mailto:development at qt-project.org>
> Subject: [Development] QUIP 12: Code of Conduct
>
> Hi,
>
> regarding our earlier discussions on a possible Code of Conduct, here as
> well as at the Contributors' Summit 2017, I've pushed a QUIP with the
> necessary rules and definitions:
>
> https://codereview.qt-project.org/243623
>
> Please review it.
>
> regards,
> Ulf
> _______________________________________________
> Development mailing list
> Development at qt-project.org<mailto:Development at qt-project.org>
> http://lists.qt-project.org/mailman/listinfo/development
> _______________________________________________
> Development mailing list
> Development at qt-project.org<mailto:Development at qt-project.org>
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20181025/4ab30dee/attachment.html>