RE: [office] Using JIRA

[robert_weir@us.ibm.com]

During a public review, we are required to respond to comments.  But this 
is typically done in batch.  If we receive 500 comments, we are not 
expected to send 500 acknowledgements to the comment list.   When the 
public review period is over, we can create a document that indicates the 
resolution of each comment received and then notify the comment list with 
a link to that document. 

My preference is to keep the comment list informative, with as little 
redundant information as possible.  This means that it should 
predominately consist of:

1) public comments
2) questions on those comments where the comment was unclear
3) clarifications from the original commenter

If we responded to every comment with a boiler-plate acknowledgement, it 
would immediately make half of the posting useless, and substantially 
increase the work I need to do to find the real comments to transcribe 
into JIRA. 

Also, note that all submissions to the comment list end up being send back 
to the poster themselves (if they are still on the list) so they already 
receive confirmation that the comment was received. 

-Rob

"Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote on 05/26/2009 
12:21:10 PM:
>
> 
> Although I still think an explicit response is more powerful (since I 
think
> we are supposed to do that during public review anyhow?), I accept that 
it
> might be burdensome to do. 
> 
> I'm happy to do that much since it doesn't require JIRA privileges to 
carry
> out, if you're willing for it to be done on a voluntary, casual basis.
> 
>  - Dennis 
> 
> -----Original Message-----
> From: robert_weir@us.ibm.com [mailto:robert_weir@us.ibm.com] 
> Sent: Monday, May 25, 2009 10:22
> To: office@lists.oasis-open.org
> Subject: RE: [office] Using JIRA
> 
> "Dennis E. Hamilton" <dennis.hamilton@acm.org> wrote on 05/24/2009 
> 12:44:52 PM:
> 
> > 
> > I think your (3) is also great, but for us to do that we have to 
recall 
> that
> > the public commenter might want to know where the JIRA issue is, so 
they 
> can
> > see our discussion.  Also, it would help in any follow-up from public
> > commenters concerning what they see us making of their comment, since 
> they
> > can't put comments directly on JIRA.
> 
> This is easy.  Since every issue ported over to JIRA has the original 
URL 
> in the "Description" field, the original poster can simply search for 
that 
> URL in JIRA to retrieve the current status of that issue.
> 
> I also include the original submitters email address, so they can easily 

> look up the current status of all of their issues.
> 
> > Although it feels clumsy and will add material to the office-comment 
> list, I
> > have the following suggestion for at least new JIRA issues that are 
> created
> > for a submission on office-comment: (1) reply to the office-comment, 
(2)
> > include the comment submitter and the office-comment list in the 
reply, 
> and
> > (3) report that the comment has been turned into JIRA issue(s) with 
> their
> > numbers and their URLs.  (I have confirmed that the JIRA is available 
to
> > public access, so this should all work.)
> 
> This is unnecessary and would just make more work for me.  See above for 

> how the original submitter can look up their items on JIRA. 
> 
> We can put the information on how to search JIRA in a monthly note to 
the 
> comment list.
> 
> -Rob
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>