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 25307DB93 for ; Thu, 25 Oct 2012 11:32:35 +0000 (UTC) Received: (qmail 15226 invoked by uid 500); 25 Oct 2012 11:32:34 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 15017 invoked by uid 500); 25 Oct 2012 11:32:34 -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 15003 invoked by uid 99); 25 Oct 2012 11:32:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2012 11:32:33 +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 (nike.apache.org: domain of binoabn@gmail.com designates 209.85.210.175 as permitted sender) Received: from [209.85.210.175] (HELO mail-ia0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Oct 2012 11:32:26 +0000 Received: by mail-ia0-f175.google.com with SMTP id b35so1221161iac.6 for ; Thu, 25 Oct 2012 04:32:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=nF3WyvvsUgiYkJLTKh4f/B63vYjNB7rUcnFYsxPkMmI=; b=zjNiTArwxzHpc9LQWpluMwFHIdsZ+04pcK3Mx0Nc1AMZbgHZy0N5jp62Ah0B4sKFf0 C6EVpWxySa3uzv5DML5fW4LNjYYMGei20Zl2ZaFkUKcHKFF1iR+kWeRFp84e56K1iJsS XPUg/nwwz0k6Zjd3jgPcSMEr3HD0/RReEse64lyV84TPOanOpZdOH68cdW7Jf62pC/gT kgKS6wkpSJ4wJXeNye1vwBTVaT0CflQI88qsrCeZfZzCWoNqMiW3svNHqUib+3ioMRK1 LjEIAgGWmS6UnZb0mqX83Sm4pVPI+TNxf00rtY8PrBqjGPXyY2h8fJMN5r83IS4N4M4I WmKA== MIME-Version: 1.0 Received: by 10.50.190.131 with SMTP id gq3mr4065990igc.68.1351164725100; Thu, 25 Oct 2012 04:32:05 -0700 (PDT) Sender: binoabn@gmail.com Received: by 10.64.62.201 with HTTP; Thu, 25 Oct 2012 04:32:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Oct 2012 09:32:04 -0200 X-Google-Sender-Auth: jLjd78dngYqujoj9d5tnSjVH6NQ Message-ID: Subject: Re: [PROPOSAL] "difficulty" field for Bugzilla From: Albino B Neto To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi. On Wed, Oct 24, 2012 at 5:08 PM, Rob Weir wrote: > As you have probably noticed, I'm engaged in a variety of initiatives > to grow the community, bring in more volunteers, etc. One additional > piece that I think would be useful is to add a new field to Bugzilla > to indicate the difficulty level of the bug. Of course, this will > often not be known. But in some cases, we do know, and where we do > know we can indicate this. > > What this allows us to do is then have search filters that return only > open easy bugs. These are ideal for new developer volunteers on the > project who are looking for items that match their lesser familiarity > with the code. It also allows a developer to step up to more > challenging bugs over time. > > A similar approach, which they called "easy hacks", was successfully > used by LibreOffice. > > If there are no objections, I'll add a new field to Bugzilla called > "cf_difficulty_level", and which a drop down UI with the following > choices: > > UNKNOWN (default) > TRIVIAL > EASY > MODERATE > HARD > WIZARD > > (I'm certainly open to variations on the names) > > I'd then rely on other developers to help "seed" the database with > some TRIVIAL and EASY bugs, so new volunteers will have something to > work with as they familiarize themselves with the project. > > I'll wait 72 hours, etc. > > Regards, > > -Rob +1 -- Albino