Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C4D3F9260 for ; Sat, 31 Mar 2012 02:18:31 +0000 (UTC) Received: (qmail 58930 invoked by uid 500); 31 Mar 2012 02:18:30 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 58862 invoked by uid 500); 31 Mar 2012 02:18:30 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 58853 invoked by uid 99); 31 Mar 2012 02:18:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 Mar 2012 02:18:30 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of helenyuehy@gmail.com designates 209.85.210.48 as permitted sender) Received: from [209.85.210.48] (HELO mail-pz0-f48.google.com) (209.85.210.48) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 Mar 2012 02:18:24 +0000 Received: by dadp12 with SMTP id p12so212814dad.7 for ; Fri, 30 Mar 2012 19:18:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/Bs/SHye8HxgqPHn6Ioo+NSg6BEs2vdE2g2aE7yWatA=; b=n0hOJN4o8Sat87grGjSrw4vxcsUj2uJivftZylzVxdPQvAly09FbtcVLAbkTqPRlSO fP6lDFZF1Yw9zbn3pimyvEjCVMkv+vzbF69LktVSwKkd4+3d/0MJx/4MozP6jcnBmtQe e8FWMe8dlN/sqEf1NJofUAiB62TO4y+tCVuzUeswqSrY9cGRqPpAFs7RWD6GkROhFc5Q 2YjenLoc3eX2Ej2I++hQKOXX/RZq+irgDxP+LCsR4yggwwUuUZ5NMSimIxTbJ3E3w+zs BKL00sKC5/1M9PndsTeUgNAvRlgoa0PbF/lor0MAnnIL6FRdy3m9IJprqzN10tgtMumO Rvhg== MIME-Version: 1.0 Received: by 10.68.230.104 with SMTP id sx8mr2143414pbc.16.1333160282992; Fri, 30 Mar 2012 19:18:02 -0700 (PDT) Received: by 10.68.66.131 with HTTP; Fri, 30 Mar 2012 19:18:02 -0700 (PDT) In-Reply-To: References: Date: Sat, 31 Mar 2012 10:18:02 +0800 Message-ID: Subject: Re: And idea for OOo From: Yue Helen To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=047d7b339e6718b0af04bc809136 --047d7b339e6718b0af04bc809136 Content-Type: text/plain; charset=ISO-8859-1 Besides the two solutions to use AOO together with storage, Cody has one more great idea which is to edit the document directly in the storage...I think he is talking about a web-based editor solution based on OO. Have we had such discussion before? Helen 2012/3/30 Rob Weir > On Fri, Mar 30, 2012 at 9:01 AM, Cody Miller >wrote: > > > Hello, > > > > I have a really great idea for the OpenOffice Community. Almost every > > Office Suite has its own storage house (cloud drive) nowadays, and I was > > thinking that OOo should have its own too. But I was also thinking that > not > > only could you retrieve your documents, but even edit them while your in > > the storage as well. That way, you could take and edit your documents > > wherever you are. This would be a huge step for the OOo community, and it > > may increase our popularity if accomplished. And if the popularity > > increase, that will mean more developers where be really to help > worldwide. > > Please take my idea into consideration. > > > > > Two things to consider: > > 1) Enabling OpenOffice for use with existing cloud storage > > 2) Enabling an OpenOffice cloud > > > #1 is easy, and in fact is already done, via extensions. For example, this > extension allows the user to save/retrieve documents to a variety of cloud > storage providers, including Amazon, DropBox, Google, SkyDrive, etc: > > http://extensions.services.openoffice.org/en/project/MultiCloud > > #2 is harder. The main issue is that open source projects are run by > volunteers. What we can offer is our time, our skills, our labor. But > having our own cloud requires more than that. It requires storage, > bandwidth, servers,and additional security and privacy concerns, including > different laws in different countries, needing to respond to law > enforcement authorities when they demand access, etc. This all takes us > further away from our core mission, which is to provide free software to > the public. > > So I think we should focus on #1, enabling OpenOffice to work with cloud > providers. But we can then rely on 3rd parties -- the broader ecosystem -- > to develop and maintain the cloud storage options. > > -Rob > > > > > > > Thanks, > > > > Cmiller > --047d7b339e6718b0af04bc809136--