Re: [PHPiCalendar-DEV] Fwd: Licensing Issues

[Wesley M. <we...@we...>]

I'm fine with any of the "you can do pretty much whatever you want"  
licenses.
--
Wesley Miaw
we...@we...

On Sep 10, 2009, at 11:29 AM, Chad Little wrote:

> BTW this was me preferring to just move to the Apache License.
>
> -C
>
> On Sep 10, 2009, at 8:29 AM, Chad Little wrote:
>
>> Yep,
>>
>> http://www.apache.org/licenses/LICENSE-2.0
>>
>>
>>
>> On Sep 10, 2009, at 8:00 AM, Rich Bowen wrote:
>>
>>> Or, you could go all the way to ASL2.0 and make even more people  
>>> happy.
>>>
>>> On Sep 10, 2009, at 10:58 AM, Jim Hu wrote:
>>>
>>>> Does anyone have a problem with making a change from GPL to LGPL?
>>>>
>>>> Begin forwarded message:
>>>>
>>>>> From: Steven Oxley <ste...@gm...>
>>>>> Date: September 10, 2009 9:31:48 AM CDT
>>>>> To: Jim Hu <ji...@ta...>
>>>>> Subject: Re: Licensing Issues
>>>>>
>>>>> I believe that is all that would be required, but everyone who  
>>>>> has contributed code to the project has a copyright to their  
>>>>> code and in order to release their code under a different  
>>>>> license, their consent would be required.  (At least that's what  
>>>>> I have picked up from other open source projects I've been  
>>>>> "around").
>>>>>
>>>>> Steven Oxley
>>>>>
>>>>> On Thu, Sep 10, 2009 at 10:27 AM, Jim Hu <ji...@ta...> wrote:
>>>>> Hi Steven,
>>>>>
>>>>> That would be OK with me.  Not being a licensing expert, do I  
>>>>> just change the license file?
>>>>>
>>>>> Jim
>>>>>
>>>>> On Sep 10, 2009, at 9:01 AM, Steven Oxley wrote:
>>>>>
>>>>>> Hi guys,
>>>>>>
>>>>>> I was looking at the PHP iCalendar package you have on  
>>>>>> sourceforge and I was thinking that I might like to use some of  
>>>>>> the iCalendar parsing code in a library of my own.  The problem  
>>>>>> is that your license is GPL v2 and I will be using this  
>>>>>> "library" that I want to create in a software package that I  
>>>>>> cannot release under GPL v2.  I was wondering if it might be  
>>>>>> possible to release the parsing code under LGPL so that I can  
>>>>>> modify it and use it in my own code without having to release  
>>>>>> my entire software package under GPL v2.
>>>>>>
>>>>>> Thanks for considering it,
>>>>>> Steven Oxley