public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "AsDaGo at posteo dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25877] New: Unclear license for example files
Date: Sun, 26 Apr 2020 18:21:34 +0000	[thread overview]
Message-ID: <bug-25877-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=25877

            Bug ID: 25877
           Summary: Unclear license for example files
           Product: glibc
           Version: 2.31
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: AsDaGo at posteo dot net
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

The manual/examples/README file appears to say that the examples are available
*only* under the GPL. The license notices for the individual files appear to
only allow distribution under the GPL as well. However, since the manual is
licensed under the GFDL, it seems to me that the example files must allow
distribution under the GFDL as well in order to be included in the manual.

So I think this should be clarified by adding a dual-license notice to both the
README and the individual examples allowing distribution under both the GPL and
GFDL.

P.S. Since there is no "documentation" component available, I chose "libc"
instead.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-04-26 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 18:21 AsDaGo at posteo dot net [this message]
2021-02-04 11:34 ` [Bug libc/25877] " balint at balintreczey dot hu
2021-02-04 14:21 ` [Bug manual/25877] " fweimer at redhat dot com
2021-02-09  1:06 ` AsDaGo at posteo dot net
2021-02-09 19:56 ` balint at balintreczey dot hu

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=bug-25877-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).