Can I translate App under GPLv3 into Swift without using GLPv3?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
Can I translate an App from Android using GPLv3 into Swift? Because actually I don't use any source code. Do I need to keep it under GPLv3 and open source? Is there any method to avoid infection if it must under GPLv3?
gpl-3
New contributor
add a comment |Â
up vote
1
down vote
favorite
Can I translate an App from Android using GPLv3 into Swift? Because actually I don't use any source code. Do I need to keep it under GPLv3 and open source? Is there any method to avoid infection if it must under GPLv3?
gpl-3
New contributor
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Can I translate an App from Android using GPLv3 into Swift? Because actually I don't use any source code. Do I need to keep it under GPLv3 and open source? Is there any method to avoid infection if it must under GPLv3?
gpl-3
New contributor
Can I translate an App from Android using GPLv3 into Swift? Because actually I don't use any source code. Do I need to keep it under GPLv3 and open source? Is there any method to avoid infection if it must under GPLv3?
gpl-3
gpl-3
New contributor
New contributor
New contributor
asked 1 hour ago
F.Jiang
61
61
New contributor
New contributor
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
The GPLv3 licence of the original requires that, if you create a work which is (in copyright terms) a derivative of the original, and you distribute your derivative, you must do so under GPLv3.
It's not clear to me in what sense you're using translate. If you mean it in the linguistic sense, translating from one human language to another, then I can't see any way not to create a derivative.
If you're using it to mean converting an application from one programming language to another, this is normally referred to as porting. It is possible to do this in a way that doesn't create a derivative work, but it requires two people, and is known as a clean-room reimplementation. To do this, one person must take the current work apart, and express exactly what it does in a document called a functional specification. The other person then, without ever seeing the original work or directly communicating with the first person, implements the functional specification in the new computer language. This is an enormous amount of work. If you decide to do the port by yourself it is very likely that the work you create would be regarded as a derivative of the original work.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
The GPLv3 licence of the original requires that, if you create a work which is (in copyright terms) a derivative of the original, and you distribute your derivative, you must do so under GPLv3.
It's not clear to me in what sense you're using translate. If you mean it in the linguistic sense, translating from one human language to another, then I can't see any way not to create a derivative.
If you're using it to mean converting an application from one programming language to another, this is normally referred to as porting. It is possible to do this in a way that doesn't create a derivative work, but it requires two people, and is known as a clean-room reimplementation. To do this, one person must take the current work apart, and express exactly what it does in a document called a functional specification. The other person then, without ever seeing the original work or directly communicating with the first person, implements the functional specification in the new computer language. This is an enormous amount of work. If you decide to do the port by yourself it is very likely that the work you create would be regarded as a derivative of the original work.
add a comment |Â
up vote
2
down vote
The GPLv3 licence of the original requires that, if you create a work which is (in copyright terms) a derivative of the original, and you distribute your derivative, you must do so under GPLv3.
It's not clear to me in what sense you're using translate. If you mean it in the linguistic sense, translating from one human language to another, then I can't see any way not to create a derivative.
If you're using it to mean converting an application from one programming language to another, this is normally referred to as porting. It is possible to do this in a way that doesn't create a derivative work, but it requires two people, and is known as a clean-room reimplementation. To do this, one person must take the current work apart, and express exactly what it does in a document called a functional specification. The other person then, without ever seeing the original work or directly communicating with the first person, implements the functional specification in the new computer language. This is an enormous amount of work. If you decide to do the port by yourself it is very likely that the work you create would be regarded as a derivative of the original work.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
The GPLv3 licence of the original requires that, if you create a work which is (in copyright terms) a derivative of the original, and you distribute your derivative, you must do so under GPLv3.
It's not clear to me in what sense you're using translate. If you mean it in the linguistic sense, translating from one human language to another, then I can't see any way not to create a derivative.
If you're using it to mean converting an application from one programming language to another, this is normally referred to as porting. It is possible to do this in a way that doesn't create a derivative work, but it requires two people, and is known as a clean-room reimplementation. To do this, one person must take the current work apart, and express exactly what it does in a document called a functional specification. The other person then, without ever seeing the original work or directly communicating with the first person, implements the functional specification in the new computer language. This is an enormous amount of work. If you decide to do the port by yourself it is very likely that the work you create would be regarded as a derivative of the original work.
The GPLv3 licence of the original requires that, if you create a work which is (in copyright terms) a derivative of the original, and you distribute your derivative, you must do so under GPLv3.
It's not clear to me in what sense you're using translate. If you mean it in the linguistic sense, translating from one human language to another, then I can't see any way not to create a derivative.
If you're using it to mean converting an application from one programming language to another, this is normally referred to as porting. It is possible to do this in a way that doesn't create a derivative work, but it requires two people, and is known as a clean-room reimplementation. To do this, one person must take the current work apart, and express exactly what it does in a document called a functional specification. The other person then, without ever seeing the original work or directly communicating with the first person, implements the functional specification in the new computer language. This is an enormous amount of work. If you decide to do the port by yourself it is very likely that the work you create would be regarded as a derivative of the original work.
answered 1 hour ago
MadHatter
7,0691533
7,0691533
add a comment |Â
add a comment |Â
F.Jiang is a new contributor. Be nice, and check out our Code of Conduct.
F.Jiang is a new contributor. Be nice, and check out our Code of Conduct.
F.Jiang is a new contributor. Be nice, and check out our Code of Conduct.
F.Jiang is a new contributor. Be nice, and check out our Code of Conduct.
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%2f7464%2fcan-i-translate-app-under-gplv3-into-swift-without-using-glpv3%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