[Development] QUIP 12: Code of Conduct

[NIkolai Marchenko]

Note that installing a conflict resolution authority doesn't need
installing a controversial CoC and formalizing every thing a contributor
can or cannot do..
True, there won't be formalized and standadized rules for resolution, but
aren't people in this project sensible enough, in general, to have the
common sense to reach an adequate solution?

On Sat, Oct 27, 2018 at 4:10 PM Martin Smith <Martin.Smith at qt.io> wrote:

> >Well, then let me give you my simple minded opinion on this topic, an
> engineers
> >opinion:
> >Do not introduce a CoC.
>
> In that case, if a contributor is mistreated by another contributor, what
> recourse does the victim have?
>
> martin
>
> ________________________________________
> From: Development <development-bounces+martin.smith=qt.io at qt-project.org>
> on behalf of Bernhard Lindner <private at bernhard-lindner.de>
> Sent: Saturday, October 27, 2018 12:39:40 AM
> To: development at qt-project.org
> Subject: Re: [Development] QUIP 12: Code of Conduct
>
> > But the only mailing list with sufficient representation of the
> community is
> > this one. We don't have to like discussing this, but it seems necessary
> that
> > we do.
>
> Well, then let me give you my simple minded opinion on this topic, an
> engineers opinion:
> Do not introduce a CoC.
>
> Resisting to have anything and everything in black and white is hard and
> is not popular
> and surely not zeitgeist but sometimes the better way.
>
> Please do not make me discuss about that as well, I prefer to wrangle with
> item delegate
> code ;)
>
> --
> Best regards,
> Bernhard Lindner
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
> _______________________________________________
> Development mailing list
> 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/20181027/2ccdd1c4/attachment.html>