You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by Davanum Srinivas <da...@gmail.com> on 2005/06/03 22:04:49 UTC
Increasing cross project cooperation
Hi all,
Does anyone think that moving to a jakarta-commons/cocoon model where
there is a single ACL for all of web services will help? We can still
have separate release cycles for all projects., and each project can
have a list of active participants.
For example, i want the Axis/C++ folks (and the folks on
Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to
reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can
get everyone more involved (it's not too late yet!) now, it will ease
the pains of "porting" existing code to Axis2...and so on.
Basically, we will have 1 list on CVS/SVN with all web services
committers and all of them will have rw privileges on all CVS/SVN
modules. Existing committers who want to contribute to another sister
WS project can sign up in the list of active folks for that project
and help out with that project.
Yes, we are all scared of folks changing stuff willy-nilly. But it
just implies, we need to monitor changes more closely and work a bit
more on mentoring others on our code.
What do you all think?
Thanks,
dims
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Increasing cross project cooperation
Posted by Davanum Srinivas <da...@gmail.com>.
commits for commons stuff has been redirected to this mailing list :)
-- dims
On 6/6/05, Jongjin Choi <gu...@hotmail.com> wrote:
> Dims,
>
> It is a very good idea.
> WSDL2Java stuff is now included in axis, apllo, herms, muse, addressing.
> It is better if we can merge it to addressing, resource, notification, management,etc-enabled wsdl processor.
>
> One thing, is there any 'ws-common-cvs' mailing list to get a commit log?
>
> Thanks
>
> ----- Original Message -----
> From: "Davanum Srinivas" <da...@gmail.com>
> To: <ge...@ws.apache.org>
> Sent: Saturday, June 04, 2005 5:04 AM
> Subject: Increasing cross project cooperation
>
>
> Hi all,
>
> Does anyone think that moving to a jakarta-commons/cocoon model where
> there is a single ACL for all of web services will help? We can still
> have separate release cycles for all projects., and each project can
> have a list of active participants.
>
> For example, i want the Axis/C++ folks (and the folks on
> Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to
> reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can
> get everyone more involved (it's not too late yet!) now, it will ease
> the pains of "porting" existing code to Axis2...and so on.
>
> Basically, we will have 1 list on CVS/SVN with all web services
> committers and all of them will have rw privileges on all CVS/SVN
> modules. Existing committers who want to contribute to another sister
> WS project can sign up in the list of active folks for that project
> and help out with that project.
>
> Yes, we are all scared of folks changing stuff willy-nilly. But it
> just implies, we need to monitor changes more closely and work a bit
> more on mentoring others on our code.
>
> What do you all think?
>
> Thanks,
> dims
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Increasing cross project cooperation
Posted by Jongjin Choi <gu...@hotmail.com>.
Dims,
It is a very good idea.
WSDL2Java stuff is now included in axis, apllo, herms, muse, addressing.
It is better if we can merge it to addressing, resource, notification, management,etc-enabled wsdl processor.
One thing, is there any 'ws-common-cvs' mailing list to get a commit log?
Thanks
----- Original Message -----
From: "Davanum Srinivas" <da...@gmail.com>
To: <ge...@ws.apache.org>
Sent: Saturday, June 04, 2005 5:04 AM
Subject: Increasing cross project cooperation
Hi all,
Does anyone think that moving to a jakarta-commons/cocoon model where
there is a single ACL for all of web services will help? We can still
have separate release cycles for all projects., and each project can
have a list of active participants.
For example, i want the Axis/C++ folks (and the folks on
Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to
reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can
get everyone more involved (it's not too late yet!) now, it will ease
the pains of "porting" existing code to Axis2...and so on.
Basically, we will have 1 list on CVS/SVN with all web services
committers and all of them will have rw privileges on all CVS/SVN
modules. Existing committers who want to contribute to another sister
WS project can sign up in the list of active folks for that project
and help out with that project.
Yes, we are all scared of folks changing stuff willy-nilly. But it
just implies, we need to monitor changes more closely and work a bit
more on mentoring others on our code.
What do you all think?
Thanks,
dims
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Increasing cross project cooperation
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Davanum Srinivas wrote:
>Hi all,
>
>Does anyone think that moving to a jakarta-commons/cocoon model where
>there is a single ACL for all of web services will help? We can still
>have separate release cycles for all projects., and each project can
>have a list of active participants.
>
>For example, i want the Axis/C++ folks (and the folks on
>Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to
>reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can
>get everyone more involved (it's not too late yet!) now, it will ease
>the pains of "porting" existing code to Axis2...and so on.
>
>Basically, we will have 1 list on CVS/SVN with all web services
>committers and all of them will have rw privileges on all CVS/SVN
>modules. Existing committers who want to contribute to another sister
>WS project can sign up in the list of active folks for that project
>and help out with that project.
>
>Yes, we are all scared of folks changing stuff willy-nilly. But it
>just implies, we need to monitor changes more closely and work a bit
>more on mentoring others on our code.
>
>What do you all think?
>
>
i think it is very good idea (especially to be able to fix bugs
introduced when common code is changed) as long as we have well
documented how to run some regression testing (like unit tests)
thanks,
alek
--
The best way to predict the future is to invent it - Alan Kay
Re: Increasing cross project cooperation
Posted by Davanum Srinivas <da...@gmail.com>.
Sanjiva,
Yes, this is a direct result of Roy's email and off line discussions
with Noel. +1 to IRC as well.
-- dims
On 6/4/05, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> Hi Dims,
>
> Is this basically the same question Roy asked on incubator@ - whether
> the WS project should become one project or split into multiple TLPs?
>
> I'm very much in favor of keeping the WS-* projects together and to
> doing things to move the projects closer to each other. The question of
> course is how to do it.
>
> While I'm in favor of your suggestion of providing a common r/w perms
> mechanism, I'm not sure its enough. How about doing some active
> community building exercises? Let's start with a regularly scheduled IRC
> chat for all the WS committers. The first topic I suggest is an
> information exchange to let everyone know what the current cross-project
> dependencies are and maybe what they could be. Then we could talk about
> plans across projects and try to get interest from across the projects.
>
> Sanjiva.
>
> On Fri, 2005-06-03 at 16:04 -0400, Davanum Srinivas wrote:
> > Hi all,
> >
> > Does anyone think that moving to a jakarta-commons/cocoon model where
> > there is a single ACL for all of web services will help? We can still
> > have separate release cycles for all projects., and each project can
> > have a list of active participants.
> >
> > For example, i want the Axis/C++ folks (and the folks on
> > Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to
> > reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can
> > get everyone more involved (it's not too late yet!) now, it will ease
> > the pains of "porting" existing code to Axis2...and so on.
> >
> > Basically, we will have 1 list on CVS/SVN with all web services
> > committers and all of them will have rw privileges on all CVS/SVN
> > modules. Existing committers who want to contribute to another sister
> > WS project can sign up in the list of active folks for that project
> > and help out with that project.
> >
> > Yes, we are all scared of folks changing stuff willy-nilly. But it
> > just implies, we need to monitor changes more closely and work a bit
> > more on mentoring others on our code.
> >
> > What do you all think?
> >
> > Thanks,
> > dims
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Increasing cross project cooperation
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Hi Dims,
Is this basically the same question Roy asked on incubator@ - whether
the WS project should become one project or split into multiple TLPs?
I'm very much in favor of keeping the WS-* projects together and to
doing things to move the projects closer to each other. The question of
course is how to do it.
While I'm in favor of your suggestion of providing a common r/w perms
mechanism, I'm not sure its enough. How about doing some active
community building exercises? Let's start with a regularly scheduled IRC
chat for all the WS committers. The first topic I suggest is an
information exchange to let everyone know what the current cross-project
dependencies are and maybe what they could be. Then we could talk about
plans across projects and try to get interest from across the projects.
Sanjiva.
On Fri, 2005-06-03 at 16:04 -0400, Davanum Srinivas wrote:
> Hi all,
>
> Does anyone think that moving to a jakarta-commons/cocoon model where
> there is a single ACL for all of web services will help? We can still
> have separate release cycles for all projects., and each project can
> have a list of active participants.
>
> For example, i want the Axis/C++ folks (and the folks on
> Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to
> reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can
> get everyone more involved (it's not too late yet!) now, it will ease
> the pains of "porting" existing code to Axis2...and so on.
>
> Basically, we will have 1 list on CVS/SVN with all web services
> committers and all of them will have rw privileges on all CVS/SVN
> modules. Existing committers who want to contribute to another sister
> WS project can sign up in the list of active folks for that project
> and help out with that project.
>
> Yes, we are all scared of folks changing stuff willy-nilly. But it
> just implies, we need to monitor changes more closely and work a bit
> more on mentoring others on our code.
>
> What do you all think?
>
> Thanks,
> dims
Re: Increasing cross project cooperation
Posted by Davanum Srinivas <da...@gmail.com>.
Nirmal,
yes, we do have webservices/commons for that kind of code.
-- dims
On 6/3/05, Nirmal Mukhi <nm...@us.ibm.com> wrote:
>
> Hi,
>
> Why can't we just define a common project with r/w priveledges for all ws
> committers, with code like WSDL2Java etc., and have (mandate) all projects
> use that common code? That way we never have to be afraid of somebody
> accidentally touching code they have no business to mess with.
>
> Nirmal.
>
>
>
> Davanum Srinivas <da...@gmail.com>
>
> 06/03/2005 04:04 PM
> Please respond to general
> To: general@ws.apache.org
> cc:
> Subject: Increasing cross project cooperation
>
>
>
> Hi all,
>
> Does anyone think that moving to a jakarta-commons/cocoon model where
> there is a single ACL for all of web services will help? We can still
> have separate release cycles for all projects., and each project can
> have a list of active participants.
>
> For example, i want the Axis/C++ folks (and the folks on
> Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to
> reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can
> get everyone more involved (it's not too late yet!) now, it will ease
> the pains of "porting" existing code to Axis2...and so on.
>
> Basically, we will have 1 list on CVS/SVN with all web services
> committers and all of them will have rw privileges on all CVS/SVN
> modules. Existing committers who want to contribute to another sister
> WS project can sign up in the list of active folks for that project
> and help out with that project.
>
> Yes, we are all scared of folks changing stuff willy-nilly. But it
> just implies, we need to monitor changes more closely and work a bit
> more on mentoring others on our code.
>
> What do you all think?
>
> Thanks,
> dims
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Increasing cross project cooperation
Posted by Nirmal Mukhi <nm...@us.ibm.com>.
Hi,
Why can't we just define a common project with r/w priveledges for all ws
committers, with code like WSDL2Java etc., and have (mandate) all projects
use that common code? That way we never have to be afraid of somebody
accidentally touching code they have no business to mess with.
Nirmal.
Davanum Srinivas <da...@gmail.com>
06/03/2005 04:04 PM
Please respond to general
To: general@ws.apache.org
cc:
Subject: Increasing cross project cooperation
Hi all,
Does anyone think that moving to a jakarta-commons/cocoon model where
there is a single ACL for all of web services will help? We can still
have separate release cycles for all projects., and each project can
have a list of active participants.
For example, i want the Axis/C++ folks (and the folks on
Apollo/Hermes/Muse) to contribute to make WSDL2Java stuff better (to
reduce duplication of code now in WSDL2Ws). Now with Axis2, if we can
get everyone more involved (it's not too late yet!) now, it will ease
the pains of "porting" existing code to Axis2...and so on.
Basically, we will have 1 list on CVS/SVN with all web services
committers and all of them will have rw privileges on all CVS/SVN
modules. Existing committers who want to contribute to another sister
WS project can sign up in the list of active folks for that project
and help out with that project.
Yes, we are all scared of folks changing stuff willy-nilly. But it
just implies, we need to monitor changes more closely and work a bit
more on mentoring others on our code.
What do you all think?
Thanks,
dims
--
Davanum Srinivas - http://webservices.apache.org/~dims/