Attendees: Lawrence Mandel, John Kaputin
Regrets: Arthur Ryman, Dan Harvey

Minutes

1. Open Action Items - Lawrence Mandel

2007-05-22 - John will follow up with Jeremy about the copyright question 
in the status file.
2007-06-19
John: Jeremy was following up to ensure the paperwork for our WSDL4J 
contribution was done. It's with IBM legal now. I'll follow up next week.
2007-06-26
John: I spoke to Jeremy last Tuesday. He's going to confirm that the 
paperwork from IBM's perspective are complete.
2007-07-10
John: I spoke with Jeremy today. He couldn't get a hold of the legal 
counsel yet. I'll hopefully have an answer for next week.
2007-07-17
John: Jeremy still hasn't got a response.
Lawrence: I spoke with the Apache secretary through e-mail. If we haven't 
copied any WSDL4J code we may not need an agreement.
John: I think we copied some of the common utility code so we should get 
this agreement in place.
2007-08-07
John: I spoke to Jeremy last week. He still doesn't have an answer yet.


2007-07-10 - John will look at CodeHaus to try and find the license for 
the Woodstox jar.
2007-07-17
John: The problem is with the API jar not the wstx jar. I reported this 
problem on the latest WS board report.
Lawrence: There are a couple options. We can follow up with Axiom to see 
if they've done the due diligence for this library. Two, we can try to 
move to the Geronimo StAX API but in this case we'll need to ensure Axiom 
plays well with the Geronimo API.
2007-08-07
John: No progress yet. I'm going to follow up with the Woodstox and Axiom 
projects to see what they've done to reconcile the license.


2007-05-22 - John will document the Woden decision making and development 
processes on the Woden site.
2007-06-19
John: No progress.
2007-06-26
John: I'll revisit this in another week after I'm made some further 
progress on the Woden extensions.
2007-07-10
John: No progress.
2007-07-17
John: No progress. I don't think I'll have a chance to take care of this 
action this week.
2007-08-07
John: No progress. I think what's needed here is what a new developer 
would need to get involved. Using Jira and the mailing list. Using the W3C 
test suite. Open development. Milestones. I haven't had a chance to look 
at the Apache documentation to see what exactly is required.
Lawrence: I'll look at the requirements and put up a skeleton document 
that we can all work to fill in.


2007-07-10 - John will follow up with Jeremy to make the change in SVN for
EOL.
2007-07-17
John: I haven't spoken with Jeremy yet. I had a look at the subclipse 
client to figure out how to set the property. I haven't found the way yet.
2007-08-07
John: Dan has uploaded some patches to a Jira that he'll review with me 
tomorrow. It looks like we'll need to configure each subversion client so 
this is something each developer will have to do. We may need to capture 
this in the process document.


2. Milestone 8 (M8) Status - John Kaputin

John: Dan's been working on 9 Jiras. I've been working closely with him. 
I've committed the code for 5 of the Jiras and there are 2 more that are 
about ready to close. We're now at 28 issues open for M8 down from 40. I'm 
working on 4 Jiras to do with extensions. After these are done we can 
address the bulk of the Jiras to do with assertions. I don't know what 
date we can hit for M8 but I think we're now looking at the last two weeks 
of Aug.

John: Dan's implemented toString with fragid. He should upload the patch 
to Jira shortly.


3. Graduation from Incubation - Lawrence Mandel

Lawrence: We covered this with the open actions.


4. Development Discussion - All

John: Sagara is back and working on serialization. I think he's working on 
an old Woden base. I need to check.
Lawrence: We need to encourage Sagara to start to work with the Woden 
process keeping up communication on the woden-dev list and posting to 
Jira. We should also get him to sign an ICLA.


5. Other Business - All

Thanks to Graham for acting as the release manager for the M7b release.


Thanks,

Lawrence Mandel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to