public inbox for
help / color / mirror / Atom feed
* gcc-wwwdocs branch master updated. 95cf0688ab3b1973f60133d32bcd29e373186cec
@ 2021-06-02 13:40 Jason Merrill
  0 siblings, 0 replies; only message in thread
From: Jason Merrill @ 2021-06-02 13:40 UTC (permalink / raw)
  To: gcc-cvs-wwwdocs

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
 <a href=""></a> a copy of
 your request.</p>
-<p>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.</p>
-<p>We can accept small changes without a copyright disclaimer or a
-copyright assignment on file.</p>
+<p>Alternatively, a contributor can certify the
+<a href="">Developer Certificate of Origin</a>
+for their contribution by adding
+the <a href="dco.html"><code>Signed-off-by:</code></a> tag to their submission.
+Contributors with
+<a href="">commit access</a> can certify the
+DCO for all future commits by adding their name to the DCO list in the
+<p>We can accept small changes without copyright assignment or DCO
 <h2 id="standards">Coding Standards</h2>
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 @@
+<!DOCTYPE html>
+<html lang="en">
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Contributing to GCC: DCO Sign-off</title>
+<link rel="stylesheet" type="text/css" href="" />
+<h1>Developer's Certificate of Origin (DCO) Sign-off</h1>
+<p>The GCC project now allows contributions to use the "sign-off" procedure
+originally introduced by the
+<a href="">Linux
+Kernel</a> 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.</p>
+<p>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:</p>
+<h4><a href="">Developer's Certificate of Origin 1.1</a></h4>
+<p>By making a contribution to this project, I certify that:</p>
+<ol type="a">
+<li>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</li>
+<li>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</li>
+<li>The contribution was provided directly to me by some other
+  person who certified (a), (b) or (c) and I have not modified
+  it.</li>
+<li>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.</li>
+then you just add a line saying:
+<pre>    Signed-off-by: Random J Developer &lt;></pre>
+using your real name (sorry, no pseudonyms or anonymous contributions.)  This
+will be done for you automatically if you use `git commit -s`.
+<p>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.</p>
+<p>Developers with <a href="gitwrite.html">write access</a> should certify the DCO
+for all their patches by adding themselves to the DCO list in the MAINTAINERS
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 @@
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>GCC Development Mission Statement (1999-04-22)</title>
+<title>GCC Development Mission Statement (2021-06-01)</title>
 <link rel="stylesheet" type="text/css" href="" />
-<h1>GCC Development Mission Statement (1999-04-22)</h1>
+<h1>GCC Development Mission Statement (2021-06-01)</h1>
 <p>GCC development is a part of the <a href="">GNU
 Project</a>, aiming to improve the compiler used in the GNU system
@@ -24,16 +24,13 @@ GCC.</p>
 <h2>Free Software Project</h2>
-<li>Supporting the goals of the GNU project, as defined by the FSF.</li>
+<li>Supporting the goals of the GNU project.</li>
 <li>Compilers are available under the terms of the GPL.</li>
-<li>Copyrights for the compilers are to be held by the FSF.</li>
-<li>Other components (runtime libraries, testsuites, etc) will be
-    available under various free licenses with copyrights being held
-    by individual authors or the FSF.</li>
-<li>All legal relationships with contributors and users are the
-    responsibility of the FSF.</li>
-<li>Patches must be legally acceptable for inclusion into the GNU
-    project.</li>
+<li>Other components (runtime libraries, testsuites, etc) are
+  available under various free licenses.</li>
+<li>Copyrights are held by individual authors or the FSF.</li>
+<li>Patches must be <a href="contribute.html#legal">legally acceptable</a> for
+  redistribution under the applicable license.</li>
 <h2>Design and Development Goals</h2>
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 <em>must</em>
 be exactly the same between your account on 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").</p>
+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.</p>
 <p>Then produce a diff to that file and circulate it to the
 <code>gcc-patches</code> list, whilst also checking in your change to
@@ -139,8 +140,8 @@ the appropriate policies.</p>
   patches may be checked in.  The steering committee
   or a well-established GCC maintainer (including reviewers) can
   <a href="#authenticated">approve for write access</a> any person
-  with GNU copyright assignment papers in place and known to submit
-  good patches.</p></dd>
+  with GNU copyright assignment or <a href="dco.html">DCO</a> certification
+  in place and known to submit good patches.</p></dd>
 <p>The list of folks with write access to the repository can be found
@@ -171,8 +172,9 @@ outside the tree from their official versions</a>.</p>
 <p><a href="#branches">Creating and using a branch</a> 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.</p>
+changes on the branch have copyright assignments or <a href="dco.html">DCO</a>
+certification.  Merging such developments back to the mainline still needs
+approval in the usual way.</p>
 <hr />


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


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-06-02 13:40 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-02 13:40 gcc-wwwdocs branch master updated. 95cf0688ab3b1973f60133d32bcd29e373186cec Jason Merrill

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).