From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2122) id 23EC23886C7F; Wed, 2 Jun 2021 13:40:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 23EC23886C7F To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 95cf0688ab3b1973f60133d32bcd29e373186cec X-Git-Refname: refs/heads/master X-Git-Reftype: branch X-Git-Oldrev: cc39141b5c2caa600aa90532d4e6ea6e97fd2d4b X-Git-Newrev: 95cf0688ab3b1973f60133d32bcd29e373186cec Message-Id: <20210602134044.23EC23886C7F@sourceware.org> Date: Wed, 2 Jun 2021 13:40:44 +0000 (GMT) From: Jason Merrill X-BeenThere: gcc-cvs-wwwdocs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-cvs-wwwdocs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2021 13:40:44 -0000 This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 95cf0688ab3b1973f60133d32bcd29e373186cec (commit) from cc39141b5c2caa600aa90532d4e6ea6e97fd2d4b (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 95cf0688ab3b1973f60133d32bcd29e373186cec Author: Jason Merrill Date: Tue May 18 10:32:57 2021 -0400 contribute, gccmission, gitwrite: update for DCO diff --git a/htdocs/contribute.html b/htdocs/contribute.html index a913565b..c0cce359 100644 --- a/htdocs/contribute.html +++ b/htdocs/contribute.html @@ -50,14 +50,17 @@ It's a good idea to send assign@gnu.org a copy of your request.

If a contributor is reluctant to sign a copyright assignment for a -change, a copyright disclaimer to put the change in the public domain is -acceptable as well. A copyright assignment is more convenient if a -contributor plans to make several separate contributions.

- -

We can accept small changes without a copyright disclaimer or a -copyright assignment on file.

Alternatively, a contributor can certify the +Developer Certificate of Origin +for their contribution by adding +the Signed-off-by: tag to their submission. +Contributors with +commit access can certify the +DCO for all future commits by adding their name to the DCO list in the +MAINTAINERS file. +

We can accept small changes without copyright assignment or DCO +certification.

Coding Standards

diff --git a/htdocs/dco.html b/htdocs/dco.html new file mode 100644 index 00000000..52f7607a --- /dev/null +++ b/htdocs/dco.html @@ -0,0 +1,67 @@ + + + + +Contributing to GCC: DCO Sign-off + + + + + +

Developer's Certificate of Origin (DCO) Sign-off

+ +

The GCC project now allows contributions to use the "sign-off" procedure +originally introduced by the +Linux +Kernel project, and subsequently adopted by many other free software +projects. This procedure is required for contributions not covered by either +FSF copyright assignment or the MAINTAINERS DCO list.

+ +

The sign-off is a simple line at the end of the explanation for the +patch, which certifies that you wrote it or otherwise have the right to +pass it on as a free software patch. The rules are pretty simple: if you + can certify the below:

+ +

Developer's Certificate of Origin 1.1

+ +

By making a contribution to this project, I certify that:

+ +

The contribution was created in whole or in part by me and I + have the right to submit it under the open source license + indicated in the file; or
The contribution is based upon previous work that, to the best + of my knowledge, is covered under an appropriate open source + license and I have the right under that license to submit that + work with modifications, whether created in whole or in part + by me, under the same open source license (unless I am + permitted to submit under a different license), as indicated + in the file; or
The contribution was provided directly to me by some other + person who certified (a), (b) or (c) and I have not modified + it.
I understand and agree that this project and the contribution + are public and that a record of the contribution (including all + personal information I submit with it, including my sign-off) is + maintained indefinitely and may be redistributed consistent with + this project or the open source license(s) involved.

+ +then you just add a line saying: + +

    Signed-off-by: Random J Developer <random@developer.example.org>

+ +using your real name (sorry, no pseudonyms or anonymous contributions.) This +will be done for you automatically if you use `git commit -s`. + +

Some people also put extra optional tags at the end. The GCC project does +not require tags from anyone other than the original author of the patch, but +other people involved in passing along the patch can add their own +Signed-off-by if they wish.

+ +

Developers with write access should certify the DCO +for all their patches by adding themselves to the DCO list in the MAINTAINERS +file.

diff --git a/htdocs/gccmission.html b/htdocs/gccmission.html index d7e5ce1d..d5f4c1de 100644 --- a/htdocs/gccmission.html +++ b/htdocs/gccmission.html @@ -3,13 +3,13 @@ -GCC Development Mission Statement (1999-04-22) +GCC Development Mission Statement (2021-06-01) -

GCC Development Mission Statement (1999-04-22)

GCC Development Mission Statement (2021-06-01)

GCC development is a part of the GNU Project, aiming to improve the compiler used in the GNU system @@ -24,16 +24,13 @@ GCC.

Free Software Project

Supporting the goals of the GNU project, as defined by the FSF.
Supporting the goals of the GNU project.
Compilers are available under the terms of the GPL.
Copyrights for the compilers are to be held by the FSF.
Other components (runtime libraries, testsuites, etc) will be - available under various free licenses with copyrights being held - by individual authors or the FSF.
All legal relationships with contributors and users are the - responsibility of the FSF.
Patches must be legally acceptable for inclusion into the GNU - project.
Other components (runtime libraries, testsuites, etc) are + available under various free licenses.
Copyrights are held by individual authors or the FSF.
Patches must be legally acceptable for + redistribution under the applicable license.

Design and Development Goals

diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index 596f3bef..51f611f0 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -48,7 +48,8 @@ to the MAINTAINERS file. Note: Your first and last names must be exactly the same between your account on gcc.gnu.org and the MAINTAINERS file. Place your name in the correct section following the conventions specified in the file (e.g. "Write After Approval" -is "last name alphabetical order").

+is "last name alphabetical order"). If you do not have an FSF copyright +assignment on file, also add yourself to the DCO section in the file.

Then produce a diff to that file and circulate it to the gcc-patches list, whilst also checking in your change to @@ -139,8 +140,8 @@ the appropriate policies.

patches may be checked in. The steering committee or a well-established GCC maintainer (including reviewers) can approve for write access any person - with GNU copyright assignment papers in place and known to submit - good patches.

+ with GNU copyright assignment or DCO certification + in place and known to submit good patches.

The list of folks with write access to the repository can be found @@ -171,8 +172,9 @@ outside the tree from their official versions.

Creating and using a branch for development, including outside the parts of the compiler one maintains, provided that -changes on the branch have copyright assignments on file. Merging such -developments back to the mainline still needs approval in the usual way.

+changes on the branch have copyright assignments or DCO +certification. Merging such developments back to the mainline still needs +approval in the usual way.

----------------------------------------------------------------------- Summary of changes: htdocs/contribute.html | 19 ++++++++------ htdocs/dco.html | 67 ++++++++++++++++++++++++++++++++++++++++++++++++++ htdocs/gccmission.html | 19 ++++++-------- htdocs/gitwrite.html | 12 +++++---- 4 files changed, 93 insertions(+), 24 deletions(-) create mode 100644 htdocs/dco.html hooks/post-receive -- gcc-wwwdocs