Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to improve doclicense? Integrate with https://reuse.software/? #72

Open
1 of 3 tasks
ypid opened this issue Mar 14, 2021 · 0 comments
Open
1 of 3 tasks

How to improve doclicense? Integrate with https://reuse.software/? #72

ypid opened this issue Mar 14, 2021 · 0 comments

Comments

@ypid
Copy link
Owner

ypid commented Mar 14, 2021

First of all: I am not a lawyer

The Problem

Currently, doclicense is designed to put a footer into the document like this:

doclicenseThis

(Specifying one license only).

But are you sure that?

  1. All included text or artifact (image/figure/table/source code listing) are under this license? Or can they be released under this license?
  2. What the original licensing and copyright situation of all the source files that end up or influence the final document is?

Proposal

https://reuse.software/ was created to address this but with focus on software projects. I made the source code of doclicense itself compliant with this spec in #71. This got me thinking and I propose the following:

  • Include a hint in the docs that document source files should be compliant with the REUSE Specification. Add section to doclicense what license to use and REUSE spec #73
  • Check the license of all files included in LaTeX compilation that are covered by the REUSE Specification and if they are different to the "main license of the document" (as set with the package options), emit warnings during compilation.
  • Provide a macro to attribute artifacts differently, based on REUSE Specification.

The question is if we could go further than that. Would it be useful for the package to check all included files for their license, if it is the same license, pick that (making the package options optional). I am not sure about that.

Further discussion is welcome. I have no timeline if or when I implement this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant