Oshani,
Europe and North America returned from daylight savings time last
weekend...the clocks went back 1 hour. The woden web site says the call is
at 11AM EST (US east coast time, which is now 1 hour later than last week),
but it also says UTC 15:00 (i.e. GMT 15:00 which has not changed). A bit
confusing! Anyway I'm going to try at 4pm my time (i.e. 4pm GMT).
John Kaputin
"Oshani
Seneviratne"
<[EMAIL PROTECTED] To
m> [email protected]
cc
31/10/2006 15:17
Subject
Re: Agenda of the Woden Status
Please respond to Telecon, 2006-10-31
[EMAIL PROTECTED]
he.org
Hi,
Is there no telecon today, or am I dialling the wrong numbers
(+1-866-245-5059, conf id 5823140#) ?
Oshani
On 10/31/06, Lawrence Mandel <[EMAIL PROTECTED]> wrote:
See [1] for call and IRC information.
[1] http://incubator.apache.org/woden/dev/index.html#Weekly+Status+Call
Agenda
1. Open Action Items - Lawrence Mandel
2006-09-12 - John, or others, review Graham's WODEN-14 patch
2006-09-26
Jeremy: I had a look. I spoke with Graham about putting a test together
so we can easily test this enhancement.
Graham: No update on the test yet.
2006-10-03
Graham: This patch has not been merged with head yet. Jeremy requested
that it only be merged once there was a test case. There is one
outstanding problem with the DOM parser. Once that is resolved I'll
provide a new patch.
2006-10-17
Lawrence: Has the patch been applied?
Graham: Not yet. There were a few conflicts with head so I have to rework
the patch again. The tests patch needs to be updated as well. This should
be done this week.
Lawrence: Jeremy, will you review and apply?
Jeremy: Yes. I'll continue to handle this.
2006-10-03 - John will check to see if there is a Jira open for
modularizing the build and open one if it doesn't exist.
2006-10-10
John: Woden-36 is about Mavenizing the build. It's not exactly
modularizing except this is required for Maven.
Arthur: Apparently you can run Ant tasks under Maven. Maven build scripts
have more structure. I don't think we should force all of our users onto
Maven. We should still support Ant.
John: I think we should have a separate Jira to ensure the build is
modularized properly then. I'll add a comment to the Jira about
modularizing the build and continuing to support Ant. I'll also follow up
with someone I know that may be interested in Mavenizing the Woden build.
2006-10-17
John: No update.
2006-10-03 - John will post to the dev list with information about
signing releases.
Note: Chinthaka posted the following link after the meeting:
http://wiki.apache.org/ws/FrontPage/Axis2/releases/steps
2006-10-10
John: No status.
2006-10-17
John: Chinthaka posted an Axis wiki page. I found an Apache page that
I'll post to the list.
Lawrence: Should we all have keys?
John: Yes. Every artifact that Apache distributes should be signed.
2006-10-03 - Graham will investigate any Apache process that needs to be
followed to bundle the W3C WSDL 2.0 schemas with Woden.
2006-10-17
Graham: I sent an e-mail to Dims to get some pointers. I haven't heard
back yet.
Jeremy: I've heard a response in the past to talk to legal-discuss. You
can also try [EMAIL PROTECTED]
2006-10-17 - Lawrence will add the FAQ link to the Woden site.
2006-10-17 - Lawrence will propose moving Woden's documentation to the
wiki.
2. Milestone (M7) Status - John Kaputin
3.Development Discussion - All
Chinthaka has asked to discuss Woden serialization.
4. Other Business - All
Question posted to the newsgroup by Chinthaka:
Maintaining a TODO list in a wiki so that new comers can pick up
tasks from them.
Question posted to the newsgroup by Chinthaka:
More documentation on Woden. This will be a JIRA, but I'd like to
discuss a bit about this with the devs about their plans.
Question posted to the newsgroup by Chinthaka:
What role should Axis2 play in the upcoming WSDL 2.0 interop. I'd like to
talk about things that we are thinking of covering, which involves Axis2,
so that Axis2 team can be ready to get the maximum out of the interop.
Perhaps this discussion can be extended to the next implementors call as
well.
Thanks,
Lawrence Mandel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
