Mailing-List: contact bloodhound-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Apache Bloodhound" <bloodhound-dev@incubator.apache.org>
Cc: bloodhound-commits@incubator.apache.org
Auto-Submitted: auto-generated
Date: Fri, 31 Aug 2012 15:56:55 -0000
Reply-To: bloodhound-dev@incubator.apache.org
Subject: Re: [Apache Bloodhound] #194: examine workflow for Bloodhound site
Message-ID: <067.9c4bde1cf67f633fd6fe7aa7143c9f69@incubator.apache.org>
References: <052.915f20130ba69063f69ac0b8589be5f4@incubator.apache.org>
In-Reply-To: <052.915f20130ba69063f69ac0b8589be5f4@incubator.apache.org>

#194: examine workflow for Bloodhound site
------------------------+--------------------
  Reporter:  gjm        |      Owner:  nobody
      Type:  task       |     Status:  new
  Priority:  major      |  Milestone:
 Component:  siteadmin  |    Version:
Resolution:             |   Keywords:
------------------------+--------------------

Comment (by gjm):

 2. I think we could probably just make use of a helpus (or similar)
 keyword and provide a query like this:
 query:status=new|reopened&keywords=helpus. Actually, I wonder if leaving
 tickets untouched is helpful. We really just need a lot more and perhaps a
 good understanding of how they interrelate.
 3. Problem there is that different people will have different abilities
 and so a number of hours work might put some off if they don't think that
 they can do it in the stated time.
 4. Work should not imply code. There is more to tickets than coding.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/194#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker