Re: [office] office-comment list -- Monthly Administrivia Reminder(draft)

[Michael Brauer - Sun Germany - ham02 - Hamburg <Michael.Brauer@Sun.COM>]

Rob,

sounds good. I think we should have a copy of the text to the TC's Wiki.

Michael

On 06/01/09 18:07, robert_weir@us.ibm.com wrote:
> I'd like to send the following memo out to the comment list at the start 
> of each month.  Before I send it out for June, I wanted to quick run it by 
> Mary and the TC. 
> 
> Is there anything else I should be saying?  Or not saying?  Any other 
> submission guidelines I should mention?
> 
> 
> -Rob
> -----------------------------------------
> 
> This is the office-comment list <office-comment@lists.oasis-open.org>
> 
> 
> == Purpose of the List ==
> 
> This publicly archived list offers a means to provide input to the OASIS 
> Open Document Format for Office Applications TC.
> 
> he TC's home page is here:  
> http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
>  
> This list is not a support avenue for ODF applications, nor is it a 
> general-purpose discussion list on ODF topics. 
> 
> 
> ==  Using the List  ==
> 
> You can subscribe to the list by following the instructions here:  
> http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=office
> 
> You can unsubscribe to the list by sending an email to: 
> office-comment-unsubscribe@lists.oasis-open.org
> 
> A searchable archive of the list contents is here: 
> http://lists.oasis-open.org/archives/office-comment/
> 
> 
> == Submitting a comment ==
> 
> When submitting a comment to the list, please follow these guidelines:
> 
> 1) Indicate clearly in the subject line the nature of your comment, the 
> ODF version to which your comment pertains, and the section number in the 
> specification to which you refer.  "Defect", "problem" or "clarification 
> needed" are not good subject lines.  But "Missing comma in ODF 1.2 CD02 
> section 1.2.3" is an example of great comment.
> 
> 2) If you are proposing a new feature or capability, then make sure that 
> the subject line contains the "Proposal", such as "Proposal for new 
> spreadsheet function FOO()" or "Double text overline proposal"
> 
> 3) If you have a desired outcome in mind, then describe what you want to 
> see in the body of your comment.
> 
> 4) Every new comment should be in a new thread.  We risk losing track of 
> issues if they are submitted 5 levels deep in a thread. 
> 
> 
> == What to expect after submitting a comment ==
> 
> Comments are of three kinds: those submitted during official Public 
> Reviews, those that are part of ISO/IEC JTC1 defect reports, and all other 
> comments.
> 
> 1) For comments submitted during a Public Review, we will follow the 
> process defined here:  
> http://www.oasis-open.org/committees/process.php#publicReview
> 
> 2) For ISO/IEC JTC1 defect reports, we will follow the process described 
> in our existing agreements with ISO/IEC JTC1.
> 
> 3)  The TC has agreed to consider all submitted comments, regardless of 
> when they were submitted.  Although you may not receive an immediate 
> response from the TC, be assured that your comments have been archived on 
> the list, and you can track their resolution via JIRA, as explained below. 
>  
> 
> 
> == Tracking the resolution of your comment in JIRA ==
> 
> The ODF TC uses JIRA for issue tracking.   We periodically run automation 
> that transcribes comments from the office-comment list into JIRA.  This 
> automation works best when the guidelines described above are followed. 
> The public can examine the current status of all issues in JIRA here:   
> http://tools.oasis-open.org/issues/browse/office
> 
> To see the status of issues that you have submitted, you can search for 
> your email address in the "Quick Search"  box in the upper left.
> 
> To find the status of a specific comment from the list, search for the 
> subject line (in quotes).
> 
> Some other useful pre-defined searches are listed here:  
> http://tools.oasis-open.org/issues/secure/ManageFilters.jspa
> 
> 
> == Other Useful Lists ==
> 
> opendocument-users: an unmoderated, public mail list that provides an open 
> forum for developers to exchange ideas and information on implementing the 
> office OASIS Standard.
> 
> You can subscribe here:  http://www.oasis-open.org/mlmanage/ 
> 
> There are additional discussion forums hosted at OpenDocument.xml.org 
> here: http://opendocument.xml.org/forum
> 
> The ODF TC has its own list for TC member discussion.  You can view the 
> archives here:
> http://lists.oasis-open.org/archives/office/
> 
> Posting rights are a privilege of TC membership.  Information on joining 
> OASIS can be found here:
> http://www.oasis-open.org/join/
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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 
> 


-- 
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