[gentoo-project] [PATCH] glep-{0001,0002}: New GLEPs are to be licensed under CC-BY-SA-4.0.

[gentoo-project] [PATCH] glep-{0001,0002}: New GLEPs are to be licensed under CC-BY-SA-4.0.

[Ulrich Müller]

[-- Attachment #1.1: Type: text/plain, Size: 4142 bytes --]

GLEP 76 says that new documentation must be released under CC-BY-SA
version 4.0. Update the guidelines (GLEP 1) and the template (GLEP 2)
to agree with this policy.

Drop the wording about older GLEPs in the public domain or released
under the OPL, because all of them have been updated.

Signed-off-by: Ulrich Müller <ulm@gentoo.org>
---
 glep-0001.rst | 23 ++++++++++-------------
 glep-0002.rst | 12 ++++++------
 2 files changed, 16 insertions(+), 19 deletions(-)

diff --git a/glep-0001.rst b/glep-0001.rst
index 15deccb..61a08a4 100644
--- a/glep-0001.rst
+++ b/glep-0001.rst
@@ -6,11 +6,11 @@ Author: Grant Goodyear <g2boojum@gentoo.org>,
         Ulrich Müller <ulm@gentoo.org>
 Type: Informational
 Status: Active
-Version: 3
+Version: 4
 Created: 2003-05-31
 Last-Modified: 2019-11-24
 Post-History: 2003-06-01, 2003-07-02, 2008-01-19, 2008-06-05, 2011-03-09,
-              2013-12-14, 2017-09-17, 2018-07-10
+              2013-12-14, 2017-09-17, 2018-07-10, 2019-11-24
 Content-Type: text/x-rst
 ---
 
@@ -211,13 +211,10 @@ Each GLEP should have the following parts:
    specification and rationale first and reach consensus on it before writing
    code or significantly modifying ebuilds.
 
-8. Copyright -- Every new GLEP must be explicitly labelled
-   as licensed under the Creative Commons Attribution-ShareAlike (CC-BY-SA)
-   license, version 3.0 [#CC-BY-SA3.0]_. Older GLEPs in the public domain
-   should be relicensed to CC-BY-SA 3.0 when they are updated.
-   GLEPs released under the Open Publication License (OPL) may remain
-   as-is, but are strongly encouraged to be relicensed under CC-BY-SA
-   3.0 with the consent of all authors.
+8. Copyright -- Every new GLEP must be explicitly labelled as licensed under
+   the Creative Commons Attribution-ShareAlike 4.0 International License
+   (CC-BY-SA-4.0) [#CC-BY-SA-4.0]_.  Older GLEPs released under CC-BY-SA-3.0
+   should be relicensed to CC-BY-SA-4.0 when they are updated.
 
 
 GLEP Formating and Template
@@ -374,7 +371,7 @@ References and Footnotes
 
 .. [#COUNCIL] https://www.gentoo.org/glep/glep-0039.html
 
-.. [#CC-BY-SA3.0] https://creativecommons.org/licenses/by-sa/3.0/
+.. [#CC-BY-SA-4.0] https://creativecommons.org/licenses/by-sa/4.0/
 
 .. [#ReSTHOME] http://docutils.sourceforge.net/rst.html
 
@@ -388,6 +385,6 @@ References and Footnotes
 Copyright
 =========
 
-This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
-Unported License.  To view a copy of this license, visit
-https://creativecommons.org/licenses/by-sa/3.0/.
+This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
+International License.  To view a copy of this license, visit
+https://creativecommons.org/licenses/by-sa/4.0/.
diff --git a/glep-0002.rst b/glep-0002.rst
index 67ce3ce..6ef72ca 100644
--- a/glep-0002.rst
+++ b/glep-0002.rst
@@ -6,10 +6,10 @@ Author: Grant Goodyear <g2boojum@gentoo.org>,
         Ulrich Müller <ulm@gentoo.org>
 Type: Informational
 Status: Active
-Version: 3
+Version: 4
 Created: 2003-05-31
 Last-Modified: 2019-11-24
-Post-History: 2003-06-02, 2013-12-17, 2017-09-17
+Post-History: 2003-06-02, 2013-12-17, 2017-09-17, 2019-11-24
 Content-Type: text/x-rst
 ---
 
@@ -128,7 +128,7 @@ directions below.
 
 - Update your References section.  You should leave the Copyright section
   as-is, since all new GLEPs are to be licensed under the Creative Commons
-  Attribution-ShareAlike License, Version 3.0.
+  Attribution-ShareAlike 4.0 International License (CC-BY-SA-4.0).
 
 - Send your GLEP submission to the GLEP editors at glep@gentoo.org.
 
@@ -602,6 +602,6 @@ References
 Copyright
 =========
 
-This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
-Unported License.  To view a copy of this license, visit
-https://creativecommons.org/licenses/by-sa/3.0/.
+This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
+International License.  To view a copy of this license, visit
+https://creativecommons.org/licenses/by-sa/4.0/.
-- 
2.24.0


[-- Attachment #1.2: glep-0001.rst --]
[-- Type: text/plain, Size: 17692 bytes --]

---
GLEP: 1
Title: GLEP Purpose and Guidelines
Author: Grant Goodyear <g2boojum@gentoo.org>,
        Michał Górny <mgorny@gentoo.org>,
        Ulrich Müller <ulm@gentoo.org>
Type: Informational
Status: Active
Version: 4
Created: 2003-05-31
Last-Modified: 2019-11-24
Post-History: 2003-06-01, 2003-07-02, 2008-01-19, 2008-06-05, 2011-03-09,
              2013-12-14, 2017-09-17, 2018-07-10, 2019-11-24
Content-Type: text/x-rst
---

Credits
=======

The GLEP concept, and, in fact, much of the text of this document,
is liberally stolen from Python's [#Python]_ PEPs [#PEPS]_, especially
PEP-0001 [#PEP1]_ by Barry A. Warsaw, Jeremy Hylton, and David Goodger.

What is a GLEP?
===============

GLEP stands for "Gentoo Linux Enhancement Proposal".  A GLEP is a design
document providing information to the Gentoo Linux community, or describing
a new feature for Gentoo Linux.  The GLEP should provide a concise technical
specification of the feature and rationale for the feature.

We intend GLEPs to be the primary mechanisms for proposing *significant* new
features, for collecting community input on an issue, and for
documenting the design decisions that have gone into Gentoo Linux.  The GLEP
author is responsible for building consensus within the community and
documenting dissenting opinions.

Because the GLEPs are maintained as text files in a VCS, their revision
history is the historical record of the feature proposal [#VCS]_. For older
GLEPs, the base repository may provide an approximate history of the changes.
The original changes can still be found in [#CVS]_ for changes up to June 2013
and/or [#WIKI]_ for changes onwards up to September 2017.


Kinds of GLEPs
==============

There are two kinds of GLEPs.  A Standards Track GLEP describes a new feature
or implementation for Gentoo Linux.  An Informational GLEP provides
general guidelines or information to the Gentoo Linux community, but does not
propose a new feature.  Informational GLEPs do not necessarily represent a
Gentoo Linux community consensus or recommendation, so users and implementors
are free to ignore Informational GLEPs or follow their advice.


GLEP Work Flow
==============

The GLEP editors assign GLEP numbers and change their status. Please send all
GLEP-related email to <glep@gentoo.org>.

The GLEP process begins with a new idea for Gentoo Linux.  It is highly
recommended that a single GLEP contain a single key proposal or new idea.  The
more focused the GLEP, the more successful it tends to be.  The GLEP editors
reserve the right to reject GLEP proposals if they appear too unfocused or
too broad.  If in doubt, split your GLEP into several well-focused ones.

Each GLEP must have a champion -- someone who writes the GLEP using the style
and format described below, shepherds the discussions in the appropriate
forums, and attempts to build community consensus around the idea.  The GLEP
champion (a.k.a. Author) should first attempt to ascertain whether the idea is
GLEP-able.  Small enhancements or patches often don't need a GLEP and can be
injected into the Gentoo Linux development work flow with an enhancement "bug"
submitted to the Gentoo Linux bugzilla [#BUGS]_.

The GLEP champion then files a bug on Bugzilla in the GLEP product, under
the "New GLEP submissions" component of the "Documentation" product
and prepares a rough, but fleshed out, draft of the GLEP on a dedicated
branch of the GLEP repository or a private fork of that repository.  This
draft must be written in GLEP style as described below and in GLEP 2.

If the GLEP editors accept the GLEP, they will assign the GLEP a number, label
it as Standards Track (a better name would be nice here -- suggestions?) or
Informational, give it status "Draft", and merge the initial draft of the GLEP
to the master branch of the repository.  The GLEP editors will
not unreasonably deny a GLEP. Reasons for denying GLEP status include
duplication of effort, being technically unsound, not providing proper
motivation or addressing backwards compatibility, or not in keeping with
Gentoo Linux philosophy.

If a pre-GLEP is rejected, the author may elect to take the pre-GLEP
to the gentoo-dev@lists.gentoo.org mailing list (for technical GLEPs)
or the gentoo-project@lists.gentoo.org mailing list (for non-technical GLEPs)
to help flesh it out, gain feedback and consensus from the community at large,
and improve the GLEP for re-submission.

The author of the GLEP is then responsible for posting the GLEP to
the gentoo-dev or gentoo-project mailing list (and additionally to
the Gentoo Linux forums [#FORUMS]_ if they so desire), and marshaling community
support for it.  As updates are necessary, the GLEP author should request
merging changes to the master branch from a GLEP editor.

Standards Track GLEPs consist of two parts, a design document and a reference
implementation.  The GLEP should be reviewed and accepted before a reference
implementation is begun, unless a reference implementation will aid people in
studying the GLEP.  Standards Track GLEPs must include an implementation -- in
the form of code, patch, or URL to same -- before it can be considered Final.

GLEP authors are responsible for collecting community feedback on a GLEP
before submitting it for review.  A GLEP that has not been discussed on
the mailing lists will not be accepted.  However, wherever possible, long
open-ended discussions on public mailing lists should be avoided.  Strategies
to keep the discussions efficient include setting up a specific forums thread
for the topic, having the GLEP author accept private comments in the early
design phases, etc.  GLEP authors should use their discretion here.

Once the authors have completed a GLEP, they must inform the Gentoo Council
[#COUNCIL]_ that it is ready for review by way of the appropriate mailing
list.  GLEPs are then reviewed at a Council meeting where they may be approved
or rejected outright, or sent back to the author(s) for revision.  This
generally should be done a few weeks in advance of the actual review so as to
avoid the appearance of "slipping" a GLEP in without proper public review
by the Gentoo developer community. Any revisions should be added to the GLEP
bug on Bugzilla.

For a GLEP to be approved it must meet certain minimum criteria.  It must be a
clear and complete description of the proposed enhancement.  The enhancement
must represent a net improvement.  The proposed implementation, if applicable,
must be solid and must not complicate the distribution unduly.  Finally, a
proposed enhancement must satisfy the philosophy of Gentoo Linux.

Once a GLEP has been accepted, the reference implementation must be completed.
When the reference implementation is complete and accepted, the status will be
changed to "Final".

A GLEP can also be assigned status "Deferred".  The GLEP author or editor can
assign the GLEP this status when no progress is being made on the GLEP.  Once
a GLEP is deferred, the GLEP editor can re-assign it to draft status.

A GLEP can also be "Rejected".  Perhaps after all is said and done it was not
a good idea.  It is still important to have a record of this fact.

The "Withdrawn" status is similar - it means that the GLEP author has decided
that the GLEP is actually a bad idea, or has accepted that a competing
proposal is a better alternative.

GLEPs can also be replaced by a different GLEP, rendering the original
obsolete (where version 2 of a policy, for example, might replace version 1).

If a "Final" GLEP becomes obsolete and requires no explicit replacement,
it can be marked "Moribund".

GLEP work flow is as follows::

    Draft -> Accepted -> Final -> Replaced
      ^                    |
      +----> Rejected      +----> Moribund
      |
      +----> Withdrawn
      v
    Deferred

Some Informational GLEPs may also have a status of "Active" if they are never
meant to be completed, e.g. GLEP 1 (this GLEP).


What belongs in a successful GLEP?
==================================

Each GLEP should have the following parts:

1. Preamble -- RFC 2822 style headers containing meta-data about the
   GLEP, including the GLEP number, a short descriptive title (limited
   to a maximum of 44 characters), the names, and optionally the
   contact info for each author, etc.

   Described further below.

2. Abstract -- a short (~200 word) description of the technical issue
   being addressed.

3. Motivation -- The motivation is critical for GLEPs that want to
   modify Gentoo Linux functionality.  It should clearly explain why the
   existing functionality or policy is inadequate to address the problem that
   the GLEP solves.  GLEP submissions without sufficient motivation may be
   rejected outright.

4. Specification -- The technical specification should describe the
   specific areas of Gentoo Linux that would be touched by this GLEP.  If new
   functionality is being introduced, what packages will that functionality
   affect?  If new policy, who will be affected?

5. Rationale -- The rationale fleshes out the specification by
   describing what motivated the design and why particular design decisions
   were made.  It should describe alternate designs that were considered and
   related work, e.g. how the feature is supported in other distributions.

   The rationale should provide evidence of consensus within the community and
   discuss important objections or concerns raised during discussion.

6. Backwards Compatibility -- All GLEPs 
   must include a section describing any issues of backwards incompatibilities
   and their severity.  The GLEP must explain how the author proposes to deal
   with these incompatibilities.  (Even if there are none, this section should
   be included to clearly state that fact.) GLEP submissions without a
   sufficient backwards compatibility treatise may be rejected outright.

7. Reference Implementation -- The reference implementation must be
   completed before any GLEP is given status "Final", but it need not be
   completed before the GLEP is accepted.  It is better to finish the
   specification and rationale first and reach consensus on it before writing
   code or significantly modifying ebuilds.

8. Copyright -- Every new GLEP must be explicitly labelled as licensed under
   the Creative Commons Attribution-ShareAlike 4.0 International License
   (CC-BY-SA-4.0) [#CC-BY-SA-4.0]_.  Older GLEPs released under CC-BY-SA-3.0
   should be relicensed to CC-BY-SA-4.0 when they are updated.


GLEP Formating and Template
===========================

GLEPs are UTF-8 encoded text files written in ReStructuredText markup
[#ReSTHOME]_ that is then converted to HTML using Docutils [#DOCUTILS]_.
ReStructuredText allows for rich markup that is still quite easy to read,
but also results in good-looking and functional HTML.  GLEP 2 contains
a boilerplate template [#GLEP2]_ for use with ReStructuredText GLEPs.

For best interoperability, the GLEPs using ReStructuredText format must use
``.rst`` file suffix.


GLEP Header
===========

Every GLEP has certain attributes associated with it. When a GLEP is sent
to the mailing lists for discussion, it should begin with an RFC 2822 style
header preamble between two triple-dashed lines.  The headers must appear
in the following order.  For interoperability, the header preamble should also
conform to the YAML standard [#YAML]_.  Headers marked with "*" are optional.
All other headers are required.

::

    ---
    GLEP: <glep number>
    Title: <glep title>
    Author: <list of authors' real names and optionally, email addrs>
    Type: <Informational | Standards Track>
    Status: <Draft | Active | Accepted | Deferred | Withdrawn | Rejected |
             Final | Replaced | Moribund>
    Version: <major>[.<minor>]
    Created: <date created on>
    Last-Modified: <date of last update>
    Post-History: <dates of postings to mailing lists>
    Content-Type: <text/x-rst>
  * Requires: <glep numbers>
  * Replaces: <glep numbers>
  * Replaced-By: <glep number>
    ---

The Author header lists the names, and optionally the email addresses
of all the authors/owners of the GLEP.  Anybody who submits changes to
the GLEP should be added to this field.  The format of the Author header
value must be

    Random J. User <address@example.org>

if the email address is included, and just

    Random J. User

if the address is not given.

If there are multiple authors, each should be on a separate line
following RFC 2822 continuation line conventions.

The Type header specifies the type of GLEP: Informational or Standards
Track.

The Version field specifies the current version of the GLEP. The Version
consists of a major version, optionally followed by a minor version (if
non-zero). Every GLEP starts at version 1 which is successively incremented
as changes are merged to the GLEP.

The major version number should be incremented (and minor reset to zero)
whenever the meaning of the GLEP changes. The minor version number should
be incremented for changes that do not affect the basic meaning (e.g.
clarifications, reference implementation updates). Editorial changes should
be merged without increasing the version.

The Created header records the date that the GLEP was assigned a number,
Last-Modified specifies the date that the GLEP was last updated in the master
branch, while Post-History is used to record the dates of when new versions
of the GLEP are posted to the appropriate mailing list.  All three headers
should be in ISO 8601 ``yyyy-mm-dd`` format, e.g. 2001-08-14.

The format of a GLEP is specified with a Content-Type header, which
must be "text/x-rst" for ReStructuredText GLEPs (see GLEP 2 [#GLEP2]_).

GLEPs may have a Requires header, indicating the GLEP numbers that this GLEP
depends on.

GLEPs may also have a Replaces header indicating that a GLEP is meant
to replace one or more older GLEPs.  Once such a GLEP is accepted, a matching
Replaced-By should be added to all replaced GLEPs and their status should
be updated to Replaced.


Reporting GLEP Bugs, or Submitting GLEP Updates
===============================================

How you report a bug, or submit a GLEP update depends on several factors, such
as the maturity of the GLEP, the preferences of the GLEP author, and the
nature of your comments.  For the early draft stages of the GLEP, it's
probably best to send your comments and changes directly to the GLEP author
or comment on the GLEP bug. For more mature, or finished GLEPs you may want
to submit corrections to the Gentoo Linux bugzilla [#BUGS]_ under the "GLEP
Changes" component of the "Documentation" product so that your changes don't get
lost. Be sure to CC the GLEP author on the bug. When in doubt about where
to send your changes, please check first with the GLEP author and/or GLEP
editors.

GLEP authors must have a GLEP editor merge their changes to the master branch,
as the write access is restricted to GLEP editors in order to protect
the integrity of the GLEPs.

Any major updates to GLEPs (that is, those that change the content of
the GLEP rather than just fixing typos or adding small clarifications)
should be approved by the Gentoo Council before being merged.


Transferring GLEP Ownership
===========================

It occasionally becomes necessary to transfer ownership of GLEPs to a new
champion.  In general, we'd like to retain the original author as a co-author
of the transferred GLEP, but that's really up to the original author.  A good
reason to transfer ownership is because the original author no longer has the
time or interest in updating it or following through with the GLEP process, or
has fallen off the face of the 'net (i.e. is unreachable or not responding to
email).  A bad reason to transfer ownership is because you don't agree with
the direction of the GLEP.  We try to build consensus around a GLEP, but if
that's not possible, you can always submit a competing GLEP.

If you are interested in assuming ownership of a GLEP, send a message asking
to take over, addressed to both the original author and the GLEP editors
<glep@gentoo.org>, or comment on the GLEP bug.  If the original author doesn't
respond to email in a timely manner, the GLEP editors will make a unilateral
decision (it's not like such decisions can't be reversed :).


References and Footnotes
========================

.. [#PYTHON] https://www.python.org/

.. [#PEPS] https://www.python.org/dev/peps/

.. [#PEP1] https://www.python.org/dev/peps/pep-0001/

.. [#VCS] https://gitweb.gentoo.org/data/glep.git

.. [#CVS] https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/glep/

.. [#WIKI] https://wiki.gentoo.org/index.php?title=Special%3AAllPages&from=&to=&namespace=550

.. [#BUGS] https://bugs.gentoo.org/

.. [#FORUMS] https://forums.gentoo.org/

.. [#COUNCIL] https://www.gentoo.org/glep/glep-0039.html

.. [#CC-BY-SA-4.0] https://creativecommons.org/licenses/by-sa/4.0/

.. [#ReSTHOME] http://docutils.sourceforge.net/rst.html

.. [#DOCUTILS] http://docutils.sourceforge.net/

.. [#GLEP2] https://www.gentoo.org/glep/glep-0002.html

.. [#YAML] https://yaml.org/


Copyright
=========

This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
International License.  To view a copy of this license, visit
https://creativecommons.org/licenses/by-sa/4.0/.

[-- Attachment #1.3: glep-0002.rst --]
[-- Type: text/plain, Size: 21700 bytes --]

---
GLEP: 2
Title: Sample ReStructuredText GLEP Template
Author: Grant Goodyear <g2boojum@gentoo.org>,
        Chris Reffett <creffett@gentoo.org>,
        Ulrich Müller <ulm@gentoo.org>
Type: Informational
Status: Active
Version: 4
Created: 2003-05-31
Last-Modified: 2019-11-24
Post-History: 2003-06-02, 2013-12-17, 2017-09-17, 2019-11-24
Content-Type: text/x-rst
---


Credits
=======

The text of this GLEP was, to a significant extent, stolen from Python's
[#PYTHON]_ PEP-0012 [#PEP12]_ by David Goodger and Barry A. Warsaw.


Abstract
========

This GLEP provides a boilerplate or sample template for creating your own
reStructuredText GLEPs.  In conjunction with the content guidelines in GLEP 1
[#GLEP1]_, this should make it easy for you to conform your own GLEPs to the
format outlined below.

Note: if you are reading this GLEP via the web, you should first grab the text
(reStructuredText) source of this GLEP in order to complete the steps below.
**DO NOT USE THE HTML FILE AS YOUR TEMPLATE!**

To get the source of this (or any) GLEP, look at the top of the HTML page and
click on the link titled "GLEP Source".

Motivation
==========

Provide adequate motivation here.  In this particular case, we need to provide
people with the information necessary to submit GLEPs in the proper form.

Rationale
=========

GLEP submissions come in a wide variety of forms, not all adhering to the
format guidelines set forth below.  Use this template, in conjunction with the
format guidelines below, to ensure that your GLEP submission won't get
automatically rejected because of form.

ReStructuredText is used to allow GLEP authors more functionality and
expressivity, while maintaining easy readability in the source text.  The
processed HTML form makes the functionality accessible to readers: live
hyperlinks, styled text, tables, images, and automatic tables of contents,
among other advantages.  


Backwards Compatibility
=======================

Not a problem for this GLEP.  This section should be included *even* when it
is only to state that there are no backwards compatibility issues.


How to Use This Template
========================

To use this template you must first decide whether your GLEP is going to be an
Informational or Standards Track GLEP.  Most GLEPs are Standards Track because
they propose new functionality for some aspect of Gentoo Linux.  When in
doubt, read GLEP 1 for details or contact the GLEP editors <glep@gentoo.org>.

Once you've decided which type of GLEP yours is going to be, follow the
directions below.

- Make a copy of this file (``.rst`` file, **not** HTML!) and perform
  the following edits.

- Replace the "GLEP: 2" header with "GLEP: 9999" since you don't yet have
  a GLEP number assignment.

- Change the Title header to the title of your GLEP.

- Change the Author header to include your name, and optionally your
  email address.  Be sure to follow the format carefully: your name must
  appear first, and it must not be contained in parentheses.  Your email
  address may appear second (or it can be omitted) and if it appears, it must
  appear in angle brackets.

- For Standards Track GLEPs, change the Type header to "Standards Track".

- For Informational GLEPs, change the Type header to "Informational".

- Change the Status header to "Draft".

- Reset the Version to "1".

- Change the Created and Last-Modified headers to today's date.  Be sure to
  follow the format carefully: it must be in ISO 8601 ``yyyy-mm-dd`` format.

- Reset the Post-History to empty for now; you'll add dates to this header
  each time you post your GLEP to gentoo-dev@lists.gentoo.org.  If you
  posted your GLEP to the list on August 14, 2003 and September 3, 2003,
  the Post-History header would look like::

      Post-History: 2003-08-14, 2003-09-03

  You must manually add new dates and check them in.  If you don't have
  check-in privileges, send your changes to the GLEP editors.

- For Standards Track GLEPs, if your feature depends on the acceptance
  of some other currently in-development GLEP, add a Requires header right
  after the Type header.  The value should be the GLEP number of the GLEP
  yours depends on.  Don't add this header if your dependent feature is
  described in a Final GLEP.

- Add a Replaces header if your GLEP obsoletes one or more earlier GLEPs.
  The value of this header is the numbers of the GLEPs that your new GLEP is
  replacing, separated by commas.  Only add this header if the older GLEP is
  in "final" form, i.e. is either Accepted, Final, or Rejected.  You aren't
  replacing an older open GLEP if you're submitting a competing idea.

- Now write your Abstract, Rationale, and other content for your GLEP,
  replacing all of this gobbledygook with your own text. Be sure to adhere to
  the format guidelines below, specifically on the indentation requirements.

- Update your References section.  You should leave the Copyright section
  as-is, since all new GLEPs are to be licensed under the Creative Commons
  Attribution-ShareAlike 4.0 International License (CC-BY-SA-4.0).

- Send your GLEP submission to the GLEP editors at glep@gentoo.org.


ReStructuredText GLEP Formatting Requirements
=============================================

The following is a GLEP-specific summary of reStructuredText syntax.  For the
sake of simplicity and brevity, much detail is omitted.  For more detail, see
`Resources`_ below.  `Literal blocks`_ (in which no markup processing is done)
are used for examples throughout, to illustrate the plaintext markup.


General
-------

You must adhere to the convention of adding two spaces at the end of every
sentence.  You should fill your paragraphs to column 70, but under no
circumstances should your lines extend past column 79.  If your code samples
spill over column 79, you should rewrite them.


Section Headings
----------------

GLEP headings must begin in column zero and the initial letter of each word
must be capitalized as in book titles.  Acronyms should be in all capitals.
Section titles must be adorned with an underline, a single repeated
punctuation character, which begins in column zero and must extend at least as
far as the right edge of the title text (4 characters minimum).  First-level
section titles are underlined with "=" (equals signs), second-level section
titles with "-" (hyphens), and third-level section titles with "'" (single
quotes or apostrophes).  For example::

    First-Level Title
    =================

    Second-Level Title
    ------------------

    Third-Level Title
    '''''''''''''''''

If there are more than three levels of sections in your GLEP, you may insert
overline/underline-adorned titles for the first and second levels as follows::

    ============================
    First-Level Title (optional)
    ============================

    -----------------------------
    Second-Level Title (optional)
    -----------------------------

    Third-Level Title
    =================

    Fourth-Level Title
    ------------------

    Fifth-Level Title
    '''''''''''''''''

You shouldn't have more than five levels of sections in your GLEP.  If you do,
you should consider rewriting it.

You must use two blank lines between the last line of a section's body and the
next section heading.  If a subsection heading immediately follows a section
heading, a single blank line in-between is sufficient.

The body of each section is not normally indented, although some constructs do
use indentation, as described below.  Blank lines are used to separate
constructs.


Paragraphs
----------

Paragraphs are left-aligned text blocks separated by blank lines.  Paragraphs
are not indented unless they are part of an indented construct (such as a
block quote or a list item).


Inline Markup
-------------

Portions of text within paragraphs and other text blocks may be
styled.  For example::

    Text may be marked as *emphasized* (single asterisk markup,
    typically shown in italics) or **strongly emphasized** (double
    asterisks, typically boldface).  ``Inline literals`` (using double
    backquotes) are typically rendered in a monospaced typeface.  No
    further markup recognition is done within the double backquotes,
    so they're safe for any kind of code snippets.


Block Quotes
------------

Block quotes consist of indented body elements.  For example::

    This is a paragraph.

        This is a block quote.

        A block quote may contain many paragraphs.

Block quotes are used to quote extended passages from other sources.
Block quotes may be nested inside other body elements.  Use a 4-space tab
per indent level.


Literal Blocks
--------------

..  
    In the text below, double backquotes are used to denote inline
    literals.  "``::``" is written so that the colons will appear in a
    monospaced font; the backquotes (``) are markup, not part of the
    text.  See "Inline Markup" above.

    By the way, this is a comment, described in "Comments" below.

Literal blocks are used for code samples or preformatted ASCII art. To
indicate a literal block, preface the indented text block with
"``::``" (two colons).  The literal block continues until the end of
the indentation.  Indent the text block by a tab.  For example::

    This is a typical paragraph.  A literal block follows.

    ::

        for a in [5,4,3,2,1]:   # this is program code, shown as-is
            print a
        print "it's..."
        # a literal block continues until the indentation ends

The paragraph containing only "``::``" will be completely removed from
the output; no empty paragraph will remain.  "``::``" is also
recognized at the end of any paragraph.  If immediately preceded by
whitespace, both colons will be removed from the output.  When text
immediately precedes the "``::``", *one* colon will be removed from
the output, leaving only one colon visible (i.e., "``::``" will be
replaced by "``:``").  For example, one colon will remain visible
here::

    Paragraph::

        Literal block


Lists
-----

Bullet list items begin with one of "-", "*", or "+" (hyphen,
asterisk, or plus sign), followed by whitespace and the list item
body.  List item bodies must be left-aligned and indented relative to
the bullet; the text immediately after the bullet determines the
indentation.  For example::

    This paragraph is followed by a list.

    * This is the first bullet list item.  The blank line above the
      first list item is required; blank lines between list items
      (such as below this paragraph) are optional.

    * This is the first paragraph in the second item in the list.

      This is the second paragraph in the second item in the list.
      The blank line above this paragraph is required.  The left edge
      of this paragraph lines up with the paragraph above, both
      indented relative to the bullet.

      - This is a sublist.  The bullet lines up with the left edge of
        the text blocks above.  A sublist is a new list so requires a
        blank line above and below.

    * This is the third item of the main list.

    This paragraph is not part of the list.

Enumerated (numbered) list items are similar, but use an enumerator
instead of a bullet.  Enumerators are numbers (1, 2, 3, ...), letters
(A, B, C, ...; uppercase or lowercase), or Roman numerals (i, ii, iii,
iv, ...; uppercase or lowercase), formatted with a period suffix
("1.", "2."), parentheses ("(1)", "(2)"), or a right-parenthesis
suffix ("1)", "2)").  For example::

    1. As with bullet list items, the left edge of paragraphs must
       align.

    2. Each list item may contain multiple paragraphs, sublists, etc.

       This is the second paragraph of the second list item.

       a) Enumerated lists may be nested.
       b) Blank lines may be omitted between list items.

Definition lists are written like this::

    what
        Definition lists associate a term with a definition.

    how
        The term is a one-line phrase, and the definition is one
        or more paragraphs or body elements, indented relative to
        the term.


Tables
------

Simple tables are easy and compact::

    =====  =====  =======
      A      B    A and B
    =====  =====  =======
    False  False  False
    True   False  False
    False  True   False
    True   True   True
    =====  =====  =======

There must be at least two columns in a table (to differentiate from
section titles).  Column spans use underlines of hyphens ("Inputs"
spans the first two columns)::

    =====  =====  ======
       Inputs     Output
    ------------  ------
      A      B    A or B
    =====  =====  ======
    False  False  False
    True   False  True
    False  True   True
    True   True   True
    =====  =====  ======

Text in a first-column cell starts a new row.  No text in the first
column indicates a continuation line; the rest of the cells may
consist of multiple lines.  For example::

    =====  =========================
    col 1  col 2
    =====  =========================
    1      Second column of row 1.
    2      Second column of row 2.
           Second line of paragraph.
    3      - Second column of row 3.

           - Second item in bullet
             list (row 3, column 2).
    =====  =========================


Hyperlinks
----------

When referencing an external web page in the body of a GLEP, you should
include the title of the page in the text, with either an inline
hyperlink reference to the URL or a footnote reference (see
`Footnotes`_ below).  Do not include the URL in the body text of the
GLEP.

Hyperlink references use backquotes and a trailing underscore to mark
up the reference text; backquotes are optional if the reference text
is a single word.  For example::

    In this paragraph, we refer to the `Python web site`_.

An explicit target provides the URL.  Put targets in a References
section at the end of the GLEP, or immediately after the reference.
Hyperlink targets begin with two periods and a space (the "explicit
markup start"), followed by a leading underscore, the reference text,
a colon, and the URL (absolute or relative)::

    .. _Python web site: https://www.python.org/

The reference text and the target text must match (although the match
is case-insensitive and ignores differences in whitespace).  Note that
the underscore trails the reference text but precedes the target text.
If you think of the underscore as a right-pointing arrow, it points
*away* from the reference and *toward* the target.

The same mechanism can be used for internal references.  Every unique
section title implicitly defines an internal hyperlink target.  We can
make a link to the Abstract section like this::

    Here is a hyperlink reference to the `Abstract`_ section.  The
    backquotes are optional since the reference text is a single word;
    we can also just write: Abstract_.

Footnotes containing the URLs from external targets will be generated
automatically at the end of the References section of the GLEP, along
with footnote references linking the reference text to the footnotes.

Text of the form "GLEP x" or "RFC x" (where "x" is a number) will be
linked automatically to the appropriate URLs.


Footnotes
---------

Footnote references consist of a left square bracket, a number, a
right square bracket, and a trailing underscore::

    This sentence ends with a footnote reference [1]_.

Whitespace must precede the footnote reference.  Leave a space between
the footnote reference and the preceding word.

When referring to another GLEP, include the GLEP number in the body
text, such as "GLEP 1".  The title may optionally appear.  Add a
footnote reference following the title.  For example::

    Refer to GLEP 1 [2]_ for more information.

Add a footnote that includes the GLEP's title and author.  It may
optionally include the explicit URL on a separate line, but only in
the References section.  Footnotes begin with ".. " (the explicit
markup start), followed by the footnote marker (no underscores),
followed by the footnote body.  For example::

    References
    ==========

    .. [2] GLEP 1, "GLEP Purpose and Guidelines", Goodyear, Warsaw, Hylton
       (https://www.gentoo.org/glep/glep-0001.html)

If you decide to provide an explicit URL for a GLEP, please use this as
the URL template::

    https://www.gentoo.org/glep/glep-xxxx.html

GLEP numbers in URLs must be padded with zeros from the left, so as to
be exactly 4 characters wide, however GLEP numbers in the text are
never padded.

During the course of developing your GLEP, you may have to add, remove,
and rearrange footnote references, possibly resulting in mismatched
references, obsolete footnotes, and confusion.  Auto-numbered
footnotes allow more freedom.  Instead of a number, use a label of the
form "#word", where "word" is a mnemonic consisting of alphanumerics
plus internal hyphens, underscores, and periods (no whitespace or
other characters are allowed).  For example::

    Refer to GLEP 1 [#GLEP-1]_ for more information.

    References
    ==========

    .. [#GLEP-1] GLEP 1, "GLEP Purpose and Guidelines", Goodyear
       https://www.gentoo.org/glep/glep-0001.html

Footnotes and footnote references will be numbered automatically, and
the numbers will always match.  Once a GLEP is finalized, auto-numbered
labels should be replaced by numbers for simplicity.


Images
------

If your GLEP contains a diagram, you may include it in the processed
output using the "image" directive::

    .. image:: diagram.png

Any browser-friendly graphics format is possible: .png, .jpeg, .gif,
.tiff, etc.

Since this image will not be visible to readers of the GLEP in source
text form, you should consider including a description or ASCII art
alternative, using a comment (below).


Comments
--------

A comment block is an indented block of arbitrary text immediately
following an explicit markup start: two periods and whitespace.  Leave
the ".." on a line by itself to ensure that the comment is not
misinterpreted as another explicit markup construct.  Comments are not
visible in the processed document.  For the benefit of those reading
your GLEP in source form, please consider including a descriptions of
or ASCII art alternatives to any images you include.  For example::

     .. image:: dataflow.png

     ..
        Data flows from the input module, through the "black box"
        module, and finally into (and through) the output module.



Escaping Mechanism
------------------

reStructuredText uses backslashes ("``\``") to override the special
meaning given to markup characters and get the literal characters
themselves.  To get a literal backslash, use an escaped backslash
("``\\``").  There are two contexts in which backslashes have no
special meaning: `literal blocks`_ and inline literals (see `Inline
Markup`_ above).  In these contexts, no markup recognition is done,
and a single backslash represents a literal backslash, without having
to double up.

If you find that you need to use a backslash in your text, consider
using inline literals or a literal block instead.


Habits to Avoid
===============

Many programmers who are familiar with TeX often write quotation marks
like this::

    `single-quoted' or ``double-quoted''

Backquotes are significant in reStructuredText, so this practice
should be avoided.  For ordinary text, use ordinary 'single-quotes' or
"double-quotes".  For inline literal text (see `Inline Markup`_
above), use double-backquotes::

    ``literal text: in here, anything goes!``


Resources
=========

Many other constructs and variations are possible.  For more details
about the reStructuredText markup, in increasing order of
thoroughness, please see:

* `A ReStructuredText Primer`__, a gentle introduction.

  __ http://docutils.sourceforge.net/docs/rst/quickstart.html

* `Quick reStructuredText`__, a users' quick reference.

  __ http://docutils.sourceforge.net/docs/rst/quickref.html

* `reStructuredText Markup Specification`__, the final authority.

  __ http://docutils.sourceforge.net/spec/rst/reStructuredText.html

The processing of reStructuredText GLEPs is done using Docutils_.  If
you have a question or require assistance with reStructuredText or
Docutils, please `post a message`_ to the `Docutils-Users mailing
list`_.  The `Docutils project web site`_ has more information.

.. _Docutils: http://docutils.sourceforge.net/
.. _post a message:
   mailto:docutils-users@lists.sourceforge.net?subject=GLEPs
.. _Docutils-Users mailing list:
   https://sourceforge.net/projects/docutils/lists/docutils-users
.. _Docutils project web site: http://docutils.sourceforge.net/


References
==========

.. [#PYTHON] https://www.python.org/

.. [#PEP12] https://www.python.org/dev/peps/pep-0012/

.. [#GLEP1] GLEP 1, GLEP Purpose and Guidelines, Goodyear, 
   (https://www.gentoo.org/glep/glep-0001.html)


Copyright
=========

This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
International License.  To view a copy of this license, visit
https://creativecommons.org/licenses/by-sa/4.0/.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: [gentoo-project] [PATCH] glep-{0001,0002}: New GLEPs are to be licensed under CC-BY-SA-4.0.

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 4646 bytes --]

On Sun, 2019-11-24 at 11:41 +0100, Ulrich Müller wrote:
> GLEP 76 says that new documentation must be released under CC-BY-SA
> version 4.0. Update the guidelines (GLEP 1) and the template (GLEP 2)
> to agree with this policy.
> 
> Drop the wording about older GLEPs in the public domain or released
> under the OPL, because all of them have been updated.
> 
> Signed-off-by: Ulrich Müller <ulm@gentoo.org>
> ---
>  glep-0001.rst | 23 ++++++++++-------------
>  glep-0002.rst | 12 ++++++------
>  2 files changed, 16 insertions(+), 19 deletions(-)
> 
> diff --git a/glep-0001.rst b/glep-0001.rst
> index 15deccb..61a08a4 100644
> --- a/glep-0001.rst
> +++ b/glep-0001.rst
> @@ -6,11 +6,11 @@ Author: Grant Goodyear <g2boojum@gentoo.org>,
>          Ulrich Müller <ulm@gentoo.org>
>  Type: Informational
>  Status: Active
> -Version: 3
> +Version: 4
>  Created: 2003-05-31
>  Last-Modified: 2019-11-24
>  Post-History: 2003-06-01, 2003-07-02, 2008-01-19, 2008-06-05, 2011-03-09,
> -              2013-12-14, 2017-09-17, 2018-07-10
> +              2013-12-14, 2017-09-17, 2018-07-10, 2019-11-24
>  Content-Type: text/x-rst
>  ---
>  
> @@ -211,13 +211,10 @@ Each GLEP should have the following parts:
>     specification and rationale first and reach consensus on it before writing
>     code or significantly modifying ebuilds.
>  
> -8. Copyright -- Every new GLEP must be explicitly labelled
> -   as licensed under the Creative Commons Attribution-ShareAlike (CC-BY-SA)
> -   license, version 3.0 [#CC-BY-SA3.0]_. Older GLEPs in the public domain
> -   should be relicensed to CC-BY-SA 3.0 when they are updated.
> -   GLEPs released under the Open Publication License (OPL) may remain
> -   as-is, but are strongly encouraged to be relicensed under CC-BY-SA
> -   3.0 with the consent of all authors.
> +8. Copyright -- Every new GLEP must be explicitly labelled as licensed under
> +   the Creative Commons Attribution-ShareAlike 4.0 International License
> +   (CC-BY-SA-4.0) [#CC-BY-SA-4.0]_.  Older GLEPs released under CC-BY-SA-3.0
> +   should be relicensed to CC-BY-SA-4.0 when they are updated.

I wonder if we should explicitly allow using a newer version, or maybe
even reword it to the 'latest version' or something like that, so we
don't have to update it whenever new license version is released.

>  
>  
>  GLEP Formating and Template
> @@ -374,7 +371,7 @@ References and Footnotes
>  
>  .. [#COUNCIL] https://www.gentoo.org/glep/glep-0039.html
>  
> -.. [#CC-BY-SA3.0] https://creativecommons.org/licenses/by-sa/3.0/
> +.. [#CC-BY-SA-4.0] https://creativecommons.org/licenses/by-sa/4.0/
>  
>  .. [#ReSTHOME] http://docutils.sourceforge.net/rst.html
>  
> @@ -388,6 +385,6 @@ References and Footnotes
>  Copyright
>  =========
>  
> -This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
> -Unported License.  To view a copy of this license, visit
> -https://creativecommons.org/licenses/by-sa/3.0/.
> +This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
> +International License.  To view a copy of this license, visit
> +https://creativecommons.org/licenses/by-sa/4.0/.
> diff --git a/glep-0002.rst b/glep-0002.rst
> index 67ce3ce..6ef72ca 100644
> --- a/glep-0002.rst
> +++ b/glep-0002.rst
> @@ -6,10 +6,10 @@ Author: Grant Goodyear <g2boojum@gentoo.org>,
>          Ulrich Müller <ulm@gentoo.org>
>  Type: Informational
>  Status: Active
> -Version: 3
> +Version: 4
>  Created: 2003-05-31
>  Last-Modified: 2019-11-24
> -Post-History: 2003-06-02, 2013-12-17, 2017-09-17
> +Post-History: 2003-06-02, 2013-12-17, 2017-09-17, 2019-11-24
>  Content-Type: text/x-rst
>  ---
>  
> @@ -128,7 +128,7 @@ directions below.
>  
>  - Update your References section.  You should leave the Copyright section
>    as-is, since all new GLEPs are to be licensed under the Creative Commons
> -  Attribution-ShareAlike License, Version 3.0.
> +  Attribution-ShareAlike 4.0 International License (CC-BY-SA-4.0).
>  
>  - Send your GLEP submission to the GLEP editors at glep@gentoo.org.
>  
> @@ -602,6 +602,6 @@ References
>  Copyright
>  =========
>  
> -This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
> -Unported License.  To view a copy of this license, visit
> -https://creativecommons.org/licenses/by-sa/3.0/.
> +This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
> +International License.  To view a copy of this license, visit
> +https://creativecommons.org/licenses/by-sa/4.0/.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

Re: [gentoo-project] [PATCH] glep-{0001,0002}: New GLEPs are to be licensed under CC-BY-SA-4.0.

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

>>>>> On Sun, 24 Nov 2019, Michał Górny wrote:

> On Sun, 2019-11-24 at 11:41 +0100, Ulrich Müller wrote:
>> +8. Copyright -- Every new GLEP must be explicitly labelled as licensed under
>> +   the Creative Commons Attribution-ShareAlike 4.0 International License
>> +   (CC-BY-SA-4.0) [#CC-BY-SA-4.0]_.  Older GLEPs released under CC-BY-SA-3.0
>> +   should be relicensed to CC-BY-SA-4.0 when they are updated.

> I wonder if we should explicitly allow using a newer version, or maybe
> even reword it to the 'latest version' or something like that, so we
> don't have to update it whenever new license version is released.

I'd rather not, because version 4.0 is what Council and Trustees have
explicitly approved in GLEP 76.

We can discuss this again when there will be newer CC license versions.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: [gentoo-project] [PATCH] glep-{0001,0002}: New GLEPs are to be licensed under CC-BY-SA-4.0.

[Aaron Bauman]

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

On Sun, Nov 24, 2019 at 01:08:29PM +0100, Ulrich Mueller wrote:
> >>>>> On Sun, 24 Nov 2019, Michał Górny wrote:
> 
> > On Sun, 2019-11-24 at 11:41 +0100, Ulrich Müller wrote:
> >> +8. Copyright -- Every new GLEP must be explicitly labelled as licensed under
> >> +   the Creative Commons Attribution-ShareAlike 4.0 International License
> >> +   (CC-BY-SA-4.0) [#CC-BY-SA-4.0]_.  Older GLEPs released under CC-BY-SA-3.0
> >> +   should be relicensed to CC-BY-SA-4.0 when they are updated.
> 
> > I wonder if we should explicitly allow using a newer version, or maybe
> > even reword it to the 'latest version' or something like that, so we
> > don't have to update it whenever new license version is released.
> 
> I'd rather not, because version 4.0 is what Council and Trustees have
> explicitly approved in GLEP 76.
> 
> We can discuss this again when there will be newer CC license versions.
> 
> Ulrich

I agree that not doing it now is wise. Aside from the trustees and council
having approved it, I would be concerned that some breaking change in legalase
is done. e.g. GPLv2 vs GPLv3.

I am not trying to debate the validity of said licenses, but ensure that we do
not "blindly" accept changes we, as a distro, agree with.

-- 
Cheers,
Aaron

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [gentoo-project] [PATCH] glep-{0001,0002}: New GLEPs are to be licensed under CC-BY-SA-4.0.

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]

On Sun, 2019-11-24 at 15:51 -0500, Aaron Bauman wrote:
> On Sun, Nov 24, 2019 at 01:08:29PM +0100, Ulrich Mueller wrote:
> > > > > > > On Sun, 24 Nov 2019, Michał Górny wrote:
> > > On Sun, 2019-11-24 at 11:41 +0100, Ulrich Müller wrote:
> > > > +8. Copyright -- Every new GLEP must be explicitly labelled as licensed under
> > > > +   the Creative Commons Attribution-ShareAlike 4.0 International License
> > > > +   (CC-BY-SA-4.0) [#CC-BY-SA-4.0]_.  Older GLEPs released under CC-BY-SA-3.0
> > > > +   should be relicensed to CC-BY-SA-4.0 when they are updated.
> > > I wonder if we should explicitly allow using a newer version, or maybe
> > > even reword it to the 'latest version' or something like that, so we
> > > don't have to update it whenever new license version is released.
> > 
> > I'd rather not, because version 4.0 is what Council and Trustees have
> > explicitly approved in GLEP 76.
> > 
> > We can discuss this again when there will be newer CC license versions.
> > 
> > Ulrich
> 
> I agree that not doing it now is wise. Aside from the trustees and council
> having approved it, I would be concerned that some breaking change in legalase
> is done. e.g. GPLv2 vs GPLv3.
> 
> I am not trying to debate the validity of said licenses, but ensure that we do
> not "blindly" accept changes we, as a distro, agree with.

CC licenses contain an upgrade clause, so we do accept them.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

Re: [gentoo-project] [PATCH] glep-{0001,0002}: New GLEPs are to be licensed under CC-BY-SA-4.0.

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 429 bytes --]

>>>>> On Sun, 24 Nov 2019, Ulrich Müller wrote:

> GLEP 76 says that new documentation must be released under CC-BY-SA
> version 4.0. Update the guidelines (GLEP 1) and the template (GLEP 2)
> to agree with this policy.

> Drop the wording about older GLEPs in the public domain or released
> under the OPL, because all of them have been updated.

This has been accepted in today's Council meeting.
Pushed.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: [gentoo-project] [PATCH] glep-{0001,0002}: New GLEPs are to be licensed under CC-BY-SA-4.0.

[Joonas Niilola]

[-- Attachment #1.1: Type: text/plain, Size: 632 bytes --]


On 12/8/19 9:41 PM, Ulrich Mueller wrote:
>>>>>> On Sun, 24 Nov 2019, Ulrich Müller wrote:
>> GLEP 76 says that new documentation must be released under CC-BY-SA
>> version 4.0. Update the guidelines (GLEP 1) and the template (GLEP 2)
>> to agree with this policy.
>> Drop the wording about older GLEPs in the public domain or released
>> under the OPL, because all of them have been updated.
> This has been accepted in today's Council meeting.
> Pushed.
>
> Ulrich

(sorry for replying on this thread, but could you push the meeting log
as well?)

((also summary is missing from last time))

-- juippis




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 642 bytes --]

Re: [gentoo-project] [PATCH] glep-{0001,0002}: New GLEPs are to be licensed under CC-BY-SA-4.0.

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

>>>>> On Tue, 10 Dec 2019, Joonas Niilola wrote:

> On 12/8/19 9:41 PM, Ulrich Mueller wrote:
>>> GLEP 76 says that new documentation must be released under CC-BY-SA
>>> version 4.0. Update the guidelines (GLEP 1) and the template (GLEP 2)
>>> to agree with this policy.
>>> Drop the wording about older GLEPs in the public domain or released
>>> under the OPL, because all of them have been updated.
>> This has been accepted in today's Council meeting.
>> Pushed.

> (sorry for replying on this thread, but could you push the meeting log
> as well?)

Log is there (thanks dilfridge):
https://projects.gentoo.org/council/meeting-logs/20191208.txt

> ((also summary is missing from last time))

Yes, we're aware of it.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]