Revision as of 14:19, 9 May 2007

There is a weekly ODF Toolkit Meeting. Minutes are gathered for one month per Wiki page, latest first.

2007/05/04

15:00–16:00 CEST

Attendees

• Juergen Schmidt (JSC)
• Malte Timmermann (MT)
• Michael Brauer (MIB)
• Stephan Bergmann (SB)
• Dieter Loeschky (DL)
• Lars Oppermann (LO)
• Bernd Eilers (BEI)
• Lars Behrmann (LB)

Associates:

• Kay Ramme (KR)
• Kai Sommerfeld (KSO)
• Matthias Hütsch (MHU)

Minute Taker: BEI (Next: LO, JSC, MIB, LB, MT, SB, DL, BEI)

Action Items

Items from last meeting and before:

• 30.3-1 Organize meeting with API implementors regarding ODF-like APIs; MIB, (JSC); done.

• 27.4-1 set up weekly IRC chat : JSE, DL done.
• 27.4-2 website: add link to Sun's ODF Plugin for MS Office: JSE done.

Discussion on action items:

• 30.3-1 Meeting took place. During that meeting some discussion came up on how compliant to the ODF spec API must get espcially when there is a conflicting goal of getting existing API compliant vs. staying compatible with older versions of that API.
• 27.4-1 regular IRC meetings start next Fr 9:30
• 27.4-2 Some changes to the website have been made more can be done in the future.

New action items:

Topics

• JSE: is analysing Office without UI use cases for Office API. For those we likely do need a higher level API close to the use cases than to XML Elements and Attributes. Considering wrapper Layer. While thinking about how to create an easy to use API some tought came up about wether there could be also enhancements in the java uno language binding which might make things easier for java programmers.

• KSO: summarized that there are three categories into which we must put potential API use cases. Our main goal should be to be able to use Functionality of the existing UNO API (Category A). When Functionality in that Catagory is not intuitive enough new API (eventually based on existing one) must be created (Category B). Last Category (Category C) would be those use cases where we detect that functionality is missing and we need complete new implementation.

• DL: Talked with Charles Schulz about perl module from Jean Marie. Willingness to contribute this to the ODF Toolkit project is there if that module can be maintained by someone from us in the future. Identified Ingo Schmidth as a potential candidate.

A community member showed up with some intrest of doing QA work for the ODF Toolkit project. When discussing this we came to the conclusion that there are already some unit test in AODL and in odf4j. A possibility to contribute in the field of QA would be to spezify and execute Tests on functional level.

Next week there should be a kickoff for the Validator web service.

• LB: GSOC Mentee did provide plan on what he wants to do. Agreed that UML Diagrams for new API should be created.

• SB: made some progress on the separation of URE / Office. Had a follow up meeting on the topic of package restructuring.