I have been thinking about this, and I think I might need to go back on
my comment on "Code of Conduct" as a name - maybe Groovy needs
something, that better expresses how non-toxic and constructive the
environment here is, especially when compared to some of the worse
examples out t
Paul King wrote:
>> Hi everyone,
>> We have been fortunate that most of the time, the discussions within our
>> community are very respectful, so I don't think we need to have an elaborate
>> discussion about a project-specific code of conduct. It seems worthwhile
ly - be my guest. I really want to know.
>> Thank you!
>>
>> With regards,
>>Cos
>>
>> On 18.11.2020 02:47, Paul King wrote:
>> >
>> > Hi everyone,
>> >
>> > We have been fortunate that most of the time, the discussions wi
gt; >
> > We have been fortunate that most of the time, the discussions within
> > our community are very respectful, so I don't think we need to have an
> > elaborate discussion about a project-specific code of conduct. It seems
> > worthwhile though, pointing to the g
about a project-specific code of conduct. It seems worthwhile
> though, pointing to the general code of conduct established by the ASF[1]
> which I propose to do:
>
> https://github.com/apache/groovy/pull/1422
>
> Let me know if you see any possible improvements/issue
cussion about a project-specific code of conduct. It seems
worthwhile though, pointing to the general code of conduct established
by the ASF[1] which I propose to do:
https://github.com/apache/groovy/pull/1422
<https://github.com/apache/groovy/pull/1422>
Let me know if you see any possibl
very respectful, so I don't think we
need to have an elaborate discussion about a project-specific
code of conduct. It seems worthwhile though, pointing to the
general code of conduct established by the ASF[1] which I
propose to do:
https://github.c
very respectful, so I don't think we need to have an
>> elaborate discussion about a project-specific code of conduct. It seems
>> worthwhile though, pointing to the general code of conduct established by
>> the ASF[1] which I propose to do:
>>
>> https://gi
bout a project-specific code of
conduct. It seems worthwhile though, pointing to the general code
of conduct established by the ASF[1] which I propose to do:
https://github.com/apache/groovy/pull/1422
<https://github.com/apache/groovy/pull/1422>
Let me know if you see any p
We have been fortunate that most of the time, the discussions within
> our community are very respectful, so I don't think we need to have an
> elaborate discussion about a project-specific code of conduct. It seems
> worthwhile though, pointing to the general code of conduct establish
Hi everyone,
We have been fortunate that most of the time, the discussions within
our community are very respectful, so I don't think we need to have an
elaborate discussion about a project-specific code of conduct. It seems
worthwhile though, pointing to the general code of conduct establ
11 matches
Mail list logo
