On Tue, Oct 18, 2016 at 7:07 AM, Igor Sapego <isap...@gridgain.com> wrote:
> 1. This tool is licensed under Microsoft Reciprocal License (MS-RL). > The license requires that fixes and improvements to the WiX toolset must be > published using the same license. > This is OK, since we are not going to be changing the tool. Let's make sure that we do not store the tool itself in our GIT repository. > 2. We store XML in our sources (written by us) which is used to > generate binaries - installers. It was planned to distribute them in binary > distribution. These binaries are not considered as a derived work as stated > here - [1], so it seems that it's OK to distribute them. This gets a bit delicate. Given that the installer packages are not considered a derivative work, we can license them under Apache. However, we can not store binary files in our repository. If there are binary files or libraries that are generated for the installer, then we must generate them as part of our build process. Makes sense? > Here is the quote: > OuterCurve Foundation (and the .NET Foundation) does not view the installer > > packages > > generated by WiX as falling within the definition of a derivative work, > > merely because > > they are produced using WiX. Thus, the installer packages generated by > WiX > > will normally > > fall outside the scope of the MS-RL, and any of your source code, > > binaries, libraries, routines > > or other software components that are incorporated in installer packages > > generated by WiX > > can be governed by other licensing terms. > > > [1] - http://wixtoolset.org/about/license/ > > > > > Best Regards, > Igor > > On Tue, Oct 18, 2016 at 3:18 PM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > 1. Do you know the license of WixToolset? > > 2. Keep in mind, that Apache source code cannot store any binary files in > > it. Do we generate any binaries with this tool, or only XML? > > > > On Tue, Oct 18, 2016 at 3:47 AM, Igor Sapego <isap...@gridgain.com> > wrote: > > > > > Dmitriy, > > > > > > I don't think there is a problem, I just wanted to be sure as I don't > > have > > > a lot of experience with licensing. > > > > > > To me it looks like everything is fine. > > > > > > Best Regards, > > > Igor > > > > > > On Mon, Oct 17, 2016 at 10:09 PM, Dmitriy Setrakyan < > > dsetrak...@apache.org > > > > > > > wrote: > > > > > > > Igor, > > > > > > > > In my understanding, it is OK to use any tool, as long as it does not > > get > > > > into Ignite source or binary distributions. Everything in the source > > code > > > > should either be licensed under Apache license or have a friendly > > > license. > > > > > > > > Given the above, can you please clarify whether using this tool is a > > > > problem? > > > > > > > > D. > > > > > > > > On Mon, Oct 17, 2016 at 11:51 AM, Igor Sapego <isap...@gridgain.com> > > > > wrote: > > > > > > > > > Hello Igniters, > > > > > > > > > > Recently I've been working on .msi installer for the ODBC driver > [1]. > > > > > > > > > > I've decided to use WiX toolset [2] for this task. However, I'm not > > > > > quite sure if it's OK from the legal standpoint to use this tool > for > > > the > > > > > Apache > > > > > product. > > > > > > > > > > What we are going to distribute is two XML files with configuration > > and > > > > > two installers in binary packages. > > > > > > > > > > Can someone from community who is more familiar with the licensing > > > take a > > > > > look? > > > > > I believe, WiX license information can be found here [3]. > > > > > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-3873 > > > > > [2] - http://wixtoolset.org > > > > > [3] - http://wixtoolset.org/about/license > > > > > > > > > > Best Regards, > > > > > Igor > > > > > > > > > > > > > > >
