Questions about usage in case of AGPL license

[TomFreudenberg]

Dear @kernc

I am Tom, the author of https://github.com/tokeo/tokeo.

In there I wrote an extension named pdoc at https://github.com/tokeo/tokeo/blob/master/tokeo/ext/pdoc.py

I really heavily customized and extended the pdoc3 engine so do create smart and nice styled documentations for people using tokeo but maybe also others.

In case that the patent clauses are not regulared by MIT license, I changed tokeo into Apache 2.0

While I started with you mako files, I am not sure if this tangles me. My template files are located at:

https://github.com/tokeo/tokeo/tree/master/tokeo/templates/pdoc/html

My simple question is: Are the template files also AGPL license or may I use the shown stuff in tokeo for the use of Apache 2.0?

I checked already a transition to pdoc.dev but it would be heavy work for just the license question on the mako files.

Thanks for an answer, because I am in the process of deploying the new release.

Tom

[kernc]

I'd say the license applies exclusively to files inside pdoc dir.

If you simply do:

import pdoc
import pdoc.html_helpers

or wrap similar code with your own helpers (i.e. you just use the API), or use verbatim but unsubstantial parts of the source code, or use overridden templates in your own directories, IANAL, but I think you are fine.

👉 Might bear more expressly writing that templates are wholly exempt, though, because the alternative is senseless. 👈

Thanks for taking the time to raise this!

[TomFreudenberg]

Hi @kernc

thanks for answering so quick.

In case of the extension, I only use pdoc like you wrote

---

If this would be the case:

👉 Might bear more expressly writing that templates are wholly exempt, though, because the alternative is senseless. 👈

then there would be no license issue or question anymore.

But currently the templates are inside pdoc dir as subdir templates

I copied the mako files and adjusted them to my needs.

So if the mako template files are not meant to be AGPL licensed, then I just keep it and go on.

Please let me know, if and what I should add to the files to make sure that anybody can get that there is no license conflict.

Again, thanks for your feedback in advance
Tom

[kernc]

I copied the mako files and adjusted them to my needs.

If you had modified the files inside pdoc/templates, I believe the more correct way instead is to copy the files to your own directory outside the pdoc namespace and then use them as described in the last paragraph:

If working with pdoc programmatically, prepend the directory with modified templates into the directories list of the tpl_lookup object.

But I see that is already the case. 👍

---

The written exclusion in the source code regarding overridden templates is pending construction.

[TomFreudenberg]

Hi @kernc

yes, that is exactly the guide I followed

The written exclusion in the source code regarding overridden templates is pending construction.

If this done, the programmatic use of pdoc will be much easier in case of the license checker issues

Thanks for your support!