Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08816EA07 for ; Mon, 21 Jan 2013 16:52:37 +0000 (UTC) Received: (qmail 22624 invoked by uid 500); 21 Jan 2013 16:52:36 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 22551 invoked by uid 500); 21 Jan 2013 16:52:36 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 22542 invoked by uid 99); 21 Jan 2013 16:52:36 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jan 2013 16:52:36 +0000 Received: from localhost (HELO mail-oa0-f53.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jan 2013 16:52:36 +0000 Received: by mail-oa0-f53.google.com with SMTP id j6so6300131oag.12 for ; Mon, 21 Jan 2013 08:52:35 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.60.7.199 with SMTP id l7mr14093000oea.136.1358787155387; Mon, 21 Jan 2013 08:52:35 -0800 (PST) Received: by 10.182.225.66 with HTTP; Mon, 21 Jan 2013 08:52:35 -0800 (PST) In-Reply-To: References: <50EF64C6.1050706@apache.org> <50F5C56E.4030805@apache.org> <50FAFA4D.2060307@apache.org> <50FC07F5.7060203@apache.org> <50FCA482.7080108@gmail.com> Date: Mon, 21 Jan 2013 11:52:35 -0500 Message-ID: Subject: Re: Symphony code in AOO 4.0 From: Rob Weir To: dev@openoffice.apache.org Content-Type: text/plain; charset=UTF-8 On Sun, Jan 20, 2013 at 9:19 PM, Rob Weir wrote: > On Sun, Jan 20, 2013 at 9:14 PM, F C. Costero wrote: >> On 1/20/2013 2:48 PM, Rob Weir wrote: >>> >>> On Sun, Jan 20, 2013 at 1:30 PM, Kay Schenk wrote: >>>> >>>> On Sun, Jan 20, 2013 at 7:15 AM, Andrea >>>> Pescettiwrote: >>>> >>>>> Rob Weir wrote: >>>>> >>>>>> OK. Here is a draft: >>>>>> https://blogs.apache.org/**preview/OOo/?previewEntry=** >>>>>> >>>>>> merging_symphony_allegro_non_**troppo >>>>>> Note that there are some suggested topics at the end, where I need >>>>>> detail. I welcome help from anyone who can help fill in the details. >>>>>> >>>>> >>>> Highly interesting *and* entertaining! >>>> >>>> >>>> >>>>> >>>>> Thanks! In the draft you ask for the screenshots showing enhancements: I >>>>> think it's the same page by Shenfeng Liu we've already shared here, >>>>> http://wiki.openoffice.org/**wiki/Documentation/Fidelity_** >>>>> >>>>> Improvement_Since_AOO341 >>>>> (they are not all from Symphony, but the majority are, including all >>>>> "OOXML Support" enhancements). >>>>> >>>>> Can the long bullet list be prioritized in some ways? Not all the list, >>>>> but at least making sure that the first few items are the most relevant. >>>>> I >>>>> would put issues containing "crash" first, but maybe someone who has >>>>> better >>>>> knowledge of the impact can suggest other issues worth to be listed at >>>>> the >>>>> top. >>>>> >>>> >>>> Yes, it would be good to give category headings for this list. I >>>> understand the jsutification for length -- what, really, is being >>>> incorporated from Symphony, but if length is an issue, maybe drop some. >>>> >>> >>> OK. Look now. I re-ordered the bugs a little to put some of the more >>> interesting ones first. I also added a header. Since an article is >>> coming out in a couple of days on Lwn.net claiming that we have done >>> absolutely nothing with the Symphony code, there is value in giving >>> the full list. We should leave no doubt that work in this area has >>> been ongoing. While some were working on the more publicly visible >>> AOO 3.4.1 work on a branch, a lot was happening in the trunk. We >>> haven't really spoken about that work before. Now is a good time. >>> >>>> >>>>> The title "Allegro non troppo" is a clever pun! The expression is >>>>> clearly >>>>> recognizable as international musical jargon and a pun on Symphony, but >>>>> the >>>>> usual meaning of "allegro" in Italian is "happy" which adds an >>>>> interesting >>>>> twist... >>>>> >>>>> Minor typo just before the bullet list: "the fix fro Symphony". >>>>> >>>>> Regards, >>>>> Andrea. >>>>> >>>> >>>> Finally, although I realize that most blog readers will be non-technical, >>>> I >>>> think it might be valuable to at least broach the subject of SGA vs >>>> licensing here in some way. Even if a few sentences could be added >>>> under: >>>> >>>> "IBM Lotus Symphony is a commercial derivative of OpenOffice which IBM >>>> enhanced for >>>> their >>>> customer and corporate use. Last May IBM contributed the source code >>>> for >>>> Symphony to Apache, via a Software Grant Agreement (SGA). " >>>> >>>> to address this it would be great. What does it mean to contribute code >>>> and >>>> "use" it piecemeal vs re-licensing it , for example. >>>> >>> >>> I added some additional text to explain what an SGA is. I also >>> corrected the typo that Andrea pointed out and add the link to the >>> "before& after" screen shots that he posted. >>> >>> >>> >>> So I'm happy to make further changes or content additions. But I'm >>> generally happy with. >>> >>> -Rob >>> >>> >>>> This is a great blog! I'm sure our users and general audience will >>>> appreciate it! >>>> >>>> -- >>>> >>>> ---------------------------------------------------------------------------------------- >>>> MzK >>>> >>>> "No act of kindness, no matter how small, is ever wasted." >>>> >>>> -- >>>> Aesop >> >> Rob, >> Thanks for working on this, it is very well done. I noticed a couple of >> typos in the third movement: > > Great. Thanks for the proof-read. I made those changes. > And the blog post is now live: https://blogs.apache.org/OOo/entry/merging_lotus_symphony_allegro_moderato Thanks, all, for the review and suggestions. -Rob > -Rob > >> "A a modeless property picker" needs only one "A". >> "So we're considering at several" drop the "at" >> "and we're bring those into OpenOffice. " should be "and we're bringing >> those into OpenOffice". >> I'm also not sure "modeless" will be meaningful to regular users. Would >> "continuously available" be better? >> Regards, >> Francis