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: Notes from 27 January 2020


Our notes from the ODF TC teleconference are below.

Hope everyone is at the start of a great week!


Please change your name from 'anonymous' using the Settings button
anonymous morphed into Patrick
Patrick: 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights

2. Motion (simple majority): Approve the Agenda

3. Motion (simple majority): Approve minutes of 13 January 2020 (below)

4. Editorial issues with Committee Specification, ODF 1.3

Meta issue: Regina asks how to treat the following errors in the current
Committee Specification. (Initial suggestion: That except for editorial
nits such as double spaces, new JIRA issues be created as clones of the
existing issues so we can cleanly track their resolution and
application. by Patrick)

Part 2 (Regina Henschel reporting,

In part 2, section 4.16.9: The text lists the value PGP, but that is not
contained in the generated text in the gray box.

In part 2, section The text has version "1.2", but the
generated text in the gray box has "1.3"

Response by Francis Cave,

Part 3 (Alfred Hellstern and Francis Cave reporting, respectively,

Office-3662 - chart:interpolation -
https://issues.oasis-open.org/browse/OFFICE-3662 Regina's email:

Part 4 (Regina Henschel reporting)

Office-3667 - https://issues.oasis-open.org/browse/OFFICE-3667 Regina's

Office-3766 - https://issues.oasis-open.org/browse/OFFICE-3766 Regina's

5. Adjournment
Patrick: Quorum - yes
Patrick: Agenda - approved - consent
Patrick: Minutes of 13 January 2020 - approved by consent
Patrick: say ID for current committee specification - affects version ->
fixes version - either errata or is separate committee specification
Patrick: put resolution in the resolution -
Patrick: ID for current committee spec. 1.3 and ID for the errata
Patrick: Regina - current spec to go to ISO in current state
Patrick: Regina - collect errors in separate document
Patrick: Regina and Michael - better to handle as errata - let current
CS proceed to ISO
Patrick: create ODF 1.3 errata (Michael)
Patrick: create JIRA issues for known errors in ODF 1.3 Committee
Specification, target ODF 1.3 errata - proceed with ODF 1.3 CS as is
Patrick: proceed with consent of the TC
Patrick: Statements of Use: sent template via email
Patrick: Statements of use will be forthcoming.
Patrick: After the approval of a Committee Specification, and after
three Statements of Use referencing the Committee Specification have
been presented to the TC, a TC may resolve by Special Majority Vote to
submit the Committee Specification as a Candidate OASIS Standard. At
least one of the Statements of Use must come from an OASIS
Organizational Member. The TC may decide to withdraw the submission, by
Special Majority Vote, at any time until the final approval. The chair
shall submit the request for the Special Majority Vote using the request
mechanism designated by the OASIS TC Administrator.
Patrick: How far away are we from getting those three statements?
Patrick: Spring of 2020 - hopefully
Patrick: Next calls on ODF 1.4 issues -
Patrick: No meeting Feb. 17th - holiday in Canada and US
Patrick: No meeting April 13th - Easter Monday
Patrick: No meeting May 24th - Memorial Day
Patrick: No meeting May 18th - Queen Victoria
Patrick: No meeting June 1st - Whit Monday
Patrick: Adjourned - 12:41

Patrick Durusau
Technical Advisory Board, OASIS (TAB)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau 

Attachment: signature.asc
Description: OpenPGP digital signature

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