I have 2 files which are under the MPL. -mozilla.c -mozilla.h
Now i wrote my own stuff in two files called. -mynewstuff.c -mynewstuff.h
Now i modified "mozilla.c" so that it calls some brand new functions from "mynewstuff.h". Therefore i added #include "mynewstuff.h" and made in "mozilla.c" some calls to my brand new functions. This means i modified "mozilla.c.
1. Problem: As i understand i have to put the mozilla mpl covered file "mozilla.c" and "mozilla.h" under the MPL since they are MPL. And i can put "mynewstuff.c" and "mynewstuff.h" under my commercial license and make it closed source? Is this correct?
2. Problem: Description of my modifications made to the "mozilla.c" file.
Now MPL says in 3.3 Description of Modifications:
"You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentatio in which You describe the origin or ownership of the Covered Code."
What is the prefered way to document these changes? Is it sufficient to provide a diff file containing the changes made between original "mozilla.c" and my modified version of "mozilla.c"? Is it ok to distribute the: modified mozilla.c along with a diff file containing the changes made to "mozilla.c"? Or do i have to mark each line of code which i modified in "mozilla.c" with date and author indication this line was changed? Can someone provide me an example how modified MPL files have to look and these file documenting the changes?
Regards
Chris _______________________________________________ mozilla-license mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-license
