You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Nicola Ken Barozzi <ni...@apache.org> on 2002/10/24 11:41:49 UTC
[PROPOSAL] Avalon Component repository in Apache Commons
Dear Avalon and Turbine Community,
following prior discussions I had with you, I'm writing here to make
a proposal about a common codespace.
Turbine services will most probably become Avalon Components/Services
(C/S), and Avalon already has a lot of them too: currently they are in
Cornerstone and Excalibur.
Using a common framework will bring us closer, and will make it possible
for us to _finally_ share code in terms of C/S.
As history has showed me, external projects that use Avalon Components
are happy to be able to offload their maintainance, but this is only
when all works well... I'm sure that many users of these components
would be happy to be involved more directly in the management of their code.
I think that if Turbine devs could interact more directly with the code
of existing Avalon C/S they would use _them_ instead of making another
version. Likewise for Avalon devs.
Thus I propose that we create our dev-space about Avalon-based C/S
inside the new Apache Commons Project, and be able to share commit
privileges between our committers on a per-component basis.
This is to enable collaboration without the fear that yet-unknown
committers will step all over our code.
This has been already proposed on the Apache Commons list and seems ok.
If you want to partecipate in a common discussion about this:
general-subscribe@commons.apache.org
Thank you.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [PROPOSAL] Avalon Component repository in Apache Commons
Posted by Colin Chalmers <co...@maxware.nl>.
I'm not a comitter but in general I see that this could be a positive step
for both communities. May also help to move Turbine onto it's next phase.
/colin
----- Original Message -----
From: "Nicola Ken Barozzi" <ni...@apache.org>
To: "Avalon Developers List" <av...@jakarta.apache.org>; "Turbine
Developers List" <tu...@jakarta.apache.org>
Sent: Thursday, October 24, 2002 11:41 AM
Subject: [PROPOSAL] Avalon Component repository in Apache Commons
> Dear Avalon and Turbine Community,
>
> following prior discussions I had with you, I'm writing here to make
> a proposal about a common codespace.
>
> Turbine services will most probably become Avalon Components/Services
> (C/S), and Avalon already has a lot of them too: currently they are in
> Cornerstone and Excalibur.
>
> Using a common framework will bring us closer, and will make it possible
> for us to _finally_ share code in terms of C/S.
>
> As history has showed me, external projects that use Avalon Components
> are happy to be able to offload their maintainance, but this is only
> when all works well... I'm sure that many users of these components
> would be happy to be involved more directly in the management of their
code.
>
> I think that if Turbine devs could interact more directly with the code
> of existing Avalon C/S they would use _them_ instead of making another
> version. Likewise for Avalon devs.
>
> Thus I propose that we create our dev-space about Avalon-based C/S
> inside the new Apache Commons Project, and be able to share commit
> privileges between our committers on a per-component basis.
> This is to enable collaboration without the fear that yet-unknown
> committers will step all over our code.
>
> This has been already proposed on the Apache Commons list and seems ok.
>
> If you want to partecipate in a common discussion about this:
>
> general-subscribe@commons.apache.org
>
> Thank you.
>
> --
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [PROPOSAL] Avalon Component repository in Apache Commons
Posted by Stephen McConnell <mc...@apache.org>.
Hi Nocolas:
A repository for reusable components outside of the Avalon domain is in
my opinion a wonderful objective. While there is the question of
component portability across containers, there is also a clear cut case
of container indepedent components that exist today. One of the reasons
why I find this exciting is that it rreally drives at the question of
"what is a component" and reinforces the priority concerning the
delivery of components that are deployable across a number of different
environments. It forces us (Avalon) to look inwards and say to
ourselves - "how can we refector differences in container functionlities
to achieve portability".
I've just subscribed to the list and look forward further discussion on
the topic.
Cheers, Steve.
Nicola Ken Barozzi wrote:
> Dear Avalon and Turbine Community,
>
> following prior discussions I had with you, I'm writing here to make
> a proposal about a common codespace.
>
> Turbine services will most probably become Avalon Components/Services
> (C/S), and Avalon already has a lot of them too: currently they are in
> Cornerstone and Excalibur.
>
> Using a common framework will bring us closer, and will make it
> possible for us to _finally_ share code in terms of C/S.
>
> As history has showed me, external projects that use Avalon Components
> are happy to be able to offload their maintainance, but this is only
> when all works well... I'm sure that many users of these components
> would be happy to be involved more directly in the management of their
> code.
>
> I think that if Turbine devs could interact more directly with the
> code of existing Avalon C/S they would use _them_ instead of making
> another version. Likewise for Avalon devs.
>
> Thus I propose that we create our dev-space about Avalon-based C/S
> inside the new Apache Commons Project, and be able to share commit
> privileges between our committers on a per-component basis.
> This is to enable collaboration without the fear that yet-unknown
> committers will step all over our code.
>
> This has been already proposed on the Apache Commons list and seems ok.
>
> If you want to partecipate in a common discussion about this:
>
> general-subscribe@commons.apache.org
>
> Thank you.
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [PROPOSAL] Avalon Component repository in Apache Commons
Posted by Stephen McConnell <mc...@apache.org>.
Hi Nocolas:
A repository for reusable components outside of the Avalon domain is in
my opinion a wonderful objective. While there is the question of
component portability across containers, there is also a clear cut case
of container indepedent components that exist today. One of the reasons
why I find this exciting is that it rreally drives at the question of
"what is a component" and reinforces the priority concerning the
delivery of components that are deployable across a number of different
environments. It forces us (Avalon) to look inwards and say to
ourselves - "how can we refector differences in container functionlities
to achieve portability".
I've just subscribed to the list and look forward further discussion on
the topic.
Cheers, Steve.
Nicola Ken Barozzi wrote:
> Dear Avalon and Turbine Community,
>
> following prior discussions I had with you, I'm writing here to make
> a proposal about a common codespace.
>
> Turbine services will most probably become Avalon Components/Services
> (C/S), and Avalon already has a lot of them too: currently they are in
> Cornerstone and Excalibur.
>
> Using a common framework will bring us closer, and will make it
> possible for us to _finally_ share code in terms of C/S.
>
> As history has showed me, external projects that use Avalon Components
> are happy to be able to offload their maintainance, but this is only
> when all works well... I'm sure that many users of these components
> would be happy to be involved more directly in the management of their
> code.
>
> I think that if Turbine devs could interact more directly with the
> code of existing Avalon C/S they would use _them_ instead of making
> another version. Likewise for Avalon devs.
>
> Thus I propose that we create our dev-space about Avalon-based C/S
> inside the new Apache Commons Project, and be able to share commit
> privileges between our committers on a per-component basis.
> This is to enable collaboration without the fear that yet-unknown
> committers will step all over our code.
>
> This has been already proposed on the Apache Commons list and seems ok.
>
> If you want to partecipate in a common discussion about this:
>
> general-subscribe@commons.apache.org
>
> Thank you.
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [PROPOSAL] Avalon Component repository in Apache Commons
Posted by Colin Chalmers <co...@maxware.nl>.
I'm not a comitter but in general I see that this could be a positive step
for both communities. May also help to move Turbine onto it's next phase.
/colin
----- Original Message -----
From: "Nicola Ken Barozzi" <ni...@apache.org>
To: "Avalon Developers List" <av...@jakarta.apache.org>; "Turbine
Developers List" <tu...@jakarta.apache.org>
Sent: Thursday, October 24, 2002 11:41 AM
Subject: [PROPOSAL] Avalon Component repository in Apache Commons
> Dear Avalon and Turbine Community,
>
> following prior discussions I had with you, I'm writing here to make
> a proposal about a common codespace.
>
> Turbine services will most probably become Avalon Components/Services
> (C/S), and Avalon already has a lot of them too: currently they are in
> Cornerstone and Excalibur.
>
> Using a common framework will bring us closer, and will make it possible
> for us to _finally_ share code in terms of C/S.
>
> As history has showed me, external projects that use Avalon Components
> are happy to be able to offload their maintainance, but this is only
> when all works well... I'm sure that many users of these components
> would be happy to be involved more directly in the management of their
code.
>
> I think that if Turbine devs could interact more directly with the code
> of existing Avalon C/S they would use _them_ instead of making another
> version. Likewise for Avalon devs.
>
> Thus I propose that we create our dev-space about Avalon-based C/S
> inside the new Apache Commons Project, and be able to share commit
> privileges between our committers on a per-component basis.
> This is to enable collaboration without the fear that yet-unknown
> committers will step all over our code.
>
> This has been already proposed on the Apache Commons list and seems ok.
>
> If you want to partecipate in a common discussion about this:
>
> general-subscribe@commons.apache.org
>
> Thank you.
>
> --
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>