Can GoJS be included into an open source project?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
Context: GoJS is not open source, its license stating in particular that modification is forbidden (though the fact that its source code is hosted on GitHub seems to confuse some people).
The maintainer of GoJS wrote:
You may include the evaluation version of GoJS in open source projects, but people who use your project and want to use GoJS with it will have to purchase a license.
Is this statement true?
licensing proprietary-code redistribution
add a comment |Â
up vote
1
down vote
favorite
Context: GoJS is not open source, its license stating in particular that modification is forbidden (though the fact that its source code is hosted on GitHub seems to confuse some people).
The maintainer of GoJS wrote:
You may include the evaluation version of GoJS in open source projects, but people who use your project and want to use GoJS with it will have to purchase a license.
Is this statement true?
licensing proprietary-code redistribution
Are there any particular open source licenses you are interested in here? There's going to be a difference between a permissive license like MIT and a Free Software license like the GPL
â Philip Kendall
5 hours ago
@PhilipKendall: I am particularly interested in MIT/Apache 2/GPLv3, but answers about other OSI licenses are welcome too. The most important being, can an open source project include the library and still stay open source?
â Nicolas Raoul
4 hours ago
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Context: GoJS is not open source, its license stating in particular that modification is forbidden (though the fact that its source code is hosted on GitHub seems to confuse some people).
The maintainer of GoJS wrote:
You may include the evaluation version of GoJS in open source projects, but people who use your project and want to use GoJS with it will have to purchase a license.
Is this statement true?
licensing proprietary-code redistribution
Context: GoJS is not open source, its license stating in particular that modification is forbidden (though the fact that its source code is hosted on GitHub seems to confuse some people).
The maintainer of GoJS wrote:
You may include the evaluation version of GoJS in open source projects, but people who use your project and want to use GoJS with it will have to purchase a license.
Is this statement true?
licensing proprietary-code redistribution
licensing proprietary-code redistribution
asked 8 hours ago
Nicolas Raoul
1,456623
1,456623
Are there any particular open source licenses you are interested in here? There's going to be a difference between a permissive license like MIT and a Free Software license like the GPL
â Philip Kendall
5 hours ago
@PhilipKendall: I am particularly interested in MIT/Apache 2/GPLv3, but answers about other OSI licenses are welcome too. The most important being, can an open source project include the library and still stay open source?
â Nicolas Raoul
4 hours ago
add a comment |Â
Are there any particular open source licenses you are interested in here? There's going to be a difference between a permissive license like MIT and a Free Software license like the GPL
â Philip Kendall
5 hours ago
@PhilipKendall: I am particularly interested in MIT/Apache 2/GPLv3, but answers about other OSI licenses are welcome too. The most important being, can an open source project include the library and still stay open source?
â Nicolas Raoul
4 hours ago
Are there any particular open source licenses you are interested in here? There's going to be a difference between a permissive license like MIT and a Free Software license like the GPL
â Philip Kendall
5 hours ago
Are there any particular open source licenses you are interested in here? There's going to be a difference between a permissive license like MIT and a Free Software license like the GPL
â Philip Kendall
5 hours ago
@PhilipKendall: I am particularly interested in MIT/Apache 2/GPLv3, but answers about other OSI licenses are welcome too. The most important being, can an open source project include the library and still stay open source?
â Nicolas Raoul
4 hours ago
@PhilipKendall: I am particularly interested in MIT/Apache 2/GPLv3, but answers about other OSI licenses are welcome too. The most important being, can an open source project include the library and still stay open source?
â Nicolas Raoul
4 hours ago
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
4
down vote
accepted
You say the most important question is
can an open source project include the library and still stay open source?
IANAL/IANYL, but as I read it, no. Firstly, section 2.1.4(b) of the licence specifies that
Customer may not ... modify any Licensed Product, or create any derivative work of any Licensed Product
s2.1.5(a) allows you to modify it under certain circumstances, but then says you can't redistribute the modified version. Since our accepted definition of open source says in s3 that
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
You could not combine GoJS and any piece of free software into a derivative work, and redistribute it as a free project. I can't square the maintainer's words quoted above with the licence text, and the licence text is likely to have the final word on the subject, but even if we take his/her words at face value, your combined project would be non-free as users would be required to buy a licence for GoSJ.
While I think it is possible to create permissively-licensed open source projects that have non-free dependencies, the result would still be a non-free software system and would be of little use to other open source projects (as your answer explains). This equivalent to the âÂÂfree plugin in non-free applicationâ problem.
â amon
4 mins ago
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
accepted
You say the most important question is
can an open source project include the library and still stay open source?
IANAL/IANYL, but as I read it, no. Firstly, section 2.1.4(b) of the licence specifies that
Customer may not ... modify any Licensed Product, or create any derivative work of any Licensed Product
s2.1.5(a) allows you to modify it under certain circumstances, but then says you can't redistribute the modified version. Since our accepted definition of open source says in s3 that
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
You could not combine GoJS and any piece of free software into a derivative work, and redistribute it as a free project. I can't square the maintainer's words quoted above with the licence text, and the licence text is likely to have the final word on the subject, but even if we take his/her words at face value, your combined project would be non-free as users would be required to buy a licence for GoSJ.
While I think it is possible to create permissively-licensed open source projects that have non-free dependencies, the result would still be a non-free software system and would be of little use to other open source projects (as your answer explains). This equivalent to the âÂÂfree plugin in non-free applicationâ problem.
â amon
4 mins ago
add a comment |Â
up vote
4
down vote
accepted
You say the most important question is
can an open source project include the library and still stay open source?
IANAL/IANYL, but as I read it, no. Firstly, section 2.1.4(b) of the licence specifies that
Customer may not ... modify any Licensed Product, or create any derivative work of any Licensed Product
s2.1.5(a) allows you to modify it under certain circumstances, but then says you can't redistribute the modified version. Since our accepted definition of open source says in s3 that
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
You could not combine GoJS and any piece of free software into a derivative work, and redistribute it as a free project. I can't square the maintainer's words quoted above with the licence text, and the licence text is likely to have the final word on the subject, but even if we take his/her words at face value, your combined project would be non-free as users would be required to buy a licence for GoSJ.
While I think it is possible to create permissively-licensed open source projects that have non-free dependencies, the result would still be a non-free software system and would be of little use to other open source projects (as your answer explains). This equivalent to the âÂÂfree plugin in non-free applicationâ problem.
â amon
4 mins ago
add a comment |Â
up vote
4
down vote
accepted
up vote
4
down vote
accepted
You say the most important question is
can an open source project include the library and still stay open source?
IANAL/IANYL, but as I read it, no. Firstly, section 2.1.4(b) of the licence specifies that
Customer may not ... modify any Licensed Product, or create any derivative work of any Licensed Product
s2.1.5(a) allows you to modify it under certain circumstances, but then says you can't redistribute the modified version. Since our accepted definition of open source says in s3 that
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
You could not combine GoJS and any piece of free software into a derivative work, and redistribute it as a free project. I can't square the maintainer's words quoted above with the licence text, and the licence text is likely to have the final word on the subject, but even if we take his/her words at face value, your combined project would be non-free as users would be required to buy a licence for GoSJ.
You say the most important question is
can an open source project include the library and still stay open source?
IANAL/IANYL, but as I read it, no. Firstly, section 2.1.4(b) of the licence specifies that
Customer may not ... modify any Licensed Product, or create any derivative work of any Licensed Product
s2.1.5(a) allows you to modify it under certain circumstances, but then says you can't redistribute the modified version. Since our accepted definition of open source says in s3 that
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.
You could not combine GoJS and any piece of free software into a derivative work, and redistribute it as a free project. I can't square the maintainer's words quoted above with the licence text, and the licence text is likely to have the final word on the subject, but even if we take his/her words at face value, your combined project would be non-free as users would be required to buy a licence for GoSJ.
answered 2 hours ago
MadHatter
6,9481533
6,9481533
While I think it is possible to create permissively-licensed open source projects that have non-free dependencies, the result would still be a non-free software system and would be of little use to other open source projects (as your answer explains). This equivalent to the âÂÂfree plugin in non-free applicationâ problem.
â amon
4 mins ago
add a comment |Â
While I think it is possible to create permissively-licensed open source projects that have non-free dependencies, the result would still be a non-free software system and would be of little use to other open source projects (as your answer explains). This equivalent to the âÂÂfree plugin in non-free applicationâ problem.
â amon
4 mins ago
While I think it is possible to create permissively-licensed open source projects that have non-free dependencies, the result would still be a non-free software system and would be of little use to other open source projects (as your answer explains). This equivalent to the âÂÂfree plugin in non-free applicationâ problem.
â amon
4 mins ago
While I think it is possible to create permissively-licensed open source projects that have non-free dependencies, the result would still be a non-free software system and would be of little use to other open source projects (as your answer explains). This equivalent to the âÂÂfree plugin in non-free applicationâ problem.
â amon
4 mins ago
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f7424%2fcan-gojs-be-included-into-an-open-source-project%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Are there any particular open source licenses you are interested in here? There's going to be a difference between a permissive license like MIT and a Free Software license like the GPL
â Philip Kendall
5 hours ago
@PhilipKendall: I am particularly interested in MIT/Apache 2/GPLv3, but answers about other OSI licenses are welcome too. The most important being, can an open source project include the library and still stay open source?
â Nicolas Raoul
4 hours ago