Re: [office] ODF TC Teleconference 26 October 2020

Hi everyone,

I shortly discussed with Regina and Michael, if there are any further topics to talk about.

Michael just reminded me that if there is some time left today, we could talk about ODF 1.4 JIRA issues in general.Â

He pointed out the ODF 1.4 dashboard - I forgot about its existence - you need to log in (upper right corner)

https://issues.oasis-open.org/secure/Dashboard.jspa?selectPageId=11170#Â

Regina mentioned that from her understanding all ODF 1.4 issues should have an assignee, who take responsibility for this issue and likely prepares and present it for the TC.

There are different kind of issues as wordingÂ& bugs and on the other hand, new features, which should be in charge of an implementation owner.ÂÂ

In addition, Michal provided a basic query for ODF-Next issues:

https://issues.oasis-open.org/browse/OFFICE-4090?filter=16073

The query includes ODF-Next issues with all states. ODF-Next target was set during work on ODF 1.3 and meant as ODF 1.4 target.

Again Regina pointed out that she would like to keep this ODF-Next state in general as a pool of issues that can be taken when an assignee is found and/or the existing ODF 1.4 issues are resolved.

I did a quick check on the status of the ODF-Next query list:

RESOLVED - should have a resolution from TC and can already be changedÂto target ODF 1.4 - just one issue (OFFICE-3936)
NEW - are somehow incorrect set. Likely issues with a target should have the status OPEN as we usually evaluate a NEW issue and provide it with a target, as we did last week (two issues)
OPEN - the pool of 83 issues we can draw from.
CLOSED - can be ignored, were not accepted to be worked upon (4 issues)
DEFERRED - a pool of 27 issues, which might be changedÂto status OPEN (this state usage is not documented in ourÂJIRA documentation in our WIKIÂ[1])
APPLIED - luckily no existing, as applied should never be with target ODF-NextÂ

At some point, we might want to review and update our old ODF WIKI JIRA documentation [1], either in Wiki or preferable in GitHub.

And come back to Patrick's JIRA thoughts

https://lists.oasis-open.org/archives/office/202010/msg00002.html

and Michaels' answer:

https://lists.oasis-open.org/archives/office/202010/msg00013.html

Best regards,

Svante

[1]ÂÂhttps://wiki.oasis-open.org/office/JIRA_Conventions

Am Mo., 26. Okt. 2020 um 01:02ÂUhr schrieb Patrick Durusau <patrick@durusau.net>:

Greetings!

Below you find a draft agenda for our TC call on Monday, 2020-10-26

Time of meeting:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=10&day=26&hour=16&min=0&sec=0&p1=25&p2=37

The call counts towards voter eligibility.

Teleconference Numbers

Canada - (use US number)

Denmark - +45 78 77 25 34

Germany - +49 30 255550324

Hungary - +36 1 987 6874

The Netherlands - +31 6 35205016

USA - +1 712 770 5505

Access code (for all numbers): 438-387

Chat room for meeting is at: http://webconf.soaphub.org/conf/room/odf

Please send comments to the mailing list.

Agenda
------

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 19 October 2020
https://lists.oasis-open.org/archives/office/202010/msg00066.html

4. FYI: Special Majority Vote to consider Office Applications
(OpenDocument) Version 1.3 with
Non-Material Changes as a Committee Specification, closes 30 October
2020 at 23:59 UTC

Internal link:
https://www.oasis-open.org/apps/org/workgroup/office/ballot.php?id=3529

Publicly accessible link:
https://www.oasis-open.org/committees/ballot.php?id=3529

(5 yes votes have been registered as of the posting of this agenda)

5. Statements of Use - Anticipated, Timing, other issues?

2.8.1 of the TC process provides:

1) After the approval of a Committee Specification,

2) and after three Statements of Use referencing the Committee Specification
have been presented to the TC,

Defined terms:
https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22

'bi. "Statement of Use", with respect to a Committee Specification or
Project Specification, is a written statement that a party has
successfully used or implemented that specification in accordance with
all or some of its conformance clauses, identifying those clauses that
apply, and stating whether its use included the interoperation of
multiple independent implementations. The Statement of Use must be made
to a specific version of the Specification and must include the
Specification's approval date. The party may be an OASIS Member or a
non-member. In case of a non-member, the Statement of Use must be
submitted via the Technical Committee's or Project Governing Board's
comment facility. A TC or PGB may require a Statement of Use to include
hyperlinks to documents, files or demonstration transcripts that enable
the committee's members to evaluate the implementation or usage. A
Statement of Use submitted to the TC or PGB must be approved by TC
Resolution or PGB action as an acceptable Statement of Use with respect
to the Specification. A party can only issue one Statement of Use for a
given specification. When issued by an OASIS Organizational Member, a
Statement of Use must be endorsed by the Organizational Member's Primary
Representative.'

3) a TC may resolve by Special Majority Vote to submit the Committee
Specification as a Candidate OASIS Standard.

4) At least one of the Statements of Use must come from an OASIS
Organizational Member.

5) The TC may decide to withdraw the submission, by Special Majority
Vote, at any time until the final approval.

6) The chair shall submit the request for the Special Majority Vote
using the request mechanism designated by the OASIS TC Administrator.

Calendar AFTER Committee Specification AND TC approval of 3 statements
of use, one from an OASIS organizational member, and a Special majority
vote (bg. in
https://www.oasis-open.org/policies-guidelines/oasis-defined-terms-2018-05-22)
- minimum open for 7 days 1.10 TC voting -
https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26

60 days of public review - announced by TC Admin

If no comments, within 7 days, TC Admin starts "call for consent for
OASIS Standard approval"

Call for consent lasts 14 days, if no valid objections, becomes an OASIS
standard

Assuming no comments and maximum time periods, 81 days.

6. There are no new issues or comments for processing.

7. Other business?

8. Adjournment.

--
Patrick Durusau
patrick@durusau.net
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

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

office message