From:
GCC drops its copyright-assignment requirement
The GCC compiler, like other GNU projects, has long required contributors to complete paperwork assigning the copyrights on their work to the Free Software Foundation. That requirement has just been dropped, and contributors can now attach a Signed-off-by tag indicating use of the Developers Certificate of Origin instead. “This change is consistent with the practices of many other major Free Software projects, such as the Linux kernel.” Initial discussion suggests that some developers were surprised by this change and are yet to be convinced that it is a good idea.
From:David Edelsohn via Gcc <gcc-AT-gcc.gnu.org>
To:GCC Development <gcc-AT-gcc.gnu.org>
Subject:Update to GCC copyright assignment policy
Date:Tue, 01 Jun 2021 10:00:06 -0400
Message-ID:CAGWvnyme6cQUGb+G4=tesNYqLYBSGnDYb95LH2zVUgxovHU7kw@mail.gmail.com
Archive-link:Article
GCC was created as part of the GNU Project but has grown to operate as
an autonomous project.The GCC Steering Committee has decided to relax the requirement to
assign copyright for all changes to the Free Software Foundation. GCC
will continue to be developed, distributed, and licensed under the GNU
General Public License v3.0. GCC will now accept contributions with or
without an FSF copyright assignment. This change is consistent with
the practices of many other major Free Software projects, such as the
Linux kernel.Contributors who have an FSF Copyright Assignment don’t need to
change anything. Contributors who wish to utilize the Developer Certificate
of Origin[1] should add a Signed-off-by message to their commit messages.
Developers with commit access may add their name to the DCO list in the
MAINTAINERS file to certify the DCO for all future commits in lieu of individual
Signed-off-by messages for each commit.The GCC Steering Committee continues to affirm the principles of Free
Software, and that will never change.- The GCC Steering Committee
讨论：