Home Original page

Binutils Code of Conduct

Richard Earnshaw (lists) Richard.Earnshaw@arm.com
Tue Oct 3 09:54:39 GMT 2023 
On 28/09/2023 21:27, Carlos O'Donell via Binutils wrote:
> On 9/26/23 12:02, Nick Clifton via Binutils wrote:
>>   We are going to have a Code of Conduct for the GNU Binutils.
>>
>>   Rather than reinvent the wheel however, I have decided to take GCC's
>>   code of conduct and tweak it for us.  The revised text is attached
>>   below.
>>
>>   If you have any strong objections to this please let me know as soon
>>   as possible, as I plan to put the text up on the binutils web page and
>>   wiki by the end of the week.
>>
>>   If you are interested in volunteering to be on the Code Of Conduct
>>   committee, please let me know directly, or email
>>   binutils-conduct@sourceware.org.  In the meantime my boss Mark O'Brian
>>   has volunteered to be on the committee so we will be starting off with
>>   at least one person.
> 
> Thanks for working on this Nick.
> 
> I've been thinking of exactly the same thing for glibc:
> https://sourceware.org/glibc/wiki/conduct
> 
> Should this go on the binutils wiki?
> 
> I'd be happy to volunteer to be on the CoCC for binutils.
> 
> If we adopt something like this for all of the GNU Toolchain projects we can probably
> work together to process and respond to CoCC issues across the communities.
> 
> There is quite a bit we can learn from downstream distributions too like Gentoo,
> Debian, Fedora etc.
> 

I realize that we have separate projects, each with slightly different governance structures, but I'd really like to see *one* CoC that covers all of the GNU toolchain components - gcc, glibc, binutils and gdb - rather than one for each which is nearly, but not quite the same.  Yes, each component can have a different committee, as needed (and that might lead to slightly different interpretations), but having identical policies would help foster better understanding and compliance IMO.

R.
More information about the Binutils mailing list