Re: Introducing a GDB Code Of Conduct

[Andrew Burgess <aburgess@redhat.com>]

Mike Frysinger <vapier@gentoo.org> writes:

> On 30 Nov 2023 15:59, Andrew Burgess wrote:
>> Many GNU toolchain projects have adopted a Code of Conduct (CoC)
>> recently, and I believe that GDB should do likewise.
>
> adopting a CoC sounds fine, but really seems like we should be using the
> same one across them.  there isn't anything in the content that screams
> "this only makes sense for XXX project".  can't we do this akin to how
> we merge changes from "upstream" gcc tree ?
>
> yes, i know there are a few things inline like "here's the gdb e-mail",
> but that should be fairly trivial to summarize at the beginning/end, or
> ideally in a sep file altogether to make merging trivial.

Mike,

I agree that having a common policy would be great.  But as Eli has
already said, he strongly objects to both the GCC and binutils CoC.  And
if it comes to loosing Eli from the project or adopting a different CoC,
then I choose the latter.

I don't feel there is anything significantly different between what is
proposed here and either of the other CoC.  But I don't see any
significant cost in having a different policy.  Even if we did adopt the
same policy as some other project, I'd still be proposing that we (GDB)
should have our own CoC committee -- it's pretty important to me that
this should be the community policing itself, not some outside group
policing us.  As such, we (GDB) might choose to handle/interpret some
situation slightly differently to another project -- so simply having
the same written words wouldn't necessarily mean things are handled
exactly the same.

Thanks,
Andrew