The point is that we might have to keep several modules (e.g. modified
calendar source) outside of Apache svn. Apache is very peculiar about
code authorship.This generally does not prevent us from integrating
with that code or shipping that code as a part of our binary release.

Note, the problem like this does not prevent us entering incubation.
Though we have to clean the "foreign" code before leaving incubation.

Standard disclaimer: I'm not a lawyer. :-)

2009/10/23 Sebastian Wagner <[email protected]>:
> Okay well we have to see what Apache Foundations answer is in general.
> For Calendar Integration we have to edit the Source Code of the Calendar of
> course. After we have copied the source code into our repo.
> I did not fully understood the distinction you make between the cut-paste
> from SVN and the compilation.
>
>
>
> 2009/10/23 Alexei Fedotov <[email protected]>
>>
>> Sebastian,
>> I'm quite sure that there is a certain level of compatibility between
>> EPL and APL.
>>
>> => I have participated in Eclipse plug-in development based on Apache
>> Harmony bytecode verifier [1].
>> >= Apache Harmony uses Eclipse compiler.
>>
>> I believe this was legally ok, becase both projects involve IBM and
>> Intel who have good lawyers.
>>
>> The point is that we have to re-use modules (compiling source modules
>> ourselves by means of our build file is ok), without cut-pasting code
>> from OpenLaszlo calendar repository to our repository.
>>
>> [1] http://wiki.apache.org/harmony/Verifier_Extension
>>
>>
>> 2009/10/23 Sebastian Wagner <[email protected]>:
>> > hi,
>> >
>> > one of the main reasons for EPL is that its compatible to CPL.
>> > That means we can re-use the OpenLaszlo Calendar and replace ours with
>> > it.
>> >
>> > http://labs.openlaszlo.org/trunk-nightly/demos/calendar/calendar.lzx?lzr=swf8
>> >
>> > I think that would be also a plus for us if we can use this shinning
>> > application.
>> > And its not that big trouble to include it and replace our calendar with
>> > it
>> > but it means that we have to apply to a CPL compatible license. And APL
>> > unfortunately is not compatible.
>> >
>> > sebastian
>> >
>> > 2009/10/23 Alexei Fedotov <[email protected]>
>> >>
>> >> Hello,
>> >>
>> >> EPL is very close to Apache license. Why not to go a bit further an
>> >> apply for Apache incubation [1]?
>> >>
>> >> 1. This would give us a popular brand, which would make distributing
>> >> openmeetings and fostering our community of developers  a bit easier.
>> >>
>> >> 2. This would ease next yera GSoC participation much.
>> >>
>> >> 3. Eclipse community is quite centered on IBM business, while Apache
>> >> is more balanced (getting money from several moneybags).
>> >>
>> >> 4. GSoC admins in Apache might recall me since I wrote more than
>> >> several letters during GSoC, so we have a chance to get a champion.
>> >>
>> >> 5. For Sebastian Apache participation also would mean submitting the
>> >> proposal [1] and writing monthly reports to Apache board.
>> >>
>> >> BTW, Apache has a European svn mirror.
>> >>
>> >> [1] http://wiki.apache.org/incubator/OpenmeetingsProposal
>> >> Sorry for not listing all names, openmeetings committers are welcome
>> >> to edit and add their names - the page is free to modify.
>> >>
>> >>
>> >> On Mon, Oct 12, 2009 at 2:21 PM, Sebastian Wagner
>> >> <[email protected]>
>> >> wrote:
>> >> > hi,
>> >> >
>> >> > to bring OpenMeetings in line with the License of OpenLaszlo we will
>> >> > switch
>> >> > from the LGPL to the EPL with the next release.
>> >> >
>> >> > What does that mean for you?
>> >> > - Nothing actually.
>> >> >
>> >> > Eclipse Public License is even a bit more liberal then (L)GPL
>> >> >
>> >> > Quote from wikkipedia
>> >> >
>> >> > The Eclipse Public License is designed to be a business friendly free
>> >> > software license, and features weaker copyleft provisions than
>> >> > contemporary
>> >> > licenses such as the GNU General Public License (GPL). The receiver
>> >> > of
>> >> > EPL-licensed programs can use, modify, copy and distribute the work
>> >> > and
>> >> > modified versions, in some cases being obligated to release their own
>> >> > changes.[2]
>> >> >
>> >> > The EPL is approved by the Open Source Initiative (OSI)[3] and the
>> >> > Free
>> >> > Software Foundation (FSF)[4].
>> >> >
>> >> > see also:
>> >> >
>> >> >
>> >> > http://wagner-sebastian.com/wordpress/2009/10/12/openmeetings-becomes-even-more-liberal-with-epl-license/
>> >> >
>> >> > sebastian
>> >> >
>> >> >
>> >> > --
>> >> > Sebastian Wagner
>> >> > http://www.webbase-design.de
>> >> > http://openmeetings.googlecode.com
>> >> > http://www.laszlo-forum.de
>> >> > [email protected]
>> >> >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> With best regards / с наилучшими пожеланиями,
>> >> Alexei Fedotov / Алексей Федотов,
>> >> http://www.telecom-express.ru/
>> >> http://harmony.apache.org/
>> >> http://www.expressaas.com/
>> >> http://openmeetings.googlecode.com/
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Sebastian Wagner
>> > http://www.webbase-design.de
>> > http://openmeetings.googlecode.com
>> > http://www.laszlo-forum.de
>> > [email protected]
>> >
>> > >
>> >
>>
>>
>>
>> --
>> With best regards / с наилучшими пожеланиями,
>> Alexei Fedotov / Алексей Федотов,
>> http://www.telecom-express.ru/
>> http://harmony.apache.org/
>> http://www.expressaas.com/
>> http://openmeetings.googlecode.com/
>>
>>
>
>
>
> --
> Sebastian Wagner
> http://www.webbase-design.de
> http://openmeetings.googlecode.com
> http://www.laszlo-forum.de
> [email protected]
>
> >
>



-- 
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://www.telecom-express.ru/
http://harmony.apache.org/
http://www.expressaas.com/
http://openmeetings.googlecode.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenMeetings developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/openmeetings-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to