IANAL, etc.<br><br><div><span class="gmail_quote">On 9/9/07, <b class="gmail_sendername">Rick Moen</b> <<a href="mailto:rick@linuxmafia.com">rick@linuxmafia.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>It is clear to me that the example you cite, of a project leader<br>changing the project's licensing terms from GPLv2 to GPLv3, does qualify<br>as protecting the rights of contributors and avoiding injury to them.
</blockquote><div><br><br>So you are saying that if any of Tivo's patches were accepted, that moving the Linux kernel from GPL2 to GPL3 would not cause them injury sufficient for a cause of action?<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> I can't speak for every open source developer, but there is no way in heck<br>> I'm getting myself on the hook based on the advice of Internet IANAL's<br>> (and the occasional real lawyer), none of whom I can sue for incompetance
<br>> if they are wrong.<br><br>No, you should act on the basis of an elementary understanding of tort<br>law, which turns out to be not very difficult.</blockquote><div><br>I don't want to take legal advice from Eric Raymond or you. Based on his analysis, upgrading a GPL license to an AGPL would be OK (since the AGPL is not really functionally different from the OSL) and there is *no way* this would be acceptable to projects I work on for very practical reasons.
<br><br>Best WIshes,<br>Chris Travers<br></div></div><br>