Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On Tue, Jun 14, 2011 at 1:04 PM, Ian Lynch <ianrlynch@gmail.com> wrote:
On 14 June 2011 11:38, Keith Curtis <keithcu@gmail.com> wrote:

On Tue, Jun 14, 2011 at 2:43 AM, Christoph Jopp <jopp@gmx.de> wrote:

Not automatically. Someone might want the more restrictive license
because he wants to mix it with other code with a license incompatible
to the least restrictive license you offer.

Okay, good point.

Anyway, I'm just thinking of a way for Apache people to contribute to now.
It seems there is excitement over there, but they don't have something that
builds, etc. It seems like perhaps half will be blocked for some time.

You could let some people work here and create a tree with a queue of
changes made by Apache contributors that Apache could adopt when they are
ready. That could be a useful gift and a way for everyone to work now.


I'd like to see the desktop effort here at LibO and the developers at Apache
start on a new web based OOo even if that meant starting from scratch and
writing it in Javascript.

It's already been done:

http://www.webodf.org/

-Todd

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.