Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 36103 invoked from network); 3 Oct 2006 11:38:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Oct 2006 11:38:43 -0000 Received: (qmail 96577 invoked by uid 500); 3 Oct 2006 11:38:41 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 96509 invoked by uid 500); 3 Oct 2006 11:38:41 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 96498 invoked by uid 99); 3 Oct 2006 11:38:41 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Oct 2006 04:38:41 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=hepabolu@gmail.com; domainkeys=good X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=DNS_FROM_RFC_ABUSE,RCVD_IN_BL_SPAMCOP_NET DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [72.14.214.239] ([72.14.214.239:42724] helo=hu-out-0506.google.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id CF/7B-29668-28B42254 for ; Tue, 03 Oct 2006 04:37:40 -0700 Received: by hu-out-0506.google.com with SMTP id 20so1236155huc for ; Tue, 03 Oct 2006 04:35:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=FGKgrrC8ho2C6Zc4GFZ9lZwAHWXoVQsvVHhcOR/PdAYOlF5t58fi6mXuZB27VlJRJEWpD99cQbhxB4AxlE2tJtk1udRTZXJpRE2G2QtZmsAHdIqeHtxi2bt8OWv+s/erviJtmAenpkKHHFAqETjfw7Rsuo6lhgGG+6q8yyfT2IQ= Received: by 10.66.249.11 with SMTP id w11mr3650708ugh; Tue, 03 Oct 2006 04:35:10 -0700 (PDT) Received: from ?192.168.1.125? ( [82.215.11.44]) by mx.gmail.com with ESMTP id j33sm5348892ugc.2006.10.03.04.35.09; Tue, 03 Oct 2006 04:35:09 -0700 (PDT) Message-ID: <45224AEF.7070807@gmail.com> Date: Tue, 03 Oct 2006 13:35:11 +0200 From: hepabolu Reply-To: hepabolu@gmail.com User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [RT] User poll to find unused components References: <6DD7194CCE91BB44A41318EA7D06151070E99D@pegasus.olympus.borgus.nl> <452248FD.1020908@apache.org> In-Reply-To: <452248FD.1020908@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Sylvain Wallez said the following on 3/10/06 13:26: > Geert Josten wrote: >>> +1 for the blocks, because it simplifies the stay/leave >>> selection. In a >>> later stage the poll can be repeated per block for the >>> individual components. >>> >>> I also suggest to ask for a TOP 5 and create a TOP 10 from >>> that to cater to a larger population. >>> >> How about letting users classifying blocks as used: >> a) always, >> b) often (most of the time), >> c) rarely (only once or twice)? >> >> (and asking them how many webapps they have build using Cocoon) >> >> Sounds more informative to me than a top 5.. >> > > Sure. Defining the top 10 or top 5 is then the result of aggregating and > compiling all information provided by users. First off: I definitely agree that more information gives a more informative choice. However, it's no problem to ask a lot of information of the users, but we have to make the process quick and easy. Defining a top 5 of your favorite blocks is a quick response to a mail. Walking through a list of predefined blocks and adding a, b, or c takes more time and I do hope that people will take the time to walk through them. If we want the abc options, we need to carefully construct the poll to avoid putting off people. Bye, Helma