This is a very good point indeed and seems like a great opportunity to bring our game up to a higher level.
It seems to me that if the scaffolding app (welcome) is copyright Massimo and owned by him and/or Web2py then he/web2py have the legal right to do with it what they will. If we feel like making Massimo work some more and he is willing (or the Web2py legal entity) then we could do something like this: Create Application [ ] Target License [ ] Drop Down or cool search function Where the "Target License" could come from the list at http://www.opensource.org/licenses/alphabetical or some other trusted source of software licenses. So when I am doing an app for my commercial client he chooses MIT cause he knows he can resell it and so on and when I create his app appname/LICENSE gets populated with the content at http://www.opensource.org/licenses/mit-license.php In addition to keeping lawyers happy about the target application by forcing indecisive and/or procrastinating developers (is this not the one requirement for being Pythonic?) to decide on an "official" license for their application up front it also gives the client, the developer and anyone following in their footsteps clear legal footing which in turns allows for a greater adoption of Web2py applications and the code included in the application. I think that providing for a mechanism that gives a high level of clarity right at the initial creation of an application will go a long way towards resolving this issue for legal entities and in the minds of developers as well. On Dec 11, 4:02 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > You have a good point. The welcome scaffolding app is not GPL. It is > pubic domain (no license whatsoever). > I have said that before but it is not explicitly stated in the > license. > I will add a statement to the top of each .py file in the welcome app. > > Massimo > > On Dec 11, 2:52 pm, Branko Vukelic <bg.bra...@gmail.com> wrote: > > > On Sat, Dec 11, 2010 at 9:49 PM, VP <vtp2...@gmail.com> wrote: > > > My understanding is this. The apps that you develop with Web2py does > > > not have to be GPL, and can be licensed in any way you want. (I am > > > unsure if this violates GPL's terms or not, but this is what I think > > > how web2py's licensing permits). > > > > What is GPL is the web2py framework itself. So, as long as your app > > > does not touch web2py's core and stay within web2py/applications/ > > > yourapp directory, that should be okay. On the other hand, if you > > > want to take web2py add features to it, modify it, then it will have > > > to be GPL. > > > There's one catch, though. If a piece of code is a template that comes > > with web2py (which means the template code is also GPL), does the > > template, which is covered by GPL, also prevent you from distributing > > templates as binary-only. > > > I don't mean HTML etc. Those are static files anyway. I mean the .py > > templates like the db.py template that is included in the welcome app. > > When you start off, 100% of your app is comprised of GPL'd code from > > the welcome app. > > > -- > > Branko Vukelić > > > bg.bra...@gmail.com > > stu...@brankovukelic.com > > > Check out my blog:http://www.brankovukelic.com/ > > Check out my portfolio:http://www.flickr.com/photos/foxbunny/ > > Registered Linux user #438078 (http://counter.li.org/) > > I hang out on identi.ca:http://identi.ca/foxbunny > > > Gimp Brushmakers Guildhttp://bit.ly/gbg-group
