From: "'Julian Reich' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: License terms for pandoc's default templates
Date: Wed, 19 Jul 2023 17:14:45 -0700 (PDT) [thread overview]
Message-ID: <cf5d7116-e4c5-4a4b-923d-6b3b275d16e4n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1872 bytes --]
Hi,
I'd like to ask for clarification on the license terms for pandoc's default
template files.
According to the COPYRIGHT file, pandoc's templates can be licensed under
either the GPL version 2 (or any later version) or the 3-clause BSD license.
Taking these licenses literally, I've come to the conclusion that we *might*
be required to include a copyright notice and the license text (of our
choice) in the documents generated from these templates (and/or in the
accompanying materials).
This would not be a problem per se, pandoc is a great and immensely useful
tool, and we want to make sure we are using it in accordance with its
license terms.
However, while I suppose you *could* interpret the license terms that way,
I'm not so sure that was the intent.
For example from the 3-clause BSD license:
> 1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
>
> 2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
I guess it boils down to whether the generated documents are considered
"redistributions" of the templates.
I may be way off (not a lawyer), but perhaps others have also wondered
about this, and it might even be worth adding some clarifying wording to
the COPYRIGHT file.
Regards,
Julian Reich
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/cf5d7116-e4c5-4a4b-923d-6b3b275d16e4n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2279 bytes --]
next reply other threads:[~2023-07-20 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 0:14 'Julian Reich' via pandoc-discuss [this message]
[not found] ` <cf5d7116-e4c5-4a4b-923d-6b3b275d16e4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-20 0:36 ` John MacFarlane
[not found] ` <83606CC6-24DE-4351-8D98-60973D0DDD4F-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-24 9:05 ` 'Julian Reich' via pandoc-discuss
[not found] ` <81877b75-2b0b-4813-a073-b93f79909a28n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-07-24 9:28 ` Bastien DUMONT
2023-07-24 10:02 ` Daniel Littlewood
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=cf5d7116-e4c5-4a4b-923d-6b3b275d16e4n@googlegroups.com \
--to=pandoc-discuss-/jypxa39uh5tlh3mbocffw@public.gmane.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 NNTP newsgroup(s).