Re: SDK header translations licensing?

Helen wrote:
>There is no "declaration for an exe".  MPL is about source code.  "Open" + 
>"source".

You may not like my choice of words, but I mean the text file you
refer to later.

>MPL requires you to make the source code available for any pieces you use 
>which are distributed under the MPL and to include the standard header on 
>the source code.  If you don't distribute the source code with your exe 
>(you are not required to) then you must provide a text file indicating 
>where it can be found.

The precise contents of this text file is somewhat opaque to me... as
you have no doubt guessed. I would be grateful if someone could post a
sample, and I think it would be useful if this was also available on
the JEDI site.

>You must use it "as distributed";  or, if you change the source, then you 
>are required to release the modified source under the MPL and provide 
>public access to it.
>
>The licence does not allow you to copy/paste code from MPL sources into 
>your own source code--that is theft.

No, it is copyright violation, which is a different offense to theft.
</pedant> ;)

>Regarding the Microsoft API headers - the original doubt expressed in this 
>thread is a storm in a teacup.  As long as you retain the correct JEDI 
>header (see http://delphi-jedi.org/ADMINLICENSING you are doing the right 
>thing regarding Microsoft's copyrights on the SDK.  Microsoft's copyright 
>to the C headers remains untouched by translation.  The copyright to the 
>Pascal translation remains with the person who did the translation (*NOT* 
>Project JEDI).
>
>Some third-party (rarely!!) apply special restrictions to the use of their 
>SDKs, which you should check carefully before submitting a translation 
>under the MPL.  However, in general, if SDKs are made available in the 
>public domain and you don't have to buy a licence to use them, then 
>publishing a translation of them is always OK, as long as you properly 
>attribute the owner of the copyrighted original.
>
>If there are JEDI API conversions being distributed without the headers, 
>then JEDI is in trouble. If there are modified JEDI API conversions in the 
>wild without the properly updated headers, then the person distributing 
>them is in trouble.  If there are executables that have used the JEDI 
>conversions being distributed without the licensing stuff, then the person 
>distributing the executable is in trouble - both with Project JEDI and with 
>the owner of the SDK.

The problematic header is not actually JEDI submitted as far as I am
aware. If I am to use it this will need to be corrected (and I must
mail the translator about it.


Martin

| VAZ virtual analogue synths | www.monosect.com
| www.software-technology.com | electronoiseclash


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/i7folB/TM
---------------------------------------------------------------------~->

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/Delphi-JEDI/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/