From ooo-dev-return-28636-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Thu Nov 1 21:08:53 2012 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 B060BD0DA for ; Thu, 1 Nov 2012 21:08:53 +0000 (UTC) Received: (qmail 39362 invoked by uid 500); 1 Nov 2012 21:08:53 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 39200 invoked by uid 500); 1 Nov 2012 21:08:53 -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 39192 invoked by uid 99); 1 Nov 2012 21:08:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 21:08:53 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jogischmidt@gmail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 21:08:45 +0000 Received: by mail-bk0-f47.google.com with SMTP id jk7so1102269bkc.6 for ; Thu, 01 Nov 2012 14:08:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=IGH8Sd5AoieOjTU9DEALaxwrfgS0iEH9hshPCDSkb7Q=; b=vL+9C1L4fB7SffPuKC9AXNcp+RLN+O+0LaWk4ZLZhf+g6x4iqCyqi7ItrtAt4QxVEI dCNGPGpPsYcVz/PG4/cNoaRopa72klWZ2aoi4ATIYlCjEEERf/rNSVBRU+IZMA7ZIgu/ SLpgPiwnczV6nTcZBn4AlDW5Lwz02t+vyc2tPXZRbxkQYVWNQF4b2ZiO2jJDyDhlpTEI 86AZ2PtT87CV3BJh0mDNeGusqh8jZ/nWhi/A2o/L6EcaOYevBG7uW+OontEtb3d7ez87 PS998mFeJKWIJeXSEybc0486mdvVooU4SdCVDHl8X3Vu0/rXr1paOHpjh8cm5IU7/E7F QDNQ== Received: by 10.204.148.202 with SMTP id q10mr12099119bkv.55.1351804104010; Thu, 01 Nov 2012 14:08:24 -0700 (PDT) Received: from [192.168.178.26] (e177101175.adsl.alicedsl.de. [85.177.101.175]) by mx.google.com with ESMTPS id 1sm5694794bks.3.2012.11.01.14.08.22 (version=SSLv3 cipher=OTHER); Thu, 01 Nov 2012 14:08:23 -0700 (PDT) Message-ID: <5092E4C5.2050902@gmail.com> Date: Thu, 01 Nov 2012 22:08:21 +0100 From: =?ISO-8859-1?Q?J=FCrgen_Schmidt?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: AOO.Next IBM Priorities References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 11/1/12 9:53 PM, jan iversen wrote: > Thanks for the note, however knowing IBM I had hoped that one of the > official goals was to help the development part of the community to get > stabilized. > > I acknowledge that it is important for IBM to get an output of invested > energy/time/money, but I think IBM would benefit not only from features but > also from the soft points of helping the community. > > that being said in response to your IBM HAT, but I do feel that you and > other IBM Fellows still do a great job in getting the community to prosper. I hope so and the priorities were focused on the product only and not on the community aspects that are of course very important for us as well. Juergen > > Jan. > > On 1 November 2012 17:45, wrote: > >> A quick note, wearing my "IBM hat". >> >> We (IBM) have consulted with customers, internal users, other IBM product >> teams, on what our (IBM's) development priorities should be for the next >> AOO release. Obviously, we're not the only ones with priorities or >> interests or opinions. We don't make AOO decisions by ourselves. But we >> want to be transparent about what our own priorities are, for our >> employees participating in the AOO community, and what they will be >> focusing on. As we did with AOO 3.4.0 and 3.4.1, we'll be putting the >> details onto the wiki over the next couple of weeks. You'll hear more at >> ApacheCon, but I wanted you to hear it hear first. >> >> Our top priorities: >> >> -- Improve the install and deployment experience, especially by supporting >> digital signatures on installs, and introducing a new incremental update >> feature, so users are not required to download and install a full image >> for just a minor update. >> >> -- A major UI enhancement, a sidebar framework for the editors, ported >> over from Symphony, and including an API. If you recall, Symphony won >> quite a lot of praise for its UI, and much of this was due to the sidebar >> panel. I think we can make a good argument that this approach, say >> compared to the MS Office "ribbon" is a better use of screen real-estate, >> especially as we see more frequent use of wide screen displays. >> >> -- Improved Table of Contents in Writer >> >> -- Improved system integration on Windows and MacOS, including possible >> adoption of "gestures". >> >> -- IAccessible2 bridge, ported over from Symphony, to improve >> accessibility. This is a major effort, but very important. >> >> -- Closer integration of clipart and template libraries with user >> experience. >> >> -- Update branding and visual styling, contemporary and compelling, fresh >> and relevant. >> >> -- Social integration, allow our users to quickly and easily share their >> thoughts in a way that compliment their commercial social behavior. >> Explore the integration of consumer service-specific capabilities as well >> as generic Share... actions. >> >> -- And many other smaller items >> >> Obviously the release date for this cannot be pinned down so early, and >> releasing is PMC decision, not an IBM one. But we think that this work >> could be completed and tested for a release in the March/April 2013 >> time-frame. And the scope of the release might be significant enough to >> warrant a "4.0" designation. >> >> In any case, we'll soon set up a page on the wiki to collect these items. >> As always, I invite you to add your own priorities to the wiki, things >> that you would like to work on. This could be a new feature. Or, if one >> of the above items sound interesting to you, we always welcome help >> designing and implementing these features. >> >> Regards, >> >> -Rob >> >> >> >> >