Interoperability Minutes 2006-10-11
From MemberWiki
Full minutes: /member/wiki/Interoperability_Minutes_2006-10-11
Contents |
Attendees
Present
- Bert Halstead <rhh@curl.com>
- David Boloker <boloker@us.ibm.com>
- Greg Murray <greg.murray@sun.com>
- James Margaris <jmargaris@nexaweb.com>
- John Crupi <john.crupi@jackbe.com>
- Jon Ferraiolo <jferrai@us.ibm.com>
- Joonas Lehtinen <joonas.lehtinen@itmill.com>
- Kevin Hakman <khakman@tibco.com>
- Lindsey Simon <lsimon@finetooth.com>
- Phil Berkland <berkland@us.ibm.com>
- Rick Evans <Rick.Evans@Sun.COM>
- Ted Thibodeau <tthibodeau@openlinksw.com>
- Victor Leith <vsleith@us.ibm.com>
- Vivienne van der Vooren <vvandervooren@seagullsoftware.com>
Absent
- Adam Peller <apeller@us.ibm.com>
- Alejandro Escalante Medina <alejandroe@jackbe.com>
- Alex Russell <alex@dojotoolkit.org>
- Andrei Dragomir <adragomi@adobe.com>
- Anil Sharma <anil@vertexlogic.com>
- Arno Puder <arno@puder.org>
- Bjoern Mueller <Bjoern.Mueller@softwareag.com>
- Bradley Sipes <Bradley.Sipes@ikivo.com>
- Brandon Bloodgood <bbloodgood@goetc.net>
- Chris Matthews <cmatthews@elinkbiz.com>
- Chris Schalk <chris.schalk@oracle.com>
- Chuck Ames <CAmes@seagullsoftware.com>
- Coach Wei <coach@nexaweb.com>
- Cody Hageman <cody@goetc.net>
- Craig McClanahan <craig.mcclanahan@sun.com>
- Dave Johnson <djohnson@ebusiness-apps.com>
- David Kranz <kranz@curl.com>
- David Temkin <temkin@laszlosystems.com>
- Eric Nguyen <ericn@mercedsystems.com>
- Erik van Dongen <evandongen@seagullsoftware.com>
- Gustavo Munoz <gustavom@jackbe.com>
- Hyther Nizam <hyther@adventnet.com>
- Ian Wenig <ian@zoho.com>
- James Douma <jdouma@ebusiness-apps.com>
- Javier Gallego <Javier.Gallego@softwareag.com>
- Jay Ramasamy <Jay@adventnet.com>
- Jennifer Taylor <jetaylor@adobe.com>
- Jeremy Chone <jchone@adobe.com>
- Jim Grandy <jgrandy@openlaszlo.org>
- John Janetos <jjanetos@laszlosystems.com>
- Jorge Taylor <jotaylor@adobe.com>
- Ken Fyten <ken.fyten@icesoft.com>
- Kin Blas <jblas@adobe.com>
- Kingsley Idehen <kidehen@openlinksw.com>
- Kjell Richard Bjørntvedt <krb@24SevenOffice.com>
- Luke Birdeau <lbirdeau@tibco.com>
- Michael Peachey <mpeachey@tibco.com>
- Raju Vegesna <raju@zoho.com>
- Ross Dargahi <ross.dargahi@zimbra.com>
- Rüdiger Herrmann <rherrmann@innoopract.de>
- Stephen Maryka <steve.maryka@icesoft.com>
- Steven Pothoven <pothoven@us.ibm.com>
- Vincent Hardy <vincent.hardy@sun.com>
Agenda
- Agenda
- SourceForge setup
- 4 Contributors so far (Joonas, Lindsey, James, Jon), waiting on Alex. Who else?
- Has all code been uploaded so far?
- Coding: who will do what?
- Loading/unloading
- Collision detection/management
- Event hub
- Markup scanner
- Test cases
- Where should test cases be located within the trunk?
- How to organize test cases?
- Who will commit to developing test cases?
- Documentation
- Where should docs be located - on www.openajax.org or on SourceForge?
- Who will commit to creating docs?
- Integration of Hub with toolkits
- ITMill
- Who else?
- SourceForge setup
Minutes of OpenAjax Interoperability Working Group telephone
conference, Oct. 11, 2006.
(Meeting called to order at about 11:03am EDT.)
Topic: Rotating minutes
Jon: One resolution from last week's meetings was that working group minutes should be a rotating responsibility among working group members. Based on alphabetical ordering of first names, Bert Halstead from Curl comes first!
(Note: Jon has updated the minutes page to show who took minutes for which meeting: /member/wiki/Interoperability_Minutes)
Topic: SourceForge setup
- SourceForge setup
- 4 Contributors so far (Joonas, Lindsey, James, Jon), waiting on Alex. Who else?
- Has all code been uploaded so far?
- SourceForge setup
Congratulations to James for being the first person to upload source code to the SourceForge project.
First agenda item: SourceForge setup.
Process: boilerplate text is sent to Jon by e-mail. Contact Jon if you have questions.
Markup scanner has been uploaded by James so far.
Expecting upload soon from Alex. Jon will follow up with him about becoming an official contributor and making his contribution.
Organization: instead of one markup-scanner.js file, we should have separate files for the four features that it implements.
Kevin Hakman, TIBCO: From a code management viewpoint that's a good idea, but a single file is preferable as the final product.
James, Nexaweb: Could just concatenate the files in the right order. Could also use some compression technology. Comment stripping and such would also be useful, to save space.
RESOLUTION: We'll develop the JavaScript files so that they *can* be concatenated.
Kevin: During development, there will be dependencies between files. So contributors will still need to coordinate with each other.
James: Dojo has a mechanism where you can provide or require stuff, preventing double loading and being scalable to a larger number of files.
Jon: Lindsey, do you have any source code to upload?
Lindsey: Yes, but it's embedded in Alex's code, so we need to wait for his upload.
Jon: It would be cleaner if everybody could submit their code directly to the project.
James put his source code in an src directory and the corresponding tests in test/src. The latter should be primarily unit tests for the source files.
James: This structure was modeled after JUnit and JSUnit. JSUnit gives us a capability to have a true automated test and is easy to set up, though you do need to set up various Java components on your machine first.
Rick Evans (?): We should clearly document how you submit tests, to avoid confusion. There should also be a process for rejecting tests if the committee feels they aren't appropriate.
James: I can deal with some JSUnit stuff.
Rick: I'd like to help edit the documentation, though I don't yet feel up to creating it.
?: Likewise.
Jon: Anything that goes into a source control tree needs the boilerplate IP e-mail sent to Jon. Just go into the SourceForge project and follow the link that tells how to do that. This applies even to people who just contribute documentation.
Topic: Coding: who will do what?
- Loading/unloading
- Collision detection/management
- Event hub
- Markup scanner
Next agenda item: Who's going to work on which parts of the code?
Markup scanner: James.
Event hub: Alex.
Loading and unloading: Alex.
Collision detection: Lindsey?
Topic: Test cases
- Where should test cases be located within the trunk?
- How to organize test cases?
- Who will commit to developing test cases?
Test cases: Alex, James, (Lindsey?).
We've resolved where the test cases should be checked in. How to organize them? By feature, using a naming convention, or just random?
Joonas: How about making an index.html file to organize them?
James: Use the name of the feature being tested, e.g., <name of source file>-test-<feature area>-test1, 2, 3, etc.
Jon: Let's do that.
Vic: Interested in generating tests.
Topic: Documentation
Jon: Next agenda item: Documentation. Part of the documentation is specifications. Things like the spec for the hub should be built and developed on www.openajax.org using wiki technology, rather than on SourceForge.
(General agreement.)
Vic?: I can work on that. Do other people want to join in? It's fun!
Topic: Integration of Hub with toolkits
- ITMill
- Who else?
Jon: Final agenda item: Integration of hub with toolkits. ITMill has already said they will integrate the hub with their product. Anybody else?
James, Nexaweb: I would like to integrate them with XAP.
Jon: Alex has said in the past that he's likely to do it with Dojo, but the timing depends on release milestongs. So we can count Dojo as being in.
Kevin: TIBCO will definitely do this also.
John Crupi, Jackbe: We'll commit also.
Ted: We'll do it also.
Greg: JMaki also.
Lindsey: Let's contact scriptaculous by e-mail to see if they have interest.
Jon: Any more agenda items?
(Meeting adjourned at 11:34am EDT.)
