Re: [xwiki-devs] Official application license ambiguity

Hi, here's my take on this topic: - The code we write, be it in the core or in XE, should be licensed under the LGPL license (better suited for code than a CC license, what's the point of having the whole blog application licensed as CC when obviously it's not content?)

- We should leave the choice of the content license to the wiki owner (what's the point of imposing a default one to him / her)

- The "default" case for copyright licenses is already defined by the law of pretty much every country, thus the default we should choose should be not to display anything by default (which is also another reason why we'd want to make the code in the XE XAR licensed under the LGPL)

- Ideally we'd add a "license" field somewhere in the admin interface that, when filled, would be displayed in the footer

WDYT? Guillaume On Wed, Feb 3, 2010 at 1:55 AM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: > On 02/03/2010 01:01 AM, Caleb James DeLisle wrote: >> Gnu lists CC-BY and CC-BY-SA as GPL incompatible >> http://www.gnu.org/licenses/license-list.html#OtherLicenses >> >> In my opinion, licensing something under multiple licenses which are >> as incompatible is not the best decision, the obvious problem is it is >> not allowable to distribute the WAR with the XAR preinstalled. >> >> There may be a problem with the viral nature of LGPL given that the core >> (templates) make reference to XE (download the default pages here) and XE >> obviously makes a lot of calls to core functions. Since each references > the other >> it might be hard to claim that XE is using the core is as a library. > > I don't agree that this is a valid hard link which would cause the LGPL > core to become viral to the wiki pages. > > These are wiki pages. > This is data. > This data is sometimes executable. > This data sometime results in platform methods being called. > A shell script results in bash methods being called. > Must all shell scripts be GPL because they end up executing bash code? > This data gets converted from wiki source to HTML code through the core. > A C program gets converted from C source to executable code through GCC. > Must all C programs be GPL because they pass through GCC? > > This is obviously library usage, since it's code that calls API methods > through a proxy. > >> I think that we need to define what activity we want to allow and what we > want >> to prevent. >> >> >> Caleb >> >> >> Sergiu Dumitriu wrote: >>> On 02/02/2010 06:27 PM, Vincent Massol wrote: >>>> On Feb 1, 2010, at 10:46 AM, Sergiu Dumitriu wrote: >>>> >>>>> Hi devs, >>>>> >>>>> I just noticed that although we've been saying that "This wiki is >>>>> licensed under a Creative Commons 2.0 license", all the source files > for >>>>> the wiki pages are actually under the LGPL, which contradicts the > wiki. >>>> Actually our pages are under no license right now (There's no license > in the XML files and there should be one). >>> >>> Kind of, the license is in the pom. Although it does not appear in each >>> file, doesn't the fact that it's a file belonging to a LGPL project >>> almost make it LGPL too?