Re: SDK header translations licensing?
Helen Borrie <[email protected]>
| Newsgroups | gmane.comp.lang.delphi.jedi |
|---|---|
| Message-ID | <[email protected]> |
At 06:14 PM 4/03/2004 +0000, you wrote:
>As a slight aside does anyone have an example of the declaration
>required by MPL for an exe? For source it's obvious, but the MPL
>itself isn't that clear about what you need for exe distribution
>though it says you can...
There is no "declaration for an exe". MPL is about source code. "Open" +
"source".
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.
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.
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.
Helen
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/