jan i wrote:
> On 13 February 2015 at 08:58, jonathon <toki.kant...@gmail.com> wrote:
> 
> All:
> 
> My impression was that when Apache Foundation accepted OOo, they also
> accepted the OOo4Kids and OOoLight projects.
> 
> https://wiki.openoffice.org/wiki/Education_Project/OOo4Kids says that
> the OOo4Kids has been depreciated, and points to
> http://educoo.org/OOo4Kids.php as the main page.
> 
> As far as OOoLight goes, the only hit on the Apache Wiki is
> 
> https://wiki.openoffice.org/wiki/%D0%9E%D0%9E%D0%BE_%D0%9F%D0%BE%D0%BB%D0%B5%D0%B7%D0%BD%D0%BE%D1%81%D1%82%D0%B8:_%D1%83%D1%81%D0%BA%D0%BE%D1%80%D0%B5%D0%BD%D0%B8%D0%B5_%D1%80%D0%B0%D0%B1%D0%BE%D1%82%D1%8B_%D0%9E%D0%9E%D0%BE
> ,
> which is a description of things that can be removed from OOo, to
> improve performance/reduce the CPU/memory requirements.
> 
> OOo4Kids 1.3 can be downloaded from
> http://educoo.org/TelechargerOOo4Kids.php, and is licenced under the
> LGPL 3.0.
> 
> http://sourceforge.net/projects/educooo/ lists December 2013 as the date
> of OOo4Kids 1.3.1, as the most recent release.
> 
> OOoLight 1.1 can be downloaded from
> http://educoo.org/TelechargerOOoLight.php.
> 
> OOoLight_1.1_120609_LinuxIntel_install_rpm.tar.gz is listed at
> http://sourceforge.net/projects/educooo/files/OOoLight/Linux/1.1/en-US/
> with a modification date of 2013-12-30. The sourceforge site implies
> that it is LGPL 3.0.
> 
> Were these projects (OOo4Kids, OooLight) included, when OOo became an
> Apache project?
> If so, have they since been abandoned?
> 
> 
>> I cannot see them included in the original IP clearance, so my best guess
>> is that they were forgotten, but others might know more.
> 
>> rgds
>> jan i
> 
> 
> jonathon

These were independent projects forked from OOo. They were not part of
the original IP clearance, because Sun/Oracle never owned them.

Dave


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to