OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ws-caf-implement message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ws-caf-implement] WS-CAF Implementation Plan

OK, but I still think we need to decide exactly what we're going to produce,
if anything.


----- Original Message -----
From: "John Fuller" <jfuller@wernervas.com>
To: "Mark Little" <mark.little@arjuna.com>
Cc: <ws-caf-implement-chair@lists.oasis-open.org>;
<ws-caf-implement@lists.oasis-open.org>; "malik saheb"
<malik.saheb@arjuna.com>; <krishna@inventicasystems.com>
Sent: Wednesday, December 17, 2003 12:37 PM
Subject: Re: [ws-caf-implement] WS-CAF Implementation Plan

> I guess as my suggestion goes, I was imagining someone like Malik could
> set up a sourceforge project
> (and sourceforge.net would be the host) sort of like I did at
> http://sourceforge.net/projects/easywsrm/
> http://sourceforge.net/projects/easyasap/
> and Jeffrey Ricker did at
> http://sourceforge.net/projects/axisasap/
> and grant developers administrative permissions.
> It's free, public, you can move whatever you want into the file
> releases if you have administrative rights, etc.  So I could move in
> C++ for that package, others could move in their Java and we could also
> put our working documents out there.  It does support CVS, but you
> don't need to use it.
> ***
> Another alternative I suppose would be a yahoo group like boost C++
> uses for its files at
> http://groups.yahoo.com/group/boost/files/
> This would make the work public just to those in the group.
> On Dec 17, 2003, at 2:25 AM, Mark Little wrote:
> > It's worth considering, but who'd host it?
> >
> > Also, are we actually going to provide a single demo implementation (or
> > implementations depending on the coding language) or just a
> > model/definition
> > that each individual member can code against? There are pros and cons
> > of
> > both approaches.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]