You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Sanjiva Weerawarana <sa...@opensource.lk> on 2006/03/22 06:47:46 UTC
RE: [Synapse]RE: CryptoFactory: Cannot
loadproperties:crypto.properties
On Wed, 2006-03-22 at 09:43 +0530, Soumadeep wrote:
> Sanjiva,
>
> 1) First of all let me emphasize that Mukund's statement and my response to
> Ruchith are no way related.
OK.
> 2) We work on the mediators and do a primary test before we commit it to the
> ASF repository.
That is not a good model for development in ASF long term; ASF is about
open development as well, not just about releasing software under the
Apache license. It is a viable model for bootstrap, but now that we have
bootstrapped, we must do all the work here.
Of course *it is perfectly viable* for Infravio or anyone else to build
their own add-ons and ship them in their products.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
RE: [Synapse]RE: CryptoFactory:Cannotloadproperties:crypto.properties
Posted by Soumadeep <so...@infravio.com>.
Sure Sanjiva :) , and putting it in the scratch is a good idea at least
people can comment on a concept and on acceptance we can put it in the main
code base.
-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
Sent: Wednesday, March 22, 2006 2:21 PM
To: synapse-dev@ws.apache.org
Cc: Ruchith Fernando
Subject: RE: [Synapse]RE:
CryptoFactory:Cannotloadproperties:crypto.properties
On Wed, 2006-03-22 at 11:48 +0530, Soumadeep wrote:
> One more thing that I would like to emphasize here is that I do agree that
> all the development should happen in the repo, but from a realistic stand
> point as you may agree one can't keep writing a line of code and keep
> committing it but surely the scratch area should be fine.
Come on Soumadeep you know I didn't mean that every line should be
committed. In fact there are times when I go days without committing
changes because I'm not happy with some stuff. However, the diff is
there's no other place where the code is committed in a shared repo; I
may keep it on my machine for however long but from day 0 its meant to
go to ASF and I keep committing when I feel its good and ready to
commit.
The only reason to commit to the scratch area instead of the main tree
is if the stuff is really "scratch" .. otherwise if the code is an
improvement to the main direction of the project it belongs in the main
tree.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
RE: [Synapse]RE: CryptoFactory:
Cannotloadproperties:crypto.properties
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Wed, 2006-03-22 at 11:48 +0530, Soumadeep wrote:
> One more thing that I would like to emphasize here is that I do agree that
> all the development should happen in the repo, but from a realistic stand
> point as you may agree one can't keep writing a line of code and keep
> committing it but surely the scratch area should be fine.
Come on Soumadeep you know I didn't mean that every line should be
committed. In fact there are times when I go days without committing
changes because I'm not happy with some stuff. However, the diff is
there's no other place where the code is committed in a shared repo; I
may keep it on my machine for however long but from day 0 its meant to
go to ASF and I keep committing when I feel its good and ready to
commit.
The only reason to commit to the scratch area instead of the main tree
is if the stuff is really "scratch" .. otherwise if the code is an
improvement to the main direction of the project it belongs in the main
tree.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
RE: [Synapse]RE: CryptoFactory: Cannotloadproperties:crypto.properties
Posted by Soumadeep <so...@infravio.com>.
Sanjiva,
Please see my comments inline
Best regards
Soumadeep
-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
Sent: Wednesday, March 22, 2006 11:18 AM
To: synapse-dev@ws.apache.org
Cc: Ruchith Fernando
Subject: RE: [Synapse]RE: CryptoFactory:
Cannotloadproperties:crypto.properties
On Wed, 2006-03-22 at 09:43 +0530, Soumadeep wrote:
> Sanjiva,
>
> 1) First of all let me emphasize that Mukund's statement and my response
to
> Ruchith are no way related.
OK.
> 2) We work on the mediators and do a primary test before we commit it to
the
> ASF repository.
That is not a good model for development in ASF long term; ASF is about
open development as well, not just about releasing software under the
Apache license. It is a viable model for bootstrap, but now that we have
bootstrapped, we must do all the work here.
[Soumadeep] Yes, I completely agree and that's why I added these points in
my earlier email
2) We work on the mediators and do a primary test before we commit it to the
ASF repository.
3) And whatever that we proposed (like Mukund's management related code
base or SynapseObject) are in the scratch already
4) The reason some of the mediators that we came up with didn't make it to
the repo yet is because of issues pertaining to data sharing between
mediators, and you are aware of the long thread about SynapseObject per se.
One more thing that I would like to emphasize here is that I do agree that
all the development should happen in the repo, but from a realistic stand
point as you may agree one can't keep writing a line of code and keep
committing it but surely the scratch area should be fine. And I reiterate
that we have no intention of putting mediators in one go but put a generic
structure to it and then let the community develop it. One can argue
endlessly on this but then just to put it in the right perspective we have
developed these features and have gone through several use cases with many
customers in a rigorous manner. Hence, apart from just the code we are also
sharing the knowledgebase so that we don't start re-inventing the wheel
again but maybe add to it. On a lighter note maybe add some good tiers to it
:)
Of course *it is perfectly viable* for Infravio or anyone else to build
their own add-ons and ship them in their products.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org