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

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-08-14
John: Jeremy has made some progress and hopes to have this completed 
shortly.


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-08-14
John: I'm about to post to the Apache WS list and will cross post a couple 
other relevant lists to try and solicit more information. Someone should 
know how Axis2 redistributes this jar.
Lawrence: It was suggested that we use the Geronimo StAX API but I don't 
think this is an option as Axis2 and Axiom use the StAX API and we don't 
know what kind of problems this will create.


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-08-14
Lawrence: I posted the skeleton doc last night.
Dan: I've started some documentation that I can contribute to this page.


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.
2007-08-14
John: Dan created a config file and written documentation on how to apply 
it, which will also go on the Web site. I'm going to review his writeup 
and then add it to the Web site.


2. Milestone 8 (M8) Status - John Kaputin

John: I've made a number of code changes over the last few days. I started 
working on the extension programming model but there are some more 
fundamental problems I need to fix first. I've introduced a WSDLContext 
object to share common objects.
Lawrence: Is the extension mechanism based on Eclipse?
John: It's based on Peter Danielson's contribution. A properties file is 
provided that lists the extension registrar classes. Once I have this done 
I'm going to implement the Eclipse extension registry as well.
Lawrence: Is there a reason we need both?
John: I need to look into the Eclipse registry more. Dan's got the Eclipse 
extension registry working standalone. I think it's best not to create an 
Eclipse dependency.
Lawrence: I don't think having a dependency on the Eclipse extension 
registry is a real hindrance. We can post to the dev list and ask the 
Woden community if there is any problem with this extension.
Dan: There is an OSGi dependency. We need to see whether we can use the 
extension registry without it. The 3 Equinox jars are roughly 300Kb. The 
OSGi jar is 900Kb.
John: We should follow up on the Equinox newsgroup to see if there's a way 
around this dependency.

John: I've applied and resolved most of Dan's Jiras.

John: I don't have a specific date for M8 yet.


3. Graduation from Incubation - Lawrence Mandel

We covered this section with the open action items.

4. Development Discussion - All

Lawrence: John, have you had a chance to take a look at Sagara's 
contribution.
John: Not yet.
Lawrence: Dan, perhaps you can take a look and provide a review now that 
you're somewhat familiar with the Woden codebase.
Dan: I won't be able to look at this until next Tuesday.
John: I'll let you know if I can get to it before then. If not, please 
review it.

Lawrence: We haven't made any progress on the assertions recently. I'll 
try and float a proposal for an interface on the dev list.
John: We previously discussed having assertion dependencies to avoid 
running unnecessary assertions.
Lawrence: And the interface can either be for a single assertion or for a 
group of assertions.


5. Other Business - All

John: I'm off the rest of the week.


Thanks,

Lawrence Mandel



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

Reply via email to