Comments on: web.py Released http://scott.yang.id.au/2006/01/webpy-released/ Faith, Technology and Randomness in Life, According to Scott Wed, 08 Feb 2012 13:17:24 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: web.py Gone Public Domain | FuCoder.com http://scott.yang.id.au/2006/01/webpy-released/#comment-87920 web.py Gone Public Domain | FuCoder.com Thu, 23 Mar 2006 09:49:23 +0000 http://scott.yang.id.au/2006/01/49/#comment-87920 [...] Related Post 28 Jan: Guido wants your input on Python web frameworks04 Jan: web.py Released11 Mar: Gosling on PHP/Ruby, DHH on Gosling15 Sep: Google Blog Search08 Oct: Google Reader, the Ajaxified RSS Aggregator in Beta [...] [...] Related Post 28 Jan: Guido wants your input on Python web frameworks04 Jan: web.py Released11 Mar: Gosling on PHP/Ruby, DHH on Gosling15 Sep: Google Blog Search08 Oct: Google Reader, the Ajaxified RSS Aggregator in Beta [...]

]]> By: Guido wants your input on Python web frameworks | FuCoder.com http://scott.yang.id.au/2006/01/webpy-released/#comment-87889 Guido wants your input on Python web frameworks | FuCoder.com Fri, 27 Jan 2006 22:36:41 +0000 http://scott.yang.id.au/2006/01/49/#comment-87889 [...] Related Post 04 Jan: web.py Released04 Jan: Ajax Python!06 Jan: Ease of Deployment Matters15 Dec: Picking up Django17 Nov: Bloglines2HTML 0.2 Released [...] [...] Related Post 04 Jan: web.py Released04 Jan: Ajax Python!06 Jan: Ease of Deployment Matters15 Dec: Picking up Django17 Nov: Bloglines2HTML 0.2 Released [...]

]]> By: J http://scott.yang.id.au/2006/01/webpy-released/#comment-87888 J Mon, 16 Jan 2006 10:28:51 +0000 http://scott.yang.id.au/2006/01/49/#comment-87888 IANAL, but "must offer an equivalent opportunity for all users interacting with your Program through a computer network to request immediate transmission by HTTP of the complete source code of your modified version or other derivative work." that does at least cover any modifications you made to web.py. I don't know if the web app is a derivative work. If so, web.py indeed suffers from GPL poisoning. Wouldn't it be better if it were licensed under LGPL? IANAL, but

“must offer an equivalent opportunity for all users interacting with your Program through a computer network to request immediate transmission by HTTP of the complete source code of your modified version or other derivative work.”

that does at least cover any modifications you made to web.py. I don’t know if the web app is a derivative work. If so, web.py indeed suffers from GPL poisoning. Wouldn’t it be better if it were licensed under LGPL?

]]> By: Scott Yang http://scott.yang.id.au/2006/01/webpy-released/#comment-87884 Scott Yang Tue, 10 Jan 2006 20:36:52 +0000 http://scott.yang.id.au/2006/01/49/#comment-87884 There's no obligation to release source code created in C, because your application does not include GCC in anyway but maybe some libraries which might be licensed differently. web.py is not released under GNU GPL, but rather <a href="http://www.affero.org/oagpl.html" rel="nofollow">Affero GPL</a>. Read the article by Robert Sayre I've linked to, and cast your own judgement... There’s no obligation to release source code created in C, because your application does not include GCC in anyway but maybe some libraries which might be licensed differently.

web.py is not released under GNU GPL, but rather Affero GPL. Read the article by Robert Sayre I’ve linked to, and cast your own judgement…

]]> By: J http://scott.yang.id.au/2006/01/webpy-released/#comment-87883 J Tue, 10 Jan 2006 14:22:03 +0000 http://scott.yang.id.au/2006/01/49/#comment-87883 Isn't GCC licensed under the GPL (v2 I think) ? If so, there's no obligation to release source code created in C that's compiled with GCC, so how does that differ from a webapp vs. web.py? Isn’t GCC licensed under the GPL (v2 I think) ? If so, there’s no obligation to release source code created in C that’s compiled with GCC, so how does that differ from a webapp vs. web.py?

]]>