public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/glep:glep-0076 commit in: /
Date: Thu,  7 Jun 2018 19:26:33 +0000 (UTC)	[thread overview]
Message-ID: <1528396408.53a2e981509d66dbff15cb48cac467a20d943731.ulm@gentoo> (raw)

commit:     53a2e981509d66dbff15cb48cac467a20d943731
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Thu Jun  7 18:33:28 2018 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Thu Jun  7 18:33:28 2018 +0000
URL:        https://gitweb.gentoo.org/data/glep.git/commit/?id=53a2e981

glep-0076: Remove FLA section.

Therefore simplifying the policy, as discussed in #gentoo-council.

 glep-0076.rst | 51 +++++++++++----------------------------------------
 1 file changed, 11 insertions(+), 40 deletions(-)

diff --git a/glep-0076.rst b/glep-0076.rst
index 9fc4605..58bed23 100644
--- a/glep-0076.rst
+++ b/glep-0076.rst
@@ -10,7 +10,7 @@ Type: Informational
 Status: Draft
 Version: 1
 Created: 2013-04-23
-Last-Modified: 2018-06-03
+Last-Modified: 2018-06-07
 Post-History: 
 Content-Type: text/x-rst
 ---
@@ -72,10 +72,9 @@ License Agreement [#FLA]_, which takes a copyleft approach to
 copyright licensing, while also better complying with copyright laws
 in nations that have author's rights.
 
-The goal here was to create a policy that was both flexible enough to
-cover forks and situations where Gentoo would not own the majority of
-the copyright in a file, while also preserving our ability to formally
-own copyrights on as much of our works as possible.
+The goal here was to create a policy that was flexible enough to cover
+forks and situations where Gentoo would not own the majority of the
+copyright in a file.
 
 
 Specification
@@ -192,28 +191,6 @@ Any concerns not addressed by a maintainer can be appealed to the
 Trustees.
 
 
-Licensing to the Gentoo Foundation
-----------------------------------
-
-All are welcome and encouraged (but *not* required) to assign copyright
-for their contributions to the Gentoo Foundation.  Doing so makes
-compliance with this policy easier (fewer copyright holders to list),
-and allows the Foundation to enforce copyrights and re-license content
-if appropriate (this will only be done in accordance with the social
-contract and the Gentoo FLA).
-
-Copyright is assigned to the Foundation by electronically signing the
-Gentoo Fiduciary License Agreement (FLA) [#GFLA]_.
-
-The agreement may be signed BY **TODO...**  If the scope of the signed
-agreement included future contributions, the contributor may document
-their wish to stop assigning copyright by **TODO...**
-
-A list of those who have signed this agreement and the scope of their
-assignments may be found at **LINK**.  This list may be useful when
-attributing copyright.
-
-
 Rationale
 =========
 
@@ -227,17 +204,14 @@ including its contributors, developers and users.  Additionally, it is
 enforced for all other projects hosted on Gentoo infrastructure in order
 to protect the Gentoo infrastructure owners and improve consistency.
 
-The copyright model is built on a combination of DCO model used
-by the Linux kernel with FLA model used by different open source
-projects.  It requires all contributors to certify the legitimacy
-of their contributions; however, they can freely choose whether to
-assign the copyright to Gentoo, or not.
+The copyright model is built on the DCO model used by the Linux kernel
+and requires all contributors to certify the legitimacy of their
+contributions.
 
-Ideally, all major contributors to Gentoo would choose to sign the FLA.
-However, enforcing it for all contributors would only create unnecessary
-bureaucracy for trivial contributions and discourage a number of users
-from actually contributing to Gentoo.  The mixed model allows users to
-choose a way of contributing that is appropriate to them.
+In the future, a second stage of this policy may use a combination of
+the DCO model and an FLA model as it is used by different open source
+projects.  Contributors would be able to freely choose whether they
+sign the FLA document or not.
 
 
 DCO changes
@@ -376,9 +350,6 @@ References
 .. [#FLA] FSFE Legal: Fiduciary Licence Agreement (FLA),
    https://fsfe.org/activities/ftf/fla.en.html
 
-.. [#GFLA] Gentoo Fiduciary License Agreement,
-   https://dev.gentoo.org/~rich0/fla.pdf
-
 .. [#DEBIAN-LICENSE] [debian-legal] License of the GPL license,
    https://lists.debian.org/debian-legal/2018/04/msg00006.html
 


             reply	other threads:[~2018-06-07 19:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 19:26 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-07 19:26 [gentoo-commits] data/glep:glep-0076 commit in: / Ulrich Müller
2018-06-07 19:26 Ulrich Müller
2018-06-07 19:26 Ulrich Müller
2018-06-19 17:31 Ulrich Müller
2018-06-23 21:37 Ulrich Müller
2018-06-23 21:37 Ulrich Müller
2018-08-24 20:15 Ulrich Müller
2018-08-24 20:15 Ulrich Müller
2018-08-24 20:15 Ulrich Müller
2018-08-24 20:15 Ulrich Müller
2018-08-29 16:56 Ulrich Müller
2018-08-29 16:56 Ulrich Müller
2018-08-31 15:35 Ulrich Müller
2018-09-03 14:48 Ulrich Müller
2018-09-08 13:42 [gentoo-commits] data/glep:master " Ulrich Müller
2018-09-08 13:41 ` [gentoo-commits] data/glep:glep-0076 " Ulrich Müller

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=1528396408.53a2e981509d66dbff15cb48cac467a20d943731.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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