OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [office] So what happens in a public review?

Hi Michael,

  You don't post it to the comment list; you post it to the TC list. (Remember, the email archives, as well as every other resource associated with a TC, is always publicly viewable.) Assuming that the export would contain a link to the original email, the name of the person submitting the comment, a description of the comment, and a description of its resolution, then you would satisfy the requirement.


On Nov 16, 2009, at 3:39 AM, Michael Brauer - Sun Germany - ham02 - Hamburg wrote:

> Hi Mary,
> On 11/16/09 01:55, Mary McRae wrote:
>>> 3) The TC must acknowledge the receipt of each public comment.  This occurs automatically, since we use an email reflector list.  Each person who submits a comment will immediately receive a copy of the comment back to them via email.  That is the acknowledgement. 
>> [actually no - the language is as follows: "The TC must acknowledge the receipt of each comment, track the comments received, and publish to its primary e-mail list the disposition of each comment at the end of the review period."
>> Depending on various settings, a sender may or may not receive a copy of a message they posted. But the acknowledgement of receipt isn't meant to imply that you send something directly back to the submitter, but that the comment is noted in a log of some sort along with its resolution.]
>>> 4) We need to track all comments received.  This will be done in JIRA. I have automation that will automatically transfer comments into JIRA from the office-comment list.  This works best when we observe the prohibition against discussion on the comment list.  Otherwise we will end up with extraneous comments in JIRA.
>>> 5) Sometime after the end of the review period (60 days) we need to publish the disposition of each comment.  Typically, we propose dispositions on the list, or directly in JIRA, and then vote to approve the dispositions in a meeting.  The dispositions are then published in the 
>>> meeting minutes and that satisfies the requirement to publish dispositions.   However, if there are more than a handful of comments we could also just minute that the comments are disposed as per their resolutions in JIRA, and then give their OFFICE-X numbers.  Since all JIRA 
>>> resolutions get echoed to the mailing list, this should meet the requirements as well.
>> [actually, no, it doesn't. A comment resolution log must be prepared and posted ("at the end of the review period"). I'm guessing you can just export this from JIRA and that in JIRA there's a link to the original comment posted to the comment list for traceability?]
> If we export that resolution log from JIRA and post that to the comment list, are we then meeting the requirement to acknowledge the receipt  of each comment (as discussed in item 3 above)?
> Best regards
> Michael
> -- 
> Michael Brauer, Technical Architect Software Engineering
> StarOffice/OpenOffice.org
> Sun Microsystems GmbH             Nagelsweg 55
> D-20097 Hamburg, Germany          michael.brauer@sun.com
> http://sun.com/staroffice         +49 40 23646 500
> http://blogs.sun.com/GullFOSS
> Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1,
> 	   D-85551 Kirchheim-Heimstetten
> Amtsgericht Muenchen: HRB 161028
> Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
> Vorsitzender des Aufsichtsrates: Martin Haering

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]