Questions about usage in case of AGPL license
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked tokeo/ext/pdoc.py file and the tokeo/templates/pdoc/html directory first, then inspect the relevant license notices and repository history. The issue is done when a maintainer-approved answer clearly explains the licensing status of the referenced code and templates for the reporter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100