[nem-en] Legally Distributing Visual Studio Plugin Source

[NoiseEHC]

>>>> Excluded Licenses ... or (b) others have the
>>>> right to modify it.
>>>>         
>> How can others be able to look at the code, but not be able to modify
>> it?
>>     
>
> I think it states, that if you take their sample code, you cannot use
> a license, that requires the version derived from yours, to be
> modifable by third parties.
>
>
>   
OK, as usually I have left out some critical information from my email... :)

EULA (snipped) (last time snipped too much...)
1. Definitions.
1.1 “Eligible Products” means your software development tools or 
products that:
· work in conjunction with Visual Studio; and
· run on one or more Microsoft Platforms; and
· EITHER:
o have as a primary purpose the creation of applications or components 
that natively operate on any Microsoft Platforms; OR
o do not integrate with the Visual Studio integrated development 
environment, but provide data integration or web services integration to 
Visual Studio Team Foundation Server.
1.2 “Integration Code” means the code you develop, using the Software, 
to integrate Eligible Products with Visual Studio.
...
· Excluded Licenses. You will not modify or distribute the source code 
of any Distributable Code so that any part of it becomes subject to an 
Excluded License. An “Excluded License” is one that requires, as a 
condition of use, modification or distribution, that (a) the code be 
disclosed or distributed in source code form; or (b) others have the 
right to modify it.

So, the last paragraph is about a license which affects the 
Distributable Code, eg the SDK.
The BSD only affects the Integration Code, what we will write.
With the GPL the whole package could became GPL, even MS's code what is 
in Distributable Code. So it is completely normal to prohibit that.