From: Nick Clifton <nickc@redhat.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
Sagar Patel <sagarmp@cs.unc.edu>
Cc: Chenghua Xu <paul.hua.gm@gmail.com>, binutils@sourceware.org
Subject: Re: [committed v2] MIPS/opcodes: Fix alias annotation for branch instructions
Date: Mon, 7 Mar 2022 12:50:29 +0000 [thread overview]
Message-ID: <2a102aea-e99f-aa4c-9b49-e618f04ba660@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2203071140470.47558@angie.orcam.me.uk>
Hi Maciej, Hi Sagar,
>> It would be great if this project could drop the copyright assignment
>> requirement like gcc [1]. This would certainly reduce friction in the
>> process of contributing. (I know you're probably not the person that
>> makes these decisions. Just putting this out there.)
>
> I do not know if any decision WRT the copyright policy for binutils will
> be unilateral or consensus-based (probably the latter, in which case I
> will most likely have a chance to speak out), but in any case Nick will
> be the best person to tell. Nick?
This really needs to be a consensus based decision. I would not feel comfortable
imposing such a change on the project, especially if there are strong objections
to it.
From a personal point of view, I would like to continue to support the FSF and
it goal of Free Software for all. But I understand that recent events have made
some contributors unhappy with the governance of the FSF and as a result they are
less willing to pursue copyright assignments.
Cheers
Nick
prev parent reply other threads:[~2022-03-07 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 18:32 Maciej W. Rozycki
2022-03-07 7:13 ` Sagar Patel
2022-03-07 11:51 ` Maciej W. Rozycki
2022-03-07 12:50 ` Nick Clifton [this message]
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=2a102aea-e99f-aa4c-9b49-e618f04ba660@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=paul.hua.gm@gmail.com \
--cc=sagarmp@cs.unc.edu \
/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).