OASIS Open Document Format for Office Applications (OpenDocument) TC

  • 1.  Next steps in completing ODF 1.2

    Posted 10-29-2010 07:19 
    Dear TC members,

Rob and I have discussed where we are with completing ODF 1.2 right now, 
and what the next steps could be:

First of all, we would like to thank TC members for their extra efforts 
in recent weeks (and months!) to resolve the open ODF 1.2 issues in 
JIRA.  Your hard work has brought the number of unresolved issues down 
from many hundreds to less than 50.  This is a tremendous achievement 
and this puts us within "shooting distance" of the end.

Patrick has published a new working draft that includes 100's of
additional issue fixes from JIRA.  This is not ready for a CD vote yet 
(or a CSD == Committee Specification Draft, as OASIS calls them now), 
but it is recommended that you review the draft against your highest 
priority JIRA issues to ensure that the fix was made correctly.  In any 
editing project of this size, errors are inevitable, so please go back 
and review the applied fixes from your issues:

http://www.oasis-open.org/committees/document.php?document_id=39878&wg_abbrev=office
http://www.oasis-open.org/committees/document.php?document_id=39880&wg_abbrev=office
http://www.oasis-open.org/committees/document.php?document_id=39881&wg_abbrev=office

In addition, we must now continue the effort to resolve the remaining 
open issues, where a proposal can be quickly developed and consensus 
gained.

However, it is clear that some of these issues have been open for a long
time, in some cases over a year.  There are many reasons why an issue
might remain open for a year, including lack of interest, lack of a good
solution, lack of consensus, etc.  Whatever the reason, it is time to
either resolve these issues or to defer them to "ODF-Next".

In order to make the above happen, we propose the following:


1) After the TC call next Monday, we will retarget all new open ODF 1.2
issues to ODF-Next


2) We only accept new issues with a CD06 target under the following
conditions:

a) the issue comes with an uncontroversial resolution. (Uncontroversial
will be mean that there are no "-1" votes in JIRA)

b) or, the TC votes that the issue is important enough to further delay
ODF 1.2.  TC members can request an ODF 1.2 CD06 target on the mailing
list. If that request is seconded by another TC member, the approval of
the target takes place in the next TC call.

Note that any specific issues deferred to ODF-Next may be re-targetted 
to CD 06 according to a) or b).


After the TC call on Monday, November 8th, condition a) above is 
replaced by:

a')the issue comes with an uncontroversial resolution. (Uncontroversial
will be mean that there are no "-1" votes in JIRA) AND the candidate 
draft for the CD06 ballot has not yet been posted AND the Editor is able 
to integrate the resolution without further delaying the drafts.


In other words, we always preserve the ability for the TC, via a 
majority vote, to open and resolve any issue, even if this results in a 
delay of ODF 1.2.  However, we at the same time take steps to transition 
from the review and editing phase of ODF 1.2 to the final editing and 
approval stage.


3) The TC editor will prepare the final drafts after the November 8th
call. This may actually take a few days, because the generated text has 
to be updated and consistency checks have to run. As soon as the final 
drafts are ready and no motions for resolving further issues do exist, 
the TC editor or chairs will make a motion for approval of the drafts as 
a Committee Specification Draft (CSD) and a follow-up 15-day public review.


This means that the TC has another week to provide resolutions. From
November the 8th on, we prepare the final drafts, and we only further
delay ODF 1.2 in order to resolve further issues if a majority of TC
members approved that.


Best regards

Michael

-- 
Michael Brauer | Oracle Office Development
Phone: +49 40 23646 500
Oracle Office GBU

ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Rijnzathe 6, 3454PV De Meern, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven


  • 2.  Re: [office] Next steps in completing ODF 1.2

    Posted 10-29-2010 07:38 
    On Fri, 2010-10-29 at 01:17 -0600, Michael Brauer wrote:
> 1) After the TC call next Monday, we will retarget all new open ODF
> 1.2
> issues to ODF-Next
> 
> 
> 2) We only accept new issues with a CD06 target under the following
> conditions:
> 
> a) the issue comes with an uncontroversial resolution.
> (Uncontroversial
> will be mean that there are no "-1" votes in JIRA)
> 
> b) or, the TC votes that the issue is important enough to further
> delay
> ODF 1.2.  TC members can request an ODF 1.2 CD06 target on the mailing
> list. If that request is seconded by another TC member, the approval
> of
> the target takes place in the next TC call.
> 
> Note that any specific issues deferred to ODF-Next may be
> re-targetted 
> to CD 06 according to a) or b).
> 
> 

I believe this suggestion violates the spirit of the required public
review. Any new approved CSD will go to a public review during which we
may receive comments both on the comment list as well as directly from
TC members. We need to address those comments on a one-by-one basis
rather than a genral referral to ODF-Next.

Andreas

 
-- 
Andreas J. Guelzow


  • 3.  Re: [office] Next steps in completing ODF 1.2

    Posted 10-29-2010 08:06 
    Andreas,

Andreas J. Guelzow wrote:
> On Fri, 2010-10-29 at 01:17 -0600, Michael Brauer wrote:
>> 1) After the TC call next Monday, we will retarget all new open ODF
>> 1.2
>> issues to ODF-Next
>>
>>
>> 2) We only accept new issues with a CD06 target under the following
>> conditions:
>>
>> a) the issue comes with an uncontroversial resolution.
>> (Uncontroversial
>> will be mean that there are no "-1" votes in JIRA)
>>
>> b) or, the TC votes that the issue is important enough to further
>> delay
>> ODF 1.2.  TC members can request an ODF 1.2 CD06 target on the mailing
>> list. If that request is seconded by another TC member, the approval
>> of
>> the target takes place in the next TC call.
>>
>> Note that any specific issues deferred to ODF-Next may be
>> re-targetted 
>> to CD 06 according to a) or b).
>>
>>
> 
> I believe this suggestion violates the spirit of the required public
> review. Any new approved CSD will go to a public review during which we
> may receive comments both on the comment list as well as directly from
> TC members. We need to address those comments on a one-by-one basis
> rather than a genral referral to ODF-Next.

This suggestion is intended to be in place until the CSD for the next 
public review is ready only. If we receive comments during the follow-up 
public review, we of course need to address them individually.

Please note however that the requirement is:

"The TC must acknowledge the receipt of each comment, track the comments 
received, and post to its primary e-mail list its disposition of each 
comment at the end of the review period."

I'm not recommending that we defer all further comments that we receive 
during the public review automatically to ODF-Next, but deferring an 
issue is anyway a permissible action.

I hope this clarified the suggestion.

Michael

> 
> Andreas
> 
>  


-- 
Michael Brauer | Oracle Office Development
Phone: +49 40 23646 500
Oracle Office GBU

ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Rijnzathe 6, 3454PV De Meern, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven


  • 4.  Re: [office] Next steps in completing ODF 1.2

    Posted 10-29-2010 16:58 
    On Fri, 2010-10-29 at 02:04 -0600, Michael Brauer wrote:
> Andreas,
> 
> Andreas J. Guelzow wrote:
> > On Fri, 2010-10-29 at 01:17 -0600, Michael Brauer wrote:
> >> 1) After the TC call next Monday, we will retarget all new open ODF
> >> 1.2
> >> issues to ODF-Next
> >>
> >>
> >> 2) We only accept new issues with a CD06 target under the following
> >> conditions:
> >>
> >> a) the issue comes with an uncontroversial resolution.
> >> (Uncontroversial
> >> will be mean that there are no "-1" votes in JIRA)
> >>
> >> b) or, the TC votes that the issue is important enough to further
> >> delay
> >> ODF 1.2.  TC members can request an ODF 1.2 CD06 target on the mailing
> >> list. If that request is seconded by another TC member, the approval
> >> of
> >> the target takes place in the next TC call.
> >>
> >> Note that any specific issues deferred to ODF-Next may be
> >> re-targetted 
> >> to CD 06 according to a) or b).
> >>
> >>
> > 
> > I believe this suggestion violates the spirit of the required public
> > review. Any new approved CSD will go to a public review during which we
> > may receive comments both on the comment list as well as directly from
> > TC members. We need to address those comments on a one-by-one basis
> > rather than a genral referral to ODF-Next.
> 
> This suggestion is intended to be in place until the CSD for the next 
> public review is ready only. If we receive comments during the follow-up 
> public review, we of course need to address them individually.
> 
> Please note however that the requirement is:
> 
> "The TC must acknowledge the receipt of each comment, track the comments 
> received, and post to its primary e-mail list its disposition of each 
> comment at the end of the review period."
> 
> I'm not recommending that we defer all further comments that we receive 
> during the public review automatically to ODF-Next, but deferring an 
> issue is anyway a permissible action.
> 
Your initial message as well as your reply appear to imply that for
current JIRA issues there are only two possibilities, namely to fix them
for CD06 or to move them to ODF-Next, when in fact there should also be
a target CD07. While we can hope that CD07 should not be necessary we
cannot know whether it will be until we have received all comments
during the next public review.

Andreas
-- 
Andreas J. Guelzow


  • 5.  RE: [office] Next steps in completing ODF 1.2

    Posted 10-29-2010 16:50 
    I think it would be better to allow targeting new issues that address
defects in CD05/CD06 to a CD07 and then decide whether there is to be no
CD07 later (in which case the retargeting to ODF-Next will be inevitable).
This provides important differentiation between issues that are
intentionally created as ODF-Next items or are intentionally deferred
already, versus ones where we might still deliberate on their importance for
inclusion in a potential further ODF 1.2 draft.

It would be helpful if we created the provisional CD07 target now (after
discussion on Monday) so that it is available for straightforward usage.

 - Dennis


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 6.  RE: [office] Next steps in completing ODF 1.2

    Posted 10-29-2010 17:37 
    "Dennis E. Hamilton"


  • 7.  Discrepancy in ODF 1.2 Part 1 Editions?

    Posted 11-01-2010 03:05 
    Michael and Patrick,

I notice that the changed-tracked ODF 1.2 CD05 Part 1 editor revision 03 is
identified as being based on the draft of 29 May 2010.  But the CD05 that
was submitted to Public Review is identified as being the draft or 19 June
2010.  The changed-tracked editor revision cd01-s for Part 2 and Part 3 have
covers that match the CD05 Public Review editions.

I trust that there is no material discrepancy as the result of
change-tracking an earlier copy than the one that ended up being the CD05
Public Review document.  I thought it wise to draw attention to this as a
precaution.

Also, *both* the CD05 Part 1Public Review .odt and the editor revision still
has a File | Properties | Description | Title entry that names the document
the "OASIS Open Office Specification".  This ends up in the title bar when
the resulting PDFs are viewed in Adobe Reader.  CAN WE PLEASE CORRECT THAT.

 - Dennis 


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


Related Content