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 938CAD6C1 for ; Fri, 24 Aug 2012 14:58:38 +0000 (UTC) Received: (qmail 13987 invoked by uid 500); 24 Aug 2012 14:58:38 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 13784 invoked by uid 500); 24 Aug 2012 14:58:38 -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 13775 invoked by uid 99); 24 Aug 2012 14:58:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Aug 2012 14:58:38 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=HK_RANDOM_ENVFROM,HK_RANDOM_FROM,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [193.95.142.37] (HELO mail05.mail.esat.net) (193.95.142.37) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Aug 2012 14:58:30 +0000 Received: from (100AkerWood) [109.78.216.195] by mail05.mail.esat.net with smtp id 1T4vKr-00011f-82; Fri, 24 Aug 2012 15:58:09 +0100 Date: Fri, 24 Aug 2012 15:58:08 +0100 From: Rory O'Farrell To: ooo-dev@incubator.apache.org Subject: Re: [Discuss] Triage of Brainstorming Message-Id: <20120824155808.80c94d0610a99d113228cd91@iol.ie> In-Reply-To: References: <20120824133100.34f5bb02264d84750e86ffb4@iol.ie> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.6; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 24 Aug 2012 07:49:02 -0700 Dave Fisher wrote: > > On Aug 24, 2012, at 7:39 AM, Rob Weir wrote: > > > On Fri, Aug 24, 2012 at 8:31 AM, Rory O'Farrell wrote: > >> > >> In due course, when we've all had a little rest after the release of AOO 3.4.1, it will be necessary to do some triage work on the Brainstorming, so that the most requested changes make their way onto the planning table for AOO 4.0. Many of the suggestions can be amalgamated, for example improved doc/docx, xls/xlsx etc support; within reason these can all be amalgamated into "improved support for MS Office formats, current and legacy". Other suggestions are readily achievable by existing faciites in OpenOffice; such requests might indicate need for better education of Users or more accessible documentation/tutorials. > >> > >> Supposing that the Brainstorm is continued beyond AOO 4.0, should we prune it in the light of whatever choices are made for AOO 4.0; should we also register comments against some of the already readily achievable functions, to give pointers to (say) the Forums and/or tutorials which indicate how to do that function? > >> > >> Could we have some discussion on how best to analyse and progress the current nearly 300 suggestions [as of date of posting) > >> > > > > We're getting a lot more feedback than I expected: 305 people have > > submitted 284 ideas and cast 3,106 votes. > > > > IMHO, this is wonderful. In some sense the voting process itself > > helps triage, especially if project members are also submitting ideas > > and voting, which I hope we all are. > > Not all of us have the time. > > > > I like your idea of combining closely related or duplicate ideas. > > Maybe in the end we could promote a "top 10" list of ideas, in a blog > > post, and collect also commentary from project members related to > > these top 10 ideas. > > I think that coming back to ooo-dev with "Top" ideas is appropriate. One of my concerns was that the multiple requests for similar features/support might cause these to drop off the radar as their voting would be too fragmented. Hence my suggestion that we consider amalgamation of closely related suggestions; the coding for one specific suggestion might easily expand to cover the coding necessary for a particular range. Hence the need for some form of triage to make best use of coding resources. > > > > > Another approach would be to take the top ideas and use them as > > additional input to a survey design that Kevin and Graham were looking > > into. We could take the top 10 (or 20) ideas and in the survey ask > > users to rate them. > > FYI - The ASF Board has created a new TLP called Apache Steve which will expose the Voting mechanism used by the ASF membership. > > Regards, > Dave > > > > > That help us get around the natural bias of Google Moderator, which is > > that ideas submitted first will get more votes because they've had > > more time to be voted on. > > > > Regards, > > > > -Rob > > > >> -- > >> Rory O'Farrell > > -- Rory O'Farrell