OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office-collab message

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

Subject: IRC log from our meeting on 2016-06-01

Our next meeting will be on the 15th of February:

The teleconference login data for next call will be found in the OASIS calendar event:

Please find the IRC log of today's meeting below: 
Attendees: Patrick, Peter, Svante

[16:29] Svante Schubert: Hello Peter
[16:29] Peter Rakyta: Hi Svante
[16:30] Peter Rakyta: dialing in
[16:32] Svante Schubert: Today's agenda - https://lists.oasis-open.org/archives/office-collab/201605/msg00006.html
[16:34] Svante Schubert: 1. Status update on the current implementations 
a) LibreOffice as part of the Google Summer of Code program

b) Calligra, i.e. MultiRacio's branch

c) ODF Toolkit ODFDOM fork from Open-XChange
[16:39] Svante Schubert: Peter: The calligra branch is still ongoing, bugfixes and modifications are still coming.
[16:45] Svante Schubert: 2. Definition of Done

What is our minimum feature set we aim to archive for a first public version?

a) Likely it is the minimum set of operations equal to the maximum set of changes supported by current change-tracking of any ODF application? 

b) What kind of tooling should be developed for the OASIS SC?
* Sorting / Normalizing a sequence of operations
* Testing environment: Document to Operations to Document to Operations 
   Comparing the operation sequences for automated testing
   Removing a new change pattern - like a new feature - to remove noise and realize regressions
* A tool to align the collaboration of applications with different feature set (has much in common with the previous test tool, but the sequences of operations
[16:46] Patrick: Start with the existing set of changes that are being tracked -
[16:48] Patrick: There are user expectations - do what MS is able to do
[16:51] Svante Schubert: The absolute minimum is the existing ODF 1.2 change-tracking feature set.
[16:53] Svante Schubert: Patrick: There are features as session IDs in some ODF applications that might worth to investigate
[17:13] Svante Schubert: Peter, can you ask your developers what test tools they are using or what they mind need as in 2b)?
[17:13] Svante Schubert: 3. Roadmap

After the detailed idea of what we want archive in the first step, we can discuss who might take over and in what time frame. Than we are able to draft a road map.
[17:15] Svante Schubert: Peter: Regarding the roadmap we need to get to a mile stone, to get the interest from other people.
[17:15] Svante Schubert: Peter: We need to develop a prototype to show
[17:16] Patrick: what if we specified the ODF 1.2 features and MS features as a target? to give the effort more specific to sell to others
[17:26] Svante Schubert: Alone paragraph and text with formats took very long to implement, I am uncertain if the missing feature set is holding back developers. Test tools on the other side might speed up developers.
[17:39] Svante Schubert: Patrick: He is working on a feature list of change-tracking in OOXML. A similar feature list would be desirable for the ODF 1.2. The combination would be likely our estimated feature set for changes by operations.
[17:39] Svante Schubert: Thanks for joining the call. Good-Bye!

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