From: Daniel Littlewood <danielittlewood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: License terms for pandoc's default templates
Date: Mon, 24 Jul 2023 11:02:28 +0100 [thread overview]
Message-ID: <CAFDSbVfut0occwpOm-JbZmy_7bOZ0K==uBEEbWV1oKTt4wuBYg@mail.gmail.com> (raw)
In-Reply-To: <ZL5EI44Nne793BiM@localhost>
I suspect that the pandoc templates are not sufficiently novel to be protected.
In particular, see https://www.gnu.org/licenses/gpl-faq.html#GPLOutput (quoted
below, my emphasis)
> ... the only way you have a say in the use of the output is if *substantial
> parts of the output* are copied (more or less) from text in your program
Having at least looked at the HTML template, I don't think it would qualify as
a "creative work" at all. You could add a clarification to the LICENSE that
it's pandoc's position that output documents are not copyrightable, or you
could explicitly license them as Public Domain / some Permissive license. But I
doubt that it's necessary - it's intuitively obvious that the output of pandoc
should inherit the license of its input.
All the best,
Dan
On Mon, Jul 24, 2023 at 10:28 AM Bastien DUMONT
<bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org> wrote:
>
> For the mere pleasure of discussing theoretical legal aspects, here is a Q&A that clarifies the issue (especially the first paragraph): https://www.gnu.org/licenses/gpl-faq.html#WMS
>
> Le Monday 24 July 2023 à 02:05:36AM, 'Julian Reich' via pandoc-discuss a écrit :
> > Hi,
> >
> > On Thursday, July 20, 2023 at 2:36:49 AM UTC+2 John MacFarlane wrote:
> >
> > What I can say is that I certainly never intended a requirement that
> > documents generated
> > using these templates contain a copyright or license notice.
> >
> >
> > Thank you for your prompt response and clarification.
> > The more I think about it: if we consider the template to be a program itself,
> > and the generated document to be the output of that program, it seems rather
> > far-fetched that the license of the program should extend to its output.
> > Then again, these are just my personal rationalizations, still not a lawyer.
> >
> >
> > 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [2]https://groups.google.com/d/msgid/
> > pandoc-discuss/81877b75-2b0b-4813-a073-b93f79909a28n%40googlegroups.com.
> >
> > References:
> >
> > [1] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [2] https://groups.google.com/d/msgid/pandoc-discuss/81877b75-2b0b-4813-a073-b93f79909a28n%40googlegroups.com?utm_medium=email&utm_source=footer
>
> --
> 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/ZL5EI44Nne793BiM%40localhost.
--
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/CAFDSbVfut0occwpOm-JbZmy_7bOZ0K%3D%3DuBEEbWV1oKTt4wuBYg%40mail.gmail.com.
prev parent reply other threads:[~2023-07-24 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 0:14 'Julian Reich' via pandoc-discuss
[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 [this message]
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='CAFDSbVfut0occwpOm-JbZmy_7bOZ0K==uBEEbWV1oKTt4wuBYg@mail.gmail.com' \
--to=danielittlewood-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=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).