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

Make Project Name actually effect the scope of the Material and Contribution? #54

Open
silverhook opened this issue Oct 14, 2022 · 2 comments
Labels
legal legal question

Comments

@silverhook
Copy link

Currently, there is a Project Name (+ website + email) field, but that field could be construed as solely informational, if anything at all, since it occurs before the title of the document and is nowhere referred to in the document itself.

Consequentially, it seems like the FLA (or any other CA.org CLA) could be interpreted to apply to any contribution from “You” to “Us” that is not explicitly marked as “not a contribution”, whatever you write in the Project Name field.

Would it make sense to somehow make the scope clearer to what Material and Contribution apply to …or am I being too pedantic?

@silverhook silverhook added the legal legal question label Oct 14, 2022
@silverhook
Copy link
Author

silverhook commented Jan 17, 2023

@catharinamaracke and I agree that we should limit it to the Project and use the Project name field in the actual text.

In that case the Project Name could be used to narrow down the project to the detail that would be good enough also for a B2B use case.

@silverhook
Copy link
Author

We use the Project Name in the Contribution definition, for it to have a better scope and get rid of ambiguity.

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

No branches or pull requests

1 participant