bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <>
Subject Re: [Apache Bloodhound] #194: Examine workflow for Bloodhound site (was: examine workflow for Bloodhound site)
Date Sun, 02 Sep 2012 03:20:46 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 olemis):

 I was trying to follow this conversation and it's been hard in general .
 Many times I had to scroll up to know was said before and connect it with
 comment text , until I had to scroll once again because I forgot and had
 no means to «refresh my RAM» quickly. Could we please use reply button
 more often ? Especially in this kind of branchy conversations ... for the
 sake of legibility ;).

 This also makes me wonder that maybe we should have collapsible replies
 plus (expand / collapse) all replies links/buttons .

 Replying to [comment:1 jdreimann]:
 > I can think of a few things that could help here, some immediate, some
 longer term:

 I welcome all these suggestions, yes . Especially sometimes it's a bit
 hard for me to know what assigned tickets have pending patches , for
 instance .

 > 1. People shouldn't assign tickets to themselves unless they are
 planning to work on them in the near future -> it's not a landgrab.

 Sometimes I've had the intention to start with a ticket but something
 happens ... please read below ;)

 > 2. The status of tickets is currently either 'new', 'assigned',
 'accepted' or 'resolved' and 're-opened' as far as I can tell. In reality
 something like this happens: 'new', 'work in progress', 'pending review',
 'resolved'. (Work usually means code). Matching this more closely and
 providing better control to move between states would help.

 The only thing I'd like to add is that sometimes between 'work in
 progress', and 'pending review' , ticket enters an state in which nothing
 can be done until something happens (e.g. another ticket has to be closed,
 green light to a decision, pending discussion with trac-dev et al.,
 research, improvements needed, down ... and alike) . Maybe
 it's worth having a separate status for this (i.e. remove owner , but
 ticket is not technically ''new'' ;) . This is related to 1 above , btw .

Ticket URL: <>
Apache Bloodhound <>
The Apache Bloodhound (incubating) issue tracker

View raw message