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

Update README.md - question regarding context #21

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

jeremiah
Copy link
Collaborator

@jeremiah jeremiah commented Dec 2, 2024

Small changes for clarity.

I feel more detail around "context" is needed. What do you mean when you say context here? Do you mean how is a given component used? E.g. is it source code, a combined work, or compiled binary?

Small changes for clarity.

I feel more detail around "context" is needed. What do you mean when you say context here? Do you mean how is a given component used? E.g. is it source code, a combined work, or compiled binary?
@jeremiah jeremiah added the documentation Improvements or additions to documentation label Dec 2, 2024
@jeremiah jeremiah changed the title Update README.md Update README.md - question regarding context Dec 2, 2024
@jeremiah jeremiah requested a review from hesa December 2, 2024 12:55
@hesa
Copy link
Owner

hesa commented Dec 2, 2024

Thanks.

The sections "Usecase", "Provisioning" and "Modification" are that context. But this is not presented clearly, agreed.

How about adding some words to the first section to, like this:


Answering whether one license is compatible with another needs some context. This context is often missing in the question but sometimes also in tooling. We have tried to organise this context and a way to provide this to the tool.

The context currently supported (more details below)

  • Usecase
  • Provisioning
  • Modification

@jeremiah jeremiah self-assigned this Dec 2, 2024
@jeremiah
Copy link
Collaborator Author

jeremiah commented Dec 2, 2024

Determining if a license is compatible with another requires context which is often missing in tooling. We have tried to organise this context and to provide this to the tool. [Here I would describe the context itself. This is important because the use case won't really make sense to most people if the context is not understood.]

Usecase
Provisioning
Modification

@hesa hesa merged commit 34c7649 into main Dec 4, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants