bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject Re: [Apache Bloodhound] #194: examine workflow for Bloodhound site
Date Fri, 31 Aug 2012 16:10:45 GMT
#194: examine workflow for Bloodhound site
------------------------+--------------------
  Reporter:  gjm        |      Owner:  nobody
      Type:  task       |     Status:  new
  Priority:  major      |  Milestone:
 Component:  siteadmin  |    Version:
Resolution:             |   Keywords:
------------------------+--------------------

Comment (by jdreimann):

 2. I like the keyword based approach. What I wanted to say by untouched is
 that we leave those tickets alone, other than with helpful comments and
 hints for those that will pick them up -> not resolve the tickets. Showing
 them in the Dashboard when not logged in would work well in our use case,
 but maybe not in a general one for Bloodhound? Not sure.
 3. So a more abstract '''I''' / '''II''' / '''III''' approach may work
 better?
 4. That's why I didn't call it code. debates, wireframes and mockups also
 fall into this category.

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

Mime
View raw message