Oh?  We have to commit this to SVN?  I wasn't sure how the website
template stuff was stored - either on a server directly or actually
checked in to SVN.

If we have to commit it to SVN, I guess we'll have to write our own...

On Sun, Jan 11, 2009 at 2:49 PM, Emmanuel Lecharny <[email protected]> wrote:
> Niklas Gustavsson wrote:
>>
>> On Sun, Jan 4, 2009 at 9:11 PM, Niklas Gustavsson <[email protected]>
>> wrote:
>>
>>>
>>> On Thu, Jan 1, 2009 at 11:13 PM, Les Hazlewood <[email protected]>
>>> wrote:
>>>
>>>>>
>>>>> Having it zipped up would be good enough, just email it to me offlist.
>>>>> I guess since the site is not really used, I can use it freely for a
>>>>> few days while I get the template up and running?
>>>>>
>>>>
>>>> Of course - please feel free.  I'll zip it up and send it over asap.
>>>>
>>>
>>> Looking closer at this, if I'm correct, the current jsecurity.org uses
>>> the default Drupal skin, which seems to be GPL2 (at least the Drupal
>>> API is, I fail to find any license for the theme). I'm not sure what
>>> consequences re-using this theme would have for the JSecurity site at
>>> Apache. For example, it's common to redistribute the site with a
>>> release, I suspect that might be impossible.
>>>
>>> Anyone got a clue? Does anyone know what license really apply to the
>>> theme?
>>>
>>
>> Any takers? I would like to move forward with this but would like to
>> have a clear understanding of if the template would be allowed to be
>> used :-)
>>
>
> Looking at some Legal mail :
>
> "On Nov 25, 2008, at 2:24 PM, Craig L Russell wrote:
>
>> ...
>> At issue is whether artifacts with unacceptable licenses can appear in
>> Apache public svn repositories.
>
> They can't.  Only open source is allowed in Apache's public svn.
>
> ....Roy
> "
>
> It seems that if we are using a Drupal Theme, as it is distributed under a
> GPL license, then we can't use it, as we will have to inject this theme into
> svn.
>
> wdyt ?
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>

Reply via email to