2016-01-24 18:53 GMT+01:00 Martin Pool <m...@sourcefrog.net>: ... >> You might be right but I am a bit hesitant. >> >> >> http://programmers.stackexchange.com/questions/58338/when-porting-code-must-i-follow-the-original-license >> >> http://programmers.stackexchange.com/questions/90232/original-author-rights-in-a-licensed-software-project?rq=1 >> >> http://programmers.stackexchange.com/questions/86754/is-it-possible-to-rewrite-every-line-of-an-open-source-project-in-a-slightly-dif > > > These are talking about different situations: > > - 'porting' in the sense of making code run on a different platform while > still having some code in common > - line-by-line rewrite or translation > - writing a new program using the rsync source as documentation of the > protocol, as you are doing > > In my (not a lawyer) opinion, the last of them does not create a copyright > derivative, and (separately) I don't object to you doing that on GPL'd work > that I wrote. I would consider the first two to be a violation.
OK, that distinction does make sense. > I think you have a couple of cheap options to get some clarity: > > - mail the other key authors listed above explaining what you're doing and > ask if they object > - mail the FSF or SFLC as custodians of the L/GPL Yes that is a very good idea. I will start by contacting FSF and see if they can clarify this. Thanks. -- Per Lundqvist -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
