Howdy folks,
A query from Frank Swiderski of HauteSecure on whether they can link
their closed source product against libxul (and include Mozilla headers
in some of their source files) and still keep their product closed source.
What's the normal process for reviewing and responding to these types of
queries?
Thanks,
kev
--- Begin Message ---
Basil said this list was the right place to send this query.
W
---------- Forwarded message ----------
From: Frank Swiderski <[EMAIL PROTECTED]>
Date: Thu, Mar 20, 2008 at 2:42 PM
Subject: Mozilla Licensing Questions
To: Iain Mulholland <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Hi Window,
If you could find someone to answer these questions, that would be great.
We're in the process of revamping parts of Haute Secure (including going
cross-platform with certain features). We'd like to use the Mozilla
libraries and build environment to assist in the portability. However,
we're having a bit of difficulty understanding the exact licensing for our
scenario. The majority of our software will remain closed-source for the
near future, and we'd like to keep it that way. If we use the Mozilla
libraries in unmodified binary form, can we utilize the Mozilla headers and
build environment for our code without making it open source?
For example, we will be re-writing our administration UI and would like to
create the UI using XUL and use functionality of XPCOM within the code for
our admin program. That means we may link against libxul, and that our code
would #include Mozilla headers in some of our source files. We know that
the license is on a binary basis, but does the inclusion of Mozilla headers
then require our source that includes those headers to be open, or can it
remain closed? Furthermore, if we use the Mozilla build environment to
compile the program, does that have licensing implications? We would
obviously adhere to any copyright notice requirements, etc.
I *think* that the "copyleft" clause/Covered Code/Modification
definition for the MPL as discussed in the MPL FAQ
(http://www.mozilla.org/MPL/mpl-faq.html)
are <http://www.mozilla.org/MPL/mpl-faq.html%29+are> such that we can
#include Mozilla headers and use the build environment, but I wanted to make
sure.
Thanks,
fes
_______________________________________________
partners mailing list
[EMAIL PROTECTED]
https://mail.mozilla.org/listinfo/partners
--- End Message ---
_______________________________________________
legal mailing list
[email protected]
https://lists.mozilla.org/listinfo/legal
