From: Alexandre Oliva <oliva@gnu.org>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: Nick Clifton via Binutils <binutils@sourceware.org>,
Nick Clifton <nickc@redhat.com>,
ganandan@redhat.com, markobri@redhat.com
Subject: Re: Binutils Code of Conduct
Date: Thu, 28 Sep 2023 20:12:31 -0300 [thread overview]
Message-ID: <or1qehdh9c.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <8b2e929d-e5bf-1e13-3b5e-ced3871246d9@redhat.com> (Carlos O'Donell's message of "Thu, 28 Sep 2023 16:42:08 -0400")
On Sep 28, 2023, "Carlos O'Donell" <carlos@redhat.com> wrote:
> On 9/28/23 15:27, Alexandre Oliva via Binutils wrote:
>> On Sep 26, 2023, Nick Clifton via Binutils <binutils@sourceware.org> wrote:
>>
>>> We are going to have a Code of Conduct for the GNU Binutils.
>>
>> This sounds like the decision has already been made. Is that so? Did I
>> miss any discussion with volunteer port maintainers like myself, and
>> other community members?
> I support Nick's decision, and I think it's the right decision to make for the project.
It looks like your response was a reaction to my alternate proposal of
community governance. Would you be considerate enough to summarize the
relevant differences you perceive between the proposals, and justify
your preference for one over the other? Otherwise it might seem like
you didn't even look.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice but
very few check the facts. Think Assange & Stallman. The empires strike back
next prev parent reply other threads:[~2023-09-28 23:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 16:02 Nick Clifton
2023-09-28 19:27 ` Alexandre Oliva
2023-09-28 20:42 ` Carlos O'Donell
2023-09-28 23:12 ` Alexandre Oliva [this message]
2023-09-28 23:35 ` Mark Wielaard
2023-09-29 13:39 ` Nick Clifton
2023-09-29 15:03 ` Matt Rice
2023-09-29 17:30 ` Alexandre Oliva
2023-09-28 20:27 ` Carlos O'Donell
2023-10-03 9:54 ` Richard Earnshaw (lists)
2023-10-03 10:36 ` Nick Clifton
2023-10-03 17:52 ` Tom Tromey
2023-09-29 12:52 ` Gomathi Anandan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=or1qehdh9c.fsf@lxoliva.fsfla.org \
--to=oliva@gnu.org \
--cc=binutils@sourceware.org \
--cc=carlos@redhat.com \
--cc=ganandan@redhat.com \
--cc=markobri@redhat.com \
--cc=nickc@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).