Re: [office] Proposed Resolution for the ODF 1.3 schedule

[robert_weir@us.ibm.com]

Michael,

I'm not sure I understand this part:

"Exceptions from this rule shall be granted only if the TC is confident 
that the new feature does not break, and that it further gets 
implemented."

But maybe we don't need to specify a detailed criterion here.  We could 
just say, "Exceptions from this rule shall be granted only by simple 
majority approval by the TC in a meeting vote or electronic ballot".

I don't think that it makes sense to have a more stringent requirement, 
since a simple majority is sufficient change the standing rule.  So you 
can't really have a standing rule that prevents the majority from doing 
whatever they want.

-Rob

Michael Brauer <michael.brauer@oracle.com> wrote on 02/03/2011 09:35:18 
AM:
> 
> Dear TC members,
> 
> in the past weeks we have discussed a schedule for ODF-Next, and it 
> seems to me we reached consensus on a two year schedule for ODF 1.3,
> based on 4 Committee Drafts. 
> 
> Having a schedule (regardless what it looks like in detail) is a 
> critical item for our daily work. That's because the schedule tells 
> all of us by when we must have our proposals ready, and when we can 
> expect them in a specification. The schedule therefore is the basis 
> for planing our own personal work on ODF 1.3.
> 
> It is therefore important that we are all familiar with the 
> schedule, and that we stay with it whenever possible. I therefore 
> propose that we formally agree on the schedule in a resolution. 
> Please note that this does not mean that the schedule cannot be 
> changed if there are good reasons for this. It can be changed, but 
> this would require also a formal resolution.
> 
> Below is what I would like to propose as resolution text. I 
> intentionally have not used any CSD numbers, because it is not 
> unlikely that we need additional CSDs. For instance if  we have 
> approved a CSD and want to send it out for public review, but then 
> notice an issue we think needs to be addressed first.
> 
> Resolution:
> -The ODF TC aims to develop ODF 1.3 as a sequence of committee 
> specification drafts (CSDs). Committee specification drafts shall be
> ready for approval by the TC every 6 months. 
> - The first committee specification draft shall be ready for 
> approval in September 2011, subsequent CSDs in March 2012, September
> 2012 and March 2013. Additional CSDs are permitted.
> - For the September 2011 CSD, no proposal shall be integrated after 
> July 2011. 
> - For the March  2012 CSD, no proposal shall be integrated after 
> January 2012. 
> - For the September 2012 CSD, no proposal shall be integrated after 
> July 2012. 
> - After the September 2012 CSD, no new features shall be integrated 
> into the ODF specification. Exceptions from this rule shall be 
> granted only if the TC is confident that the new feature does not 
> break, and that it further gets implemented.
> - The March 2013 CSD  shall be advanced to an OASIS standard. It may
> be approved earlier than March 2013 if no proposals or severe issues
> are outstanding.
> 
> Best regards
> 
> Michael
> -- 
> [image removed] 
> Michael Brauer | Oracle Office Development
> Phone: +49 40 23646 500 
> Oracle Office Global Business Unit
> 
> 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
> 
> [image removed] Oracle is committed to developing practices and 
> products that help protect the environment