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

License compliance #26

Open
Necklaces opened this issue Nov 14, 2019 · 0 comments
Open

License compliance #26

Necklaces opened this issue Nov 14, 2019 · 0 comments

Comments

@Necklaces
Copy link

Looking around this repository, coming from someone who never looked at it before, I'm having trouble identifying the license that applies to the entire codebase.

Am I correct to guess that this file: https://github.com/vusec/ridl/blob/master/tool/LICENSE is applicable to all code in this repository (excluding the git submodules, of course), or does it only apply to the code in that tool directory?

If the latter, is the code found in the other folders then unlicensed, meaning regular copyright applies to it?

If the first, should this file maybe be moved to the top directory so that both Github and visiting viewers can identify what license this repository is under?

Another thing, it seems to me the MPL requires the license notice to be attached in some way to every file it is applied to: https://www.mozilla.org/en-US/MPL/2.0/FAQ/#header-locations

So it would probably be advisable to add a license header to every source file that the MPL is applied to in this codebase:

/* This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at https://mozilla.org/MPL/2.0/. */

Thoughts?

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

No branches or pull requests

1 participant