search for: coc

...anl NH Black 26+ 0.3748 0.06124 anl NH AM-AK 26+ 1.4842 0.52284 anl NH HI-OPI 26+ 0.3898 0.34827 anl NH Asian 26+ 0.2536 0.07643 anl NH Multiracial 26+ 0.5120 0.18326 anl Mexican 12-17 0.2453 0.15761 coc Puerto Rican 12-17 0.4351 0.06999 coc Cuban 12-17 0.2472 0.24698 coc C-S American 12-17 0.2399 0.15804 coc Dominican 12-17 0.0000 0.00000 coc Spanish (Spain) 12-17 0.5315 0.30907 coc Multi Hisp Eth 12-17 0.9797 0.53981 coc...

...s I've seen was the kernel and docker, both fairly loose communities, where it didn't seem to have *any* consensus on behaviour whatsoever. We're not like that. When kernel folks come to us and start swearing, we ask them to stop, then we ignore their emails. That's better than and CoC could ever ask for. So, here's a turn on the tables... * Can anyone prove that a CoC would be more effective against abuse than the already very effective and cost free method we use? * Can anyone come up with a threat that the current consensus would not protect us from, and at the same t...

On Fri, 30 Nov 2018, Kees Cook wrote: >On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen ><jarkko.sakkinen at linux.intel.com> wrote: >> >> In order to comply with the CoC, replace **** with a hug. I hope this is some kind of joke. How would anyone get offended by reading technical comments? This is all beyond me... Thanks, Davidlohr

> Also, the problem with enumerating all the inacceptable behaviour is > that the text tends to become TL;DR. Which means permanent discomfort: I > never fully read the rules, so I'm never fully sure that I'm not > violating the CoC, nor am I sure whether others violate it. > > In terms of size and complexity, the proposed CoC is shorter than the > typical bulletin board CoC, so it's not bad; however, it think it could > be made more compact. Compactness is a definite virtue. I remember attending a very succe...

On 14 October 2015 at 14:32, Krzysztof Parzyszek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > CoC is not going to stop or prevent any harassment. True. > The current administrators of the mailing > lists, or the organizers of the LLVM conferences already have the means to > deal with it. Not really. We haven't had to ban anyone from the list or kick anyone from a conference yet...

...dev" <llvm-dev at lists.llvm.org> > Sent: Tuesday, October 13, 2015 6:08:08 PM > Subject: Re: [llvm-dev] RFC: Introducing an LLVM Community Code of Conduct > ... > > > The only bit that seems to me really needs fleshing out is what the > process for appointing the CoC committee is. I'd sort of assume > based on what other organizations do that the LLVM Foundation Board > would be responsible for appointing the Committee, but that the > Board and the Committe would not be one and the same. > > Of course, the LLVM Foundation Board *really* must...

...t fear of irrational (to our minds) reprimands. This is not a simple matter, it's quite real and have made me seriously consider many times leaving the open source realm for good. I have left jobs and regressed in my career because of things like that. >From the very wording in the proposed CoC, we don't want to leave anyone behind, including physical and mental disabilities. If that's true, and we really mean it, than imposing such a harsh CoC from the majority of opinions is exactly the opposite of that. People like me are clearly not the majority, the NAS UK estimates 1 every 1...

...t 11:56:52AM -0800, Davidlohr Bueso wrote: > > On Fri, 30 Nov 2018, Kees Cook wrote: > > > > > On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen > > > <jarkko.sakkinen at linux.intel.com> wrote: > > > > > > > > In order to comply with the CoC, replace **** with a hug. > > > > I hope this is some kind of joke. How would anyone get offended by > > reading technical comments? This is all beyond me... > > Well... Not a joke really but more like conversation starter :-) > > I had 10h flight from Amsterdam to...

> On Oct 13, 2015, at 10:23 AM, Bill Kelly via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Renato Golin via llvm-dev wrote: >> On 13 October 2015 at 17:16, Kuperstein, Michael M via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> The FreeBSD CoC is, IMHO, much better in this respect ( https://www.freebsd.org/internal/code-of-conduct.html ). >> >> Nice! This is so succinct and beautiful! >> >> It doesn't need an overseeing foundation to take opaque decisions, and >> focus on what's really important: t...

...eople consider to be bad language > > isn't necessarily abusive, offensive or degrading. Our most > > heavily censored medium is TV and "fuck" is now considered > > acceptable in certain contexts on most channels in the UK and EU. > > This makes following the CoC extremely hard to a non-native speaker > as it is not too explicit on what is OK and what is not. I did > through the whole thing with an eye glass and this what I deduced > from it. OK, so something that would simply be considered in some quarters as bad language isn't explicitly ban...

I like the NCoC approach, actually. I think the community can manage itself quite well. Echoing a prior response---if this community really needs a set of rules, then it has already deteriorated. We are not there and it doesn't look like we are going in that direction. The FreeBSD CoC also looks reasona...

While I'm replying to Renato here, that is mostly because there are too many replies on this subject, and too many of them have wandered off into other topics. I want to specifically address the concerns with verbosity. For example: On Tue, Oct 13, 2015 at 3:52 AM Renato Golin <renato.golin at linaro.org> wrote: > I also agree that some descriptions are too verbose, and trying to

On 13 October 2015 at 17:16, Kuperstein, Michael M via llvm-dev <llvm-dev at lists.llvm.org> wrote: > The FreeBSD CoC is, IMHO, much better in this respect ( https://www.freebsd.org/internal/code-of-conduct.html ). Nice! This is so succinct and beautiful! It doesn't need an overseeing foundation to take opaque decisions, and focus on what's really important: the code. I particularly like "Do not ma...

...e this is just as bad as having no code of conduct at all. It trivializes the importance of a code of conduct and its pretty much impossible to enforce. Code of conduct should reflect the community standards, not define them. These standards come from the minds of the members of the community. A CoC that states this much and outlines the core principles underlying these standards is a statement of faith in the community itself. It stresses the fact that the community can enforce its own standards, and in doing so be guided by the core principle of respect, and not by a list of prohibited b...

...ental, physical, logical, > or anything else that still doesn't exist, we don't need to be > specific. Someone said earlier, the more specific we are now, the more > we'll argue about it. We don't need that. > > I also don't understand why specifically the Django CoC is so > important for us to follow. > > cheers, > --renato Hi Renato, I sense you feel passionate about this issue. I read the Django CoC. And I personally do not feel there is anything in there that is overarching nor exclusionary. I don't think such a CoC would limit reasonable...

...has multiple convictions for sexual assault or other violent crime. Person A does not get to attend LLVM events. 3) Person A (an existing LLVM contributor) takes a technical discussion from LLVM with Person B into an alternate channel so as to personally attack person B without being subject to CoC. Workaround does not work, still a violation of CoC. 4) Person A uses CoC to attack Person B based on Person B's stated political views in an outside venue. Person B has always followed CoC in LLVM interactions and has keep personal politics separate. Person A (who may not even be a member...

...M, Davidlohr Bueso wrote: > >> On Fri, 30 Nov 2018, Kees Cook wrote: > >> > >>> On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen > >>> <jarkko.sakkinen at linux.intel.com> wrote: > >>>> > >>>> In order to comply with the CoC, replace **** with a hug. > >> > >> I hope this is some kind of joke. How would anyone get offended by reading > >> technical comments? This is all beyond me... > > > > Agree, this is insanity. > > And even worse it is censorship. It is not close to...

...to welcome people of all "political belief". Except > those whose political belief mean that they don't agree with the code > of conduct. Since agreement is required to take part in the > conferences, I am no longer able to attend. > I feel exactly the same way about the CoC. The whole CoC idea is just a bullshit that brings discord in open source projects. I haven't seen a project that adopted a CoC and had no members leaved after that. > > The last drop was llvm associating itself with an organization that > openly discriminates based on sex and ances...

+1 for this TL;DR suggestion - you can guarantee most people would read < 7 short bullet points. Cheers, -Neil. On 06/05/16 15:53, Arnaud Allard de Grandmaison via llvm-dev wrote: > For what it's worth, I think this is an improved version of the CoC, > and I'm OK with it. Thanks to Chandler and all those who have been > working on it. > > It's not perfect --- and will never be --- but that's a good base to > settle on. We can always evolve it later based on real life feedback. > > My only suggestion for impr...

...from calling someone else out > for generally being a bully or troll.. Specifically if I went through > and found say 6 cases where X caused friction in the community and in > general their behavior was more noise than actually productive. Your point is directly contradicted by the current CoC proposal. Calling someone out on inappropriate behavior is absolutely appropriate. However, doing so without making it into a personal attack is important as well. "Hey, what you just said is not okay. I'm sure you didn't mean to be personal insulting, but that came across as......