Please correct me if I am wrong.<br>
If existing codes of a project are licensed under GPL 2, and if someone
from that project wants to license the codes with GPL 3 that command,
EVERY code owner or contributor will need to agree on using the *new*
license.<br>
<br>
realistically, if at least one ojbects the change, the codes can't be licensed&nbsp; with the new license.<br>
<br>
so GPL3 with that command&nbsp; doesn't apply to most of the existing
projects.&nbsp; or someone can fork an project and apply the GPL 3
license.<br>
<br>
It can be used on any new project though.<br>
<br>
<br><br><div><span class="gmail_quote">On 9/30/05, <b class="gmail_sendername">Karoly Negyesi</b> &lt;<a href="mailto:karoly@negyesi.net">karoly@negyesi.net</a>&gt; 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>Some companies, such as Google, use code covered by GPL to offer their<br>services through the Web. Do you plan to extend GPL 3 copyleft to request<br>code publication in this case too, considering this behavior like a
<br>product distribution?<br><br>Running a program in a public server is not distribution; it is public<br>use. We're looking at an approach where programs used in this way will<br>have to include a command for the user to download the source for the
<br>version that is running.<br><br>But this will not apply to all GPL-covered programs, only to programs that<br>already contain such a command. Thus, this change would have no effect on<br>existing software, but developers could activate it in the future.
<br><br>This is only a tentative plan, because we have not finished studying the<br>matter to be sure it will work.<br><br>How would it work?<br><br>If you release a program that implements such a command, GPL 3 will<br>require others to keep the command working in their modified versions of
<br>the program.<br>-------<br></blockquote></div><br>