[Development] QUIP 12: Code of Conduct

Ulf Hermann ulf.hermann at qt.io
Thu Oct 25 08:06:15 CEST 2018


On 10/25/18 1:19 AM, Konstantin Shegunov wrote:
> I  think you're over-engineering the whole thing and you don't drive the 
> point of such a document home. My best suggestion is to simplify 
> (heavily) the process and the phrasing.

The CoC is not only a guide on how to behave, but also a "welcome" 
message to new contributors. Therefore, there may be slightly redundant 
language in there which specifically addresses people currently 
under-represented in the Qt community.

> Secondly, that whole committee thing is somewhat of a stretch in my 
> mind. It's going to be much more practical to have one contact person to 
> "shuffle the paper" and consider complaints/issues, answering questions 
> about and for the community, helping newer persons to get on with the 
> program and so on. Election can be by majority voting ran for a 
> reasonable time period (say 1 week) from a pool of proposed candidates. 
> Alternatively, as the community is somewhat dispersed over different 
> media - forums, mailing lists, IRC and so on a person for each of the 
> channels mentioned can be elected. On that note the proposed CoC doesn't 
> take into account that specific, for one we mostly police ourselves in 
> the forum, and I imagine people have an operator on IRC, but it's not 
> clear how the committee is supposed to operate on the differen > channels, are they to be omnipresent?

Phrasing this proposal in a water-proof way would require more wording 
and a much more complicated process than the current proposal. The CoC 
has to withstand conflict, and in a conflict each party will try to find 
loop holes.

> Thirdly, and I'll stop with my ramblings, there will always be grating 
> between people that work on something together for extended periods, no 
> matter if it's a huge C++ library or some triviality. If you try to stop 
> all of it, what my feeling of the proposed document is, brace 
> yourselves, you're going to fail miserably. I'd rather suggest handling 
> the extreme cases only and leave people blow off steam once in a while. 
> Disruptions to good order are more often than not correctable by a 
> simple private notice. 

The Committee has the option of only handing out "a private reprimand" 
in case of minor misconduct. See section "Resolutions".

Ulf


More information about the Development mailing list