Okay, now that I'm me on Mantis, I wouldn't mind having docs issues assigned to me by default, but I would like to warn: the new job has my time looking pretty limited, and there's some risk that I could become a bottleneck. What do other folks think?
On Wed, Aug 25, 2010 at 5:55 PM, Ken Causey <[hidden email]> wrote: Oh yeah, I had completely forgotten about that. I've come to think of -- Casey Ransberger |
OK, I went ahead and assigned 'casey' as the default for the
Documentation project, it can always be changed again if necessary. Ken > -------- Original Message -------- > Subject: [squeak-dev] Re: [Box-Admins] please add "Documentation" > category in Mantis > From: Casey Ransberger <[hidden email]> > Date: Wed, August 25, 2010 9:49 pm > To: The general-purpose Squeak developers list > <[hidden email]> > > > Okay, now that I'm me on Mantis, I wouldn't mind having docs issues assigned > to me by default, but I would like to warn: the new job has my time looking > pretty limited, and there's some risk that I could become a bottleneck. What > do other folks think? > > On Wed, Aug 25, 2010 at 5:55 PM, Ken Causey <[hidden email]> wrote: > > > Oh yeah, I had completely forgotten about that. I've come to think of > > you as Casey and more or less forgotten Ron. > > > > Ken > > > > > -------- Original Message -------- > > > Subject: Re: [Box-Admins] please add "Documentation" category in Mantis > > > From: Casey Ransberger <[hidden email]> > > > Date: Wed, August 25, 2010 7:37 pm > > > To: Ken Causey <[hidden email]> > > > > > > > > > Good call, I should handle that and put dear Ronny to rest. He was a good > > man. His middle name (and not many people know this) was "Squeak." > > > > > > On Aug 25, 2010, at 11:03 AM, Ken Causey <[hidden email]> wrote: > > > > > > > As requested I have added a 'Documentation' category to the 'Squeak' > > > > project at http://bugs.squeak.org/ . Is there a user to which all > > new > > > > Documentation issues should be initially assigned by default? Also > > note > > > > that we also have a 'HelpSystem' category that was previously added and > > > > I suspect there is going to be a little tension between whether textual > > > > changes to the help text provided by HelpSystem go under the > > > > Documentation or HelpSystem categories; you may wish to give this some > > > > thought and let me know if I can make any appropriate changes. > > > > > > > > I also should make the two of you Developers so you can modify reports > > > > appropriately. > > > > > > > > I find a 'hirzel' account but it is using a different email address. > > Is > > > > this you Hannes? If so check the email address and let me know. > > > > > > > > I find an account 'ronnys' for you Casey, at least with the email > > > > address you have used here, is this your account? Users may find that > > > > user name confusing, care to change it? > > > > > > > > Ken > > > > > > > > On Wed, 2010-08-25 at 16:24 +0200, Michael Haupt wrote: > > > >> Dear box admins, > > > >> > > > >> to facilitate a structured handling of documentation issues, we (that > > > >> is, at least Casey Ransberger, Hannes Hirzel, and myself) would like > > > >> to be able to have people report such issues via Mantis. To that end, > > > >> having a "Documentation" category would make sense. > > > >> > > > >> Could you please add this? > > > >> > > > >> Thanks, > > > >> > > > >> Michael > > > >> > > > > > > > > > > > -- > Casey Ransberger<hr> |
In reply to this post by Casey Ransberger-2
On 8/26/10, Casey Ransberger <[hidden email]> wrote:
> Okay, now that I'm me on Mantis, I wouldn't mind having docs issues assigned > to me by default, but I would like to warn: the new job has my time looking > pretty limited, and there's some risk that I could become a bottleneck. What > do other folks think? That is fine for me. In case you become the bottleneck you can ask that somebody else will be assigned for 'default'. Or maybe later we can work with a roaster scheme. You have it for let's say for 4 months, than somebody else takes over. --Hannes |
On 2010/08/26 06:45, Hannes Hirzel wrote:
> On 8/26/10, Casey Ransberger<[hidden email]> wrote: >> Okay, now that I'm me on Mantis, I wouldn't mind having docs issues assigned >> to me by default, but I would like to warn: the new job has my time looking >> pretty limited, and there's some risk that I could become a bottleneck. What >> do other folks think? > > That is fine for me. In case you become the bottleneck you can ask > that somebody else will be assigned for 'default'. If you have a "second in command" you could always farm out issues by assigning them to someone else. (Or of course people could simply take them from you too.) If I recall correctly Ken used to be (is still?) the "default assignee" for issues on Mantis, and would sometimes reassign the issues as appropriate. (But I'm speaking from years-old memory, so I might be mistaken.) > Or maybe later we can work with a roaster scheme. You have it for > let's say for 4 months, than somebody else takes over. I think you meant "roster", but I rather like "roaster" too - one person's on the burner, and then swaps places with someone else! (And if you're on the roaster too long, you burn out!) frank |
In reply to this post by Ken Causey-3
Hi,
On Thu, Aug 26, 2010 at 4:55 AM, Ken Causey <[hidden email]> wrote: > OK, I went ahead and assigned 'casey' as the default for the > Documentation project, it can always be changed again if necessary. can assignments be changed? I.e., if all doc issues are automatically assigned to Casey, could I, if I have some time on my hands, grab one of the issues from him, assign it to me, and thereby point out that I'm working on it? (Is there a difference between "assigned" and "being worked on"? I wouldn't want to grab assigned issues from Casey on which *he* is already working.) Best, Michael, Mantis noob |
On 2010/08/26 08:34, Michael Haupt wrote:
> Hi, > > On Thu, Aug 26, 2010 at 4:55 AM, Ken Causey<[hidden email]> wrote: >> OK, I went ahead and assigned 'casey' as the default for the >> Documentation project, it can always be changed again if necessary. > > can assignments be changed? I.e., if all doc issues are automatically > assigned to Casey, could I, if I have some time on my hands, grab one > of the issues from him, assign it to me, and thereby point out that > I'm working on it? Yes: either the currently responsible person may assign the task to you, or you may (given suitable permissions) take over a task by assigning it to yourself. > (Is there a difference between "assigned" and "being worked on"? I > wouldn't want to grab assigned issues from Casey on which *he* is > already working.) I'm not sure of the precise meanings the community associates with the different task states. I interpret "assigned" as "this person's either investigating the task, or working on it in some other way, but at any rate is currently responsible for the task". If you're working on a piece of documentation - say, WebClient - you could always bounce the task to the maintainer of that package (Andreas, in this case) by moving the task state to feedback. (This prompts you for a name, and possibly a note.) Mantis then sends that person an email, so one doesn't have to poll Mantis all the time. I'd expect, for a bug report, for a task to go new -> assigned -> confirmed, and then maybe request feedback from someone (-> feedback) or "it's not a bug" (-> closed) or "yes it's done and here's the fix (-> resolved -> closed). For documentation, I think simply assign -> resolved (or maybe -> feedback -> resolved) -> closed should be fine? frank |
Hi,
On Thu, Aug 26, 2010 at 9:48 AM, Frank Shearar <[hidden email]> wrote: > For documentation, I think simply assign -> resolved (or maybe -> feedback > -> resolved) -> closed should be fine? hm, I'd opt for having "confirmed" in the middle, as a sign of someone actually working on it. It's more clear that way, especially with automatic assignment being used. Best, Michael |
On 2010/08/26 09:57, Michael Haupt wrote:
> Hi, > > On Thu, Aug 26, 2010 at 9:48 AM, Frank Shearar > <[hidden email]> wrote: >> For documentation, I think simply assign -> resolved (or maybe -> feedback >> -> resolved) -> closed should be fine? > > hm, I'd opt for having "confirmed" in the middle, as a sign of someone > actually working on it. It's more clear that way, especially with > automatic assignment being used. Sure: I use "confirmed" in my solo work as a similar signal - "this is a long-running task, and I'm halfway through it". Your interpretation for "confirmed" seems fine. As you say, it allows us to differentiate between "responsible for" and "responsible for and have started fixing". I'm just not sure how exactly the community as a whole interprets the various states. frank |
Free forum by Nabble | Edit this page |