>Note that installing a conflict resolution authority doesn't need installing a >controversial CoC and formalizing every thing a contributor can or cannot do..
But it does require specifying how to lodge a complaint, which specifies conduct, and it then ought to say something about the kinds of complaints that will be resolved by the resolution authority and the kinds of complaints that will not. That also specifies conduct. >but aren't people in this project sensible enough, in general, to have the >common sense to reach an adequate solution? That's what we're doing now. ________________________________________ From: NIkolai Marchenko <enmarantis...@gmail.com> Sent: Saturday, October 27, 2018 3:17:09 PM To: Martin Smith Cc: priv...@bernhard-lindner.de; Qt development mailing list Subject: Re: [Development] QUIP 12: Code of Conduct 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.sm...@qt.io<mailto:martin.sm...@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...@qt-project.org<mailto:qt...@qt-project.org>> on behalf of Bernhard Lindner <priv...@bernhard-lindner.de<mailto:priv...@bernhard-lindner.de>> Sent: Saturday, October 27, 2018 12:39:40 AM To: development@qt-project.org<mailto:development@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@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
