openlp-core team mailing list archive

Thread
Date

Re: [Merge] lp:~bastian-germann/openlp/pymupdf into lp:openlp

To: mp+366749@xxxxxxxxxxxxxxxxxx
From: Bastian Germann <bastiangermann@xxxxxxxxxxx>
Date: Wed, 01 May 2019 11:52:00 -0000
In-reply-to: <155670303973.23875.15656810483775482091.launchpad@ackee.canonical.com>
Reply-to: mp+366749@xxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

No, we do not have to include MuPDF's source code. The AGPL has additional obligations for an OPERATOR who makes a AGPL-licenced work available via network. As OpenLP has the remote features, this applies here.

So a church that runs a MODIFIED MuPDF with OpenLP would have to provide its MuPDF version via a website to their users. I do not think that this will apply to any users.

In fact if you apply a strict interpretation of the AGPL's term "covered work" you already have this situation now when using MuPDF via subprocess.
-- 
https://code.launchpad.net/~bastian-germann/openlp/pymupdf/+merge/366749
Your team OpenLP Core is subscribed to branch lp:openlp.

References

[Merge] lp:~bastian-germann/openlp/pymupdf into lp:openlp
From: Bastian Germann, 2019-05-01