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 2(b) use the definition of Defensive Purpose rather than providing a different definition of "defensively" #14

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

joshtriplett
Copy link

This ensures that a company filing a patent suit for a Defensive Purpose does not open themselves to lawsuits by other companies who follow this agreement.

@jrconlin
Copy link

In addition, can we have some clarification of what "Defensive" means or in what context it applies?

For instance, say I create a library that uses GPL. I discover that Twitter uses it, but fails to publish the code/include copyright statement/etc. If I sought correction, would that trigger a "Defensive" action of being sued for any patent related content my library (or other libraries I may have authored) may contain?

The above is just one potential non-patent related scenario that could trigger the defense mechanism. I can easily imagine others.

@joshtriplett
Copy link
Author

@jrconlin That seems like a separate issue. This pull request will make sure the whole agreement uses the same definition of "Defensive Purpose"; if you want to clarify that definition, I'd suggest filing a separate issue about that.

I do agree that the issue you raised seems significant.

@jrconlin
Copy link

Thanks, will do. Also took the opportunity to generalize it a bit:
#15

@joshtriplett
Copy link
Author

I like this pull request (even though recursion sometimes makes my head hurt). Unless I can think of some reason over the weekend for not doing this, I think I will merge it...

Any status on this? Any reasons not to merge? (Happy to update if doesn't apply.)

@joshtriplett
Copy link
Author

Any plans to incorporate this change?

@CLAassistant
Copy link

CLAassistant commented Jul 18, 2019

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@sarasfox
Copy link

sarasfox commented Jul 18, 2019 via email

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

Successfully merging this pull request may close these issues.

None yet

4 participants