Re: [VOTE] [Proposal] WS-Commons transports project

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I agree in priniciple/theory. But IMHO, it won't work because folks who are directly involved in day-to-day efforts on
this do not agree and even if they do right now, we will back to square one in a few months one way or another.

So my VOTE is +0 as this is not practically workable.

thanks,
dims

Sanjaya Karunasena wrote:
| I am +1 for this. In terms of seperation of concerns this make lot of since.
|
| /Sanjaya
|
| On Wednesday 23 April 2008, Glen Daniels wrote:
|> [ Please refer to this thread for context :
|>    http://markmail.org/message/lg3giq5kj74gjnxb
|> ]
|>
|>
|> OK, let me make a concrete proposal here.
|>
|> I hereby propose that we kick off a ws-commons "transports" project.  As
|> with the other ws-commons projects, this would have its own release
|> schedule.  All current ws-all committers would have commit rights, and
|> we'd add anyone from the Synapse team that would like to work on
|> transports, and isn't already a committer.
|>
|> Each transport within ws-commons Transports would be a separate
|> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and each
|> such transport would be releasable on its own with an appropriate VOTE
|> of the ws-commons committers.
|>
|> We'd use commons-dev and commons-user mailing lists as per usual for
|> communication, and SVN would be
|> webservices/commons/trunk/modules/transports.
|>
|> We'd get started by moving whichever transports in Axis2 and Synapse are
|> appropriate into the new source tree.
|>
|> Here's my +1.  Please comment / VOTE at will.
|>
|> --Glen
|>
|> ---------------------------------------------------------------------
|> To unsubscribe, e-mail: [email protected]
|> For additional commands, e-mail: [email protected]
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFIDoA8gNg6eWEDv1kRArHmAKDpA6NGXu9lY/oiGPutHI+x8r1R9wCgn7wu
VwngzO1z0zLOVRTvVL61Q9Y=
=0zQ5
-----END PGP SIGNATURE-----