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

Top-level license file #2862

Open
Maniues opened this issue Dec 27, 2024 · 2 comments
Open

Top-level license file #2862

Maniues opened this issue Dec 27, 2024 · 2 comments

Comments

@Maniues
Copy link

Maniues commented Dec 27, 2024

I know there are many license files for specific packages, but I think it would be nice to add a top-level LICENSE file that will:

  1. Inform repo viewers under which license this project licensed is
  2. Cover unrelated of packages files (like README, global package.json etc.)
@ckeshava
Copy link
Collaborator

This repository is organized into distinct Javascript packages (xrpl, ripple-binary-codec and so forth). Consequently, each of them have their own LICENSE files: https://github.com/XRPLF/xrpl.js/blob/main/packages/xrpl/LICENSE

Is this required for any legal purposes? Can you point me to other open-source examples where the umbrella repo has a LICENSE file ?

@Maniues
Copy link
Author

Maniues commented Dec 31, 2024

@ckeshava

Is this required for any legal purposes?

There are several files that may be useful for usage AND that are UNLICENSED:

  • markdown files like README, MIGRATION etc
  • config files *.json, *.js in top-level directory
  • there is documentation (docs directory)

Can you point me to other open-source examples where the umbrella repo has a LICENSE file ?

I can search for some examples, but I don't know many libraries that are split into many licenses.
Some similar can be Notesnook: one app, many packages or NocoDB.

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

2 participants