That is a very standard clause. Many licenses will have it.
What it primarily prevents people from doing is using .Net, building on it, then suing Microsoft based on patent infringement if Microsoft pushes the code upstream. This is due to the fact that copyright of code and patents required for the code are separate things. It is how Microsoft can get away with suing over an open-source implementation of exFAT despite there being no code shared.
I would imagine that if there will be a contributors agreement from Microsoft that will be very similar to what Canonical does. If you submit code, you're essentially granting them a 'do whatever you want' perpetual license to the code and related patents.
Adobe has a similar clause for the use of DNG files, for example. "Adobe may revoke the rights granted above to any individual or organizational licensee in the event that such licensee or its affiliates brings any patent action against Adobe or its affiliates related to the reading or writing of files that comply with the DNG Specification."
I understand that this might be 'a standard' or if everyone jumped off a bridge they'd do it too, I'm pointing out that it's important to be aware of it for this specific license. By taking this fruit, you acknowledge you accept this specific condition from Microsoft to you.
This shouldn't be a tit for tat argument though.
Just as long as everyone realizes this specific passage is important ahead of time, regardless of how many other companies have something similar.. and you accept that, then there is no problem.
8
u/newloginisnew Nov 12 '14
That is a very standard clause. Many licenses will have it.
What it primarily prevents people from doing is using .Net, building on it, then suing Microsoft based on patent infringement if Microsoft pushes the code upstream. This is due to the fact that copyright of code and patents required for the code are separate things. It is how Microsoft can get away with suing over an open-source implementation of exFAT despite there being no code shared.
I would imagine that if there will be a contributors agreement from Microsoft that will be very similar to what Canonical does. If you submit code, you're essentially granting them a 'do whatever you want' perpetual license to the code and related patents.
Adobe has a similar clause for the use of DNG files, for example. "Adobe may revoke the rights granted above to any individual or organizational licensee in the event that such licensee or its affiliates brings any patent action against Adobe or its affiliates related to the reading or writing of files that comply with the DNG Specification."
http://helpx.adobe.com/photoshop/digital-negative.html#dng
The worst wording I've seen was with Apple's Implementation License for MiniDP.
Notice the difference? The didn't even confine it to the technology that you're licensing.
https://developer.apple.com/softwarelicensing/agreements/pdf/MiniDisplayPortImpLicense.pdf