You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Jeremy Hughes <hu...@apache.org> on 2009/09/01 16:38:49 UTC

[PROPOSAL] Apache Aries incubator for Enterprise OSGi

Hi, we would like to propose a new incubator podling called Aries.

http://wiki.apache.org/incubator/AriesProposal

Here is a quick summary of the proposal

The Aries project will deliver a set of pluggable Java components
enabling an enterprise OSGi application programming model. This
includes implementations and extensions of application-focused
specifications defined by the OSGi Alliance Enterprise Expert Group
(EEG) and an assembly format for multi-bundle applications, for
deployment to a variety of OSGi based runtimes.

Aries aims to build a community of developers interested in the
definition and delivery of software components that support an
enterprise OSGi programming model and which can be integrated into a
number of different runtime environments.

We appreciate any feedback and comments on the proposal.

Here is a plain text copy of the whole proposal:

Apache Aries
Abstract

The Aries project will deliver a set of pluggable Java components
enabling an enterprise OSGi application programming model. This
includes implementations and extensions of application-focused
specifications defined by the OSGi Alliance Enterprise Expert Group
(EEG) and an assembly format for multi-bundle applications, for
deployment to a variety of OSGi based runtimes.
Proposal

It is a goal of the Aries project to provide a natural home for open
source implementations of current and future OSGi EEG specifications,
including the opportunity for the collaborative development of
compliance tests, and an environment to demonstrate the composition of
these technologies and to explore areas where EEG specifications lack
coverage. A further goal of this project is to leverage experience
gained from it to inform contributions to OSGi EEG requirements and
specification documents.

Aries will offer an enterprise OSGi application programming model that
enables applications to leverage Java EE and other enterprise
technologies and to benefit from the modularity, dynamism and
versioning capabilities of OSGi. A significant feature of Aries will
be a container for OSGi Blueprint components - an implementation of
the new OSGi v4.2 Blueprint component model that defines a standard
dependency injection mechanism for Java components, which is derived
from the Spring framework and extended for OSGi to declaratively
register component interfaces as services in the OSGi service
registry.

In addition, the Aries project will develop a model for assembling an
application/subsystem into a deployable unit, consisting of multiple
bundles, as an archive which may include metadata that describes the
version and external location of the application's constituent bundles
or which may contain the bundles directly.

The Aries project will deliver run-time componentry that supports
applications, running in an OSGi framework, exploiting enterprise Java
technologies common in web applications and integration scenarios
including web application bundles, remote services integration and
JPA. The project is not expected to deliver a complete application or
integration server runtime but will instead deliver enterprise
application componentry that can be integrated into such runtimes. The
project will develop extensions that go beyond the OSGi EEG
specifications to provide a more complete integration of OSGi
modularity with Java enterprise technologies, in particular delivering
support that includes but is not restricted to:

   * isolated enterprise applications composed of multiple, versioned
bundles with dynamic lifecycle.
   * declarative transactions and security for Blueprint components
   * Container-managed JPA for Blueprint components
   * Message-driven Blueprint components
   * Configuration of resource references in module blueprints.
   * Annotation-based Blueprint configuration
   * Federation of lookup mechanisms between local JNDI and the OSGi
service registry.
   * Fully declarative application metadata to enable reflection of
an SCA component type definition.

In order to maximise the potential scope of Aries adoption it is
anticipated the project will remain agnostic of a number of
complementary technologies and projects. It is the expectation that
Aries will therefore not be delivering components such as: an
application or integration server runtime kernel; a persistence
provider; distribution provider; a deployment provider or a Web
container. Aries will instead seek to enable the use of such
components from other projects.
Background

OSGi is a mature and Java modularity technology that is well-used in
many environments but, in the enterprise space, has more typically
been exploited by the internals of the runtime infrastructure than the
applications that run on it. This is primarily because of a lack of a
clear enterprise OSGi application programming model and implementation
of OSGi-enabled Java technology to support enterprise applications.
OSGi specifications are specified and maintained by the OSGi Alliance
which recognized this state of affairs several years ago and
established the Enterprise Expert Group within the Alliance to focus
specifically on the needs of enterprise applications. The objective of
this project is to deliver open source implementations of these
application-centric technologies to enable the development of
application components, benefiting from the modularity of OSGi
combined with standards-based programming models, which can be
deployed to a variety of target runtimes.
Rationale

Aries aims to build a community of developers interested in the
delivery of software components that support an enterprise OSGi
programming model and which can be integrated into a number of
different runtime environments. Apache hosts the Felix project which
provides an OSGi framework implementation and a variety of projects
which provide technologies exploited by enterprise application
components as well as projects which provide runtimes to host
application components. There is currently no Apache project focussed
on OSGi enterprise applications that is independent from both the OSGi
framework and the enterprise runtime environment in which application
components are hosted. By maintaining independence of both the target
runtime and underlying OSGi framework it is our intention to build the
broadest possible community of developers for Aries, and to maximize
the potential environments where Aries componentry can be used.
Initial Goals

We will initially focus on the Blueprint container and extend this
with enterprise features such as support for container managed JPA and
container managed transactions. Another initial focus area will be the
contribution of code to support the assembly of isolated, multi-bundle
applications that can be deployed as a unit.
Current Status
Meritocracy

The Aries contributors recognize the desirability of running the
project as a meritocracy. We are eager to engage other members of the
community and operate to the standard of meritocracy that Apache
emphasizes; we believe this is the most effective method of growing
our community and enabling widespread adoption.
Community

OSGi is a mature Java modularity technology that is well-used in many
environments but, in the enterprise space, has more typically been
exploited by the internals of the runtime infrastructure than the
applications that run on it. This is primarily because of a lack of a
clear enterprise OSGi application programming model and implementation
of OSGi-enabled Java technology to support enterprise applications.
There is a need for open source implementations of these technologies
and there is currently no Apache project focused on the wider goal of
delivering components for an enterprise OSGi application programming
model. Aries aims to build a community of developers interested in the
definition and delivery of software components that support an
enterprise OSGi programming model and which can be integrated into a
number of different runtime environments. By maintaining independence
of both the target runtime and underlying OSGi framework it is our
intention to build the broadest possible community of developers.
Alignment

The purpose of Aries is to develop implementations of
application-centric enterprise OSGi technologies that run on an OSGi
framework, but not a specific one, and are used by application
components deployed into a variety of runtime environments without
being tied to any specific environment. For this reason we believe
Aries is a project whose community would be best served if it could
leverage but be independent from the communities that provide
underlying OSGi framework technology and enterprise application server
and integration bus technologies, all of which exist as open source
efforts within Apache and elsewhere. We expect, for example, that some
code developed in Aries will run directly on top of an OSGi framework
such as Felix and that applications exploiting Aries technologies
could be deployed to runtimes such as ServiceMix and Geronimo.
Avoiding the Warning Signs
Orphaned products

The contributors are leading vendors of OSGi-based technologies and
have a long standing in the OSGi Alliance whose application-centric
specifications this project will implement. There is minimal risk of
this work becoming non-strategic and the contributors are confident
that a larger community will form within the project in a relatively
short space of time.
Inexperience with Open Source

Many of the committers have experience working in one or more open
source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
and CXF.

Homogeneous Developers

The list of initial committers, geographically distributed across the
U.S. and Europe, consists of developers from two companies - IBM and
Progress software - with similar goals but for different scenarios.
Many of these developers are experienced Apache committers already and
all are experienced with working in distributed development
communities. It is our hope that, through the incubator, further
contributors with a broad background of experience but common interest
in enterprise OSGi technologies will become involved with this
project.

Relationships with Other Apache Projects

Aries will have a potential relationship with the Apache projects
listed in this section. These projects all serve different purposes
from Aries and have their own communities. It is hoped that each of
these communities will become involved with Aries and help to build a
diverse but independent Aries community.

Apache Felix Karaf -
http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
Karaf is an OSGi based runtime which provides a lightweight container
onto which various components and applications can be deployed. It is
related to Aries:

  1. as a target OSGi based runtime to which Aries applications can
be deployed. In this role, Karaf is a consumer of Aries technology.

Apache Felix - http://felix.apache.org/site/index.html Apache
Felix is primarily a core OSGi framework implementation. It is related
to Aries:

  1. as an underlying OSGi framework implementation and potentially
other extensions that can be used both by Aries run-time components
and the applications which use them.

Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
a server runtime framework and fully certified Java EE 5 application
server runtime. It is related to Aries in two ways:

  1. as a target runtime to which Aries applications can be deployed.
In this role, Geronimo is a consumer of Aries technology.
  2. the Geronimo blueprint sandbox -
http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
an implementation of the OSGi Blueprint container which will be moved
to Aries.

Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
provides a comprehensive infrastructure for SOA development and
management that is based on Service Component Architecture (SCA)
standard. It can be a consumer of Aries technology to provide an Aries
SCA implementation type for composing Aries applications in coarse
grained and potentially heterogeneous service assemblies.

Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
Web Services framework for distributed computing and remote service
realization and invocation using API's such as JAX-WS and JAX-RS. It
also provides the OSGi Remote Services (OSGi RFC 119) reference
implementation in a subproject:
http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
the following way:

  1. As Remote Services is a significant Enterprise specification
being produced by the EEG, it is expected that consumers of Aries will
be looking for an implementation of this specification. CXF provides
an implementation of this specification which already has a
significant active community. The Aries project will make it easy for
Aries consumers to consume the CXF Remote Services implementation,
possibly by providing an instance of the application model that
references the CXF Remote Services implementation. This would mean
that end users will seamlessly pull in the required components from
CXF by using the Aries-provided definition.

Apache ServiceMix - http://servicemix.apache.org/ Apache
ServiceMix provides an ESB that combines the functionality of a
Service Oriented Architecture (SOA) and Event Driven Architecture
(EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
source of the Apache Felix Karaf runtime. It can be a consumer of
Aries applications and associated componentry as a natural evolution
of its existing Karaf "feature" usage.

Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
Java persistence project. It is related to Aries as a JPA persistence
provider, including entity scanning and enhancement. The Aries project
will make it easy for JPA persistence providers such as OpenJPA to be
used in an OSGi environment and will provide container managed
persistence for the Blueprint container.

Documentation

An early draft of OSGi v4.2 core and compendium specifications - which
includes the Blueprint container specification - is available at:
http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
Initial Source

   * The Blueprint container impl from the Geronimo sandbox will be
moved to the Aries project for further development:
http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
   * IBM will also contribute code for:
         o container-managed JPA support in an OSGi environment.
         o making OSGi services visible to Java EE components through JNDI.
         o packaging web components as bundles and a URL handler for
recognizing and converting non-bundled Web components
   * We will also be soliciting implementations of other OSGi
enterprise application-centric specifications.

External Dependencies

   * Apache Ant http://ant.apache.org Apache License
   * Apache Commons http://commons.apache.org Apache License
   * Junit (Java unit test framework) http://junit.sourceforge.net CPL
v1.0 license: http://junit.sourceforge.net/cpl-v10.html
   * Apache Felix (implementation of the OSGi Core and Compendium
specifications - compliance level unknown) http://felix.apache.org
Apache License (hosted by ASF).
   * Eclipse Equinox (compliant implementation of the OSGi Core
Specification and Compendium specifications)
http://eclipse.org/equinox/ Eclipse Public License
   * OpenJPA http://openjpa.apache.org Apache License
   * Serp http://serp.sourceforge.net/ BSD
   * Apache Geronimo http://geronimo.apache.org Apache License

Required Resources
Mailing lists

aries-private (with moderated subscriptions)
aries-dev
aries-commits
aries-user

Subversion Directory

http://svn.apache.org/repos/asf/incubator/aries

Issue Tracking

JIRA (ARIES)

Web Site

Confluence (Aries)

Initial Committers

Names of initial committers with affiliation and current ASF status:

   * Alasdair Nottingham (IBM)
   * Andrew Osborne (IBM)
   * Dan Kulp (Progress, ASF member)
   * David Bosschaert (Progress, ASF committer)
   * David Jencks (IBM, ASF member)
   * Eoghan Glynn (Progress, ASF committer)
   * Graham Charters (IBM)
   * Guillaume Nodet (Progress, ASF member)
   * Hiram Chirino (Progress, ASF member)
   * Ian Robinson (IBM)
   * James Strachan (Progress, ASF member)
   * Jarek Gawor (IBM, ASF member)
   * Jeremy Hughes (IBM, ASF committer)
   * Joe Bohn (IBM, ASF committer)
   * Lin Sun (IBM, ASF committer)
   * Mark Nuttall (IBM)
   * Oisin Hurley (Progress)
   * Rick McGuire (IBM, ASF committer)
   * Sergey Beryozkin (Progress, ASF committer),
   * Timothy Ward (IBM)
   * Valentin Mahrwald (IBM)
   * Zoe Slattery (IBM)

Affiliations

The majority of the initial committers are employed by IBM corp or
Progress Software. One objective of the incubator is to attract a
diverse community of contributors and we anticipate future
contributors to have other affiliations.

Sponsors
Champions

Kevan Miller, Guillaume Nodet

Nominated Mentors

Guillaume Nodet, Davanum Srinivas (Dims)

Sponsoring Entity

The incubator. Successful graduation from Incubator should result in
Aries becoming a new TLP.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Fwd: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
This might be interesting to Geronimo and Felix communities.
Any further discussion should happen on general@incubator.apache.org

---------- Forwarded message ----------
From: Jeremy Hughes <hu...@apache.org>
Date: Tue, Sep 1, 2009 at 16:38
Subject: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
To: general@incubator.apache.org


Hi, we would like to propose a new incubator podling called Aries.

http://wiki.apache.org/incubator/AriesProposal

Here is a quick summary of the proposal

The Aries project will deliver a set of pluggable Java components
enabling an enterprise OSGi application programming model. This
includes implementations and extensions of application-focused
specifications defined by the OSGi Alliance Enterprise Expert Group
(EEG) and an assembly format for multi-bundle applications, for
deployment to a variety of OSGi based runtimes.

Aries aims to build a community of developers interested in the
definition and delivery of software components that support an
enterprise OSGi programming model and which can be integrated into a
number of different runtime environments.

We appreciate any feedback and comments on the proposal.

Here is a plain text copy of the whole proposal:

Apache Aries
Abstract

The Aries project will deliver a set of pluggable Java components
enabling an enterprise OSGi application programming model. This
includes implementations and extensions of application-focused
specifications defined by the OSGi Alliance Enterprise Expert Group
(EEG) and an assembly format for multi-bundle applications, for
deployment to a variety of OSGi based runtimes.
Proposal

It is a goal of the Aries project to provide a natural home for open
source implementations of current and future OSGi EEG specifications,
including the opportunity for the collaborative development of
compliance tests, and an environment to demonstrate the composition of
these technologies and to explore areas where EEG specifications lack
coverage. A further goal of this project is to leverage experience
gained from it to inform contributions to OSGi EEG requirements and
specification documents.

Aries will offer an enterprise OSGi application programming model that
enables applications to leverage Java EE and other enterprise
technologies and to benefit from the modularity, dynamism and
versioning capabilities of OSGi. A significant feature of Aries will
be a container for OSGi Blueprint components - an implementation of
the new OSGi v4.2 Blueprint component model that defines a standard
dependency injection mechanism for Java components, which is derived
from the Spring framework and extended for OSGi to declaratively
register component interfaces as services in the OSGi service
registry.

In addition, the Aries project will develop a model for assembling an
application/subsystem into a deployable unit, consisting of multiple
bundles, as an archive which may include metadata that describes the
version and external location of the application's constituent bundles
or which may contain the bundles directly.

The Aries project will deliver run-time componentry that supports
applications, running in an OSGi framework, exploiting enterprise Java
technologies common in web applications and integration scenarios
including web application bundles, remote services integration and
JPA. The project is not expected to deliver a complete application or
integration server runtime but will instead deliver enterprise
application componentry that can be integrated into such runtimes. The
project will develop extensions that go beyond the OSGi EEG
specifications to provide a more complete integration of OSGi
modularity with Java enterprise technologies, in particular delivering
support that includes but is not restricted to:

   * isolated enterprise applications composed of multiple, versioned
bundles with dynamic lifecycle.
   * declarative transactions and security for Blueprint components
   * Container-managed JPA for Blueprint components
   * Message-driven Blueprint components
   * Configuration of resource references in module blueprints.
   * Annotation-based Blueprint configuration
   * Federation of lookup mechanisms between local JNDI and the OSGi
service registry.
   * Fully declarative application metadata to enable reflection of
an SCA component type definition.

In order to maximise the potential scope of Aries adoption it is
anticipated the project will remain agnostic of a number of
complementary technologies and projects. It is the expectation that
Aries will therefore not be delivering components such as: an
application or integration server runtime kernel; a persistence
provider; distribution provider; a deployment provider or a Web
container. Aries will instead seek to enable the use of such
components from other projects.
Background

OSGi is a mature and Java modularity technology that is well-used in
many environments but, in the enterprise space, has more typically
been exploited by the internals of the runtime infrastructure than the
applications that run on it. This is primarily because of a lack of a
clear enterprise OSGi application programming model and implementation
of OSGi-enabled Java technology to support enterprise applications.
OSGi specifications are specified and maintained by the OSGi Alliance
which recognized this state of affairs several years ago and
established the Enterprise Expert Group within the Alliance to focus
specifically on the needs of enterprise applications. The objective of
this project is to deliver open source implementations of these
application-centric technologies to enable the development of
application components, benefiting from the modularity of OSGi
combined with standards-based programming models, which can be
deployed to a variety of target runtimes.
Rationale

Aries aims to build a community of developers interested in the
delivery of software components that support an enterprise OSGi
programming model and which can be integrated into a number of
different runtime environments. Apache hosts the Felix project which
provides an OSGi framework implementation and a variety of projects
which provide technologies exploited by enterprise application
components as well as projects which provide runtimes to host
application components. There is currently no Apache project focussed
on OSGi enterprise applications that is independent from both the OSGi
framework and the enterprise runtime environment in which application
components are hosted. By maintaining independence of both the target
runtime and underlying OSGi framework it is our intention to build the
broadest possible community of developers for Aries, and to maximize
the potential environments where Aries componentry can be used.
Initial Goals

We will initially focus on the Blueprint container and extend this
with enterprise features such as support for container managed JPA and
container managed transactions. Another initial focus area will be the
contribution of code to support the assembly of isolated, multi-bundle
applications that can be deployed as a unit.
Current Status
Meritocracy

The Aries contributors recognize the desirability of running the
project as a meritocracy. We are eager to engage other members of the
community and operate to the standard of meritocracy that Apache
emphasizes; we believe this is the most effective method of growing
our community and enabling widespread adoption.
Community

OSGi is a mature Java modularity technology that is well-used in many
environments but, in the enterprise space, has more typically been
exploited by the internals of the runtime infrastructure than the
applications that run on it. This is primarily because of a lack of a
clear enterprise OSGi application programming model and implementation
of OSGi-enabled Java technology to support enterprise applications.
There is a need for open source implementations of these technologies
and there is currently no Apache project focused on the wider goal of
delivering components for an enterprise OSGi application programming
model. Aries aims to build a community of developers interested in the
definition and delivery of software components that support an
enterprise OSGi programming model and which can be integrated into a
number of different runtime environments. By maintaining independence
of both the target runtime and underlying OSGi framework it is our
intention to build the broadest possible community of developers.
Alignment

The purpose of Aries is to develop implementations of
application-centric enterprise OSGi technologies that run on an OSGi
framework, but not a specific one, and are used by application
components deployed into a variety of runtime environments without
being tied to any specific environment. For this reason we believe
Aries is a project whose community would be best served if it could
leverage but be independent from the communities that provide
underlying OSGi framework technology and enterprise application server
and integration bus technologies, all of which exist as open source
efforts within Apache and elsewhere. We expect, for example, that some
code developed in Aries will run directly on top of an OSGi framework
such as Felix and that applications exploiting Aries technologies
could be deployed to runtimes such as ServiceMix and Geronimo.
Avoiding the Warning Signs
Orphaned products

The contributors are leading vendors of OSGi-based technologies and
have a long standing in the OSGi Alliance whose application-centric
specifications this project will implement. There is minimal risk of
this work becoming non-strategic and the contributors are confident
that a larger community will form within the project in a relatively
short space of time.
Inexperience with Open Source

Many of the committers have experience working in one or more open
source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
and CXF.

Homogeneous Developers

The list of initial committers, geographically distributed across the
U.S. and Europe, consists of developers from two companies - IBM and
Progress software - with similar goals but for different scenarios.
Many of these developers are experienced Apache committers already and
all are experienced with working in distributed development
communities. It is our hope that, through the incubator, further
contributors with a broad background of experience but common interest
in enterprise OSGi technologies will become involved with this
project.

Relationships with Other Apache Projects

Aries will have a potential relationship with the Apache projects
listed in this section. These projects all serve different purposes
from Aries and have their own communities. It is hoped that each of
these communities will become involved with Aries and help to build a
diverse but independent Aries community.

Apache Felix Karaf -
http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
Karaf is an OSGi based runtime which provides a lightweight container
onto which various components and applications can be deployed. It is
related to Aries:

  1. as a target OSGi based runtime to which Aries applications can
be deployed. In this role, Karaf is a consumer of Aries technology.

Apache Felix - http://felix.apache.org/site/index.html Apache
Felix is primarily a core OSGi framework implementation. It is related
to Aries:

  1. as an underlying OSGi framework implementation and potentially
other extensions that can be used both by Aries run-time components
and the applications which use them.

Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
a server runtime framework and fully certified Java EE 5 application
server runtime. It is related to Aries in two ways:

  1. as a target runtime to which Aries applications can be deployed.
In this role, Geronimo is a consumer of Aries technology.
  2. the Geronimo blueprint sandbox -
http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
an implementation of the OSGi Blueprint container which will be moved
to Aries.

Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
provides a comprehensive infrastructure for SOA development and
management that is based on Service Component Architecture (SCA)
standard. It can be a consumer of Aries technology to provide an Aries
SCA implementation type for composing Aries applications in coarse
grained and potentially heterogeneous service assemblies.

Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
Web Services framework for distributed computing and remote service
realization and invocation using API's such as JAX-WS and JAX-RS. It
also provides the OSGi Remote Services (OSGi RFC 119) reference
implementation in a subproject:
http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
the following way:

  1. As Remote Services is a significant Enterprise specification
being produced by the EEG, it is expected that consumers of Aries will
be looking for an implementation of this specification. CXF provides
an implementation of this specification which already has a
significant active community. The Aries project will make it easy for
Aries consumers to consume the CXF Remote Services implementation,
possibly by providing an instance of the application model that
references the CXF Remote Services implementation. This would mean
that end users will seamlessly pull in the required components from
CXF by using the Aries-provided definition.

Apache ServiceMix - http://servicemix.apache.org/ Apache
ServiceMix provides an ESB that combines the functionality of a
Service Oriented Architecture (SOA) and Event Driven Architecture
(EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
source of the Apache Felix Karaf runtime. It can be a consumer of
Aries applications and associated componentry as a natural evolution
of its existing Karaf "feature" usage.

Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
Java persistence project. It is related to Aries as a JPA persistence
provider, including entity scanning and enhancement. The Aries project
will make it easy for JPA persistence providers such as OpenJPA to be
used in an OSGi environment and will provide container managed
persistence for the Blueprint container.

Documentation

An early draft of OSGi v4.2 core and compendium specifications - which
includes the Blueprint container specification - is available at:
http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
Initial Source

   * The Blueprint container impl from the Geronimo sandbox will be
moved to the Aries project for further development:
http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
   * IBM will also contribute code for:
         o container-managed JPA support in an OSGi environment.
         o making OSGi services visible to Java EE components through JNDI.
         o packaging web components as bundles and a URL handler for
recognizing and converting non-bundled Web components
   * We will also be soliciting implementations of other OSGi
enterprise application-centric specifications.

External Dependencies

   * Apache Ant http://ant.apache.org Apache License
   * Apache Commons http://commons.apache.org Apache License
   * Junit (Java unit test framework) http://junit.sourceforge.net CPL
v1.0 license: http://junit.sourceforge.net/cpl-v10.html
   * Apache Felix (implementation of the OSGi Core and Compendium
specifications - compliance level unknown) http://felix.apache.org
Apache License (hosted by ASF).
   * Eclipse Equinox (compliant implementation of the OSGi Core
Specification and Compendium specifications)
http://eclipse.org/equinox/ Eclipse Public License
   * OpenJPA http://openjpa.apache.org Apache License
   * Serp http://serp.sourceforge.net/ BSD
   * Apache Geronimo http://geronimo.apache.org Apache License

Required Resources
Mailing lists

aries-private (with moderated subscriptions)
aries-dev
aries-commits
aries-user

Subversion Directory

http://svn.apache.org/repos/asf/incubator/aries

Issue Tracking

JIRA (ARIES)

Web Site

Confluence (Aries)

Initial Committers

Names of initial committers with affiliation and current ASF status:

   * Alasdair Nottingham (IBM)
   * Andrew Osborne (IBM)
   * Dan Kulp (Progress, ASF member)
   * David Bosschaert (Progress, ASF committer)
   * David Jencks (IBM, ASF member)
   * Eoghan Glynn (Progress, ASF committer)
   * Graham Charters (IBM)
   * Guillaume Nodet (Progress, ASF member)
   * Hiram Chirino (Progress, ASF member)
   * Ian Robinson (IBM)
   * James Strachan (Progress, ASF member)
   * Jarek Gawor (IBM, ASF member)
   * Jeremy Hughes (IBM, ASF committer)
   * Joe Bohn (IBM, ASF committer)
   * Lin Sun (IBM, ASF committer)
   * Mark Nuttall (IBM)
   * Oisin Hurley (Progress)
   * Rick McGuire (IBM, ASF committer)
   * Sergey Beryozkin (Progress, ASF committer),
   * Timothy Ward (IBM)
   * Valentin Mahrwald (IBM)
   * Zoe Slattery (IBM)

Affiliations

The majority of the initial committers are employed by IBM corp or
Progress Software. One objective of the incubator is to attract a
diverse community of contributors and we anticipate future
contributors to have other affiliations.

Sponsors
Champions

Kevan Miller, Guillaume Nodet

Nominated Mentors

Guillaume Nodet, Davanum Srinivas (Dims)

Sponsoring Entity

The incubator. Successful graduation from Incubator should result in
Aries becoming a new TLP.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org




-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by James Strachan <ja...@gmail.com>.
2009/9/1 Richard S. Hall <he...@ungoverned.org>:
> The Apache Felix project, since its inception, has been intended to host
> implementations of the OSGi specifications, which includes both the
> framework as well as other standard services. A framework implementation was
> just one of the goals.
>
> This proposal seems to be saying a separate project is needed to create some
> illusion of independence from Apache Felix, but the whole point of OSGi is
> to be vendor neutral, so I am not sure I follow the rationale.
>
> Apache Felix
> subprojects are not tied to the Apache Felix framework subproject and by us
> pretending that they are, it only serves to perpetuate this myth.
>
> I have no issues with new efforts around and on top of OSGi being incubated,
> but it gets a little trickier when we are talking about implementing
> standard OSGi specs which was the intended community goal of the Apache
> Felix project. Are we supposed to compete now for standard service
> implementations? Or come to some sort of cartel-like agreement about who
> gets what?

Apache has always supported letting a thousand flowers bloom. Multiple
projects can overlap or even have competing implementations of the
exact same specification or idea. (e.g. we've 2 JAXRS providers, 2
JAXWS providers, 2 message brokers, so many web frameworks I lost
track some time ago etc).

-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Ian Robinson <ia...@googlemail.com>.
The objective is to create a community who focus is to enable 
applications to use both OSGi and Java EE capabilities, independent of 
either a specific OSGi f/w or a specific enterprise runtime. Given the 
Java enterprise focus of Geronimo, we could have proposed a sub-project 
there but considered it better to start a off independent of both but 
encouraging the involve of both (and indeed the other communities 
mentioned in the proposal).


Richard S. Hall wrote:
> The Apache Felix project, since its inception, has been intended to 
> host implementations of the OSGi specifications, which includes both 
> the framework as well as other standard services. A framework 
> implementation was just one of the goals.
>
> This proposal seems to be saying a separate project is needed to 
> create some illusion of independence from Apache Felix, but the whole 
> point of OSGi is to be vendor neutral, so I am not sure I follow the 
> rationale. Apache Felix subprojects are not tied to the Apache Felix 
> framework subproject and by us pretending that they are, it only 
> serves to perpetuate this myth.
>
> I have no issues with new efforts around and on top of OSGi being 
> incubated, but it gets a little trickier when we are talking about 
> implementing standard OSGi specs which was the intended community goal 
> of the Apache Felix project. Are we supposed to compete now for 
> standard service implementations? Or come to some sort of cartel-like 
> agreement about who gets what?
>
> -> richard
>
> On 9/1/09 10:38, Jeremy Hughes wrote:
>> Hi, we would like to propose a new incubator podling called Aries.
>>
>> http://wiki.apache.org/incubator/AriesProposal
>>
>> Here is a quick summary of the proposal
>>
>> The Aries project will deliver a set of pluggable Java components
>> enabling an enterprise OSGi application programming model. This
>> includes implementations and extensions of application-focused
>> specifications defined by the OSGi Alliance Enterprise Expert Group
>> (EEG) and an assembly format for multi-bundle applications, for
>> deployment to a variety of OSGi based runtimes.
>>
>> Aries aims to build a community of developers interested in the
>> definition and delivery of software components that support an
>> enterprise OSGi programming model and which can be integrated into a
>> number of different runtime environments.
>>
>> We appreciate any feedback and comments on the proposal.
>>
>> Here is a plain text copy of the whole proposal:
>>
>> Apache Aries
>> Abstract
>>
>> The Aries project will deliver a set of pluggable Java components
>> enabling an enterprise OSGi application programming model. This
>> includes implementations and extensions of application-focused
>> specifications defined by the OSGi Alliance Enterprise Expert Group
>> (EEG) and an assembly format for multi-bundle applications, for
>> deployment to a variety of OSGi based runtimes.
>> Proposal
>>
>> It is a goal of the Aries project to provide a natural home for open
>> source implementations of current and future OSGi EEG specifications,
>> including the opportunity for the collaborative development of
>> compliance tests, and an environment to demonstrate the composition of
>> these technologies and to explore areas where EEG specifications lack
>> coverage. A further goal of this project is to leverage experience
>> gained from it to inform contributions to OSGi EEG requirements and
>> specification documents.
>>
>> Aries will offer an enterprise OSGi application programming model that
>> enables applications to leverage Java EE and other enterprise
>> technologies and to benefit from the modularity, dynamism and
>> versioning capabilities of OSGi. A significant feature of Aries will
>> be a container for OSGi Blueprint components - an implementation of
>> the new OSGi v4.2 Blueprint component model that defines a standard
>> dependency injection mechanism for Java components, which is derived
>> from the Spring framework and extended for OSGi to declaratively
>> register component interfaces as services in the OSGi service
>> registry.
>>
>> In addition, the Aries project will develop a model for assembling an
>> application/subsystem into a deployable unit, consisting of multiple
>> bundles, as an archive which may include metadata that describes the
>> version and external location of the application's constituent bundles
>> or which may contain the bundles directly.
>>
>> The Aries project will deliver run-time componentry that supports
>> applications, running in an OSGi framework, exploiting enterprise Java
>> technologies common in web applications and integration scenarios
>> including web application bundles, remote services integration and
>> JPA. The project is not expected to deliver a complete application or
>> integration server runtime but will instead deliver enterprise
>> application componentry that can be integrated into such runtimes. The
>> project will develop extensions that go beyond the OSGi EEG
>> specifications to provide a more complete integration of OSGi
>> modularity with Java enterprise technologies, in particular delivering
>> support that includes but is not restricted to:
>>
>>     * isolated enterprise applications composed of multiple, versioned
>> bundles with dynamic lifecycle.
>>     * declarative transactions and security for Blueprint components
>>     * Container-managed JPA for Blueprint components
>>     * Message-driven Blueprint components
>>     * Configuration of resource references in module blueprints.
>>     * Annotation-based Blueprint configuration
>>     * Federation of lookup mechanisms between local JNDI and the OSGi
>> service registry.
>>     * Fully declarative application metadata to enable reflection of
>> an SCA component type definition.
>>
>> In order to maximise the potential scope of Aries adoption it is
>> anticipated the project will remain agnostic of a number of
>> complementary technologies and projects. It is the expectation that
>> Aries will therefore not be delivering components such as: an
>> application or integration server runtime kernel; a persistence
>> provider; distribution provider; a deployment provider or a Web
>> container. Aries will instead seek to enable the use of such
>> components from other projects.
>> Background
>>
>> OSGi is a mature and Java modularity technology that is well-used in
>> many environments but, in the enterprise space, has more typically
>> been exploited by the internals of the runtime infrastructure than the
>> applications that run on it. This is primarily because of a lack of a
>> clear enterprise OSGi application programming model and implementation
>> of OSGi-enabled Java technology to support enterprise applications.
>> OSGi specifications are specified and maintained by the OSGi Alliance
>> which recognized this state of affairs several years ago and
>> established the Enterprise Expert Group within the Alliance to focus
>> specifically on the needs of enterprise applications. The objective of
>> this project is to deliver open source implementations of these
>> application-centric technologies to enable the development of
>> application components, benefiting from the modularity of OSGi
>> combined with standards-based programming models, which can be
>> deployed to a variety of target runtimes.
>> Rationale
>>
>> Aries aims to build a community of developers interested in the
>> delivery of software components that support an enterprise OSGi
>> programming model and which can be integrated into a number of
>> different runtime environments. Apache hosts the Felix project which
>> provides an OSGi framework implementation and a variety of projects
>> which provide technologies exploited by enterprise application
>> components as well as projects which provide runtimes to host
>> application components. There is currently no Apache project focussed
>> on OSGi enterprise applications that is independent from both the OSGi
>> framework and the enterprise runtime environment in which application
>> components are hosted. By maintaining independence of both the target
>> runtime and underlying OSGi framework it is our intention to build the
>> broadest possible community of developers for Aries, and to maximize
>> the potential environments where Aries componentry can be used.
>> Initial Goals
>>
>> We will initially focus on the Blueprint container and extend this
>> with enterprise features such as support for container managed JPA and
>> container managed transactions. Another initial focus area will be the
>> contribution of code to support the assembly of isolated, multi-bundle
>> applications that can be deployed as a unit.
>> Current Status
>> Meritocracy
>>
>> The Aries contributors recognize the desirability of running the
>> project as a meritocracy. We are eager to engage other members of the
>> community and operate to the standard of meritocracy that Apache
>> emphasizes; we believe this is the most effective method of growing
>> our community and enabling widespread adoption.
>> Community
>>
>> OSGi is a mature Java modularity technology that is well-used in many
>> environments but, in the enterprise space, has more typically been
>> exploited by the internals of the runtime infrastructure than the
>> applications that run on it. This is primarily because of a lack of a
>> clear enterprise OSGi application programming model and implementation
>> of OSGi-enabled Java technology to support enterprise applications.
>> There is a need for open source implementations of these technologies
>> and there is currently no Apache project focused on the wider goal of
>> delivering components for an enterprise OSGi application programming
>> model. Aries aims to build a community of developers interested in the
>> definition and delivery of software components that support an
>> enterprise OSGi programming model and which can be integrated into a
>> number of different runtime environments. By maintaining independence
>> of both the target runtime and underlying OSGi framework it is our
>> intention to build the broadest possible community of developers.
>> Alignment
>>
>> The purpose of Aries is to develop implementations of
>> application-centric enterprise OSGi technologies that run on an OSGi
>> framework, but not a specific one, and are used by application
>> components deployed into a variety of runtime environments without
>> being tied to any specific environment. For this reason we believe
>> Aries is a project whose community would be best served if it could
>> leverage but be independent from the communities that provide
>> underlying OSGi framework technology and enterprise application server
>> and integration bus technologies, all of which exist as open source
>> efforts within Apache and elsewhere. We expect, for example, that some
>> code developed in Aries will run directly on top of an OSGi framework
>> such as Felix and that applications exploiting Aries technologies
>> could be deployed to runtimes such as ServiceMix and Geronimo.
>> Avoiding the Warning Signs
>> Orphaned products
>>
>> The contributors are leading vendors of OSGi-based technologies and
>> have a long standing in the OSGi Alliance whose application-centric
>> specifications this project will implement. There is minimal risk of
>> this work becoming non-strategic and the contributors are confident
>> that a larger community will form within the project in a relatively
>> short space of time.
>> Inexperience with Open Source
>>
>> Many of the committers have experience working in one or more open
>> source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
>> and CXF.
>>
>> Homogeneous Developers
>>
>> The list of initial committers, geographically distributed across the
>> U.S. and Europe, consists of developers from two companies - IBM and
>> Progress software - with similar goals but for different scenarios.
>> Many of these developers are experienced Apache committers already and
>> all are experienced with working in distributed development
>> communities. It is our hope that, through the incubator, further
>> contributors with a broad background of experience but common interest
>> in enterprise OSGi technologies will become involved with this
>> project.
>>
>> Relationships with Other Apache Projects
>>
>> Aries will have a potential relationship with the Apache projects
>> listed in this section. These projects all serve different purposes
>> from Aries and have their own communities. It is hoped that each of
>> these communities will become involved with Aries and help to build a
>> diverse but independent Aries community.
>>
>> Apache Felix Karaf -
>> http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
>> Karaf is an OSGi based runtime which provides a lightweight container
>> onto which various components and applications can be deployed. It is
>> related to Aries:
>>
>>    1. as a target OSGi based runtime to which Aries applications can
>> be deployed. In this role, Karaf is a consumer of Aries technology.
>>
>> Apache Felix - http://felix.apache.org/site/index.html Apache
>> Felix is primarily a core OSGi framework implementation. It is related
>> to Aries:
>>
>>    1. as an underlying OSGi framework implementation and potentially
>> other extensions that can be used both by Aries run-time components
>> and the applications which use them.
>>
>> Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
>> a server runtime framework and fully certified Java EE 5 application
>> server runtime. It is related to Aries in two ways:
>>
>>    1. as a target runtime to which Aries applications can be deployed.
>> In this role, Geronimo is a consumer of Aries technology.
>>    2. the Geronimo blueprint sandbox -
>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
>> an implementation of the OSGi Blueprint container which will be moved
>> to Aries.
>>
>> Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
>> provides a comprehensive infrastructure for SOA development and
>> management that is based on Service Component Architecture (SCA)
>> standard. It can be a consumer of Aries technology to provide an Aries
>> SCA implementation type for composing Aries applications in coarse
>> grained and potentially heterogeneous service assemblies.
>>
>> Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
>> Web Services framework for distributed computing and remote service
>> realization and invocation using API's such as JAX-WS and JAX-RS. It
>> also provides the OSGi Remote Services (OSGi RFC 119) reference
>> implementation in a subproject:
>> http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
>> the following way:
>>
>>    1. As Remote Services is a significant Enterprise specification
>> being produced by the EEG, it is expected that consumers of Aries will
>> be looking for an implementation of this specification. CXF provides
>> an implementation of this specification which already has a
>> significant active community. The Aries project will make it easy for
>> Aries consumers to consume the CXF Remote Services implementation,
>> possibly by providing an instance of the application model that
>> references the CXF Remote Services implementation. This would mean
>> that end users will seamlessly pull in the required components from
>> CXF by using the Aries-provided definition.
>>
>> Apache ServiceMix - http://servicemix.apache.org/ Apache
>> ServiceMix provides an ESB that combines the functionality of a
>> Service Oriented Architecture (SOA) and Event Driven Architecture
>> (EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
>> source of the Apache Felix Karaf runtime. It can be a consumer of
>> Aries applications and associated componentry as a natural evolution
>> of its existing Karaf "feature" usage.
>>
>> Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
>> Java persistence project. It is related to Aries as a JPA persistence
>> provider, including entity scanning and enhancement. The Aries project
>> will make it easy for JPA persistence providers such as OpenJPA to be
>> used in an OSGi environment and will provide container managed
>> persistence for the Blueprint container.
>>
>> Documentation
>>
>> An early draft of OSGi v4.2 core and compendium specifications - which
>> includes the Blueprint container specification - is available at:
>> http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
>> Initial Source
>>
>>     * The Blueprint container impl from the Geronimo sandbox will be
>> moved to the Aries project for further development:
>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
>>     * IBM will also contribute code for:
>>           o container-managed JPA support in an OSGi environment.
>>           o making OSGi services visible to Java EE components 
>> through JNDI.
>>           o packaging web components as bundles and a URL handler for
>> recognizing and converting non-bundled Web components
>>     * We will also be soliciting implementations of other OSGi
>> enterprise application-centric specifications.
>>
>> External Dependencies
>>
>>     * Apache Ant http://ant.apache.org Apache License
>>     * Apache Commons http://commons.apache.org Apache License
>>     * Junit (Java unit test framework) http://junit.sourceforge.net CPL
>> v1.0 license: http://junit.sourceforge.net/cpl-v10.html
>>     * Apache Felix (implementation of the OSGi Core and Compendium
>> specifications - compliance level unknown) http://felix.apache.org
>> Apache License (hosted by ASF).
>>     * Eclipse Equinox (compliant implementation of the OSGi Core
>> Specification and Compendium specifications)
>> http://eclipse.org/equinox/ Eclipse Public License
>>     * OpenJPA http://openjpa.apache.org Apache License
>>     * Serp http://serp.sourceforge.net/ BSD
>>     * Apache Geronimo http://geronimo.apache.org Apache License
>>
>> Required Resources
>> Mailing lists
>>
>> aries-private (with moderated subscriptions)
>> aries-dev
>> aries-commits
>> aries-user
>>
>> Subversion Directory
>>
>> http://svn.apache.org/repos/asf/incubator/aries
>>
>> Issue Tracking
>>
>> JIRA (ARIES)
>>
>> Web Site
>>
>> Confluence (Aries)
>>
>> Initial Committers
>>
>> Names of initial committers with affiliation and current ASF status:
>>
>>     * Alasdair Nottingham (IBM)
>>     * Andrew Osborne (IBM)
>>     * Dan Kulp (Progress, ASF member)
>>     * David Bosschaert (Progress, ASF committer)
>>     * David Jencks (IBM, ASF member)
>>     * Eoghan Glynn (Progress, ASF committer)
>>     * Graham Charters (IBM)
>>     * Guillaume Nodet (Progress, ASF member)
>>     * Hiram Chirino (Progress, ASF member)
>>     * Ian Robinson (IBM)
>>     * James Strachan (Progress, ASF member)
>>     * Jarek Gawor (IBM, ASF member)
>>     * Jeremy Hughes (IBM, ASF committer)
>>     * Joe Bohn (IBM, ASF committer)
>>     * Lin Sun (IBM, ASF committer)
>>     * Mark Nuttall (IBM)
>>     * Oisin Hurley (Progress)
>>     * Rick McGuire (IBM, ASF committer)
>>     * Sergey Beryozkin (Progress, ASF committer),
>>     * Timothy Ward (IBM)
>>     * Valentin Mahrwald (IBM)
>>     * Zoe Slattery (IBM)
>>
>> Affiliations
>>
>> The majority of the initial committers are employed by IBM corp or
>> Progress Software. One objective of the incubator is to attract a
>> diverse community of contributors and we anticipate future
>> contributors to have other affiliations.
>>
>> Sponsors
>> Champions
>>
>> Kevan Miller, Guillaume Nodet
>>
>> Nominated Mentors
>>
>> Guillaume Nodet, Davanum Srinivas (Dims)
>>
>> Sponsoring Entity
>>
>> The incubator. Successful graduation from Incubator should result in
>> Aries becoming a new TLP.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>    
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Fwd: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 9/1/09 12:23, Guillaume Nodet wrote:
> On Tue, Sep 1, 2009 at 18:15, Richard S. Hall<he...@ungoverned.org>  wrote:
>
>    
>> For me personally, I have no problem with referring to things as Apache
>> iPOJO, etc. I was under the [apparently mistaken] impression that we could
>> not do this, because it implied it was a TLP. So, we could change all of
>> those names in one swoop and I would be fine with that.
>>
>> As far as coming up with a name for the framework subproject, I don't have
>> an issue with that either. Maybe it has been long enough now that we could
>> go back to using Oscar. ;-) Technically, its name now is Framework, but this
>> may be too generic, e.g., Apache Framework.
>>
>>      
> Yeah, "Apache Framework"  would be a very bad name imho.  In the recent
> past, the ASF tend to use project names that are not technology names.
> Apache WebServices is a really good example of a bad name, and that's for
> this very reason that the ASF now try to find non technology related names.
> Oscar would be fine, though I think to ease removing the confusion, it would
> be better to rename the TLP itself if ever possible.
>    

I don't think I would actually want to reuse Oscar...it would probably 
make more sense to come up with something similar to Felix.

I don't agree about renaming the TLP. There are so many examples of 
similar situations. I cannot believe we are truly in a unique situation 
here:

    * "Apache" typically means the HTTP Server project, but it also
      refers to the foundation and all of its independent projects.
    * "Eclipse" typically means the IDE, but there is also a runtime and
      foundation with independent projects.

Acting like this isn't normal or something that is too confusing to ever 
resolve seems a bit preposterous.

-> richard

>
>    
>> ->  richard
>>
>>
>> On 9/1/09 12:10, Guillaume Nodet wrote:
>>
>>      
>>> Forwarding an exerpt of one of my answer to Richard reply.
>>> I really think it's worth discussing it anyway.
>>>
>>> Most of the TLP I know about that have subprojects usually refer to those
>>> subprojects as Apache Foo and not Apache Bar Foo.
>>> So this would mean Apache iPojo and not Apache Felix iPojo, ditto for
>>> other
>>> subprojects.
>>>
>>> I also think the "branding" problem should be addressed (if possible) by
>>> renaming either the framework or the TLP.  It looks to me that renaming
>>> the
>>> TLP (even if I think would better) might be more difficult to achieve from
>>> an infra pov, but I may be wrong (I know there are some tools for
>>> migrating
>>> mailing lists and such, so it might not be so difficult).
>>>
>>> I'd like to hear other's thoughts.
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Guillaume Nodet<gn...@gmail.com>
>>> Date: Tue, Sep 1, 2009 at 17:45
>>> Subject: Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
>>> To: general@incubator.apache.org
>>>
>>> The problem I have with Felix is really a branding problem.  While *we*
>>> (as
>>> developers) very well know that all the subprojects of Felix are not tied
>>> to
>>> the Felix Framework itself, it's really difficult to spread this word
>>> around
>>> to non techies.  The name Felix is often associated to the OSGi framework
>>> implementation itself, and it's kinda hard to remove this tie unless
>>> either
>>> the project or the framework change its name to something else.  For
>>> example, the framework could be referred to as Apache Foo and other
>>> subprojects as Apache iPojo or Apache Karaf.  I think it would help
>>> removing
>>> this tie.   The other way around is possible too, rename the project to
>>> something else, and keep Apache Felix as referring to the framework itself
>>> (which might be even better, but slightly more difficult to actually
>>> achieve).  I'm not sure there is a very easy way, but dev@felix.a.o would
>>> a
>>> better place to discuss that.
>>>
>>>
>>>
>>>        
>>      
>
>    

Re: Fwd: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
On Tue, Sep 1, 2009 at 18:15, Richard S. Hall <he...@ungoverned.org> wrote:

> For me personally, I have no problem with referring to things as Apache
> iPOJO, etc. I was under the [apparently mistaken] impression that we could
> not do this, because it implied it was a TLP. So, we could change all of
> those names in one swoop and I would be fine with that.
>
> As far as coming up with a name for the framework subproject, I don't have
> an issue with that either. Maybe it has been long enough now that we could
> go back to using Oscar. ;-) Technically, its name now is Framework, but this
> may be too generic, e.g., Apache Framework.
>

Yeah, "Apache Framework"  would be a very bad name imho.  In the recent
past, the ASF tend to use project names that are not technology names.
Apache WebServices is a really good example of a bad name, and that's for
this very reason that the ASF now try to find non technology related names.
Oscar would be fine, though I think to ease removing the confusion, it would
be better to rename the TLP itself if ever possible.


>
> -> richard
>
>
> On 9/1/09 12:10, Guillaume Nodet wrote:
>
>> Forwarding an exerpt of one of my answer to Richard reply.
>> I really think it's worth discussing it anyway.
>>
>> Most of the TLP I know about that have subprojects usually refer to those
>> subprojects as Apache Foo and not Apache Bar Foo.
>> So this would mean Apache iPojo and not Apache Felix iPojo, ditto for
>> other
>> subprojects.
>>
>> I also think the "branding" problem should be addressed (if possible) by
>> renaming either the framework or the TLP.  It looks to me that renaming
>> the
>> TLP (even if I think would better) might be more difficult to achieve from
>> an infra pov, but I may be wrong (I know there are some tools for
>> migrating
>> mailing lists and such, so it might not be so difficult).
>>
>> I'd like to hear other's thoughts.
>>
>>
>> ---------- Forwarded message ----------
>> From: Guillaume Nodet<gn...@gmail.com>
>> Date: Tue, Sep 1, 2009 at 17:45
>> Subject: Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
>> To: general@incubator.apache.org
>>
>> The problem I have with Felix is really a branding problem.  While *we*
>> (as
>> developers) very well know that all the subprojects of Felix are not tied
>> to
>> the Felix Framework itself, it's really difficult to spread this word
>> around
>> to non techies.  The name Felix is often associated to the OSGi framework
>> implementation itself, and it's kinda hard to remove this tie unless
>> either
>> the project or the framework change its name to something else.  For
>> example, the framework could be referred to as Apache Foo and other
>> subprojects as Apache iPojo or Apache Karaf.  I think it would help
>> removing
>> this tie.   The other way around is possible too, rename the project to
>> something else, and keep Apache Felix as referring to the framework itself
>> (which might be even better, but slightly more difficult to actually
>> achieve).  I'm not sure there is a very easy way, but dev@felix.a.o would
>> a
>> better place to discuss that.
>>
>>
>>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: Fwd: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
For me personally, I have no problem with referring to things as Apache 
iPOJO, etc. I was under the [apparently mistaken] impression that we 
could not do this, because it implied it was a TLP. So, we could change 
all of those names in one swoop and I would be fine with that.

As far as coming up with a name for the framework subproject, I don't 
have an issue with that either. Maybe it has been long enough now that 
we could go back to using Oscar. ;-) Technically, its name now is 
Framework, but this may be too generic, e.g., Apache Framework.

-> richard

On 9/1/09 12:10, Guillaume Nodet wrote:
> Forwarding an exerpt of one of my answer to Richard reply.
> I really think it's worth discussing it anyway.
>
> Most of the TLP I know about that have subprojects usually refer to those
> subprojects as Apache Foo and not Apache Bar Foo.
> So this would mean Apache iPojo and not Apache Felix iPojo, ditto for other
> subprojects.
>
> I also think the "branding" problem should be addressed (if possible) by
> renaming either the framework or the TLP.  It looks to me that renaming the
> TLP (even if I think would better) might be more difficult to achieve from
> an infra pov, but I may be wrong (I know there are some tools for migrating
> mailing lists and such, so it might not be so difficult).
>
> I'd like to hear other's thoughts.
>
>
> ---------- Forwarded message ----------
> From: Guillaume Nodet<gn...@gmail.com>
> Date: Tue, Sep 1, 2009 at 17:45
> Subject: Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
> To: general@incubator.apache.org
>
> The problem I have with Felix is really a branding problem.  While *we* (as
> developers) very well know that all the subprojects of Felix are not tied to
> the Felix Framework itself, it's really difficult to spread this word around
> to non techies.  The name Felix is often associated to the OSGi framework
> implementation itself, and it's kinda hard to remove this tie unless either
> the project or the framework change its name to something else.  For
> example, the framework could be referred to as Apache Foo and other
> subprojects as Apache iPojo or Apache Karaf.  I think it would help removing
> this tie.   The other way around is possible too, rename the project to
> something else, and keep Apache Felix as referring to the framework itself
> (which might be even better, but slightly more difficult to actually
> achieve).  I'm not sure there is a very easy way, but dev@felix.a.o would a
> better place to discuss that.
>
>    

Fwd: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
Forwarding an exerpt of one of my answer to Richard reply.
I really think it's worth discussing it anyway.

Most of the TLP I know about that have subprojects usually refer to those
subprojects as Apache Foo and not Apache Bar Foo.
So this would mean Apache iPojo and not Apache Felix iPojo, ditto for other
subprojects.

I also think the "branding" problem should be addressed (if possible) by
renaming either the framework or the TLP.  It looks to me that renaming the
TLP (even if I think would better) might be more difficult to achieve from
an infra pov, but I may be wrong (I know there are some tools for migrating
mailing lists and such, so it might not be so difficult).

I'd like to hear other's thoughts.


---------- Forwarded message ----------
From: Guillaume Nodet <gn...@gmail.com>
Date: Tue, Sep 1, 2009 at 17:45
Subject: Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
To: general@incubator.apache.org

The problem I have with Felix is really a branding problem.  While *we* (as
developers) very well know that all the subprojects of Felix are not tied to
the Felix Framework itself, it's really difficult to spread this word around
to non techies.  The name Felix is often associated to the OSGi framework
implementation itself, and it's kinda hard to remove this tie unless either
the project or the framework change its name to something else.  For
example, the framework could be referred to as Apache Foo and other
subprojects as Apache iPojo or Apache Karaf.  I think it would help removing
this tie.   The other way around is possible too, rename the project to
something else, and keep Apache Felix as referring to the framework itself
(which might be even better, but slightly more difficult to actually
achieve).  I'm not sure there is a very easy way, but dev@felix.a.o would a
better place to discuss that.

-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by James Strachan <ja...@gmail.com>.
2009/9/1 Guillaume Nodet <gn...@gmail.com>:
> Not sure how to articulate my thoughts here.
>
> First, it's not about competing against Felix, though you'll find in the ASF
> multiple competing products (Axis vs CXF to mention only this one) and the
> ASF has never stated as a goal that it would provide a coherent offer or
> anything like this.
>
> The problem I have with Felix is really a branding problem.  While *we* (as
> developers) very well know that all the subprojects of Felix are not tied to
> the Felix Framework itself, it's really difficult to spread this word around
> to non techies.  The name Felix is often associated to the OSGi framework
> implementation itself, and it's kinda hard to remove this tie unless either
> the project or the framework change its name to something else.  For
> example, the framework could be referred to as Apache Foo and other
> subprojects as Apache iPojo or Apache Karaf.  I think it would help removing
> this tie.   The other way around is possible too, rename the project to
> something else, and keep Apache Felix as referring to the framework itself
> (which might be even better, but slightly more difficult to actually
> achieve).  I'm not sure there is a very easy way, but dev@felix.a.o would a
> better place to discuss that.
>
> Another thought that comes to my mind is that over the past years, the ASF
> has tried to dismantle umbrella projects when it makes sense: i.e. when one
> of the subproject has sufficient momentum to create a community on its own.
> ACE is another podling related to OSGi and AFAIK it implements the
> DeploymentAdmin OSGi spec.   I also see Karaf as a possible TLP at some
> point.   That would become a problem with Felix, as the communities are
> rather disjoint between the subprojects (not all, I do agree).  Not sure
> what the good size for a TLP is and other members can join the discussion
> and provide feedback.   I don't think felix is oversized right now, but it
> might become a problem if it goes too far.    Given this proposal includes
> more than 20 committers and most of them are not felix committers, we'd need
> the incubator for building up this community anyway.   And btw, as any other
> incubator proposal, everyone interested is free to join the proposal and we
> would particularly welcome any felix committer here.
>
> That said, Aries wants to focus on application focused enterprise OSGi
> specs, which I do agree, could fit in the Felix scope, as could Ace do
> too.   I guess in all cases, things can be discussed at the time the podling
> will graduate out of the incubator.  The current goal is to aim to TLP as we
> think the size of the project can back that, but this is not written in
> stone.

FWIW I agree too. I think the name "Felix" is now synonymous with the
Felix OSGi framework implementation in most peoples eyes.

-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Marcel Offermans <ma...@luminis.nl>.
On Sep 1, 2009, at 17:45 , Guillaume Nodet wrote:

> ACE is another podling related to OSGi and AFAIK it implements the
> DeploymentAdmin OSGi spec.

Just to clear up any misconceptions:

ACE does not implement the DeploymentAdmin spec. That was donated to  
Felix and ACE uses it.

ACE is an application that uses OSGi as its architecture and can  
provision components to OSGi targets, but it can distribute software  
and configuration to non-OSGi targets too. In other words, it uses the  
OSGi specification and some of the compendium services to build a  
modular application.

Of course this type of application can very well be used together with  
OSGi applications, but I think there is a difference between  
implementing the enterprise parts of the OSGi spec and using bundles  
from Felix for another application.

Greetings, Marcel


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 9/1/09 12:14, Guillaume Nodet wrote:
> On Tue, Sep 1, 2009 at 18:06, Richard S. Hall<he...@ungoverned.org>  wrote:
>
>    
>> Creating another project to host OSGi spec implementations seems
>> unnecessary. And, from my point of view, only serves to foster this
>> mentality that Felix projects are framework specific. I do not buy your
>> argument that we cannot educate the non-techie that this is not true. Do
>> such work at Felix is exactly how we educate them. Of course, we could also
>> discuss other ways to improve this.
>>
>>
>>      
> Well, the problem I see here is that we *need* to educate non-techies.  This
> obvisouly mean that there is a confusion.  Education is just a work around
> the need to remove the confusion imho.  So let's discuss that on
> dev@felix.a.o, I don't think this thread belongs here.
>    

Hmm. The sole reason all of our communities exist is to educate people 
about what we are doing...to dev@felix...

-> richard

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
How is it that so many people already use Felix subprojects on other 
frameworks if there isn't already some understanding on this already? 
Just because some people perceive it to not be that way, doesn't mean we 
should throw the baby out with the bathwater. It is a poor argument. 
Just starting walking the walk and people will figure it out...they 
aren't that stupid.

-> richard

On 9/1/09 14:27, Niclas Hedhman wrote:
> Uhhh... So you intend to re-educate the 'masses' in two ways;
>
> 1. "NO, NO, NO, Felix is not an OSGi framework, it is a group of OSGi
> projects... Apache Foo is an OSGi framework..."
>
> 2. "NO, NO, NO, Felix bundles works on other things than Felix, I mean the
> Apache Foo..."
>
> Or did I misunderstand something here?
>
> That way is just plain stupid, and serves no purpose at all. Either keep
> Felix what it represents to people (the framework) and rename/move/juggle
> the other bits, or don't do anything.
>
> Yes, you are right that for most non-Java software developers in the world,
> Apache == web server, and I think this is a general problem...
>
> Good Luck with whatever tack you guys choose on this.
>
> As for Aries, I would like to see the scope arrive at ASF, and I would hope
> now is the time to review the organization in this field.
>
> +1 for Incubation, btw. I might sign up as Mentor, if I can squeeze in the
> time...
>
> -- Niclas
>
> On Sep 2, 2009 1:52 AM, "Richard S. Hall"<he...@ungoverned.org>  wrote:
>
> As I said on dev@felix and will repeat here:
>
> ----
>
> I don't agree about renaming the [Felix] TLP. There are so many examples of
> similar situations. I cannot believe we are truly in a unique situation
> here:
>
>    * "Apache" typically means the HTTP Server project, but it also
>      refers to the foundation and all of its independent projects.
>    * "Eclipse" typically means the IDE, but there is also a runtime and
>      foundation with independent projects.
>
> Acting like this isn't normal or something that is too confusing to ever
> resolve seems a bit preposterous.
>
> ----
>
> While I don't believe the situation is as confusing as is contended, I have
> no issue with coming up with a different name for the Apache Felix Framework
> (its name is technically Framework right now), so that the Apache Felix
> project can continue to pursue its original charter.
>
> ->  richard
>
> On 9/1/09 12:58, Niclas Hedhman wrote:>  >  I'm not subscribing to
> dev@felix.a.o at the moment, but...
>
>    

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
How is it that so many people already use Felix subprojects on other 
frameworks if there isn't already some understanding on this already? 
Just because some people perceive it to not be that way, doesn't mean we 
should throw the baby out with the bathwater. It is a poor argument. 
Just starting walking the walk and people will figure it out...they 
aren't that stupid.

-> richard

On 9/1/09 14:27, Niclas Hedhman wrote:
> Uhhh... So you intend to re-educate the 'masses' in two ways;
>
> 1. "NO, NO, NO, Felix is not an OSGi framework, it is a group of OSGi
> projects... Apache Foo is an OSGi framework..."
>
> 2. "NO, NO, NO, Felix bundles works on other things than Felix, I mean the
> Apache Foo..."
>
> Or did I misunderstand something here?
>
> That way is just plain stupid, and serves no purpose at all. Either keep
> Felix what it represents to people (the framework) and rename/move/juggle
> the other bits, or don't do anything.
>
> Yes, you are right that for most non-Java software developers in the world,
> Apache == web server, and I think this is a general problem...
>
> Good Luck with whatever tack you guys choose on this.
>
> As for Aries, I would like to see the scope arrive at ASF, and I would hope
> now is the time to review the organization in this field.
>
> +1 for Incubation, btw. I might sign up as Mentor, if I can squeeze in the
> time...
>
> -- Niclas
>
> On Sep 2, 2009 1:52 AM, "Richard S. Hall"<he...@ungoverned.org>  wrote:
>
> As I said on dev@felix and will repeat here:
>
> ----
>
> I don't agree about renaming the [Felix] TLP. There are so many examples of
> similar situations. I cannot believe we are truly in a unique situation
> here:
>
>    * "Apache" typically means the HTTP Server project, but it also
>      refers to the foundation and all of its independent projects.
>    * "Eclipse" typically means the IDE, but there is also a runtime and
>      foundation with independent projects.
>
> Acting like this isn't normal or something that is too confusing to ever
> resolve seems a bit preposterous.
>
> ----
>
> While I don't believe the situation is as confusing as is contended, I have
> no issue with coming up with a different name for the Apache Felix Framework
> (its name is technically Framework right now), so that the Apache Felix
> project can continue to pursue its original charter.
>
> ->  richard
>
> On 9/1/09 12:58, Niclas Hedhman wrote:>  >  I'm not subscribing to
> dev@felix.a.o at the moment, but...
>
>    

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Kevan Miller <ke...@gmail.com>.
On Sep 10, 2009, at 2:30 AM, Niclas Hedhman wrote:

> On Wed, Sep 9, 2009 at 3:58 PM, Jeremy Hughes <hu...@apache.org>  
> wrote:
>> 2009/9/1 Niclas Hedhman <ni...@hedhman.org>:
>> ...
>>> +1 for Incubation, btw. I might sign up as Mentor, if I can  
>>> squeeze in the
>>> time...
>> Can I persuade you to sign up :-) ... we have two experienced ASF
>> members as mentors, but I think the additional perspective outside  
>> the
>> two companies putting the proposal forward would be really useful.
>
> At $50 an hour, yes no problem ;-) otherwise, I am already
> overcommitted on ASF related stuff and also need to "somehow" increase
> both the time spent with family, sleeping and new job (if any).

Heh. Would a beer suffice? ;-)

I've added my name to the Mentors list. So, we'll have 3 mentors. If  
anyone is interested/willing, would be good to have another...

--kevan



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <jp...@gmail.com>.
2009/9/10 Niclas Hedhman <ni...@hedhman.org>:
> On Wed, Sep 9, 2009 at 3:58 PM, Jeremy Hughes <hu...@apache.org> wrote:
>> 2009/9/1 Niclas Hedhman <ni...@hedhman.org>:
>> ...
>>> +1 for Incubation, btw. I might sign up as Mentor, if I can squeeze in the
>>> time...
>> Can I persuade you to sign up :-) ... we have two experienced ASF
>> members as mentors, but I think the additional perspective outside the
>> two companies putting the proposal forward would be really useful.
>
> At $50 an hour, yes no problem ;-) otherwise, I am already
> overcommitted on ASF related stuff and also need to "somehow" increase
> both the time spent with family, sleeping and new job (if any).

Ah well, it was worth a try :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Wed, Sep 9, 2009 at 3:58 PM, Jeremy Hughes <hu...@apache.org> wrote:
> 2009/9/1 Niclas Hedhman <ni...@hedhman.org>:
> ...
>> +1 for Incubation, btw. I might sign up as Mentor, if I can squeeze in the
>> time...
> Can I persuade you to sign up :-) ... we have two experienced ASF
> members as mentors, but I think the additional perspective outside the
> two companies putting the proposal forward would be really useful.

At $50 an hour, yes no problem ;-) otherwise, I am already
overcommitted on ASF related stuff and also need to "somehow" increase
both the time spent with family, sleeping and new job (if any).


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
2009/9/1 Niclas Hedhman <ni...@hedhman.org>:
...
> +1 for Incubation, btw. I might sign up as Mentor, if I can squeeze in the
> time...
Can I persuade you to sign up :-) ... we have two experienced ASF
members as mentors, but I think the additional perspective outside the
two companies putting the proposal forward would be really useful.

Thanks,
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
Uhhh... So you intend to re-educate the 'masses' in two ways;

1. "NO, NO, NO, Felix is not an OSGi framework, it is a group of OSGi
projects... Apache Foo is an OSGi framework..."

2. "NO, NO, NO, Felix bundles works on other things than Felix, I mean the
Apache Foo..."

Or did I misunderstand something here?

That way is just plain stupid, and serves no purpose at all. Either keep
Felix what it represents to people (the framework) and rename/move/juggle
the other bits, or don't do anything.

Yes, you are right that for most non-Java software developers in the world,
Apache == web server, and I think this is a general problem...

Good Luck with whatever tack you guys choose on this.

As for Aries, I would like to see the scope arrive at ASF, and I would hope
now is the time to review the organization in this field.

+1 for Incubation, btw. I might sign up as Mentor, if I can squeeze in the
time...

-- Niclas

On Sep 2, 2009 1:52 AM, "Richard S. Hall" <he...@ungoverned.org> wrote:

As I said on dev@felix and will repeat here:

----

I don't agree about renaming the [Felix] TLP. There are so many examples of
similar situations. I cannot believe we are truly in a unique situation
here:

  * "Apache" typically means the HTTP Server project, but it also
    refers to the foundation and all of its independent projects.
  * "Eclipse" typically means the IDE, but there is also a runtime and
    foundation with independent projects.

Acting like this isn't normal or something that is too confusing to ever
resolve seems a bit preposterous.

----

While I don't believe the situation is as confusing as is contended, I have
no issue with coming up with a different name for the Apache Felix Framework
(its name is technically Framework right now), so that the Apache Felix
project can continue to pursue its original charter.

-> richard

On 9/1/09 12:58, Niclas Hedhman wrote: > > I'm not subscribing to
dev@felix.a.o at the moment, but...

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
Uhhh... So you intend to re-educate the 'masses' in two ways;

1. "NO, NO, NO, Felix is not an OSGi framework, it is a group of OSGi
projects... Apache Foo is an OSGi framework..."

2. "NO, NO, NO, Felix bundles works on other things than Felix, I mean the
Apache Foo..."

Or did I misunderstand something here?

That way is just plain stupid, and serves no purpose at all. Either keep
Felix what it represents to people (the framework) and rename/move/juggle
the other bits, or don't do anything.

Yes, you are right that for most non-Java software developers in the world,
Apache == web server, and I think this is a general problem...

Good Luck with whatever tack you guys choose on this.

As for Aries, I would like to see the scope arrive at ASF, and I would hope
now is the time to review the organization in this field.

+1 for Incubation, btw. I might sign up as Mentor, if I can squeeze in the
time...

-- Niclas

On Sep 2, 2009 1:52 AM, "Richard S. Hall" <he...@ungoverned.org> wrote:

As I said on dev@felix and will repeat here:

----

I don't agree about renaming the [Felix] TLP. There are so many examples of
similar situations. I cannot believe we are truly in a unique situation
here:

  * "Apache" typically means the HTTP Server project, but it also
    refers to the foundation and all of its independent projects.
  * "Eclipse" typically means the IDE, but there is also a runtime and
    foundation with independent projects.

Acting like this isn't normal or something that is too confusing to ever
resolve seems a bit preposterous.

----

While I don't believe the situation is as confusing as is contended, I have
no issue with coming up with a different name for the Apache Felix Framework
(its name is technically Framework right now), so that the Apache Felix
project can continue to pursue its original charter.

-> richard

On 9/1/09 12:58, Niclas Hedhman wrote: > > I'm not subscribing to
dev@felix.a.o at the moment, but...

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
A goal of Aries is to seed a new community focused on the development
of an Enterprise Java OSGi application programming model, and runtime
that is agnostic of server runtime or OSGi framework implementation.
This independence from underlying technology will make Aries' appeal
as broad as possible - to Enterprise Java consumers of Equinox's spec
implementations and Felix's spec implementations, alike. Keeping the
two concerns of application programming model and JEE/OSGi integration
together in the same project is (IMHO) sensible considering the
dependence of one on the other and therefore the likelihood of one
influencing the other. In addition our initial contribution has been
developed by people working on both concerns.

The fact that some of the JEE/OSGi integration has already been
brought to OSGi shouldn't mean an implementation (in our contribution)
needs to be hosted under a different TLP. While Felix has a charter to
"create software implementing the OSGi Service Platform", does this
preclude another project from overlapping with that charter? I didn't
think so. Also, I think in this case it makes sense as the EEG
specifications mentioned don't have implementations in Felix and they
are tightly related to the Aries goal of creating an Enterprise Java
OSGi application programming model.

Much of the discussion as to where Aries code (including initial
contribution) resides would seem to be a decision we should take at
graduation rather than before incubation starts. I would like to see
us build a single community around Enterprise Java OSGi application
programming model in one place (in the incubator) and see where that
takes us. (But of course I would say that).

Jeremy

2009/9/2 Karl Pauls <ka...@gmail.com>:
> From my perspective, the incubator isn't a loophole around the
> meritocracy approach of existing TLPs. Submitting a couple of patches
> can't be to high a barrier for people new to the ASF and the code
> base.
>
> We regularly vote people in as committers if they contribute to felix
> subprojects and typically, if we accept a larger piece of code as a
> donation, we try to get the creator as a committer too. We did this
> with Karaf recently.
>
> I think felix is an excellent place for consolidating OSGi
> spec-related development here at Apache since the community is in
> place and very active.
>
> regards,
>
> Karl
>
> On Wed, Sep 2, 2009 at 5:29 PM, Guillaume Nodet<gn...@gmail.com> wrote:
>> We have in this proposal a lot of people who are not felix committers and
>> who are not even apache committers at all.
>>
>> They want to work on some code and create a community around it.  The way
>> the ASF works means that the incubator is the right place to do so.  The
>> only other solution is to develop it in a closed source environment and
>> submit it at Apache when it's done, and i really don't think it's a good
>> idea, given the willingness to do it in open source.
>> The blueprint implementation has been developped so far inside the Geronimo
>> TLP, part of the reason is that some of the people working on it were not
>> felix committers, so it was way easier to work there instead of contributing
>> patches until getting committership.    It is very difficult to commit to
>> work on a new implementation of anything when you don't even have commit
>> priviledges.  It's ok for patches, but not for a new dev.   That's what we
>> have here.   We have people here wanting to work on some new OSGi spec
>> implementation, and the only way for them to do so at Apache in to go into
>> the incubator.
>>
>> Even, if Aries was to compete against Felix in any way, it's not a good
>> enough argument.  We already have multiple projects in the ASF that do have
>> overlap as it was pointed already multiple times in this thread: mutliple
>> REST implementations, multiple JAX-WS implementations, etc...  But the Aries
>> podling does not aim to even provide alternative implementation to what
>> Felix already has, it's goal is to create a community with new people who
>> want to work on that and deliver both implementations of new OSGi specs
>> (such as blueprint and subsystems / applications, jpa ...) and also
>> additional extensions (such as blueprint custom namespaces for transactions,
>> etc...).
>>
>> For the independance, the only real place I know which provides OSGi
>> components, not tainted with a given framework are SpringSource (though it's
>> open source, the community is not really open) and OPS4J, but I do think
>> it's a different discussion.
>>
>> I restate that the goal of the Aries proposal is to foster a community
>> around some new code implementing some OSGi specs.  And I don't think we can
>> do that inside an existing TLP, as we have non apache committers that want
>> to create this code.  That's what the incubator has been created for.
>>
>> Last, accepting to create a podling does not mean the final destination of
>> the podling is defined yet.   Aries could become either a TLP, a Felix
>> subproject, or be split across the two of them.  The one that makes the most
>> sense should prevail at graduation time.  By the time Aries is ready to
>> graduate, the discussion about it's final destination will be held.  And
>> that's where what you say will make sense and where your vote needs to be
>> cast.
>>
>> I really do understand your concerns (even if I don't share them), but now
>> is not the time to vote -1.
>>
>> On Wed, Sep 2, 2009 at 16:30, Richard S. Hall <he...@ungoverned.org> wrote:
>>
>>> I will try to keep this short.
>>>
>>> The OSGi Service Platform is composed of the core and compendium specs. The
>>> EEG specs are not in any way special and will ultimately end up as part of
>>> the compendium spec. Apache Felix was incubated to build a community at
>>> Apache around implementing the OSGi specs.
>>>
>>> Now we are being told that this mission is too tainted because we implement
>>> the framework spec, which is part of the core spec. I find this unfathomable
>>> given the nature of OSGi and the efforts to which the Felix community goes
>>> to be good OSGi citizens...we even allow for competing implementations
>>> within our community.
>>>
>>> It is also particularly odd, since the Equinox and Knopflerfish communities
>>> are in the same situation, implementing both core and compendium specs with
>>> their frameworks largely synonymous with their project name.
>>>
>>> I am not naive enough to expect this discussion to change much, since I
>>> imagine there has already been a fair amount of political calculation around
>>> this proposal, otherwise the Felix community in general would have been
>>> engaged earlier.
>>>
>>> So, here's my vote:
>>>
>>>   * -1 for the portion of the proposal creating yet another community
>>>     for implementing OSGi specs at Apache since the Felix community
>>>     would happily welcome more contribution (just like recently
>>>     occurred with ServiceMix members being accepted as Felix
>>>     committers and PMC members for the Karaf subproject)
>>>   * +1 for the rest of the proposal to explore how to build an
>>>     enterprise component model on OSGi and the other non-spec related
>>>     topics.
>>>
>>> -> richard
>>>
>>>
>>>
>>> On 9/1/09 22:53, Kevan Miller wrote:
>>>
>>>>
>>>> On Sep 1, 2009, at 2:08 PM, Richard S. Hall wrote:
>>>>
>>>>  On 9/1/09 13:59, Martin Cooper wrote:
>>>>>
>>>>>> On Tue, Sep 1, 2009 at 10:51 AM, Richard S. Hall<he...@ungoverned.org>
>>>>>>  wrote:
>>>>>>
>>>>>> I'm not sure I understand the issue here. Whether Aries becomes its
>>>>>> own TLP, or a sub-project of Felix or some other TLP, isn't relevant
>>>>>> until the project is ready to exit incubation. Why does it warrant
>>>>>> such apparently intense discussion before the project is even accepted
>>>>>>
>>>>>>
>>>>> We are actually discussing something else. We are discussing the scope of
>>>>> the proposal, which includes hosting OSGi standard service implementations,
>>>>> which is part of Felix' scope.
>>>>>
>>>>> If we are developing standard OSGi services within Apache, then Felix
>>>>> provides an enthusiastic community to do this and there is no need to start
>>>>> another incubator project for such a purpose. On the other hand, stuff like
>>>>> "a set of pluggable Java components enabling an enterprise OSGi application
>>>>> programming model" makes perfect sense to be incubated.
>>>>>
>>>>
>>>> Thanks for the clarification... So, your issue is mainly with "It is a
>>>> goal of the Aries project to provide a natural home for open source
>>>> implementations of current and future OSGi EEG specifications..."?
>>>> Personally, I tend to think of Felix in terms of OSGi Core Platform. I
>>>> certainly hadn't expected it to be the source for all OSGi standard
>>>> implementations from Apache -- not for implementations of Enterprise Expert
>>>> Group specs, anyway. I'm sure there are flaws with my perceptions...
>>>>
>>>> So, we have a group that is interested in working on an enterprise OSGi
>>>> application programming model at Apache (including implementations of at
>>>> least some EEG specifications). An incubator project would seem to be an
>>>> excellent place for this work to start. Interested Felix community members
>>>> would certainly be able to join this effort.
>>>>
>>>> It then becomes a question of, assuming successful incubation, where does
>>>> the community graduate to? TLP, Felix subproject(s), or elsewhere. All
>>>> successful outcomes, IMO.
>>>>
>>>> --kevan
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>
>
>
> --
> Karl Pauls
> karlpauls@gmail.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Karl Pauls <ka...@gmail.com>.
>From my perspective, the incubator isn't a loophole around the
meritocracy approach of existing TLPs. Submitting a couple of patches
can't be to high a barrier for people new to the ASF and the code
base.

We regularly vote people in as committers if they contribute to felix
subprojects and typically, if we accept a larger piece of code as a
donation, we try to get the creator as a committer too. We did this
with Karaf recently.

I think felix is an excellent place for consolidating OSGi
spec-related development here at Apache since the community is in
place and very active.

regards,

Karl

On Wed, Sep 2, 2009 at 5:29 PM, Guillaume Nodet<gn...@gmail.com> wrote:
> We have in this proposal a lot of people who are not felix committers and
> who are not even apache committers at all.
>
> They want to work on some code and create a community around it.  The way
> the ASF works means that the incubator is the right place to do so.  The
> only other solution is to develop it in a closed source environment and
> submit it at Apache when it's done, and i really don't think it's a good
> idea, given the willingness to do it in open source.
> The blueprint implementation has been developped so far inside the Geronimo
> TLP, part of the reason is that some of the people working on it were not
> felix committers, so it was way easier to work there instead of contributing
> patches until getting committership.    It is very difficult to commit to
> work on a new implementation of anything when you don't even have commit
> priviledges.  It's ok for patches, but not for a new dev.   That's what we
> have here.   We have people here wanting to work on some new OSGi spec
> implementation, and the only way for them to do so at Apache in to go into
> the incubator.
>
> Even, if Aries was to compete against Felix in any way, it's not a good
> enough argument.  We already have multiple projects in the ASF that do have
> overlap as it was pointed already multiple times in this thread: mutliple
> REST implementations, multiple JAX-WS implementations, etc...  But the Aries
> podling does not aim to even provide alternative implementation to what
> Felix already has, it's goal is to create a community with new people who
> want to work on that and deliver both implementations of new OSGi specs
> (such as blueprint and subsystems / applications, jpa ...) and also
> additional extensions (such as blueprint custom namespaces for transactions,
> etc...).
>
> For the independance, the only real place I know which provides OSGi
> components, not tainted with a given framework are SpringSource (though it's
> open source, the community is not really open) and OPS4J, but I do think
> it's a different discussion.
>
> I restate that the goal of the Aries proposal is to foster a community
> around some new code implementing some OSGi specs.  And I don't think we can
> do that inside an existing TLP, as we have non apache committers that want
> to create this code.  That's what the incubator has been created for.
>
> Last, accepting to create a podling does not mean the final destination of
> the podling is defined yet.   Aries could become either a TLP, a Felix
> subproject, or be split across the two of them.  The one that makes the most
> sense should prevail at graduation time.  By the time Aries is ready to
> graduate, the discussion about it's final destination will be held.  And
> that's where what you say will make sense and where your vote needs to be
> cast.
>
> I really do understand your concerns (even if I don't share them), but now
> is not the time to vote -1.
>
> On Wed, Sep 2, 2009 at 16:30, Richard S. Hall <he...@ungoverned.org> wrote:
>
>> I will try to keep this short.
>>
>> The OSGi Service Platform is composed of the core and compendium specs. The
>> EEG specs are not in any way special and will ultimately end up as part of
>> the compendium spec. Apache Felix was incubated to build a community at
>> Apache around implementing the OSGi specs.
>>
>> Now we are being told that this mission is too tainted because we implement
>> the framework spec, which is part of the core spec. I find this unfathomable
>> given the nature of OSGi and the efforts to which the Felix community goes
>> to be good OSGi citizens...we even allow for competing implementations
>> within our community.
>>
>> It is also particularly odd, since the Equinox and Knopflerfish communities
>> are in the same situation, implementing both core and compendium specs with
>> their frameworks largely synonymous with their project name.
>>
>> I am not naive enough to expect this discussion to change much, since I
>> imagine there has already been a fair amount of political calculation around
>> this proposal, otherwise the Felix community in general would have been
>> engaged earlier.
>>
>> So, here's my vote:
>>
>>   * -1 for the portion of the proposal creating yet another community
>>     for implementing OSGi specs at Apache since the Felix community
>>     would happily welcome more contribution (just like recently
>>     occurred with ServiceMix members being accepted as Felix
>>     committers and PMC members for the Karaf subproject)
>>   * +1 for the rest of the proposal to explore how to build an
>>     enterprise component model on OSGi and the other non-spec related
>>     topics.
>>
>> -> richard
>>
>>
>>
>> On 9/1/09 22:53, Kevan Miller wrote:
>>
>>>
>>> On Sep 1, 2009, at 2:08 PM, Richard S. Hall wrote:
>>>
>>>  On 9/1/09 13:59, Martin Cooper wrote:
>>>>
>>>>> On Tue, Sep 1, 2009 at 10:51 AM, Richard S. Hall<he...@ungoverned.org>
>>>>>  wrote:
>>>>>
>>>>> I'm not sure I understand the issue here. Whether Aries becomes its
>>>>> own TLP, or a sub-project of Felix or some other TLP, isn't relevant
>>>>> until the project is ready to exit incubation. Why does it warrant
>>>>> such apparently intense discussion before the project is even accepted
>>>>>
>>>>>
>>>> We are actually discussing something else. We are discussing the scope of
>>>> the proposal, which includes hosting OSGi standard service implementations,
>>>> which is part of Felix' scope.
>>>>
>>>> If we are developing standard OSGi services within Apache, then Felix
>>>> provides an enthusiastic community to do this and there is no need to start
>>>> another incubator project for such a purpose. On the other hand, stuff like
>>>> "a set of pluggable Java components enabling an enterprise OSGi application
>>>> programming model" makes perfect sense to be incubated.
>>>>
>>>
>>> Thanks for the clarification... So, your issue is mainly with "It is a
>>> goal of the Aries project to provide a natural home for open source
>>> implementations of current and future OSGi EEG specifications..."?
>>> Personally, I tend to think of Felix in terms of OSGi Core Platform. I
>>> certainly hadn't expected it to be the source for all OSGi standard
>>> implementations from Apache -- not for implementations of Enterprise Expert
>>> Group specs, anyway. I'm sure there are flaws with my perceptions...
>>>
>>> So, we have a group that is interested in working on an enterprise OSGi
>>> application programming model at Apache (including implementations of at
>>> least some EEG specifications). An incubator project would seem to be an
>>> excellent place for this work to start. Interested Felix community members
>>> would certainly be able to join this effort.
>>>
>>> It then becomes a question of, assuming successful incubation, where does
>>> the community graduate to? TLP, Felix subproject(s), or elsewhere. All
>>> successful outcomes, IMO.
>>>
>>> --kevan
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>



-- 
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Ralph,

Not yet. Let's wait for the discussions to wrap up.

thanks,
dims

On 09/06/2009 02:59 AM, Ralph Goers wrote:
>
> On Sep 5, 2009, at 10:36 AM, Niall Pemberton wrote:
>
>>>
>>
>> Voting against a bunch of people forming a new community here at the
>> ASF is v.disappointing and goes against what IMO the ASF is all about.
>> If the Felix community wants to get involved with their efforts then
>> great, if not then don't try to block what they want to do. As others
>> have said there are various options for graduation, but I think you've
>> made Felix less rather than more likely by your antagonism to this
>> proposal.
>>
>> I'm +1 to this proposal and hoping Felix members with shared interests
>> get involved.
>>
>>
>
>
> Is this an actual vote thread to accept the proposal?
>
> Ralph
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Ralph Goers <ra...@dslextreme.com>.
On Sep 5, 2009, at 10:36 AM, Niall Pemberton wrote:

>>
>
> Voting against a bunch of people forming a new community here at the
> ASF is v.disappointing and goes against what IMO the ASF is all about.
> If the Felix community wants to get involved with their efforts then
> great, if not then don't try to block what they want to do. As others
> have said there are various options for graduation, but I think you've
> made Felix less rather than more likely by your antagonism to this
> proposal.
>
> I'm +1 to this proposal and hoping Felix members with shared interests
> get involved.
>
>


Is this an actual vote thread to accept the proposal?

Ralph


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Richard,

I did agree with you that Felix would make a great choice as a destination TLP. The situation with ServiceMix/Karaf is 
not the same as what is happening here with a new set of incoming committers and code.

I sincerely do hope that cross-pollination happens even when the podling is in incubator.

thanks,
dims

On Wed, Sep 2, 2009 at 3:30 PM, Richard S. Hall<he...@ungoverned.org>  wrote:
>     * -1 for the portion of the proposal creating yet another community
>       for implementing OSGi specs at Apache since the Felix community
>       would happily welcome more contribution (just like recently
>       occurred with ServiceMix members being accepted as Felix
>       committers and PMC members for the Karaf subproject)

On 09/06/2009 12:39 AM, Richard S. Hall wrote:
>     I support the creation of a new community around an EE component
>     model for OSGi and OSGi specs dependent upon this technology;
>     however, I believe the Felix project is the best choice to work on
>     independent OSGi specs since we have been doing it for years and it
>     would guarantee cross-project collaboration.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 9/5/09 13:36, Niall Pemberton wrote:
> On Wed, Sep 2, 2009 at 3:30 PM, Richard S. Hall<he...@ungoverned.org>  wrote:
>    
>> I will try to keep this short.
>>
>> The OSGi Service Platform is composed of the core and compendium specs. The
>> EEG specs are not in any way special and will ultimately end up as part of
>> the compendium spec. Apache Felix was incubated to build a community at
>> Apache around implementing the OSGi specs.
>>
>> Now we are being told that this mission is too tainted because we implement
>> the framework spec, which is part of the core spec. I find this unfathomable
>> given the nature of OSGi and the efforts to which the Felix community goes
>> to be good OSGi citizens...we even allow for competing implementations
>> within our community.
>>
>> It is also particularly odd, since the Equinox and Knopflerfish communities
>> are in the same situation, implementing both core and compendium specs with
>> their frameworks largely synonymous with their project name.
>>
>> I am not naive enough to expect this discussion to change much, since I
>> imagine there has already been a fair amount of political calculation around
>> this proposal, otherwise the Felix community in general would have been
>> engaged earlier.
>>
>> So, here's my vote:
>>
>>    * -1 for the portion of the proposal creating yet another community
>>      for implementing OSGi specs at Apache since the Felix community
>>      would happily welcome more contribution (just like recently
>>      occurred with ServiceMix members being accepted as Felix
>>      committers and PMC members for the Karaf subproject)
>>      
> Voting against a bunch of people forming a new community here at the
> ASF is v.disappointing and goes against what IMO the ASF is all about.
>    

It is also very disappointing to have my position mischaracterized, 
since I have been pretty consistent:

    I support the creation of a new community around an EE component
    model for OSGi and OSGi specs dependent upon this technology;
    however, I believe the Felix project is the best choice to work on
    independent OSGi specs since we have been doing it for years and it
    would guarantee cross-project collaboration.

If you find this position disappointing, then I am not sure what to say. 
On the other hand, if you just disagree with it, that's fine, since I 
disagree too. And it is my understanding that this is the forum to 
discuss disagreements about project proposals.

One thing we can all agree on, is this thread is rather tiresome, so 
let's move on.

-> richard


> If the Felix community wants to get involved with their efforts then
> great, if not then don't try to block what they want to do. As others
> have said there are various options for graduation, but I think you've
> made Felix less rather than more likely by your antagonism to this
> proposal.
>
> I'm +1 to this proposal and hoping Felix members with shared interests
> get involved.
>
> Niall
>
>    
>>    * +1 for the rest of the proposal to explore how to build an
>>      enterprise component model on OSGi and the other non-spec related
>>      topics.
>>
>> ->  richard
>>
>>
>> On 9/1/09 22:53, Kevan Miller wrote:
>>      
>>> On Sep 1, 2009, at 2:08 PM, Richard S. Hall wrote:
>>>
>>>        
>>>> On 9/1/09 13:59, Martin Cooper wrote:
>>>>          
>>>>> On Tue, Sep 1, 2009 at 10:51 AM, Richard S. Hall<he...@ungoverned.org>
>>>>>   wrote:
>>>>>
>>>>> I'm not sure I understand the issue here. Whether Aries becomes its
>>>>> own TLP, or a sub-project of Felix or some other TLP, isn't relevant
>>>>> until the project is ready to exit incubation. Why does it warrant
>>>>> such apparently intense discussion before the project is even accepted
>>>>>
>>>>>            
>>>> We are actually discussing something else. We are discussing the scope of
>>>> the proposal, which includes hosting OSGi standard service implementations,
>>>> which is part of Felix' scope.
>>>>
>>>> If we are developing standard OSGi services within Apache, then Felix
>>>> provides an enthusiastic community to do this and there is no need to start
>>>> another incubator project for such a purpose. On the other hand, stuff like
>>>> "a set of pluggable Java components enabling an enterprise OSGi application
>>>> programming model" makes perfect sense to be incubated.
>>>>          
>>> Thanks for the clarification... So, your issue is mainly with "It is a
>>> goal of the Aries project to provide a natural home for open source
>>> implementations of current and future OSGi EEG specifications..."?
>>> Personally, I tend to think of Felix in terms of OSGi Core Platform. I
>>> certainly hadn't expected it to be the source for all OSGi standard
>>> implementations from Apache -- not for implementations of Enterprise Expert
>>> Group specs, anyway. I'm sure there are flaws with my perceptions...
>>>
>>> So, we have a group that is interested in working on an enterprise OSGi
>>> application programming model at Apache (including implementations of at
>>> least some EEG specifications). An incubator project would seem to be an
>>> excellent place for this work to start. Interested Felix community members
>>> would certainly be able to join this effort.
>>>
>>> It then becomes a question of, assuming successful incubation, where does
>>> the community graduate to? TLP, Felix subproject(s), or elsewhere. All
>>> successful outcomes, IMO.
>>>
>>> --kevan
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>        
>>      
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>    

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niall Pemberton <ni...@gmail.com>.
On Wed, Sep 2, 2009 at 3:30 PM, Richard S. Hall <he...@ungoverned.org> wrote:
> I will try to keep this short.
>
> The OSGi Service Platform is composed of the core and compendium specs. The
> EEG specs are not in any way special and will ultimately end up as part of
> the compendium spec. Apache Felix was incubated to build a community at
> Apache around implementing the OSGi specs.
>
> Now we are being told that this mission is too tainted because we implement
> the framework spec, which is part of the core spec. I find this unfathomable
> given the nature of OSGi and the efforts to which the Felix community goes
> to be good OSGi citizens...we even allow for competing implementations
> within our community.
>
> It is also particularly odd, since the Equinox and Knopflerfish communities
> are in the same situation, implementing both core and compendium specs with
> their frameworks largely synonymous with their project name.
>
> I am not naive enough to expect this discussion to change much, since I
> imagine there has already been a fair amount of political calculation around
> this proposal, otherwise the Felix community in general would have been
> engaged earlier.
>
> So, here's my vote:
>
>   * -1 for the portion of the proposal creating yet another community
>     for implementing OSGi specs at Apache since the Felix community
>     would happily welcome more contribution (just like recently
>     occurred with ServiceMix members being accepted as Felix
>     committers and PMC members for the Karaf subproject)

Voting against a bunch of people forming a new community here at the
ASF is v.disappointing and goes against what IMO the ASF is all about.
If the Felix community wants to get involved with their efforts then
great, if not then don't try to block what they want to do. As others
have said there are various options for graduation, but I think you've
made Felix less rather than more likely by your antagonism to this
proposal.

I'm +1 to this proposal and hoping Felix members with shared interests
get involved.

Niall

>   * +1 for the rest of the proposal to explore how to build an
>     enterprise component model on OSGi and the other non-spec related
>     topics.
>
> -> richard
>
>
> On 9/1/09 22:53, Kevan Miller wrote:
>>
>> On Sep 1, 2009, at 2:08 PM, Richard S. Hall wrote:
>>
>>> On 9/1/09 13:59, Martin Cooper wrote:
>>>>
>>>> On Tue, Sep 1, 2009 at 10:51 AM, Richard S. Hall<he...@ungoverned.org>
>>>>  wrote:
>>>>
>>>> I'm not sure I understand the issue here. Whether Aries becomes its
>>>> own TLP, or a sub-project of Felix or some other TLP, isn't relevant
>>>> until the project is ready to exit incubation. Why does it warrant
>>>> such apparently intense discussion before the project is even accepted
>>>>
>>>
>>> We are actually discussing something else. We are discussing the scope of
>>> the proposal, which includes hosting OSGi standard service implementations,
>>> which is part of Felix' scope.
>>>
>>> If we are developing standard OSGi services within Apache, then Felix
>>> provides an enthusiastic community to do this and there is no need to start
>>> another incubator project for such a purpose. On the other hand, stuff like
>>> "a set of pluggable Java components enabling an enterprise OSGi application
>>> programming model" makes perfect sense to be incubated.
>>
>> Thanks for the clarification... So, your issue is mainly with "It is a
>> goal of the Aries project to provide a natural home for open source
>> implementations of current and future OSGi EEG specifications..."?
>> Personally, I tend to think of Felix in terms of OSGi Core Platform. I
>> certainly hadn't expected it to be the source for all OSGi standard
>> implementations from Apache -- not for implementations of Enterprise Expert
>> Group specs, anyway. I'm sure there are flaws with my perceptions...
>>
>> So, we have a group that is interested in working on an enterprise OSGi
>> application programming model at Apache (including implementations of at
>> least some EEG specifications). An incubator project would seem to be an
>> excellent place for this work to start. Interested Felix community members
>> would certainly be able to join this effort.
>>
>> It then becomes a question of, assuming successful incubation, where does
>> the community graduate to? TLP, Felix subproject(s), or elsewhere. All
>> successful outcomes, IMO.
>>
>> --kevan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
We have concluded that umbrellas are no good, and IIRC we have visited this
line of argument in the past, and perhaps it is time again.

My line is; for the sake of the projects, keep them reasonably small. Learn
the art of TAG, create a browse system where each project with the TAG shows
up, and decide suitable endorsed tags among the PMCs or Members.

-- Cheers
Niclas

On Sep 2, 2009 11:58 PM, "Emmanuel Lecharny" <el...@apache.org> wrote:

Guillaume Nodet wrote: > > We have in this proposal a lot of people who are
not felix committers and...
Having apache committers from a project be granted commit access to another
project is not really a problem, as soon as the other project's PMC decide
what are the "rules".

The new project can also be a Felix subproject, with specific commit access
granted to a specific set of committers, if needed. I'm pretty sure that
infra can deal with such a granularity. Also the felix PMC can check that
the new committers are not committing in the other projects, if needed.

So far, this is how we did for FtpServer, SSHd and Vysper in MINA. In fact,
Vysper is still in a sandbox, but I can see the moment where it will get
out, either as a MINA subproject, or as a TLP. The biggest advantage is
that, as all the committers were already working on other projects, and as
the MINA PMC was able to check that the project was following the rules (IP,
etc), it's far easier than going through incubation.

I can see how better it could be for Aries to start as a felix subproject,
for many reasons.

> > Even, if Aries was to compete against Felix in any way, it's not a good
> enough argument.  We ...
It would be better to see Felix as a OSGi aggregator (a bit like WS or DB
are), with potentially many implementations. It would be so great if Buildr,
Ant, Maven, Archiva, Continuum, were all embedded in a Build Tools project,
instead of being one of the 70 TLP. From the user PoV, it's difficult to
know what they all are doing.

This is a bit more general than just Felix, here. We have more than 70 TLP,
and this number will continue to grow in the next few years. Why can't we
aggregate projects within categories at some point ?

> > For the independance, the only real place I know which provides OSGi >
components, not tainted ...
I'm not sure that because a project has non apache committers, it should be
started in incubator, as soon as the TLP can "educate" the project. of
course, if all the peope are non apache committers, that's a different
story.

That being said, the best would be to first check for synergies, then think
about creating the poddling if there are not too much overlap. Be pragmatic
!

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org

--------------------------------------------------------------------- To
unsubscribe, e-mail: ge...

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Leo Simons <ma...@leosimons.com>.
On Wed, Sep 2, 2009 at 4:29 PM, Guillaume Nodet<gn...@gmail.com> wrote:
> We have in this proposal a lot of people who are not felix committers and
> who are not even apache committers at all.
>
> They want to work on some code and create a community around it.  The way
> the ASF works means that the incubator is the right place to do so.

Sidenote: not necessarily always the *only* possible right place.

A PMC can easily grant lots of access to its repositories to existing
committers. For example, the gump repo is open to all ASF committers,
and the excalibur repo is open to cocoon, james and turbine
committers.

Adding new committers obviously has a few more barriers, but those
barriers are not all bad. It can also be quite healthy for people new
to apache to submit patches that are committed by those people that
are already apache committers; I believe its often a faster way to
learn apache-style processes than the sort-of "sandboxing" that
happens in incubator. In fact, Harmony started with 0 committers (and
lots of contributors) and the community dynamic that resulted from
that approach was actually quite a good one, and I don't think it
meant lost velocity in the end either.


cheers,


- Leo

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Emmanuel Lecharny <el...@apache.org>.
Guillaume Nodet wrote:
> We have in this proposal a lot of people who are not felix committers and
> who are not even apache committers at all.
>
> They want to work on some code and create a community around it.  The way
> the ASF works means that the incubator is the right place to do so.  The
> only other solution is to develop it in a closed source environment and
> submit it at Apache when it's done, and i really don't think it's a good
> idea, given the willingness to do it in open source.
> The blueprint implementation has been developped so far inside the Geronimo
> TLP, part of the reason is that some of the people working on it were not
> felix committers, so it was way easier to work there instead of contributing
> patches until getting committership.    It is very difficult to commit to
> work on a new implementation of anything when you don't even have commit
> priviledges.  It's ok for patches, but not for a new dev.   That's what we
> have here.   We have people here wanting to work on some new OSGi spec
> implementation, and the only way for them to do so at Apache in to go into
> the incubator.
>   
Having apache committers from a project be granted commit access to 
another project is not really a problem, as soon as the other project's 
PMC decide what are the "rules".

The new project can also be a Felix subproject, with specific commit 
access granted to a specific set of committers, if needed. I'm pretty 
sure that infra can deal with such a granularity. Also the felix PMC can 
check that the new committers are not committing in the other projects, 
if needed.

So far, this is how we did for FtpServer, SSHd and Vysper in MINA. In 
fact, Vysper is still in a sandbox, but I can see the moment where it 
will get out, either as a MINA subproject, or as a TLP. The biggest 
advantage is that, as all the committers were already working on other 
projects, and as the MINA PMC was able to check that the project was 
following the rules (IP, etc), it's far easier than going through 
incubation.

I can see how better it could be for Aries to start as a felix 
subproject, for many reasons.
> Even, if Aries was to compete against Felix in any way, it's not a good
> enough argument.  We already have multiple projects in the ASF that do have
> overlap as it was pointed already multiple times in this thread: mutliple
> REST implementations, multiple JAX-WS implementations, etc...  But the Aries
> podling does not aim to even provide alternative implementation to what
> Felix already has, it's goal is to create a community with new people who
> want to work on that and deliver both implementations of new OSGi specs
> (such as blueprint and subsystems / applications, jpa ...) and also
> additional extensions (such as blueprint custom namespaces for transactions,
> etc...).
>   
It would be better to see Felix as a OSGi aggregator (a bit like WS or 
DB are), with potentially many implementations. It would be so great if 
Buildr, Ant, Maven, Archiva, Continuum, were all embedded in a Build 
Tools project, instead of being one of the 70 TLP. From the user PoV, 
it's difficult to know what they all are doing.

This is a bit more general than just Felix, here. We have more than 70 
TLP, and this number will continue to grow in the next few years. Why 
can't we aggregate projects within categories at some point ?
> For the independance, the only real place I know which provides OSGi
> components, not tainted with a given framework are SpringSource (though it's
> open source, the community is not really open) and OPS4J, but I do think
> it's a different discussion.
>
> I restate that the goal of the Aries proposal is to foster a community
> around some new code implementing some OSGi specs.  And I don't think we can
> do that inside an existing TLP, as we have non apache committers that want
> to create this code.  That's what the incubator has been created for.
>   
I'm not sure that because a project has non apache committers, it should 
be started in incubator, as soon as the TLP can "educate" the project. 
of course, if all the peope are non apache committers, that's a 
different story.

That being said, the best would be to first check for synergies, then 
think about creating the poddling if there are not too much overlap. Be 
pragmatic !

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
We have in this proposal a lot of people who are not felix committers and
who are not even apache committers at all.

They want to work on some code and create a community around it.  The way
the ASF works means that the incubator is the right place to do so.  The
only other solution is to develop it in a closed source environment and
submit it at Apache when it's done, and i really don't think it's a good
idea, given the willingness to do it in open source.
The blueprint implementation has been developped so far inside the Geronimo
TLP, part of the reason is that some of the people working on it were not
felix committers, so it was way easier to work there instead of contributing
patches until getting committership.    It is very difficult to commit to
work on a new implementation of anything when you don't even have commit
priviledges.  It's ok for patches, but not for a new dev.   That's what we
have here.   We have people here wanting to work on some new OSGi spec
implementation, and the only way for them to do so at Apache in to go into
the incubator.

Even, if Aries was to compete against Felix in any way, it's not a good
enough argument.  We already have multiple projects in the ASF that do have
overlap as it was pointed already multiple times in this thread: mutliple
REST implementations, multiple JAX-WS implementations, etc...  But the Aries
podling does not aim to even provide alternative implementation to what
Felix already has, it's goal is to create a community with new people who
want to work on that and deliver both implementations of new OSGi specs
(such as blueprint and subsystems / applications, jpa ...) and also
additional extensions (such as blueprint custom namespaces for transactions,
etc...).

For the independance, the only real place I know which provides OSGi
components, not tainted with a given framework are SpringSource (though it's
open source, the community is not really open) and OPS4J, but I do think
it's a different discussion.

I restate that the goal of the Aries proposal is to foster a community
around some new code implementing some OSGi specs.  And I don't think we can
do that inside an existing TLP, as we have non apache committers that want
to create this code.  That's what the incubator has been created for.

Last, accepting to create a podling does not mean the final destination of
the podling is defined yet.   Aries could become either a TLP, a Felix
subproject, or be split across the two of them.  The one that makes the most
sense should prevail at graduation time.  By the time Aries is ready to
graduate, the discussion about it's final destination will be held.  And
that's where what you say will make sense and where your vote needs to be
cast.

I really do understand your concerns (even if I don't share them), but now
is not the time to vote -1.

On Wed, Sep 2, 2009 at 16:30, Richard S. Hall <he...@ungoverned.org> wrote:

> I will try to keep this short.
>
> The OSGi Service Platform is composed of the core and compendium specs. The
> EEG specs are not in any way special and will ultimately end up as part of
> the compendium spec. Apache Felix was incubated to build a community at
> Apache around implementing the OSGi specs.
>
> Now we are being told that this mission is too tainted because we implement
> the framework spec, which is part of the core spec. I find this unfathomable
> given the nature of OSGi and the efforts to which the Felix community goes
> to be good OSGi citizens...we even allow for competing implementations
> within our community.
>
> It is also particularly odd, since the Equinox and Knopflerfish communities
> are in the same situation, implementing both core and compendium specs with
> their frameworks largely synonymous with their project name.
>
> I am not naive enough to expect this discussion to change much, since I
> imagine there has already been a fair amount of political calculation around
> this proposal, otherwise the Felix community in general would have been
> engaged earlier.
>
> So, here's my vote:
>
>   * -1 for the portion of the proposal creating yet another community
>     for implementing OSGi specs at Apache since the Felix community
>     would happily welcome more contribution (just like recently
>     occurred with ServiceMix members being accepted as Felix
>     committers and PMC members for the Karaf subproject)
>   * +1 for the rest of the proposal to explore how to build an
>     enterprise component model on OSGi and the other non-spec related
>     topics.
>
> -> richard
>
>
>
> On 9/1/09 22:53, Kevan Miller wrote:
>
>>
>> On Sep 1, 2009, at 2:08 PM, Richard S. Hall wrote:
>>
>>  On 9/1/09 13:59, Martin Cooper wrote:
>>>
>>>> On Tue, Sep 1, 2009 at 10:51 AM, Richard S. Hall<he...@ungoverned.org>
>>>>  wrote:
>>>>
>>>> I'm not sure I understand the issue here. Whether Aries becomes its
>>>> own TLP, or a sub-project of Felix or some other TLP, isn't relevant
>>>> until the project is ready to exit incubation. Why does it warrant
>>>> such apparently intense discussion before the project is even accepted
>>>>
>>>>
>>> We are actually discussing something else. We are discussing the scope of
>>> the proposal, which includes hosting OSGi standard service implementations,
>>> which is part of Felix' scope.
>>>
>>> If we are developing standard OSGi services within Apache, then Felix
>>> provides an enthusiastic community to do this and there is no need to start
>>> another incubator project for such a purpose. On the other hand, stuff like
>>> "a set of pluggable Java components enabling an enterprise OSGi application
>>> programming model" makes perfect sense to be incubated.
>>>
>>
>> Thanks for the clarification... So, your issue is mainly with "It is a
>> goal of the Aries project to provide a natural home for open source
>> implementations of current and future OSGi EEG specifications..."?
>> Personally, I tend to think of Felix in terms of OSGi Core Platform. I
>> certainly hadn't expected it to be the source for all OSGi standard
>> implementations from Apache -- not for implementations of Enterprise Expert
>> Group specs, anyway. I'm sure there are flaws with my perceptions...
>>
>> So, we have a group that is interested in working on an enterprise OSGi
>> application programming model at Apache (including implementations of at
>> least some EEG specifications). An incubator project would seem to be an
>> excellent place for this work to start. Interested Felix community members
>> would certainly be able to join this effort.
>>
>> It then becomes a question of, assuming successful incubation, where does
>> the community graduate to? TLP, Felix subproject(s), or elsewhere. All
>> successful outcomes, IMO.
>>
>> --kevan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Kevan Miller wrote:
> 
> It then becomes a question of, assuming successful incubation, where
> does the community graduate to? TLP, Felix subproject(s), or elsewhere.

And remember that Felix charter is framed in terms of "the OSGi Service
Platform and other software that is associated with or related to the OSGi
Service Platform" (whatever that definition is ;)  Remember that it's always
possible to rescope a TLP (have the board change it's charter to some
wider or narrower definition), and that overlapping TLP's are an OK thing.

> All successful outcomes, IMO.

+1

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
I will try to keep this short.

The OSGi Service Platform is composed of the core and compendium specs. 
The EEG specs are not in any way special and will ultimately end up as 
part of the compendium spec. Apache Felix was incubated to build a 
community at Apache around implementing the OSGi specs.

Now we are being told that this mission is too tainted because we 
implement the framework spec, which is part of the core spec. I find 
this unfathomable given the nature of OSGi and the efforts to which the 
Felix community goes to be good OSGi citizens...we even allow for 
competing implementations within our community.

It is also particularly odd, since the Equinox and Knopflerfish 
communities are in the same situation, implementing both core and 
compendium specs with their frameworks largely synonymous with their 
project name.

I am not naive enough to expect this discussion to change much, since I 
imagine there has already been a fair amount of political calculation 
around this proposal, otherwise the Felix community in general would 
have been engaged earlier.

So, here's my vote:

    * -1 for the portion of the proposal creating yet another community
      for implementing OSGi specs at Apache since the Felix community
      would happily welcome more contribution (just like recently
      occurred with ServiceMix members being accepted as Felix
      committers and PMC members for the Karaf subproject)
    * +1 for the rest of the proposal to explore how to build an
      enterprise component model on OSGi and the other non-spec related
      topics.

-> richard


On 9/1/09 22:53, Kevan Miller wrote:
>
> On Sep 1, 2009, at 2:08 PM, Richard S. Hall wrote:
>
>> On 9/1/09 13:59, Martin Cooper wrote:
>>> On Tue, Sep 1, 2009 at 10:51 AM, Richard S. 
>>> Hall<he...@ungoverned.org>  wrote:
>>>
>>> I'm not sure I understand the issue here. Whether Aries becomes its
>>> own TLP, or a sub-project of Felix or some other TLP, isn't relevant
>>> until the project is ready to exit incubation. Why does it warrant
>>> such apparently intense discussion before the project is even accepted
>>>
>>
>> We are actually discussing something else. We are discussing the 
>> scope of the proposal, which includes hosting OSGi standard service 
>> implementations, which is part of Felix' scope.
>>
>> If we are developing standard OSGi services within Apache, then Felix 
>> provides an enthusiastic community to do this and there is no need to 
>> start another incubator project for such a purpose. On the other 
>> hand, stuff like "a set of pluggable Java components enabling an 
>> enterprise OSGi application programming model" makes perfect sense to 
>> be incubated.
>
> Thanks for the clarification... So, your issue is mainly with "It is a 
> goal of the Aries project to provide a natural home for open source 
> implementations of current and future OSGi EEG specifications..."? 
> Personally, I tend to think of Felix in terms of OSGi Core Platform. I 
> certainly hadn't expected it to be the source for all OSGi standard 
> implementations from Apache -- not for implementations of Enterprise 
> Expert Group specs, anyway. I'm sure there are flaws with my 
> perceptions...
>
> So, we have a group that is interested in working on an enterprise 
> OSGi application programming model at Apache (including 
> implementations of at least some EEG specifications). An incubator 
> project would seem to be an excellent place for this work to start. 
> Interested Felix community members would certainly be able to join 
> this effort.
>
> It then becomes a question of, assuming successful incubation, where 
> does the community graduate to? TLP, Felix subproject(s), or 
> elsewhere. All successful outcomes, IMO.
>
> --kevan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Kevan Miller <ke...@gmail.com>.
On Sep 1, 2009, at 2:08 PM, Richard S. Hall wrote:

> On 9/1/09 13:59, Martin Cooper wrote:
>> On Tue, Sep 1, 2009 at 10:51 AM, Richard S.  
>> Hall<he...@ungoverned.org>  wrote:
>>
>> I'm not sure I understand the issue here. Whether Aries becomes its
>> own TLP, or a sub-project of Felix or some other TLP, isn't relevant
>> until the project is ready to exit incubation. Why does it warrant
>> such apparently intense discussion before the project is even  
>> accepted
>>
>
> We are actually discussing something else. We are discussing the  
> scope of the proposal, which includes hosting OSGi standard service  
> implementations, which is part of Felix' scope.
>
> If we are developing standard OSGi services within Apache, then  
> Felix provides an enthusiastic community to do this and there is no  
> need to start another incubator project for such a purpose. On the  
> other hand, stuff like "a set of pluggable Java components enabling  
> an enterprise OSGi application programming model" makes perfect  
> sense to be incubated.

Thanks for the clarification... So, your issue is mainly with "It is a  
goal of the Aries project to provide a natural home for open source  
implementations of current and future OSGi EEG specifications..."?  
Personally, I tend to think of Felix in terms of OSGi Core Platform. I  
certainly hadn't expected it to be the source for all OSGi standard  
implementations from Apache -- not for implementations of Enterprise  
Expert Group specs, anyway. I'm sure there are flaws with my  
perceptions...

So, we have a group that is interested in working on an enterprise  
OSGi application programming model at Apache (including  
implementations of at least some EEG specifications). An incubator  
project would seem to be an excellent place for this work to start.  
Interested Felix community members would certainly be able to join  
this effort.

It then becomes a question of, assuming successful incubation, where  
does the community graduate to? TLP, Felix subproject(s), or  
elsewhere. All successful outcomes, IMO.

--kevan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 9/1/09 13:59, Martin Cooper wrote:
> On Tue, Sep 1, 2009 at 10:51 AM, Richard S. Hall<he...@ungoverned.org>  wrote:
>
> I'm not sure I understand the issue here. Whether Aries becomes its
> own TLP, or a sub-project of Felix or some other TLP, isn't relevant
> until the project is ready to exit incubation. Why does it warrant
> such apparently intense discussion before the project is even accepted
>    

We are actually discussing something else. We are discussing the scope 
of the proposal, which includes hosting OSGi standard service 
implementations, which is part of Felix' scope.

If we are developing standard OSGi services within Apache, then Felix 
provides an enthusiastic community to do this and there is no need to 
start another incubator project for such a purpose. On the other hand, 
stuff like "a set of pluggable Java components enabling an enterprise 
OSGi application programming model" makes perfect sense to be incubated.

-> richard

> into incubation?
>
> --
> Martin Cooper
>
>
>    
>> As I said on dev@felix and will repeat here:
>>
>> ----
>>
>> I don't agree about renaming the [Felix] TLP. There are so many examples of
>> similar situations. I cannot believe we are truly in a unique situation
>> here:
>>
>>    * "Apache" typically means the HTTP Server project, but it also
>>      refers to the foundation and all of its independent projects.
>>    * "Eclipse" typically means the IDE, but there is also a runtime and
>>      foundation with independent projects.
>>
>> Acting like this isn't normal or something that is too confusing to ever
>> resolve seems a bit preposterous.
>>
>> ----
>>
>> While I don't believe the situation is as confusing as is contended, I have
>> no issue with coming up with a different name for the Apache Felix Framework
>> (its name is technically Framework right now), so that the Apache Felix
>> project can continue to pursue its original charter.
>>
>> ->  richard
>>
>> On 9/1/09 12:58, Niclas Hedhman wrote:
>>      
>>> I'm not subscribing to dev@felix.a.o at the moment, but would still like
>>> to
>>> hear the outcome of this...
>>>
>>> Richard, we (you and I at least) have discussed this more than once in the
>>> past and I totally agree with Guillaume that the perception is there, it
>>> is
>>> everything and near impossible to change. I ALSO agree with Richard that
>>> spec implementations should reside with Felix.
>>>
>>> Now, I think name manipulations are going to be necessary. My take is;
>>>
>>> Apache Felix = a OSGi framework, runtime, installers, binaries, bells and
>>> whistles. The whole kitchen sink if you like. The framework implementation
>>> itself probably lives here, with the Core spec service implementations.
>>>
>>> Apache Foo = a foundry to dev OSGi spec implementations. One or many. Most
>>> will be dependencies to Felix, but the detach shows that they are intended
>>> for all.
>>>
>>> Apache Bar = a component foundry outside the spec suite.
>>>
>>> And let Aries, Karaf, Ace and what else in future to go TLP if/when they
>>> are
>>> ready.
>>>
>>> I think ServiceMix has with its friends shown how nice eco-systems can
>>> work,
>>> and with OSGi's modularity strengths it should be even more so... In fact,
>>> instead of seeing this as a weakening of Felix position (which is what I
>>> think Richard sees), I think it will strengthen OSGi's natural place in
>>> the
>>> Apache Landscape.
>>>
>>> Don't forget, you are free to participate at as many places as you wish.
>>>
>>> -- Niclas
>>>
>>> P.S. Sorry for poor quoting. On mobile...
>>>
>>> On Sep 2, 2009 12:14 AM, "Guillaume Nodet"<gn...@gmail.com>    wrote:
>>>
>>> On Tue, Sep 1, 2009 at 18:06, Richard S. Hall<he...@ungoverned.org>
>>>   wrote:
>>>
>>>        
>>>>> Creating another pr...
>>>>>
>>>>>            
>>> Well, the problem I see here is that we *need* to educate non-techies.
>>>   This
>>> obvisouly mean that there is a confusion.  Education is just a work around
>>> the need to remove the confusion imho.  So let's discuss that on
>>> dev@felix.a.o, I don't think this thread belongs here.
>>>
>>> -- Cheers, Guillaume Nodet ------------------------ Blog:
>>> http://gnodet.blogspot.com/ ----------...
>>>
>>>
>>>        
>>      
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>    

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Martin Cooper <ma...@apache.org>.
On Tue, Sep 1, 2009 at 10:51 AM, Richard S. Hall<he...@ungoverned.org> wrote:

I'm not sure I understand the issue here. Whether Aries becomes its
own TLP, or a sub-project of Felix or some other TLP, isn't relevant
until the project is ready to exit incubation. Why does it warrant
such apparently intense discussion before the project is even accepted
into incubation?

--
Martin Cooper


> As I said on dev@felix and will repeat here:
>
> ----
>
> I don't agree about renaming the [Felix] TLP. There are so many examples of
> similar situations. I cannot believe we are truly in a unique situation
> here:
>
>   * "Apache" typically means the HTTP Server project, but it also
>     refers to the foundation and all of its independent projects.
>   * "Eclipse" typically means the IDE, but there is also a runtime and
>     foundation with independent projects.
>
> Acting like this isn't normal or something that is too confusing to ever
> resolve seems a bit preposterous.
>
> ----
>
> While I don't believe the situation is as confusing as is contended, I have
> no issue with coming up with a different name for the Apache Felix Framework
> (its name is technically Framework right now), so that the Apache Felix
> project can continue to pursue its original charter.
>
> -> richard
>
> On 9/1/09 12:58, Niclas Hedhman wrote:
>>
>> I'm not subscribing to dev@felix.a.o at the moment, but would still like
>> to
>> hear the outcome of this...
>>
>> Richard, we (you and I at least) have discussed this more than once in the
>> past and I totally agree with Guillaume that the perception is there, it
>> is
>> everything and near impossible to change. I ALSO agree with Richard that
>> spec implementations should reside with Felix.
>>
>> Now, I think name manipulations are going to be necessary. My take is;
>>
>> Apache Felix = a OSGi framework, runtime, installers, binaries, bells and
>> whistles. The whole kitchen sink if you like. The framework implementation
>> itself probably lives here, with the Core spec service implementations.
>>
>> Apache Foo = a foundry to dev OSGi spec implementations. One or many. Most
>> will be dependencies to Felix, but the detach shows that they are intended
>> for all.
>>
>> Apache Bar = a component foundry outside the spec suite.
>>
>> And let Aries, Karaf, Ace and what else in future to go TLP if/when they
>> are
>> ready.
>>
>> I think ServiceMix has with its friends shown how nice eco-systems can
>> work,
>> and with OSGi's modularity strengths it should be even more so... In fact,
>> instead of seeing this as a weakening of Felix position (which is what I
>> think Richard sees), I think it will strengthen OSGi's natural place in
>> the
>> Apache Landscape.
>>
>> Don't forget, you are free to participate at as many places as you wish.
>>
>> -- Niclas
>>
>> P.S. Sorry for poor quoting. On mobile...
>>
>> On Sep 2, 2009 12:14 AM, "Guillaume Nodet"<gn...@gmail.com>  wrote:
>>
>> On Tue, Sep 1, 2009 at 18:06, Richard S. Hall<he...@ungoverned.org>
>>  wrote:
>>
>>>>
>>>> Creating another pr...
>>>>
>>
>> Well, the problem I see here is that we *need* to educate non-techies.
>>  This
>> obvisouly mean that there is a confusion.  Education is just a work around
>> the need to remove the confusion imho.  So let's discuss that on
>> dev@felix.a.o, I don't think this thread belongs here.
>>
>> -- Cheers, Guillaume Nodet ------------------------ Blog:
>> http://gnodet.blogspot.com/ ----------...
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
As I said on dev@felix and will repeat here:

----

I don't agree about renaming the [Felix] TLP. There are so many examples 
of similar situations. I cannot believe we are truly in a unique 
situation here:

    * "Apache" typically means the HTTP Server project, but it also
      refers to the foundation and all of its independent projects.
    * "Eclipse" typically means the IDE, but there is also a runtime and
      foundation with independent projects.

Acting like this isn't normal or something that is too confusing to ever 
resolve seems a bit preposterous.

----

While I don't believe the situation is as confusing as is contended, I 
have no issue with coming up with a different name for the Apache Felix 
Framework (its name is technically Framework right now), so that the 
Apache Felix project can continue to pursue its original charter.

-> richard

On 9/1/09 12:58, Niclas Hedhman wrote:
> I'm not subscribing to dev@felix.a.o at the moment, but would still like to
> hear the outcome of this...
>
> Richard, we (you and I at least) have discussed this more than once in the
> past and I totally agree with Guillaume that the perception is there, it is
> everything and near impossible to change. I ALSO agree with Richard that
> spec implementations should reside with Felix.
>
> Now, I think name manipulations are going to be necessary. My take is;
>
> Apache Felix = a OSGi framework, runtime, installers, binaries, bells and
> whistles. The whole kitchen sink if you like. The framework implementation
> itself probably lives here, with the Core spec service implementations.
>
> Apache Foo = a foundry to dev OSGi spec implementations. One or many. Most
> will be dependencies to Felix, but the detach shows that they are intended
> for all.
>
> Apache Bar = a component foundry outside the spec suite.
>
> And let Aries, Karaf, Ace and what else in future to go TLP if/when they are
> ready.
>
> I think ServiceMix has with its friends shown how nice eco-systems can work,
> and with OSGi's modularity strengths it should be even more so... In fact,
> instead of seeing this as a weakening of Felix position (which is what I
> think Richard sees), I think it will strengthen OSGi's natural place in the
> Apache Landscape.
>
> Don't forget, you are free to participate at as many places as you wish.
>
> -- Niclas
>
> P.S. Sorry for poor quoting. On mobile...
>
> On Sep 2, 2009 12:14 AM, "Guillaume Nodet"<gn...@gmail.com>  wrote:
>
> On Tue, Sep 1, 2009 at 18:06, Richard S. Hall<he...@ungoverned.org>  wrote:
>    
>>> Creating another pr...
>>>        
> Well, the problem I see here is that we *need* to educate non-techies.  This
> obvisouly mean that there is a confusion.  Education is just a work around
> the need to remove the confusion imho.  So let's discuss that on
> dev@felix.a.o, I don't think this thread belongs here.
>
> -- Cheers, Guillaume Nodet ------------------------ Blog:
> http://gnodet.blogspot.com/ ----------...
>
>    

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
I'm not subscribing to dev@felix.a.o at the moment, but would still like to
hear the outcome of this...

Richard, we (you and I at least) have discussed this more than once in the
past and I totally agree with Guillaume that the perception is there, it is
everything and near impossible to change. I ALSO agree with Richard that
spec implementations should reside with Felix.

Now, I think name manipulations are going to be necessary. My take is;

Apache Felix = a OSGi framework, runtime, installers, binaries, bells and
whistles. The whole kitchen sink if you like. The framework implementation
itself probably lives here, with the Core spec service implementations.

Apache Foo = a foundry to dev OSGi spec implementations. One or many. Most
will be dependencies to Felix, but the detach shows that they are intended
for all.

Apache Bar = a component foundry outside the spec suite.

And let Aries, Karaf, Ace and what else in future to go TLP if/when they are
ready.

I think ServiceMix has with its friends shown how nice eco-systems can work,
and with OSGi's modularity strengths it should be even more so... In fact,
instead of seeing this as a weakening of Felix position (which is what I
think Richard sees), I think it will strengthen OSGi's natural place in the
Apache Landscape.

Don't forget, you are free to participate at as many places as you wish.

-- Niclas

P.S. Sorry for poor quoting. On mobile...

On Sep 2, 2009 12:14 AM, "Guillaume Nodet" <gn...@gmail.com> wrote:

On Tue, Sep 1, 2009 at 18:06, Richard S. Hall <he...@ungoverned.org> wrote:
> > Creating another pr...
Well, the problem I see here is that we *need* to educate non-techies.  This
obvisouly mean that there is a confusion.  Education is just a work around
the need to remove the confusion imho.  So let's discuss that on
dev@felix.a.o, I don't think this thread belongs here.

-- Cheers, Guillaume Nodet ------------------------ Blog:
http://gnodet.blogspot.com/ ----------...

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
I'm not subscribing to dev@felix.a.o at the moment, but would still like to
hear the outcome of this...

Richard, we (you and I at least) have discussed this more than once in the
past and I totally agree with Guillaume that the perception is there, it is
everything and near impossible to change. I ALSO agree with Richard that
spec implementations should reside with Felix.

Now, I think name manipulations are going to be necessary. My take is;

Apache Felix = a OSGi framework, runtime, installers, binaries, bells and
whistles. The whole kitchen sink if you like. The framework implementation
itself probably lives here, with the Core spec service implementations.

Apache Foo = a foundry to dev OSGi spec implementations. One or many. Most
will be dependencies to Felix, but the detach shows that they are intended
for all.

Apache Bar = a component foundry outside the spec suite.

And let Aries, Karaf, Ace and what else in future to go TLP if/when they are
ready.

I think ServiceMix has with its friends shown how nice eco-systems can work,
and with OSGi's modularity strengths it should be even more so... In fact,
instead of seeing this as a weakening of Felix position (which is what I
think Richard sees), I think it will strengthen OSGi's natural place in the
Apache Landscape.

Don't forget, you are free to participate at as many places as you wish.

-- Niclas

P.S. Sorry for poor quoting. On mobile...

On Sep 2, 2009 12:14 AM, "Guillaume Nodet" <gn...@gmail.com> wrote:

On Tue, Sep 1, 2009 at 18:06, Richard S. Hall <he...@ungoverned.org> wrote:
> > Creating another pr...
Well, the problem I see here is that we *need* to educate non-techies.  This
obvisouly mean that there is a confusion.  Education is just a work around
the need to remove the confusion imho.  So let's discuss that on
dev@felix.a.o, I don't think this thread belongs here.

-- Cheers, Guillaume Nodet ------------------------ Blog:
http://gnodet.blogspot.com/ ----------...

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
On Tue, Sep 1, 2009 at 18:06, Richard S. Hall <he...@ungoverned.org> wrote:

>
> Creating another project to host OSGi spec implementations seems
> unnecessary. And, from my point of view, only serves to foster this
> mentality that Felix projects are framework specific. I do not buy your
> argument that we cannot educate the non-techie that this is not true. Do
> such work at Felix is exactly how we educate them. Of course, we could also
> discuss other ways to improve this.
>
>
Well, the problem I see here is that we *need* to educate non-techies.  This
obvisouly mean that there is a confusion.  Education is just a work around
the need to remove the confusion imho.  So let's discuss that on
dev@felix.a.o, I don't think this thread belongs here.



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
On Tue, Sep 1, 2009 at 18:06, Richard S. Hall <he...@ungoverned.org> wrote:

>
> Creating another project to host OSGi spec implementations seems
> unnecessary. And, from my point of view, only serves to foster this
> mentality that Felix projects are framework specific. I do not buy your
> argument that we cannot educate the non-techie that this is not true. Do
> such work at Felix is exactly how we educate them. Of course, we could also
> discuss other ways to improve this.
>
>
Well, the problem I see here is that we *need* to educate non-techies.  This
obvisouly mean that there is a confusion.  Education is just a work around
the need to remove the confusion imho.  So let's discuss that on
dev@felix.a.o, I don't think this thread belongs here.



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
I don't think we disagree in principle, but in approach. Apache Felix 
was charted to host Apache licensed implementations of OSGi 
specifications. So, what makes sense to me is:

   1. Having Apache community members work on standard spec
      implementations at Apache Felix.
   2. Then if those subproject take on a life of their own, the
      subproject participants can look into going through incubator to
      go TLP.

Creating another project to host OSGi spec implementations seems 
unnecessary. And, from my point of view, only serves to foster this 
mentality that Felix projects are framework specific. I do not buy your 
argument that we cannot educate the non-techie that this is not true. Do 
such work at Felix is exactly how we educate them. Of course, we could 
also discuss other ways to improve this.

I wholeheartedly encourage OSGi-realted proposals to the incubator. That 
makes sense. Apache Ace is one example, yes, and they do use Deployment 
Admin, however, luminis contributed Deployment Admin to Felix.

The very nature of the OSGi specs almost dictates lots of small 
subprojects. Admittedly, this causes some level of umbrella-ness with 
which we must cope. I believe the Apache Felix PMC is open to such 
discussions if you wanted to start them. Likewise, the Felix PMC is 
definitely open to new contributors and new subprojects.

 From my point of view, it is better to foster a cohesive OSGi community 
here at Apache, rather than fracture off in advance.

-> richard

On 9/1/09 11:45, Guillaume Nodet wrote:
> Not sure how to articulate my thoughts here.
>
> First, it's not about competing against Felix, though you'll find in the ASF
> multiple competing products (Axis vs CXF to mention only this one) and the
> ASF has never stated as a goal that it would provide a coherent offer or
> anything like this.
>
> The problem I have with Felix is really a branding problem.  While *we* (as
> developers) very well know that all the subprojects of Felix are not tied to
> the Felix Framework itself, it's really difficult to spread this word around
> to non techies.  The name Felix is often associated to the OSGi framework
> implementation itself, and it's kinda hard to remove this tie unless either
> the project or the framework change its name to something else.  For
> example, the framework could be referred to as Apache Foo and other
> subprojects as Apache iPojo or Apache Karaf.  I think it would help removing
> this tie.   The other way around is possible too, rename the project to
> something else, and keep Apache Felix as referring to the framework itself
> (which might be even better, but slightly more difficult to actually
> achieve).  I'm not sure there is a very easy way, but dev@felix.a.o would a
> better place to discuss that.
>
> Another thought that comes to my mind is that over the past years, the ASF
> has tried to dismantle umbrella projects when it makes sense: i.e. when one
> of the subproject has sufficient momentum to create a community on its own.
> ACE is another podling related to OSGi and AFAIK it implements the
> DeploymentAdmin OSGi spec.   I also see Karaf as a possible TLP at some
> point.   That would become a problem with Felix, as the communities are
> rather disjoint between the subprojects (not all, I do agree).  Not sure
> what the good size for a TLP is and other members can join the discussion
> and provide feedback.   I don't think felix is oversized right now, but it
> might become a problem if it goes too far.    Given this proposal includes
> more than 20 committers and most of them are not felix committers, we'd need
> the incubator for building up this community anyway.   And btw, as any other
> incubator proposal, everyone interested is free to join the proposal and we
> would particularly welcome any felix committer here.
>
> That said, Aries wants to focus on application focused enterprise OSGi
> specs, which I do agree, could fit in the Felix scope, as could Ace do
> too.   I guess in all cases, things can be discussed at the time the podling
> will graduate out of the incubator.  The current goal is to aim to TLP as we
> think the size of the project can back that, but this is not written in
> stone.
>
> On Tue, Sep 1, 2009 at 17:03, Richard S. Hall<he...@ungoverned.org>  wrote:
>
>    
>> The Apache Felix project, since its inception, has been intended to host
>> implementations of the OSGi specifications, which includes both the
>> framework as well as other standard services. A framework implementation was
>> just one of the goals.
>>
>> This proposal seems to be saying a separate project is needed to create
>> some illusion of independence from Apache Felix, but the whole point of OSGi
>> is to be vendor neutral, so I am not sure I follow the rationale. Apache
>> Felix subprojects are not tied to the Apache Felix framework subproject and
>> by us pretending that they are, it only serves to perpetuate this myth.
>>
>> I have no issues with new efforts around and on top of OSGi being
>> incubated, but it gets a little trickier when we are talking about
>> implementing standard OSGi specs which was the intended community goal of
>> the Apache Felix project. Are we supposed to compete now for standard
>> service implementations? Or come to some sort of cartel-like agreement about
>> who gets what?
>>
>> ->  richard
>>
>>
>> On 9/1/09 10:38, Jeremy Hughes wrote:
>>
>>      
>>> Hi, we would like to propose a new incubator podling called Aries.
>>>
>>> http://wiki.apache.org/incubator/AriesProposal
>>>
>>> Here is a quick summary of the proposal
>>>
>>> The Aries project will deliver a set of pluggable Java components
>>> enabling an enterprise OSGi application programming model. This
>>> includes implementations and extensions of application-focused
>>> specifications defined by the OSGi Alliance Enterprise Expert Group
>>> (EEG) and an assembly format for multi-bundle applications, for
>>> deployment to a variety of OSGi based runtimes.
>>>
>>> Aries aims to build a community of developers interested in the
>>> definition and delivery of software components that support an
>>> enterprise OSGi programming model and which can be integrated into a
>>> number of different runtime environments.
>>>
>>> We appreciate any feedback and comments on the proposal.
>>>
>>> Here is a plain text copy of the whole proposal:
>>>
>>> Apache Aries
>>> Abstract
>>>
>>> The Aries project will deliver a set of pluggable Java components
>>> enabling an enterprise OSGi application programming model. This
>>> includes implementations and extensions of application-focused
>>> specifications defined by the OSGi Alliance Enterprise Expert Group
>>> (EEG) and an assembly format for multi-bundle applications, for
>>> deployment to a variety of OSGi based runtimes.
>>> Proposal
>>>
>>> It is a goal of the Aries project to provide a natural home for open
>>> source implementations of current and future OSGi EEG specifications,
>>> including the opportunity for the collaborative development of
>>> compliance tests, and an environment to demonstrate the composition of
>>> these technologies and to explore areas where EEG specifications lack
>>> coverage. A further goal of this project is to leverage experience
>>> gained from it to inform contributions to OSGi EEG requirements and
>>> specification documents.
>>>
>>> Aries will offer an enterprise OSGi application programming model that
>>> enables applications to leverage Java EE and other enterprise
>>> technologies and to benefit from the modularity, dynamism and
>>> versioning capabilities of OSGi. A significant feature of Aries will
>>> be a container for OSGi Blueprint components - an implementation of
>>> the new OSGi v4.2 Blueprint component model that defines a standard
>>> dependency injection mechanism for Java components, which is derived
>>> from the Spring framework and extended for OSGi to declaratively
>>> register component interfaces as services in the OSGi service
>>> registry.
>>>
>>> In addition, the Aries project will develop a model for assembling an
>>> application/subsystem into a deployable unit, consisting of multiple
>>> bundles, as an archive which may include metadata that describes the
>>> version and external location of the application's constituent bundles
>>> or which may contain the bundles directly.
>>>
>>> The Aries project will deliver run-time componentry that supports
>>> applications, running in an OSGi framework, exploiting enterprise Java
>>> technologies common in web applications and integration scenarios
>>> including web application bundles, remote services integration and
>>> JPA. The project is not expected to deliver a complete application or
>>> integration server runtime but will instead deliver enterprise
>>> application componentry that can be integrated into such runtimes. The
>>> project will develop extensions that go beyond the OSGi EEG
>>> specifications to provide a more complete integration of OSGi
>>> modularity with Java enterprise technologies, in particular delivering
>>> support that includes but is not restricted to:
>>>
>>>     * isolated enterprise applications composed of multiple, versioned
>>> bundles with dynamic lifecycle.
>>>     * declarative transactions and security for Blueprint components
>>>     * Container-managed JPA for Blueprint components
>>>     * Message-driven Blueprint components
>>>     * Configuration of resource references in module blueprints.
>>>     * Annotation-based Blueprint configuration
>>>     * Federation of lookup mechanisms between local JNDI and the OSGi
>>> service registry.
>>>     * Fully declarative application metadata to enable reflection of
>>> an SCA component type definition.
>>>
>>> In order to maximise the potential scope of Aries adoption it is
>>> anticipated the project will remain agnostic of a number of
>>> complementary technologies and projects. It is the expectation that
>>> Aries will therefore not be delivering components such as: an
>>> application or integration server runtime kernel; a persistence
>>> provider; distribution provider; a deployment provider or a Web
>>> container. Aries will instead seek to enable the use of such
>>> components from other projects.
>>> Background
>>>
>>> OSGi is a mature and Java modularity technology that is well-used in
>>> many environments but, in the enterprise space, has more typically
>>> been exploited by the internals of the runtime infrastructure than the
>>> applications that run on it. This is primarily because of a lack of a
>>> clear enterprise OSGi application programming model and implementation
>>> of OSGi-enabled Java technology to support enterprise applications.
>>> OSGi specifications are specified and maintained by the OSGi Alliance
>>> which recognized this state of affairs several years ago and
>>> established the Enterprise Expert Group within the Alliance to focus
>>> specifically on the needs of enterprise applications. The objective of
>>> this project is to deliver open source implementations of these
>>> application-centric technologies to enable the development of
>>> application components, benefiting from the modularity of OSGi
>>> combined with standards-based programming models, which can be
>>> deployed to a variety of target runtimes.
>>> Rationale
>>>
>>> Aries aims to build a community of developers interested in the
>>> delivery of software components that support an enterprise OSGi
>>> programming model and which can be integrated into a number of
>>> different runtime environments. Apache hosts the Felix project which
>>> provides an OSGi framework implementation and a variety of projects
>>> which provide technologies exploited by enterprise application
>>> components as well as projects which provide runtimes to host
>>> application components. There is currently no Apache project focussed
>>> on OSGi enterprise applications that is independent from both the OSGi
>>> framework and the enterprise runtime environment in which application
>>> components are hosted. By maintaining independence of both the target
>>> runtime and underlying OSGi framework it is our intention to build the
>>> broadest possible community of developers for Aries, and to maximize
>>> the potential environments where Aries componentry can be used.
>>> Initial Goals
>>>
>>> We will initially focus on the Blueprint container and extend this
>>> with enterprise features such as support for container managed JPA and
>>> container managed transactions. Another initial focus area will be the
>>> contribution of code to support the assembly of isolated, multi-bundle
>>> applications that can be deployed as a unit.
>>> Current Status
>>> Meritocracy
>>>
>>> The Aries contributors recognize the desirability of running the
>>> project as a meritocracy. We are eager to engage other members of the
>>> community and operate to the standard of meritocracy that Apache
>>> emphasizes; we believe this is the most effective method of growing
>>> our community and enabling widespread adoption.
>>> Community
>>>
>>> OSGi is a mature Java modularity technology that is well-used in many
>>> environments but, in the enterprise space, has more typically been
>>> exploited by the internals of the runtime infrastructure than the
>>> applications that run on it. This is primarily because of a lack of a
>>> clear enterprise OSGi application programming model and implementation
>>> of OSGi-enabled Java technology to support enterprise applications.
>>> There is a need for open source implementations of these technologies
>>> and there is currently no Apache project focused on the wider goal of
>>> delivering components for an enterprise OSGi application programming
>>> model. Aries aims to build a community of developers interested in the
>>> definition and delivery of software components that support an
>>> enterprise OSGi programming model and which can be integrated into a
>>> number of different runtime environments. By maintaining independence
>>> of both the target runtime and underlying OSGi framework it is our
>>> intention to build the broadest possible community of developers.
>>> Alignment
>>>
>>> The purpose of Aries is to develop implementations of
>>> application-centric enterprise OSGi technologies that run on an OSGi
>>> framework, but not a specific one, and are used by application
>>> components deployed into a variety of runtime environments without
>>> being tied to any specific environment. For this reason we believe
>>> Aries is a project whose community would be best served if it could
>>> leverage but be independent from the communities that provide
>>> underlying OSGi framework technology and enterprise application server
>>> and integration bus technologies, all of which exist as open source
>>> efforts within Apache and elsewhere. We expect, for example, that some
>>> code developed in Aries will run directly on top of an OSGi framework
>>> such as Felix and that applications exploiting Aries technologies
>>> could be deployed to runtimes such as ServiceMix and Geronimo.
>>> Avoiding the Warning Signs
>>> Orphaned products
>>>
>>> The contributors are leading vendors of OSGi-based technologies and
>>> have a long standing in the OSGi Alliance whose application-centric
>>> specifications this project will implement. There is minimal risk of
>>> this work becoming non-strategic and the contributors are confident
>>> that a larger community will form within the project in a relatively
>>> short space of time.
>>> Inexperience with Open Source
>>>
>>> Many of the committers have experience working in one or more open
>>> source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
>>> and CXF.
>>>
>>> Homogeneous Developers
>>>
>>> The list of initial committers, geographically distributed across the
>>> U.S. and Europe, consists of developers from two companies - IBM and
>>> Progress software - with similar goals but for different scenarios.
>>> Many of these developers are experienced Apache committers already and
>>> all are experienced with working in distributed development
>>> communities. It is our hope that, through the incubator, further
>>> contributors with a broad background of experience but common interest
>>> in enterprise OSGi technologies will become involved with this
>>> project.
>>>
>>> Relationships with Other Apache Projects
>>>
>>> Aries will have a potential relationship with the Apache projects
>>> listed in this section. These projects all serve different purposes
>>> from Aries and have their own communities. It is hoped that each of
>>> these communities will become involved with Aries and help to build a
>>> diverse but independent Aries community.
>>>
>>> Apache Felix Karaf -
>>> http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
>>> Karaf is an OSGi based runtime which provides a lightweight container
>>> onto which various components and applications can be deployed. It is
>>> related to Aries:
>>>
>>>    1. as a target OSGi based runtime to which Aries applications can
>>> be deployed. In this role, Karaf is a consumer of Aries technology.
>>>
>>> Apache Felix - http://felix.apache.org/site/index.html Apache
>>> Felix is primarily a core OSGi framework implementation. It is related
>>> to Aries:
>>>
>>>    1. as an underlying OSGi framework implementation and potentially
>>> other extensions that can be used both by Aries run-time components
>>> and the applications which use them.
>>>
>>> Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
>>> a server runtime framework and fully certified Java EE 5 application
>>> server runtime. It is related to Aries in two ways:
>>>
>>>    1. as a target runtime to which Aries applications can be deployed.
>>> In this role, Geronimo is a consumer of Aries technology.
>>>    2. the Geronimo blueprint sandbox -
>>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
>>> an implementation of the OSGi Blueprint container which will be moved
>>> to Aries.
>>>
>>> Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
>>> provides a comprehensive infrastructure for SOA development and
>>> management that is based on Service Component Architecture (SCA)
>>> standard. It can be a consumer of Aries technology to provide an Aries
>>> SCA implementation type for composing Aries applications in coarse
>>> grained and potentially heterogeneous service assemblies.
>>>
>>> Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
>>> Web Services framework for distributed computing and remote service
>>> realization and invocation using API's such as JAX-WS and JAX-RS. It
>>> also provides the OSGi Remote Services (OSGi RFC 119) reference
>>> implementation in a subproject:
>>> http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
>>> the following way:
>>>
>>>    1. As Remote Services is a significant Enterprise specification
>>> being produced by the EEG, it is expected that consumers of Aries will
>>> be looking for an implementation of this specification. CXF provides
>>> an implementation of this specification which already has a
>>> significant active community. The Aries project will make it easy for
>>> Aries consumers to consume the CXF Remote Services implementation,
>>> possibly by providing an instance of the application model that
>>> references the CXF Remote Services implementation. This would mean
>>> that end users will seamlessly pull in the required components from
>>> CXF by using the Aries-provided definition.
>>>
>>> Apache ServiceMix - http://servicemix.apache.org/ Apache
>>> ServiceMix provides an ESB that combines the functionality of a
>>> Service Oriented Architecture (SOA) and Event Driven Architecture
>>> (EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
>>> source of the Apache Felix Karaf runtime. It can be a consumer of
>>> Aries applications and associated componentry as a natural evolution
>>> of its existing Karaf "feature" usage.
>>>
>>> Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
>>> Java persistence project. It is related to Aries as a JPA persistence
>>> provider, including entity scanning and enhancement. The Aries project
>>> will make it easy for JPA persistence providers such as OpenJPA to be
>>> used in an OSGi environment and will provide container managed
>>> persistence for the Blueprint container.
>>>
>>> Documentation
>>>
>>> An early draft of OSGi v4.2 core and compendium specifications - which
>>> includes the Blueprint container specification - is available at:
>>> http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
>>> Initial Source
>>>
>>>     * The Blueprint container impl from the Geronimo sandbox will be
>>> moved to the Aries project for further development:
>>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
>>>     * IBM will also contribute code for:
>>>           o container-managed JPA support in an OSGi environment.
>>>           o making OSGi services visible to Java EE components through
>>> JNDI.
>>>           o packaging web components as bundles and a URL handler for
>>> recognizing and converting non-bundled Web components
>>>     * We will also be soliciting implementations of other OSGi
>>> enterprise application-centric specifications.
>>>
>>> External Dependencies
>>>
>>>     * Apache Ant http://ant.apache.org Apache License
>>>     * Apache Commons http://commons.apache.org Apache License
>>>     * Junit (Java unit test framework) http://junit.sourceforge.net CPL
>>> v1.0 license: http://junit.sourceforge.net/cpl-v10.html
>>>     * Apache Felix (implementation of the OSGi Core and Compendium
>>> specifications - compliance level unknown) http://felix.apache.org
>>> Apache License (hosted by ASF).
>>>     * Eclipse Equinox (compliant implementation of the OSGi Core
>>> Specification and Compendium specifications)
>>> http://eclipse.org/equinox/ Eclipse Public License
>>>     * OpenJPA http://openjpa.apache.org Apache License
>>>     * Serp http://serp.sourceforge.net/ BSD
>>>     * Apache Geronimo http://geronimo.apache.org Apache License
>>>
>>> Required Resources
>>> Mailing lists
>>>
>>> aries-private (with moderated subscriptions)
>>> aries-dev
>>> aries-commits
>>> aries-user
>>>
>>> Subversion Directory
>>>
>>> http://svn.apache.org/repos/asf/incubator/aries
>>>
>>> Issue Tracking
>>>
>>> JIRA (ARIES)
>>>
>>> Web Site
>>>
>>> Confluence (Aries)
>>>
>>> Initial Committers
>>>
>>> Names of initial committers with affiliation and current ASF status:
>>>
>>>     * Alasdair Nottingham (IBM)
>>>     * Andrew Osborne (IBM)
>>>     * Dan Kulp (Progress, ASF member)
>>>     * David Bosschaert (Progress, ASF committer)
>>>     * David Jencks (IBM, ASF member)
>>>     * Eoghan Glynn (Progress, ASF committer)
>>>     * Graham Charters (IBM)
>>>     * Guillaume Nodet (Progress, ASF member)
>>>     * Hiram Chirino (Progress, ASF member)
>>>     * Ian Robinson (IBM)
>>>     * James Strachan (Progress, ASF member)
>>>     * Jarek Gawor (IBM, ASF member)
>>>     * Jeremy Hughes (IBM, ASF committer)
>>>     * Joe Bohn (IBM, ASF committer)
>>>     * Lin Sun (IBM, ASF committer)
>>>     * Mark Nuttall (IBM)
>>>     * Oisin Hurley (Progress)
>>>     * Rick McGuire (IBM, ASF committer)
>>>     * Sergey Beryozkin (Progress, ASF committer),
>>>     * Timothy Ward (IBM)
>>>     * Valentin Mahrwald (IBM)
>>>     * Zoe Slattery (IBM)
>>>
>>> Affiliations
>>>
>>> The majority of the initial committers are employed by IBM corp or
>>> Progress Software. One objective of the incubator is to attract a
>>> diverse community of contributors and we anticipate future
>>> contributors to have other affiliations.
>>>
>>> Sponsors
>>> Champions
>>>
>>> Kevan Miller, Guillaume Nodet
>>>
>>> Nominated Mentors
>>>
>>> Guillaume Nodet, Davanum Srinivas (Dims)
>>>
>>> Sponsoring Entity
>>>
>>> The incubator. Successful graduation from Incubator should result in
>>> Aries becoming a new TLP.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>>
>>>        
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>>      
>
>    

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
Not sure how to articulate my thoughts here.

First, it's not about competing against Felix, though you'll find in the ASF
multiple competing products (Axis vs CXF to mention only this one) and the
ASF has never stated as a goal that it would provide a coherent offer or
anything like this.

The problem I have with Felix is really a branding problem.  While *we* (as
developers) very well know that all the subprojects of Felix are not tied to
the Felix Framework itself, it's really difficult to spread this word around
to non techies.  The name Felix is often associated to the OSGi framework
implementation itself, and it's kinda hard to remove this tie unless either
the project or the framework change its name to something else.  For
example, the framework could be referred to as Apache Foo and other
subprojects as Apache iPojo or Apache Karaf.  I think it would help removing
this tie.   The other way around is possible too, rename the project to
something else, and keep Apache Felix as referring to the framework itself
(which might be even better, but slightly more difficult to actually
achieve).  I'm not sure there is a very easy way, but dev@felix.a.o would a
better place to discuss that.

Another thought that comes to my mind is that over the past years, the ASF
has tried to dismantle umbrella projects when it makes sense: i.e. when one
of the subproject has sufficient momentum to create a community on its own.
ACE is another podling related to OSGi and AFAIK it implements the
DeploymentAdmin OSGi spec.   I also see Karaf as a possible TLP at some
point.   That would become a problem with Felix, as the communities are
rather disjoint between the subprojects (not all, I do agree).  Not sure
what the good size for a TLP is and other members can join the discussion
and provide feedback.   I don't think felix is oversized right now, but it
might become a problem if it goes too far.    Given this proposal includes
more than 20 committers and most of them are not felix committers, we'd need
the incubator for building up this community anyway.   And btw, as any other
incubator proposal, everyone interested is free to join the proposal and we
would particularly welcome any felix committer here.

That said, Aries wants to focus on application focused enterprise OSGi
specs, which I do agree, could fit in the Felix scope, as could Ace do
too.   I guess in all cases, things can be discussed at the time the podling
will graduate out of the incubator.  The current goal is to aim to TLP as we
think the size of the project can back that, but this is not written in
stone.

On Tue, Sep 1, 2009 at 17:03, Richard S. Hall <he...@ungoverned.org> wrote:

> The Apache Felix project, since its inception, has been intended to host
> implementations of the OSGi specifications, which includes both the
> framework as well as other standard services. A framework implementation was
> just one of the goals.
>
> This proposal seems to be saying a separate project is needed to create
> some illusion of independence from Apache Felix, but the whole point of OSGi
> is to be vendor neutral, so I am not sure I follow the rationale. Apache
> Felix subprojects are not tied to the Apache Felix framework subproject and
> by us pretending that they are, it only serves to perpetuate this myth.
>
> I have no issues with new efforts around and on top of OSGi being
> incubated, but it gets a little trickier when we are talking about
> implementing standard OSGi specs which was the intended community goal of
> the Apache Felix project. Are we supposed to compete now for standard
> service implementations? Or come to some sort of cartel-like agreement about
> who gets what?
>
> -> richard
>
>
> On 9/1/09 10:38, Jeremy Hughes wrote:
>
>> Hi, we would like to propose a new incubator podling called Aries.
>>
>> http://wiki.apache.org/incubator/AriesProposal
>>
>> Here is a quick summary of the proposal
>>
>> The Aries project will deliver a set of pluggable Java components
>> enabling an enterprise OSGi application programming model. This
>> includes implementations and extensions of application-focused
>> specifications defined by the OSGi Alliance Enterprise Expert Group
>> (EEG) and an assembly format for multi-bundle applications, for
>> deployment to a variety of OSGi based runtimes.
>>
>> Aries aims to build a community of developers interested in the
>> definition and delivery of software components that support an
>> enterprise OSGi programming model and which can be integrated into a
>> number of different runtime environments.
>>
>> We appreciate any feedback and comments on the proposal.
>>
>> Here is a plain text copy of the whole proposal:
>>
>> Apache Aries
>> Abstract
>>
>> The Aries project will deliver a set of pluggable Java components
>> enabling an enterprise OSGi application programming model. This
>> includes implementations and extensions of application-focused
>> specifications defined by the OSGi Alliance Enterprise Expert Group
>> (EEG) and an assembly format for multi-bundle applications, for
>> deployment to a variety of OSGi based runtimes.
>> Proposal
>>
>> It is a goal of the Aries project to provide a natural home for open
>> source implementations of current and future OSGi EEG specifications,
>> including the opportunity for the collaborative development of
>> compliance tests, and an environment to demonstrate the composition of
>> these technologies and to explore areas where EEG specifications lack
>> coverage. A further goal of this project is to leverage experience
>> gained from it to inform contributions to OSGi EEG requirements and
>> specification documents.
>>
>> Aries will offer an enterprise OSGi application programming model that
>> enables applications to leverage Java EE and other enterprise
>> technologies and to benefit from the modularity, dynamism and
>> versioning capabilities of OSGi. A significant feature of Aries will
>> be a container for OSGi Blueprint components - an implementation of
>> the new OSGi v4.2 Blueprint component model that defines a standard
>> dependency injection mechanism for Java components, which is derived
>> from the Spring framework and extended for OSGi to declaratively
>> register component interfaces as services in the OSGi service
>> registry.
>>
>> In addition, the Aries project will develop a model for assembling an
>> application/subsystem into a deployable unit, consisting of multiple
>> bundles, as an archive which may include metadata that describes the
>> version and external location of the application's constituent bundles
>> or which may contain the bundles directly.
>>
>> The Aries project will deliver run-time componentry that supports
>> applications, running in an OSGi framework, exploiting enterprise Java
>> technologies common in web applications and integration scenarios
>> including web application bundles, remote services integration and
>> JPA. The project is not expected to deliver a complete application or
>> integration server runtime but will instead deliver enterprise
>> application componentry that can be integrated into such runtimes. The
>> project will develop extensions that go beyond the OSGi EEG
>> specifications to provide a more complete integration of OSGi
>> modularity with Java enterprise technologies, in particular delivering
>> support that includes but is not restricted to:
>>
>>    * isolated enterprise applications composed of multiple, versioned
>> bundles with dynamic lifecycle.
>>    * declarative transactions and security for Blueprint components
>>    * Container-managed JPA for Blueprint components
>>    * Message-driven Blueprint components
>>    * Configuration of resource references in module blueprints.
>>    * Annotation-based Blueprint configuration
>>    * Federation of lookup mechanisms between local JNDI and the OSGi
>> service registry.
>>    * Fully declarative application metadata to enable reflection of
>> an SCA component type definition.
>>
>> In order to maximise the potential scope of Aries adoption it is
>> anticipated the project will remain agnostic of a number of
>> complementary technologies and projects. It is the expectation that
>> Aries will therefore not be delivering components such as: an
>> application or integration server runtime kernel; a persistence
>> provider; distribution provider; a deployment provider or a Web
>> container. Aries will instead seek to enable the use of such
>> components from other projects.
>> Background
>>
>> OSGi is a mature and Java modularity technology that is well-used in
>> many environments but, in the enterprise space, has more typically
>> been exploited by the internals of the runtime infrastructure than the
>> applications that run on it. This is primarily because of a lack of a
>> clear enterprise OSGi application programming model and implementation
>> of OSGi-enabled Java technology to support enterprise applications.
>> OSGi specifications are specified and maintained by the OSGi Alliance
>> which recognized this state of affairs several years ago and
>> established the Enterprise Expert Group within the Alliance to focus
>> specifically on the needs of enterprise applications. The objective of
>> this project is to deliver open source implementations of these
>> application-centric technologies to enable the development of
>> application components, benefiting from the modularity of OSGi
>> combined with standards-based programming models, which can be
>> deployed to a variety of target runtimes.
>> Rationale
>>
>> Aries aims to build a community of developers interested in the
>> delivery of software components that support an enterprise OSGi
>> programming model and which can be integrated into a number of
>> different runtime environments. Apache hosts the Felix project which
>> provides an OSGi framework implementation and a variety of projects
>> which provide technologies exploited by enterprise application
>> components as well as projects which provide runtimes to host
>> application components. There is currently no Apache project focussed
>> on OSGi enterprise applications that is independent from both the OSGi
>> framework and the enterprise runtime environment in which application
>> components are hosted. By maintaining independence of both the target
>> runtime and underlying OSGi framework it is our intention to build the
>> broadest possible community of developers for Aries, and to maximize
>> the potential environments where Aries componentry can be used.
>> Initial Goals
>>
>> We will initially focus on the Blueprint container and extend this
>> with enterprise features such as support for container managed JPA and
>> container managed transactions. Another initial focus area will be the
>> contribution of code to support the assembly of isolated, multi-bundle
>> applications that can be deployed as a unit.
>> Current Status
>> Meritocracy
>>
>> The Aries contributors recognize the desirability of running the
>> project as a meritocracy. We are eager to engage other members of the
>> community and operate to the standard of meritocracy that Apache
>> emphasizes; we believe this is the most effective method of growing
>> our community and enabling widespread adoption.
>> Community
>>
>> OSGi is a mature Java modularity technology that is well-used in many
>> environments but, in the enterprise space, has more typically been
>> exploited by the internals of the runtime infrastructure than the
>> applications that run on it. This is primarily because of a lack of a
>> clear enterprise OSGi application programming model and implementation
>> of OSGi-enabled Java technology to support enterprise applications.
>> There is a need for open source implementations of these technologies
>> and there is currently no Apache project focused on the wider goal of
>> delivering components for an enterprise OSGi application programming
>> model. Aries aims to build a community of developers interested in the
>> definition and delivery of software components that support an
>> enterprise OSGi programming model and which can be integrated into a
>> number of different runtime environments. By maintaining independence
>> of both the target runtime and underlying OSGi framework it is our
>> intention to build the broadest possible community of developers.
>> Alignment
>>
>> The purpose of Aries is to develop implementations of
>> application-centric enterprise OSGi technologies that run on an OSGi
>> framework, but not a specific one, and are used by application
>> components deployed into a variety of runtime environments without
>> being tied to any specific environment. For this reason we believe
>> Aries is a project whose community would be best served if it could
>> leverage but be independent from the communities that provide
>> underlying OSGi framework technology and enterprise application server
>> and integration bus technologies, all of which exist as open source
>> efforts within Apache and elsewhere. We expect, for example, that some
>> code developed in Aries will run directly on top of an OSGi framework
>> such as Felix and that applications exploiting Aries technologies
>> could be deployed to runtimes such as ServiceMix and Geronimo.
>> Avoiding the Warning Signs
>> Orphaned products
>>
>> The contributors are leading vendors of OSGi-based technologies and
>> have a long standing in the OSGi Alliance whose application-centric
>> specifications this project will implement. There is minimal risk of
>> this work becoming non-strategic and the contributors are confident
>> that a larger community will form within the project in a relatively
>> short space of time.
>> Inexperience with Open Source
>>
>> Many of the committers have experience working in one or more open
>> source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
>> and CXF.
>>
>> Homogeneous Developers
>>
>> The list of initial committers, geographically distributed across the
>> U.S. and Europe, consists of developers from two companies - IBM and
>> Progress software - with similar goals but for different scenarios.
>> Many of these developers are experienced Apache committers already and
>> all are experienced with working in distributed development
>> communities. It is our hope that, through the incubator, further
>> contributors with a broad background of experience but common interest
>> in enterprise OSGi technologies will become involved with this
>> project.
>>
>> Relationships with Other Apache Projects
>>
>> Aries will have a potential relationship with the Apache projects
>> listed in this section. These projects all serve different purposes
>> from Aries and have their own communities. It is hoped that each of
>> these communities will become involved with Aries and help to build a
>> diverse but independent Aries community.
>>
>> Apache Felix Karaf -
>> http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
>> Karaf is an OSGi based runtime which provides a lightweight container
>> onto which various components and applications can be deployed. It is
>> related to Aries:
>>
>>   1. as a target OSGi based runtime to which Aries applications can
>> be deployed. In this role, Karaf is a consumer of Aries technology.
>>
>> Apache Felix - http://felix.apache.org/site/index.html Apache
>> Felix is primarily a core OSGi framework implementation. It is related
>> to Aries:
>>
>>   1. as an underlying OSGi framework implementation and potentially
>> other extensions that can be used both by Aries run-time components
>> and the applications which use them.
>>
>> Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
>> a server runtime framework and fully certified Java EE 5 application
>> server runtime. It is related to Aries in two ways:
>>
>>   1. as a target runtime to which Aries applications can be deployed.
>> In this role, Geronimo is a consumer of Aries technology.
>>   2. the Geronimo blueprint sandbox -
>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
>> an implementation of the OSGi Blueprint container which will be moved
>> to Aries.
>>
>> Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
>> provides a comprehensive infrastructure for SOA development and
>> management that is based on Service Component Architecture (SCA)
>> standard. It can be a consumer of Aries technology to provide an Aries
>> SCA implementation type for composing Aries applications in coarse
>> grained and potentially heterogeneous service assemblies.
>>
>> Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
>> Web Services framework for distributed computing and remote service
>> realization and invocation using API's such as JAX-WS and JAX-RS. It
>> also provides the OSGi Remote Services (OSGi RFC 119) reference
>> implementation in a subproject:
>> http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
>> the following way:
>>
>>   1. As Remote Services is a significant Enterprise specification
>> being produced by the EEG, it is expected that consumers of Aries will
>> be looking for an implementation of this specification. CXF provides
>> an implementation of this specification which already has a
>> significant active community. The Aries project will make it easy for
>> Aries consumers to consume the CXF Remote Services implementation,
>> possibly by providing an instance of the application model that
>> references the CXF Remote Services implementation. This would mean
>> that end users will seamlessly pull in the required components from
>> CXF by using the Aries-provided definition.
>>
>> Apache ServiceMix - http://servicemix.apache.org/ Apache
>> ServiceMix provides an ESB that combines the functionality of a
>> Service Oriented Architecture (SOA) and Event Driven Architecture
>> (EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
>> source of the Apache Felix Karaf runtime. It can be a consumer of
>> Aries applications and associated componentry as a natural evolution
>> of its existing Karaf "feature" usage.
>>
>> Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
>> Java persistence project. It is related to Aries as a JPA persistence
>> provider, including entity scanning and enhancement. The Aries project
>> will make it easy for JPA persistence providers such as OpenJPA to be
>> used in an OSGi environment and will provide container managed
>> persistence for the Blueprint container.
>>
>> Documentation
>>
>> An early draft of OSGi v4.2 core and compendium specifications - which
>> includes the Blueprint container specification - is available at:
>> http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
>> Initial Source
>>
>>    * The Blueprint container impl from the Geronimo sandbox will be
>> moved to the Aries project for further development:
>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
>>    * IBM will also contribute code for:
>>          o container-managed JPA support in an OSGi environment.
>>          o making OSGi services visible to Java EE components through
>> JNDI.
>>          o packaging web components as bundles and a URL handler for
>> recognizing and converting non-bundled Web components
>>    * We will also be soliciting implementations of other OSGi
>> enterprise application-centric specifications.
>>
>> External Dependencies
>>
>>    * Apache Ant http://ant.apache.org Apache License
>>    * Apache Commons http://commons.apache.org Apache License
>>    * Junit (Java unit test framework) http://junit.sourceforge.net CPL
>> v1.0 license: http://junit.sourceforge.net/cpl-v10.html
>>    * Apache Felix (implementation of the OSGi Core and Compendium
>> specifications - compliance level unknown) http://felix.apache.org
>> Apache License (hosted by ASF).
>>    * Eclipse Equinox (compliant implementation of the OSGi Core
>> Specification and Compendium specifications)
>> http://eclipse.org/equinox/ Eclipse Public License
>>    * OpenJPA http://openjpa.apache.org Apache License
>>    * Serp http://serp.sourceforge.net/ BSD
>>    * Apache Geronimo http://geronimo.apache.org Apache License
>>
>> Required Resources
>> Mailing lists
>>
>> aries-private (with moderated subscriptions)
>> aries-dev
>> aries-commits
>> aries-user
>>
>> Subversion Directory
>>
>> http://svn.apache.org/repos/asf/incubator/aries
>>
>> Issue Tracking
>>
>> JIRA (ARIES)
>>
>> Web Site
>>
>> Confluence (Aries)
>>
>> Initial Committers
>>
>> Names of initial committers with affiliation and current ASF status:
>>
>>    * Alasdair Nottingham (IBM)
>>    * Andrew Osborne (IBM)
>>    * Dan Kulp (Progress, ASF member)
>>    * David Bosschaert (Progress, ASF committer)
>>    * David Jencks (IBM, ASF member)
>>    * Eoghan Glynn (Progress, ASF committer)
>>    * Graham Charters (IBM)
>>    * Guillaume Nodet (Progress, ASF member)
>>    * Hiram Chirino (Progress, ASF member)
>>    * Ian Robinson (IBM)
>>    * James Strachan (Progress, ASF member)
>>    * Jarek Gawor (IBM, ASF member)
>>    * Jeremy Hughes (IBM, ASF committer)
>>    * Joe Bohn (IBM, ASF committer)
>>    * Lin Sun (IBM, ASF committer)
>>    * Mark Nuttall (IBM)
>>    * Oisin Hurley (Progress)
>>    * Rick McGuire (IBM, ASF committer)
>>    * Sergey Beryozkin (Progress, ASF committer),
>>    * Timothy Ward (IBM)
>>    * Valentin Mahrwald (IBM)
>>    * Zoe Slattery (IBM)
>>
>> Affiliations
>>
>> The majority of the initial committers are employed by IBM corp or
>> Progress Software. One objective of the incubator is to attract a
>> diverse community of contributors and we anticipate future
>> contributors to have other affiliations.
>>
>> Sponsors
>> Champions
>>
>> Kevan Miller, Guillaume Nodet
>>
>> Nominated Mentors
>>
>> Guillaume Nodet, Davanum Srinivas (Dims)
>>
>> Sponsoring Entity
>>
>> The incubator. Successful graduation from Incubator should result in
>> Aries becoming a new TLP.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
The Apache Felix project, since its inception, has been intended to host 
implementations of the OSGi specifications, which includes both the 
framework as well as other standard services. A framework implementation 
was just one of the goals.

This proposal seems to be saying a separate project is needed to create 
some illusion of independence from Apache Felix, but the whole point of 
OSGi is to be vendor neutral, so I am not sure I follow the rationale. 
Apache Felix subprojects are not tied to the Apache Felix framework 
subproject and by us pretending that they are, it only serves to 
perpetuate this myth.

I have no issues with new efforts around and on top of OSGi being 
incubated, but it gets a little trickier when we are talking about 
implementing standard OSGi specs which was the intended community goal 
of the Apache Felix project. Are we supposed to compete now for standard 
service implementations? Or come to some sort of cartel-like agreement 
about who gets what?

-> richard

On 9/1/09 10:38, Jeremy Hughes wrote:
> Hi, we would like to propose a new incubator podling called Aries.
>
> http://wiki.apache.org/incubator/AriesProposal
>
> Here is a quick summary of the proposal
>
> The Aries project will deliver a set of pluggable Java components
> enabling an enterprise OSGi application programming model. This
> includes implementations and extensions of application-focused
> specifications defined by the OSGi Alliance Enterprise Expert Group
> (EEG) and an assembly format for multi-bundle applications, for
> deployment to a variety of OSGi based runtimes.
>
> Aries aims to build a community of developers interested in the
> definition and delivery of software components that support an
> enterprise OSGi programming model and which can be integrated into a
> number of different runtime environments.
>
> We appreciate any feedback and comments on the proposal.
>
> Here is a plain text copy of the whole proposal:
>
> Apache Aries
> Abstract
>
> The Aries project will deliver a set of pluggable Java components
> enabling an enterprise OSGi application programming model. This
> includes implementations and extensions of application-focused
> specifications defined by the OSGi Alliance Enterprise Expert Group
> (EEG) and an assembly format for multi-bundle applications, for
> deployment to a variety of OSGi based runtimes.
> Proposal
>
> It is a goal of the Aries project to provide a natural home for open
> source implementations of current and future OSGi EEG specifications,
> including the opportunity for the collaborative development of
> compliance tests, and an environment to demonstrate the composition of
> these technologies and to explore areas where EEG specifications lack
> coverage. A further goal of this project is to leverage experience
> gained from it to inform contributions to OSGi EEG requirements and
> specification documents.
>
> Aries will offer an enterprise OSGi application programming model that
> enables applications to leverage Java EE and other enterprise
> technologies and to benefit from the modularity, dynamism and
> versioning capabilities of OSGi. A significant feature of Aries will
> be a container for OSGi Blueprint components - an implementation of
> the new OSGi v4.2 Blueprint component model that defines a standard
> dependency injection mechanism for Java components, which is derived
> from the Spring framework and extended for OSGi to declaratively
> register component interfaces as services in the OSGi service
> registry.
>
> In addition, the Aries project will develop a model for assembling an
> application/subsystem into a deployable unit, consisting of multiple
> bundles, as an archive which may include metadata that describes the
> version and external location of the application's constituent bundles
> or which may contain the bundles directly.
>
> The Aries project will deliver run-time componentry that supports
> applications, running in an OSGi framework, exploiting enterprise Java
> technologies common in web applications and integration scenarios
> including web application bundles, remote services integration and
> JPA. The project is not expected to deliver a complete application or
> integration server runtime but will instead deliver enterprise
> application componentry that can be integrated into such runtimes. The
> project will develop extensions that go beyond the OSGi EEG
> specifications to provide a more complete integration of OSGi
> modularity with Java enterprise technologies, in particular delivering
> support that includes but is not restricted to:
>
>     * isolated enterprise applications composed of multiple, versioned
> bundles with dynamic lifecycle.
>     * declarative transactions and security for Blueprint components
>     * Container-managed JPA for Blueprint components
>     * Message-driven Blueprint components
>     * Configuration of resource references in module blueprints.
>     * Annotation-based Blueprint configuration
>     * Federation of lookup mechanisms between local JNDI and the OSGi
> service registry.
>     * Fully declarative application metadata to enable reflection of
> an SCA component type definition.
>
> In order to maximise the potential scope of Aries adoption it is
> anticipated the project will remain agnostic of a number of
> complementary technologies and projects. It is the expectation that
> Aries will therefore not be delivering components such as: an
> application or integration server runtime kernel; a persistence
> provider; distribution provider; a deployment provider or a Web
> container. Aries will instead seek to enable the use of such
> components from other projects.
> Background
>
> OSGi is a mature and Java modularity technology that is well-used in
> many environments but, in the enterprise space, has more typically
> been exploited by the internals of the runtime infrastructure than the
> applications that run on it. This is primarily because of a lack of a
> clear enterprise OSGi application programming model and implementation
> of OSGi-enabled Java technology to support enterprise applications.
> OSGi specifications are specified and maintained by the OSGi Alliance
> which recognized this state of affairs several years ago and
> established the Enterprise Expert Group within the Alliance to focus
> specifically on the needs of enterprise applications. The objective of
> this project is to deliver open source implementations of these
> application-centric technologies to enable the development of
> application components, benefiting from the modularity of OSGi
> combined with standards-based programming models, which can be
> deployed to a variety of target runtimes.
> Rationale
>
> Aries aims to build a community of developers interested in the
> delivery of software components that support an enterprise OSGi
> programming model and which can be integrated into a number of
> different runtime environments. Apache hosts the Felix project which
> provides an OSGi framework implementation and a variety of projects
> which provide technologies exploited by enterprise application
> components as well as projects which provide runtimes to host
> application components. There is currently no Apache project focussed
> on OSGi enterprise applications that is independent from both the OSGi
> framework and the enterprise runtime environment in which application
> components are hosted. By maintaining independence of both the target
> runtime and underlying OSGi framework it is our intention to build the
> broadest possible community of developers for Aries, and to maximize
> the potential environments where Aries componentry can be used.
> Initial Goals
>
> We will initially focus on the Blueprint container and extend this
> with enterprise features such as support for container managed JPA and
> container managed transactions. Another initial focus area will be the
> contribution of code to support the assembly of isolated, multi-bundle
> applications that can be deployed as a unit.
> Current Status
> Meritocracy
>
> The Aries contributors recognize the desirability of running the
> project as a meritocracy. We are eager to engage other members of the
> community and operate to the standard of meritocracy that Apache
> emphasizes; we believe this is the most effective method of growing
> our community and enabling widespread adoption.
> Community
>
> OSGi is a mature Java modularity technology that is well-used in many
> environments but, in the enterprise space, has more typically been
> exploited by the internals of the runtime infrastructure than the
> applications that run on it. This is primarily because of a lack of a
> clear enterprise OSGi application programming model and implementation
> of OSGi-enabled Java technology to support enterprise applications.
> There is a need for open source implementations of these technologies
> and there is currently no Apache project focused on the wider goal of
> delivering components for an enterprise OSGi application programming
> model. Aries aims to build a community of developers interested in the
> definition and delivery of software components that support an
> enterprise OSGi programming model and which can be integrated into a
> number of different runtime environments. By maintaining independence
> of both the target runtime and underlying OSGi framework it is our
> intention to build the broadest possible community of developers.
> Alignment
>
> The purpose of Aries is to develop implementations of
> application-centric enterprise OSGi technologies that run on an OSGi
> framework, but not a specific one, and are used by application
> components deployed into a variety of runtime environments without
> being tied to any specific environment. For this reason we believe
> Aries is a project whose community would be best served if it could
> leverage but be independent from the communities that provide
> underlying OSGi framework technology and enterprise application server
> and integration bus technologies, all of which exist as open source
> efforts within Apache and elsewhere. We expect, for example, that some
> code developed in Aries will run directly on top of an OSGi framework
> such as Felix and that applications exploiting Aries technologies
> could be deployed to runtimes such as ServiceMix and Geronimo.
> Avoiding the Warning Signs
> Orphaned products
>
> The contributors are leading vendors of OSGi-based technologies and
> have a long standing in the OSGi Alliance whose application-centric
> specifications this project will implement. There is minimal risk of
> this work becoming non-strategic and the contributors are confident
> that a larger community will form within the project in a relatively
> short space of time.
> Inexperience with Open Source
>
> Many of the committers have experience working in one or more open
> source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
> and CXF.
>
> Homogeneous Developers
>
> The list of initial committers, geographically distributed across the
> U.S. and Europe, consists of developers from two companies - IBM and
> Progress software - with similar goals but for different scenarios.
> Many of these developers are experienced Apache committers already and
> all are experienced with working in distributed development
> communities. It is our hope that, through the incubator, further
> contributors with a broad background of experience but common interest
> in enterprise OSGi technologies will become involved with this
> project.
>
> Relationships with Other Apache Projects
>
> Aries will have a potential relationship with the Apache projects
> listed in this section. These projects all serve different purposes
> from Aries and have their own communities. It is hoped that each of
> these communities will become involved with Aries and help to build a
> diverse but independent Aries community.
>
> Apache Felix Karaf -
> http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
> Karaf is an OSGi based runtime which provides a lightweight container
> onto which various components and applications can be deployed. It is
> related to Aries:
>
>    1. as a target OSGi based runtime to which Aries applications can
> be deployed. In this role, Karaf is a consumer of Aries technology.
>
> Apache Felix - http://felix.apache.org/site/index.html Apache
> Felix is primarily a core OSGi framework implementation. It is related
> to Aries:
>
>    1. as an underlying OSGi framework implementation and potentially
> other extensions that can be used both by Aries run-time components
> and the applications which use them.
>
> Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
> a server runtime framework and fully certified Java EE 5 application
> server runtime. It is related to Aries in two ways:
>
>    1. as a target runtime to which Aries applications can be deployed.
> In this role, Geronimo is a consumer of Aries technology.
>    2. the Geronimo blueprint sandbox -
> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
> an implementation of the OSGi Blueprint container which will be moved
> to Aries.
>
> Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
> provides a comprehensive infrastructure for SOA development and
> management that is based on Service Component Architecture (SCA)
> standard. It can be a consumer of Aries technology to provide an Aries
> SCA implementation type for composing Aries applications in coarse
> grained and potentially heterogeneous service assemblies.
>
> Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
> Web Services framework for distributed computing and remote service
> realization and invocation using API's such as JAX-WS and JAX-RS. It
> also provides the OSGi Remote Services (OSGi RFC 119) reference
> implementation in a subproject:
> http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
> the following way:
>
>    1. As Remote Services is a significant Enterprise specification
> being produced by the EEG, it is expected that consumers of Aries will
> be looking for an implementation of this specification. CXF provides
> an implementation of this specification which already has a
> significant active community. The Aries project will make it easy for
> Aries consumers to consume the CXF Remote Services implementation,
> possibly by providing an instance of the application model that
> references the CXF Remote Services implementation. This would mean
> that end users will seamlessly pull in the required components from
> CXF by using the Aries-provided definition.
>
> Apache ServiceMix - http://servicemix.apache.org/ Apache
> ServiceMix provides an ESB that combines the functionality of a
> Service Oriented Architecture (SOA) and Event Driven Architecture
> (EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
> source of the Apache Felix Karaf runtime. It can be a consumer of
> Aries applications and associated componentry as a natural evolution
> of its existing Karaf "feature" usage.
>
> Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
> Java persistence project. It is related to Aries as a JPA persistence
> provider, including entity scanning and enhancement. The Aries project
> will make it easy for JPA persistence providers such as OpenJPA to be
> used in an OSGi environment and will provide container managed
> persistence for the Blueprint container.
>
> Documentation
>
> An early draft of OSGi v4.2 core and compendium specifications - which
> includes the Blueprint container specification - is available at:
> http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
> Initial Source
>
>     * The Blueprint container impl from the Geronimo sandbox will be
> moved to the Aries project for further development:
> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
>     * IBM will also contribute code for:
>           o container-managed JPA support in an OSGi environment.
>           o making OSGi services visible to Java EE components through JNDI.
>           o packaging web components as bundles and a URL handler for
> recognizing and converting non-bundled Web components
>     * We will also be soliciting implementations of other OSGi
> enterprise application-centric specifications.
>
> External Dependencies
>
>     * Apache Ant http://ant.apache.org Apache License
>     * Apache Commons http://commons.apache.org Apache License
>     * Junit (Java unit test framework) http://junit.sourceforge.net CPL
> v1.0 license: http://junit.sourceforge.net/cpl-v10.html
>     * Apache Felix (implementation of the OSGi Core and Compendium
> specifications - compliance level unknown) http://felix.apache.org
> Apache License (hosted by ASF).
>     * Eclipse Equinox (compliant implementation of the OSGi Core
> Specification and Compendium specifications)
> http://eclipse.org/equinox/ Eclipse Public License
>     * OpenJPA http://openjpa.apache.org Apache License
>     * Serp http://serp.sourceforge.net/ BSD
>     * Apache Geronimo http://geronimo.apache.org Apache License
>
> Required Resources
> Mailing lists
>
> aries-private (with moderated subscriptions)
> aries-dev
> aries-commits
> aries-user
>
> Subversion Directory
>
> http://svn.apache.org/repos/asf/incubator/aries
>
> Issue Tracking
>
> JIRA (ARIES)
>
> Web Site
>
> Confluence (Aries)
>
> Initial Committers
>
> Names of initial committers with affiliation and current ASF status:
>
>     * Alasdair Nottingham (IBM)
>     * Andrew Osborne (IBM)
>     * Dan Kulp (Progress, ASF member)
>     * David Bosschaert (Progress, ASF committer)
>     * David Jencks (IBM, ASF member)
>     * Eoghan Glynn (Progress, ASF committer)
>     * Graham Charters (IBM)
>     * Guillaume Nodet (Progress, ASF member)
>     * Hiram Chirino (Progress, ASF member)
>     * Ian Robinson (IBM)
>     * James Strachan (Progress, ASF member)
>     * Jarek Gawor (IBM, ASF member)
>     * Jeremy Hughes (IBM, ASF committer)
>     * Joe Bohn (IBM, ASF committer)
>     * Lin Sun (IBM, ASF committer)
>     * Mark Nuttall (IBM)
>     * Oisin Hurley (Progress)
>     * Rick McGuire (IBM, ASF committer)
>     * Sergey Beryozkin (Progress, ASF committer),
>     * Timothy Ward (IBM)
>     * Valentin Mahrwald (IBM)
>     * Zoe Slattery (IBM)
>
> Affiliations
>
> The majority of the initial committers are employed by IBM corp or
> Progress Software. One objective of the incubator is to attract a
> diverse community of contributors and we anticipate future
> contributors to have other affiliations.
>
> Sponsors
> Champions
>
> Kevan Miller, Guillaume Nodet
>
> Nominated Mentors
>
> Guillaume Nodet, Davanum Srinivas (Dims)
>
> Sponsoring Entity
>
> The incubator. Successful graduation from Incubator should result in
> Aries becoming a new TLP.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>    

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks Guillaume, understood.

Regards
JB

Guillaume Nodet wrote:
> Karaf is a runtime, which means it includes the OSGi framework and you can
> install it and start it, providing a number of additional features compared
> to a plain OSGi framework.
> The goal of Aries is not to provide such a runtime, but rather provide
> components that can be installed into different runtimes, such as Karaf (or
> even on a plain OSGi framework).
> As for OBR, it's a bundle repository format and resolver.  Such a repository
> resolver can be leveraged by the item named "isolated enterprise
> applications composed of multiple, versioned
> bundles with dynamic lifecycle", but is out of scope for Aries itself.
> 
> On Tue, Sep 1, 2009 at 16:44, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> 
>> Hi Jeremy,
>>
>> could you spot the differences with Apache Felix/Karaf and the SMX OBR ?
>>
>> Thanks,
>> Regards
>> JB
>>
>>
>> Jeremy Hughes wrote:
>>
>>> Hi, we would like to propose a new incubator podling called Aries.
>>>
>>> http://wiki.apache.org/incubator/AriesProposal
>>>
>>> Here is a quick summary of the proposal
>>>
>>> The Aries project will deliver a set of pluggable Java components
>>> enabling an enterprise OSGi application programming model. This
>>> includes implementations and extensions of application-focused
>>> specifications defined by the OSGi Alliance Enterprise Expert Group
>>> (EEG) and an assembly format for multi-bundle applications, for
>>> deployment to a variety of OSGi based runtimes.
>>>
>>> Aries aims to build a community of developers interested in the
>>> definition and delivery of software components that support an
>>> enterprise OSGi programming model and which can be integrated into a
>>> number of different runtime environments.
>>>
>>> We appreciate any feedback and comments on the proposal.
>>>
>>> Here is a plain text copy of the whole proposal:
>>>
>>> Apache Aries
>>> Abstract
>>>
>>> The Aries project will deliver a set of pluggable Java components
>>> enabling an enterprise OSGi application programming model. This
>>> includes implementations and extensions of application-focused
>>> specifications defined by the OSGi Alliance Enterprise Expert Group
>>> (EEG) and an assembly format for multi-bundle applications, for
>>> deployment to a variety of OSGi based runtimes.
>>> Proposal
>>>
>>> It is a goal of the Aries project to provide a natural home for open
>>> source implementations of current and future OSGi EEG specifications,
>>> including the opportunity for the collaborative development of
>>> compliance tests, and an environment to demonstrate the composition of
>>> these technologies and to explore areas where EEG specifications lack
>>> coverage. A further goal of this project is to leverage experience
>>> gained from it to inform contributions to OSGi EEG requirements and
>>> specification documents.
>>>
>>> Aries will offer an enterprise OSGi application programming model that
>>> enables applications to leverage Java EE and other enterprise
>>> technologies and to benefit from the modularity, dynamism and
>>> versioning capabilities of OSGi. A significant feature of Aries will
>>> be a container for OSGi Blueprint components - an implementation of
>>> the new OSGi v4.2 Blueprint component model that defines a standard
>>> dependency injection mechanism for Java components, which is derived
>>> from the Spring framework and extended for OSGi to declaratively
>>> register component interfaces as services in the OSGi service
>>> registry.
>>>
>>> In addition, the Aries project will develop a model for assembling an
>>> application/subsystem into a deployable unit, consisting of multiple
>>> bundles, as an archive which may include metadata that describes the
>>> version and external location of the application's constituent bundles
>>> or which may contain the bundles directly.
>>>
>>> The Aries project will deliver run-time componentry that supports
>>> applications, running in an OSGi framework, exploiting enterprise Java
>>> technologies common in web applications and integration scenarios
>>> including web application bundles, remote services integration and
>>> JPA. The project is not expected to deliver a complete application or
>>> integration server runtime but will instead deliver enterprise
>>> application componentry that can be integrated into such runtimes. The
>>> project will develop extensions that go beyond the OSGi EEG
>>> specifications to provide a more complete integration of OSGi
>>> modularity with Java enterprise technologies, in particular delivering
>>> support that includes but is not restricted to:
>>>
>>>   * isolated enterprise applications composed of multiple, versioned
>>> bundles with dynamic lifecycle.
>>>   * declarative transactions and security for Blueprint components
>>>   * Container-managed JPA for Blueprint components
>>>   * Message-driven Blueprint components
>>>   * Configuration of resource references in module blueprints.
>>>   * Annotation-based Blueprint configuration
>>>   * Federation of lookup mechanisms between local JNDI and the OSGi
>>> service registry.
>>>   * Fully declarative application metadata to enable reflection of
>>> an SCA component type definition.
>>>
>>> In order to maximise the potential scope of Aries adoption it is
>>> anticipated the project will remain agnostic of a number of
>>> complementary technologies and projects. It is the expectation that
>>> Aries will therefore not be delivering components such as: an
>>> application or integration server runtime kernel; a persistence
>>> provider; distribution provider; a deployment provider or a Web
>>> container. Aries will instead seek to enable the use of such
>>> components from other projects.
>>> Background
>>>
>>> OSGi is a mature and Java modularity technology that is well-used in
>>> many environments but, in the enterprise space, has more typically
>>> been exploited by the internals of the runtime infrastructure than the
>>> applications that run on it. This is primarily because of a lack of a
>>> clear enterprise OSGi application programming model and implementation
>>> of OSGi-enabled Java technology to support enterprise applications.
>>> OSGi specifications are specified and maintained by the OSGi Alliance
>>> which recognized this state of affairs several years ago and
>>> established the Enterprise Expert Group within the Alliance to focus
>>> specifically on the needs of enterprise applications. The objective of
>>> this project is to deliver open source implementations of these
>>> application-centric technologies to enable the development of
>>> application components, benefiting from the modularity of OSGi
>>> combined with standards-based programming models, which can be
>>> deployed to a variety of target runtimes.
>>> Rationale
>>>
>>> Aries aims to build a community of developers interested in the
>>> delivery of software components that support an enterprise OSGi
>>> programming model and which can be integrated into a number of
>>> different runtime environments. Apache hosts the Felix project which
>>> provides an OSGi framework implementation and a variety of projects
>>> which provide technologies exploited by enterprise application
>>> components as well as projects which provide runtimes to host
>>> application components. There is currently no Apache project focussed
>>> on OSGi enterprise applications that is independent from both the OSGi
>>> framework and the enterprise runtime environment in which application
>>> components are hosted. By maintaining independence of both the target
>>> runtime and underlying OSGi framework it is our intention to build the
>>> broadest possible community of developers for Aries, and to maximize
>>> the potential environments where Aries componentry can be used.
>>> Initial Goals
>>>
>>> We will initially focus on the Blueprint container and extend this
>>> with enterprise features such as support for container managed JPA and
>>> container managed transactions. Another initial focus area will be the
>>> contribution of code to support the assembly of isolated, multi-bundle
>>> applications that can be deployed as a unit.
>>> Current Status
>>> Meritocracy
>>>
>>> The Aries contributors recognize the desirability of running the
>>> project as a meritocracy. We are eager to engage other members of the
>>> community and operate to the standard of meritocracy that Apache
>>> emphasizes; we believe this is the most effective method of growing
>>> our community and enabling widespread adoption.
>>> Community
>>>
>>> OSGi is a mature Java modularity technology that is well-used in many
>>> environments but, in the enterprise space, has more typically been
>>> exploited by the internals of the runtime infrastructure than the
>>> applications that run on it. This is primarily because of a lack of a
>>> clear enterprise OSGi application programming model and implementation
>>> of OSGi-enabled Java technology to support enterprise applications.
>>> There is a need for open source implementations of these technologies
>>> and there is currently no Apache project focused on the wider goal of
>>> delivering components for an enterprise OSGi application programming
>>> model. Aries aims to build a community of developers interested in the
>>> definition and delivery of software components that support an
>>> enterprise OSGi programming model and which can be integrated into a
>>> number of different runtime environments. By maintaining independence
>>> of both the target runtime and underlying OSGi framework it is our
>>> intention to build the broadest possible community of developers.
>>> Alignment
>>>
>>> The purpose of Aries is to develop implementations of
>>> application-centric enterprise OSGi technologies that run on an OSGi
>>> framework, but not a specific one, and are used by application
>>> components deployed into a variety of runtime environments without
>>> being tied to any specific environment. For this reason we believe
>>> Aries is a project whose community would be best served if it could
>>> leverage but be independent from the communities that provide
>>> underlying OSGi framework technology and enterprise application server
>>> and integration bus technologies, all of which exist as open source
>>> efforts within Apache and elsewhere. We expect, for example, that some
>>> code developed in Aries will run directly on top of an OSGi framework
>>> such as Felix and that applications exploiting Aries technologies
>>> could be deployed to runtimes such as ServiceMix and Geronimo.
>>> Avoiding the Warning Signs
>>> Orphaned products
>>>
>>> The contributors are leading vendors of OSGi-based technologies and
>>> have a long standing in the OSGi Alliance whose application-centric
>>> specifications this project will implement. There is minimal risk of
>>> this work becoming non-strategic and the contributors are confident
>>> that a larger community will form within the project in a relatively
>>> short space of time.
>>> Inexperience with Open Source
>>>
>>> Many of the committers have experience working in one or more open
>>> source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
>>> and CXF.
>>>
>>> Homogeneous Developers
>>>
>>> The list of initial committers, geographically distributed across the
>>> U.S. and Europe, consists of developers from two companies - IBM and
>>> Progress software - with similar goals but for different scenarios.
>>> Many of these developers are experienced Apache committers already and
>>> all are experienced with working in distributed development
>>> communities. It is our hope that, through the incubator, further
>>> contributors with a broad background of experience but common interest
>>> in enterprise OSGi technologies will become involved with this
>>> project.
>>>
>>> Relationships with Other Apache Projects
>>>
>>> Aries will have a potential relationship with the Apache projects
>>> listed in this section. These projects all serve different purposes
>>> from Aries and have their own communities. It is hoped that each of
>>> these communities will become involved with Aries and help to build a
>>> diverse but independent Aries community.
>>>
>>> Apache Felix Karaf -
>>> http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
>>> Karaf is an OSGi based runtime which provides a lightweight container
>>> onto which various components and applications can be deployed. It is
>>> related to Aries:
>>>
>>>  1. as a target OSGi based runtime to which Aries applications can
>>> be deployed. In this role, Karaf is a consumer of Aries technology.
>>>
>>> Apache Felix - http://felix.apache.org/site/index.html Apache
>>> Felix is primarily a core OSGi framework implementation. It is related
>>> to Aries:
>>>
>>>  1. as an underlying OSGi framework implementation and potentially
>>> other extensions that can be used both by Aries run-time components
>>> and the applications which use them.
>>>
>>> Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
>>> a server runtime framework and fully certified Java EE 5 application
>>> server runtime. It is related to Aries in two ways:
>>>
>>>  1. as a target runtime to which Aries applications can be deployed.
>>> In this role, Geronimo is a consumer of Aries technology.
>>>  2. the Geronimo blueprint sandbox -
>>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
>>> an implementation of the OSGi Blueprint container which will be moved
>>> to Aries.
>>>
>>> Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
>>> provides a comprehensive infrastructure for SOA development and
>>> management that is based on Service Component Architecture (SCA)
>>> standard. It can be a consumer of Aries technology to provide an Aries
>>> SCA implementation type for composing Aries applications in coarse
>>> grained and potentially heterogeneous service assemblies.
>>>
>>> Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
>>> Web Services framework for distributed computing and remote service
>>> realization and invocation using API's such as JAX-WS and JAX-RS. It
>>> also provides the OSGi Remote Services (OSGi RFC 119) reference
>>> implementation in a subproject:
>>> http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
>>> the following way:
>>>
>>>  1. As Remote Services is a significant Enterprise specification
>>> being produced by the EEG, it is expected that consumers of Aries will
>>> be looking for an implementation of this specification. CXF provides
>>> an implementation of this specification which already has a
>>> significant active community. The Aries project will make it easy for
>>> Aries consumers to consume the CXF Remote Services implementation,
>>> possibly by providing an instance of the application model that
>>> references the CXF Remote Services implementation. This would mean
>>> that end users will seamlessly pull in the required components from
>>> CXF by using the Aries-provided definition.
>>>
>>> Apache ServiceMix - http://servicemix.apache.org/ Apache
>>> ServiceMix provides an ESB that combines the functionality of a
>>> Service Oriented Architecture (SOA) and Event Driven Architecture
>>> (EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
>>> source of the Apache Felix Karaf runtime. It can be a consumer of
>>> Aries applications and associated componentry as a natural evolution
>>> of its existing Karaf "feature" usage.
>>>
>>> Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
>>> Java persistence project. It is related to Aries as a JPA persistence
>>> provider, including entity scanning and enhancement. The Aries project
>>> will make it easy for JPA persistence providers such as OpenJPA to be
>>> used in an OSGi environment and will provide container managed
>>> persistence for the Blueprint container.
>>>
>>> Documentation
>>>
>>> An early draft of OSGi v4.2 core and compendium specifications - which
>>> includes the Blueprint container specification - is available at:
>>> http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
>>> Initial Source
>>>
>>>   * The Blueprint container impl from the Geronimo sandbox will be
>>> moved to the Aries project for further development:
>>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
>>>   * IBM will also contribute code for:
>>>         o container-managed JPA support in an OSGi environment.
>>>         o making OSGi services visible to Java EE components through JNDI.
>>>         o packaging web components as bundles and a URL handler for
>>> recognizing and converting non-bundled Web components
>>>   * We will also be soliciting implementations of other OSGi
>>> enterprise application-centric specifications.
>>>
>>> External Dependencies
>>>
>>>   * Apache Ant http://ant.apache.org Apache License
>>>   * Apache Commons http://commons.apache.org Apache License
>>>   * Junit (Java unit test framework) http://junit.sourceforge.net CPL
>>> v1.0 license: http://junit.sourceforge.net/cpl-v10.html
>>>   * Apache Felix (implementation of the OSGi Core and Compendium
>>> specifications - compliance level unknown) http://felix.apache.org
>>> Apache License (hosted by ASF).
>>>   * Eclipse Equinox (compliant implementation of the OSGi Core
>>> Specification and Compendium specifications)
>>> http://eclipse.org/equinox/ Eclipse Public License
>>>   * OpenJPA http://openjpa.apache.org Apache License
>>>   * Serp http://serp.sourceforge.net/ BSD
>>>   * Apache Geronimo http://geronimo.apache.org Apache License
>>>
>>> Required Resources
>>> Mailing lists
>>>
>>> aries-private (with moderated subscriptions)
>>> aries-dev
>>> aries-commits
>>> aries-user
>>>
>>> Subversion Directory
>>>
>>> http://svn.apache.org/repos/asf/incubator/aries
>>>
>>> Issue Tracking
>>>
>>> JIRA (ARIES)
>>>
>>> Web Site
>>>
>>> Confluence (Aries)
>>>
>>> Initial Committers
>>>
>>> Names of initial committers with affiliation and current ASF status:
>>>
>>>   * Alasdair Nottingham (IBM)
>>>   * Andrew Osborne (IBM)
>>>   * Dan Kulp (Progress, ASF member)
>>>   * David Bosschaert (Progress, ASF committer)
>>>   * David Jencks (IBM, ASF member)
>>>   * Eoghan Glynn (Progress, ASF committer)
>>>   * Graham Charters (IBM)
>>>   * Guillaume Nodet (Progress, ASF member)
>>>   * Hiram Chirino (Progress, ASF member)
>>>   * Ian Robinson (IBM)
>>>   * James Strachan (Progress, ASF member)
>>>   * Jarek Gawor (IBM, ASF member)
>>>   * Jeremy Hughes (IBM, ASF committer)
>>>   * Joe Bohn (IBM, ASF committer)
>>>   * Lin Sun (IBM, ASF committer)
>>>   * Mark Nuttall (IBM)
>>>   * Oisin Hurley (Progress)
>>>   * Rick McGuire (IBM, ASF committer)
>>>   * Sergey Beryozkin (Progress, ASF committer),
>>>   * Timothy Ward (IBM)
>>>   * Valentin Mahrwald (IBM)
>>>   * Zoe Slattery (IBM)
>>>
>>> Affiliations
>>>
>>> The majority of the initial committers are employed by IBM corp or
>>> Progress Software. One objective of the incubator is to attract a
>>> diverse community of contributors and we anticipate future
>>> contributors to have other affiliations.
>>>
>>> Sponsors
>>> Champions
>>>
>>> Kevan Miller, Guillaume Nodet
>>>
>>> Nominated Mentors
>>>
>>> Guillaume Nodet, Davanum Srinivas (Dims)
>>>
>>> Sponsoring Entity
>>>
>>> The incubator. Successful graduation from Incubator should result in
>>> Aries becoming a new TLP.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
Karaf is a runtime, which means it includes the OSGi framework and you can
install it and start it, providing a number of additional features compared
to a plain OSGi framework.
The goal of Aries is not to provide such a runtime, but rather provide
components that can be installed into different runtimes, such as Karaf (or
even on a plain OSGi framework).
As for OBR, it's a bundle repository format and resolver.  Such a repository
resolver can be leveraged by the item named "isolated enterprise
applications composed of multiple, versioned
bundles with dynamic lifecycle", but is out of scope for Aries itself.

On Tue, Sep 1, 2009 at 16:44, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:

> Hi Jeremy,
>
> could you spot the differences with Apache Felix/Karaf and the SMX OBR ?
>
> Thanks,
> Regards
> JB
>
>
> Jeremy Hughes wrote:
>
>> Hi, we would like to propose a new incubator podling called Aries.
>>
>> http://wiki.apache.org/incubator/AriesProposal
>>
>> Here is a quick summary of the proposal
>>
>> The Aries project will deliver a set of pluggable Java components
>> enabling an enterprise OSGi application programming model. This
>> includes implementations and extensions of application-focused
>> specifications defined by the OSGi Alliance Enterprise Expert Group
>> (EEG) and an assembly format for multi-bundle applications, for
>> deployment to a variety of OSGi based runtimes.
>>
>> Aries aims to build a community of developers interested in the
>> definition and delivery of software components that support an
>> enterprise OSGi programming model and which can be integrated into a
>> number of different runtime environments.
>>
>> We appreciate any feedback and comments on the proposal.
>>
>> Here is a plain text copy of the whole proposal:
>>
>> Apache Aries
>> Abstract
>>
>> The Aries project will deliver a set of pluggable Java components
>> enabling an enterprise OSGi application programming model. This
>> includes implementations and extensions of application-focused
>> specifications defined by the OSGi Alliance Enterprise Expert Group
>> (EEG) and an assembly format for multi-bundle applications, for
>> deployment to a variety of OSGi based runtimes.
>> Proposal
>>
>> It is a goal of the Aries project to provide a natural home for open
>> source implementations of current and future OSGi EEG specifications,
>> including the opportunity for the collaborative development of
>> compliance tests, and an environment to demonstrate the composition of
>> these technologies and to explore areas where EEG specifications lack
>> coverage. A further goal of this project is to leverage experience
>> gained from it to inform contributions to OSGi EEG requirements and
>> specification documents.
>>
>> Aries will offer an enterprise OSGi application programming model that
>> enables applications to leverage Java EE and other enterprise
>> technologies and to benefit from the modularity, dynamism and
>> versioning capabilities of OSGi. A significant feature of Aries will
>> be a container for OSGi Blueprint components - an implementation of
>> the new OSGi v4.2 Blueprint component model that defines a standard
>> dependency injection mechanism for Java components, which is derived
>> from the Spring framework and extended for OSGi to declaratively
>> register component interfaces as services in the OSGi service
>> registry.
>>
>> In addition, the Aries project will develop a model for assembling an
>> application/subsystem into a deployable unit, consisting of multiple
>> bundles, as an archive which may include metadata that describes the
>> version and external location of the application's constituent bundles
>> or which may contain the bundles directly.
>>
>> The Aries project will deliver run-time componentry that supports
>> applications, running in an OSGi framework, exploiting enterprise Java
>> technologies common in web applications and integration scenarios
>> including web application bundles, remote services integration and
>> JPA. The project is not expected to deliver a complete application or
>> integration server runtime but will instead deliver enterprise
>> application componentry that can be integrated into such runtimes. The
>> project will develop extensions that go beyond the OSGi EEG
>> specifications to provide a more complete integration of OSGi
>> modularity with Java enterprise technologies, in particular delivering
>> support that includes but is not restricted to:
>>
>>   * isolated enterprise applications composed of multiple, versioned
>> bundles with dynamic lifecycle.
>>   * declarative transactions and security for Blueprint components
>>   * Container-managed JPA for Blueprint components
>>   * Message-driven Blueprint components
>>   * Configuration of resource references in module blueprints.
>>   * Annotation-based Blueprint configuration
>>   * Federation of lookup mechanisms between local JNDI and the OSGi
>> service registry.
>>   * Fully declarative application metadata to enable reflection of
>> an SCA component type definition.
>>
>> In order to maximise the potential scope of Aries adoption it is
>> anticipated the project will remain agnostic of a number of
>> complementary technologies and projects. It is the expectation that
>> Aries will therefore not be delivering components such as: an
>> application or integration server runtime kernel; a persistence
>> provider; distribution provider; a deployment provider or a Web
>> container. Aries will instead seek to enable the use of such
>> components from other projects.
>> Background
>>
>> OSGi is a mature and Java modularity technology that is well-used in
>> many environments but, in the enterprise space, has more typically
>> been exploited by the internals of the runtime infrastructure than the
>> applications that run on it. This is primarily because of a lack of a
>> clear enterprise OSGi application programming model and implementation
>> of OSGi-enabled Java technology to support enterprise applications.
>> OSGi specifications are specified and maintained by the OSGi Alliance
>> which recognized this state of affairs several years ago and
>> established the Enterprise Expert Group within the Alliance to focus
>> specifically on the needs of enterprise applications. The objective of
>> this project is to deliver open source implementations of these
>> application-centric technologies to enable the development of
>> application components, benefiting from the modularity of OSGi
>> combined with standards-based programming models, which can be
>> deployed to a variety of target runtimes.
>> Rationale
>>
>> Aries aims to build a community of developers interested in the
>> delivery of software components that support an enterprise OSGi
>> programming model and which can be integrated into a number of
>> different runtime environments. Apache hosts the Felix project which
>> provides an OSGi framework implementation and a variety of projects
>> which provide technologies exploited by enterprise application
>> components as well as projects which provide runtimes to host
>> application components. There is currently no Apache project focussed
>> on OSGi enterprise applications that is independent from both the OSGi
>> framework and the enterprise runtime environment in which application
>> components are hosted. By maintaining independence of both the target
>> runtime and underlying OSGi framework it is our intention to build the
>> broadest possible community of developers for Aries, and to maximize
>> the potential environments where Aries componentry can be used.
>> Initial Goals
>>
>> We will initially focus on the Blueprint container and extend this
>> with enterprise features such as support for container managed JPA and
>> container managed transactions. Another initial focus area will be the
>> contribution of code to support the assembly of isolated, multi-bundle
>> applications that can be deployed as a unit.
>> Current Status
>> Meritocracy
>>
>> The Aries contributors recognize the desirability of running the
>> project as a meritocracy. We are eager to engage other members of the
>> community and operate to the standard of meritocracy that Apache
>> emphasizes; we believe this is the most effective method of growing
>> our community and enabling widespread adoption.
>> Community
>>
>> OSGi is a mature Java modularity technology that is well-used in many
>> environments but, in the enterprise space, has more typically been
>> exploited by the internals of the runtime infrastructure than the
>> applications that run on it. This is primarily because of a lack of a
>> clear enterprise OSGi application programming model and implementation
>> of OSGi-enabled Java technology to support enterprise applications.
>> There is a need for open source implementations of these technologies
>> and there is currently no Apache project focused on the wider goal of
>> delivering components for an enterprise OSGi application programming
>> model. Aries aims to build a community of developers interested in the
>> definition and delivery of software components that support an
>> enterprise OSGi programming model and which can be integrated into a
>> number of different runtime environments. By maintaining independence
>> of both the target runtime and underlying OSGi framework it is our
>> intention to build the broadest possible community of developers.
>> Alignment
>>
>> The purpose of Aries is to develop implementations of
>> application-centric enterprise OSGi technologies that run on an OSGi
>> framework, but not a specific one, and are used by application
>> components deployed into a variety of runtime environments without
>> being tied to any specific environment. For this reason we believe
>> Aries is a project whose community would be best served if it could
>> leverage but be independent from the communities that provide
>> underlying OSGi framework technology and enterprise application server
>> and integration bus technologies, all of which exist as open source
>> efforts within Apache and elsewhere. We expect, for example, that some
>> code developed in Aries will run directly on top of an OSGi framework
>> such as Felix and that applications exploiting Aries technologies
>> could be deployed to runtimes such as ServiceMix and Geronimo.
>> Avoiding the Warning Signs
>> Orphaned products
>>
>> The contributors are leading vendors of OSGi-based technologies and
>> have a long standing in the OSGi Alliance whose application-centric
>> specifications this project will implement. There is minimal risk of
>> this work becoming non-strategic and the contributors are confident
>> that a larger community will form within the project in a relatively
>> short space of time.
>> Inexperience with Open Source
>>
>> Many of the committers have experience working in one or more open
>> source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
>> and CXF.
>>
>> Homogeneous Developers
>>
>> The list of initial committers, geographically distributed across the
>> U.S. and Europe, consists of developers from two companies - IBM and
>> Progress software - with similar goals but for different scenarios.
>> Many of these developers are experienced Apache committers already and
>> all are experienced with working in distributed development
>> communities. It is our hope that, through the incubator, further
>> contributors with a broad background of experience but common interest
>> in enterprise OSGi technologies will become involved with this
>> project.
>>
>> Relationships with Other Apache Projects
>>
>> Aries will have a potential relationship with the Apache projects
>> listed in this section. These projects all serve different purposes
>> from Aries and have their own communities. It is hoped that each of
>> these communities will become involved with Aries and help to build a
>> diverse but independent Aries community.
>>
>> Apache Felix Karaf -
>> http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
>> Karaf is an OSGi based runtime which provides a lightweight container
>> onto which various components and applications can be deployed. It is
>> related to Aries:
>>
>>  1. as a target OSGi based runtime to which Aries applications can
>> be deployed. In this role, Karaf is a consumer of Aries technology.
>>
>> Apache Felix - http://felix.apache.org/site/index.html Apache
>> Felix is primarily a core OSGi framework implementation. It is related
>> to Aries:
>>
>>  1. as an underlying OSGi framework implementation and potentially
>> other extensions that can be used both by Aries run-time components
>> and the applications which use them.
>>
>> Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
>> a server runtime framework and fully certified Java EE 5 application
>> server runtime. It is related to Aries in two ways:
>>
>>  1. as a target runtime to which Aries applications can be deployed.
>> In this role, Geronimo is a consumer of Aries technology.
>>  2. the Geronimo blueprint sandbox -
>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
>> an implementation of the OSGi Blueprint container which will be moved
>> to Aries.
>>
>> Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
>> provides a comprehensive infrastructure for SOA development and
>> management that is based on Service Component Architecture (SCA)
>> standard. It can be a consumer of Aries technology to provide an Aries
>> SCA implementation type for composing Aries applications in coarse
>> grained and potentially heterogeneous service assemblies.
>>
>> Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
>> Web Services framework for distributed computing and remote service
>> realization and invocation using API's such as JAX-WS and JAX-RS. It
>> also provides the OSGi Remote Services (OSGi RFC 119) reference
>> implementation in a subproject:
>> http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
>> the following way:
>>
>>  1. As Remote Services is a significant Enterprise specification
>> being produced by the EEG, it is expected that consumers of Aries will
>> be looking for an implementation of this specification. CXF provides
>> an implementation of this specification which already has a
>> significant active community. The Aries project will make it easy for
>> Aries consumers to consume the CXF Remote Services implementation,
>> possibly by providing an instance of the application model that
>> references the CXF Remote Services implementation. This would mean
>> that end users will seamlessly pull in the required components from
>> CXF by using the Aries-provided definition.
>>
>> Apache ServiceMix - http://servicemix.apache.org/ Apache
>> ServiceMix provides an ESB that combines the functionality of a
>> Service Oriented Architecture (SOA) and Event Driven Architecture
>> (EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
>> source of the Apache Felix Karaf runtime. It can be a consumer of
>> Aries applications and associated componentry as a natural evolution
>> of its existing Karaf "feature" usage.
>>
>> Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
>> Java persistence project. It is related to Aries as a JPA persistence
>> provider, including entity scanning and enhancement. The Aries project
>> will make it easy for JPA persistence providers such as OpenJPA to be
>> used in an OSGi environment and will provide container managed
>> persistence for the Blueprint container.
>>
>> Documentation
>>
>> An early draft of OSGi v4.2 core and compendium specifications - which
>> includes the Blueprint container specification - is available at:
>> http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
>> Initial Source
>>
>>   * The Blueprint container impl from the Geronimo sandbox will be
>> moved to the Aries project for further development:
>> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
>>   * IBM will also contribute code for:
>>         o container-managed JPA support in an OSGi environment.
>>         o making OSGi services visible to Java EE components through JNDI.
>>         o packaging web components as bundles and a URL handler for
>> recognizing and converting non-bundled Web components
>>   * We will also be soliciting implementations of other OSGi
>> enterprise application-centric specifications.
>>
>> External Dependencies
>>
>>   * Apache Ant http://ant.apache.org Apache License
>>   * Apache Commons http://commons.apache.org Apache License
>>   * Junit (Java unit test framework) http://junit.sourceforge.net CPL
>> v1.0 license: http://junit.sourceforge.net/cpl-v10.html
>>   * Apache Felix (implementation of the OSGi Core and Compendium
>> specifications - compliance level unknown) http://felix.apache.org
>> Apache License (hosted by ASF).
>>   * Eclipse Equinox (compliant implementation of the OSGi Core
>> Specification and Compendium specifications)
>> http://eclipse.org/equinox/ Eclipse Public License
>>   * OpenJPA http://openjpa.apache.org Apache License
>>   * Serp http://serp.sourceforge.net/ BSD
>>   * Apache Geronimo http://geronimo.apache.org Apache License
>>
>> Required Resources
>> Mailing lists
>>
>> aries-private (with moderated subscriptions)
>> aries-dev
>> aries-commits
>> aries-user
>>
>> Subversion Directory
>>
>> http://svn.apache.org/repos/asf/incubator/aries
>>
>> Issue Tracking
>>
>> JIRA (ARIES)
>>
>> Web Site
>>
>> Confluence (Aries)
>>
>> Initial Committers
>>
>> Names of initial committers with affiliation and current ASF status:
>>
>>   * Alasdair Nottingham (IBM)
>>   * Andrew Osborne (IBM)
>>   * Dan Kulp (Progress, ASF member)
>>   * David Bosschaert (Progress, ASF committer)
>>   * David Jencks (IBM, ASF member)
>>   * Eoghan Glynn (Progress, ASF committer)
>>   * Graham Charters (IBM)
>>   * Guillaume Nodet (Progress, ASF member)
>>   * Hiram Chirino (Progress, ASF member)
>>   * Ian Robinson (IBM)
>>   * James Strachan (Progress, ASF member)
>>   * Jarek Gawor (IBM, ASF member)
>>   * Jeremy Hughes (IBM, ASF committer)
>>   * Joe Bohn (IBM, ASF committer)
>>   * Lin Sun (IBM, ASF committer)
>>   * Mark Nuttall (IBM)
>>   * Oisin Hurley (Progress)
>>   * Rick McGuire (IBM, ASF committer)
>>   * Sergey Beryozkin (Progress, ASF committer),
>>   * Timothy Ward (IBM)
>>   * Valentin Mahrwald (IBM)
>>   * Zoe Slattery (IBM)
>>
>> Affiliations
>>
>> The majority of the initial committers are employed by IBM corp or
>> Progress Software. One objective of the incubator is to attract a
>> diverse community of contributors and we anticipate future
>> contributors to have other affiliations.
>>
>> Sponsors
>> Champions
>>
>> Kevan Miller, Guillaume Nodet
>>
>> Nominated Mentors
>>
>> Guillaume Nodet, Davanum Srinivas (Dims)
>>
>> Sponsoring Entity
>>
>> The incubator. Successful graduation from Incubator should result in
>> Aries becoming a new TLP.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Jeremy,

could you spot the differences with Apache Felix/Karaf and the SMX OBR ?

Thanks,
Regards
JB

Jeremy Hughes wrote:
> Hi, we would like to propose a new incubator podling called Aries.
> 
> http://wiki.apache.org/incubator/AriesProposal
> 
> Here is a quick summary of the proposal
> 
> The Aries project will deliver a set of pluggable Java components
> enabling an enterprise OSGi application programming model. This
> includes implementations and extensions of application-focused
> specifications defined by the OSGi Alliance Enterprise Expert Group
> (EEG) and an assembly format for multi-bundle applications, for
> deployment to a variety of OSGi based runtimes.
> 
> Aries aims to build a community of developers interested in the
> definition and delivery of software components that support an
> enterprise OSGi programming model and which can be integrated into a
> number of different runtime environments.
> 
> We appreciate any feedback and comments on the proposal.
> 
> Here is a plain text copy of the whole proposal:
> 
> Apache Aries
> Abstract
> 
> The Aries project will deliver a set of pluggable Java components
> enabling an enterprise OSGi application programming model. This
> includes implementations and extensions of application-focused
> specifications defined by the OSGi Alliance Enterprise Expert Group
> (EEG) and an assembly format for multi-bundle applications, for
> deployment to a variety of OSGi based runtimes.
> Proposal
> 
> It is a goal of the Aries project to provide a natural home for open
> source implementations of current and future OSGi EEG specifications,
> including the opportunity for the collaborative development of
> compliance tests, and an environment to demonstrate the composition of
> these technologies and to explore areas where EEG specifications lack
> coverage. A further goal of this project is to leverage experience
> gained from it to inform contributions to OSGi EEG requirements and
> specification documents.
> 
> Aries will offer an enterprise OSGi application programming model that
> enables applications to leverage Java EE and other enterprise
> technologies and to benefit from the modularity, dynamism and
> versioning capabilities of OSGi. A significant feature of Aries will
> be a container for OSGi Blueprint components - an implementation of
> the new OSGi v4.2 Blueprint component model that defines a standard
> dependency injection mechanism for Java components, which is derived
> from the Spring framework and extended for OSGi to declaratively
> register component interfaces as services in the OSGi service
> registry.
> 
> In addition, the Aries project will develop a model for assembling an
> application/subsystem into a deployable unit, consisting of multiple
> bundles, as an archive which may include metadata that describes the
> version and external location of the application's constituent bundles
> or which may contain the bundles directly.
> 
> The Aries project will deliver run-time componentry that supports
> applications, running in an OSGi framework, exploiting enterprise Java
> technologies common in web applications and integration scenarios
> including web application bundles, remote services integration and
> JPA. The project is not expected to deliver a complete application or
> integration server runtime but will instead deliver enterprise
> application componentry that can be integrated into such runtimes. The
> project will develop extensions that go beyond the OSGi EEG
> specifications to provide a more complete integration of OSGi
> modularity with Java enterprise technologies, in particular delivering
> support that includes but is not restricted to:
> 
>    * isolated enterprise applications composed of multiple, versioned
> bundles with dynamic lifecycle.
>    * declarative transactions and security for Blueprint components
>    * Container-managed JPA for Blueprint components
>    * Message-driven Blueprint components
>    * Configuration of resource references in module blueprints.
>    * Annotation-based Blueprint configuration
>    * Federation of lookup mechanisms between local JNDI and the OSGi
> service registry.
>    * Fully declarative application metadata to enable reflection of
> an SCA component type definition.
> 
> In order to maximise the potential scope of Aries adoption it is
> anticipated the project will remain agnostic of a number of
> complementary technologies and projects. It is the expectation that
> Aries will therefore not be delivering components such as: an
> application or integration server runtime kernel; a persistence
> provider; distribution provider; a deployment provider or a Web
> container. Aries will instead seek to enable the use of such
> components from other projects.
> Background
> 
> OSGi is a mature and Java modularity technology that is well-used in
> many environments but, in the enterprise space, has more typically
> been exploited by the internals of the runtime infrastructure than the
> applications that run on it. This is primarily because of a lack of a
> clear enterprise OSGi application programming model and implementation
> of OSGi-enabled Java technology to support enterprise applications.
> OSGi specifications are specified and maintained by the OSGi Alliance
> which recognized this state of affairs several years ago and
> established the Enterprise Expert Group within the Alliance to focus
> specifically on the needs of enterprise applications. The objective of
> this project is to deliver open source implementations of these
> application-centric technologies to enable the development of
> application components, benefiting from the modularity of OSGi
> combined with standards-based programming models, which can be
> deployed to a variety of target runtimes.
> Rationale
> 
> Aries aims to build a community of developers interested in the
> delivery of software components that support an enterprise OSGi
> programming model and which can be integrated into a number of
> different runtime environments. Apache hosts the Felix project which
> provides an OSGi framework implementation and a variety of projects
> which provide technologies exploited by enterprise application
> components as well as projects which provide runtimes to host
> application components. There is currently no Apache project focussed
> on OSGi enterprise applications that is independent from both the OSGi
> framework and the enterprise runtime environment in which application
> components are hosted. By maintaining independence of both the target
> runtime and underlying OSGi framework it is our intention to build the
> broadest possible community of developers for Aries, and to maximize
> the potential environments where Aries componentry can be used.
> Initial Goals
> 
> We will initially focus on the Blueprint container and extend this
> with enterprise features such as support for container managed JPA and
> container managed transactions. Another initial focus area will be the
> contribution of code to support the assembly of isolated, multi-bundle
> applications that can be deployed as a unit.
> Current Status
> Meritocracy
> 
> The Aries contributors recognize the desirability of running the
> project as a meritocracy. We are eager to engage other members of the
> community and operate to the standard of meritocracy that Apache
> emphasizes; we believe this is the most effective method of growing
> our community and enabling widespread adoption.
> Community
> 
> OSGi is a mature Java modularity technology that is well-used in many
> environments but, in the enterprise space, has more typically been
> exploited by the internals of the runtime infrastructure than the
> applications that run on it. This is primarily because of a lack of a
> clear enterprise OSGi application programming model and implementation
> of OSGi-enabled Java technology to support enterprise applications.
> There is a need for open source implementations of these technologies
> and there is currently no Apache project focused on the wider goal of
> delivering components for an enterprise OSGi application programming
> model. Aries aims to build a community of developers interested in the
> definition and delivery of software components that support an
> enterprise OSGi programming model and which can be integrated into a
> number of different runtime environments. By maintaining independence
> of both the target runtime and underlying OSGi framework it is our
> intention to build the broadest possible community of developers.
> Alignment
> 
> The purpose of Aries is to develop implementations of
> application-centric enterprise OSGi technologies that run on an OSGi
> framework, but not a specific one, and are used by application
> components deployed into a variety of runtime environments without
> being tied to any specific environment. For this reason we believe
> Aries is a project whose community would be best served if it could
> leverage but be independent from the communities that provide
> underlying OSGi framework technology and enterprise application server
> and integration bus technologies, all of which exist as open source
> efforts within Apache and elsewhere. We expect, for example, that some
> code developed in Aries will run directly on top of an OSGi framework
> such as Felix and that applications exploiting Aries technologies
> could be deployed to runtimes such as ServiceMix and Geronimo.
> Avoiding the Warning Signs
> Orphaned products
> 
> The contributors are leading vendors of OSGi-based technologies and
> have a long standing in the OSGi Alliance whose application-centric
> specifications this project will implement. There is minimal risk of
> this work becoming non-strategic and the contributors are confident
> that a larger community will form within the project in a relatively
> short space of time.
> Inexperience with Open Source
> 
> Many of the committers have experience working in one or more open
> source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
> and CXF.
> 
> Homogeneous Developers
> 
> The list of initial committers, geographically distributed across the
> U.S. and Europe, consists of developers from two companies - IBM and
> Progress software - with similar goals but for different scenarios.
> Many of these developers are experienced Apache committers already and
> all are experienced with working in distributed development
> communities. It is our hope that, through the incubator, further
> contributors with a broad background of experience but common interest
> in enterprise OSGi technologies will become involved with this
> project.
> 
> Relationships with Other Apache Projects
> 
> Aries will have a potential relationship with the Apache projects
> listed in this section. These projects all serve different purposes
> from Aries and have their own communities. It is hoped that each of
> these communities will become involved with Aries and help to build a
> diverse but independent Aries community.
> 
> Apache Felix Karaf -
> http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
> Karaf is an OSGi based runtime which provides a lightweight container
> onto which various components and applications can be deployed. It is
> related to Aries:
> 
>   1. as a target OSGi based runtime to which Aries applications can
> be deployed. In this role, Karaf is a consumer of Aries technology.
> 
> Apache Felix - http://felix.apache.org/site/index.html Apache
> Felix is primarily a core OSGi framework implementation. It is related
> to Aries:
> 
>   1. as an underlying OSGi framework implementation and potentially
> other extensions that can be used both by Aries run-time components
> and the applications which use them.
> 
> Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
> a server runtime framework and fully certified Java EE 5 application
> server runtime. It is related to Aries in two ways:
> 
>   1. as a target runtime to which Aries applications can be deployed.
> In this role, Geronimo is a consumer of Aries technology.
>   2. the Geronimo blueprint sandbox -
> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
> an implementation of the OSGi Blueprint container which will be moved
> to Aries.
> 
> Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
> provides a comprehensive infrastructure for SOA development and
> management that is based on Service Component Architecture (SCA)
> standard. It can be a consumer of Aries technology to provide an Aries
> SCA implementation type for composing Aries applications in coarse
> grained and potentially heterogeneous service assemblies.
> 
> Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
> Web Services framework for distributed computing and remote service
> realization and invocation using API's such as JAX-WS and JAX-RS. It
> also provides the OSGi Remote Services (OSGi RFC 119) reference
> implementation in a subproject:
> http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
> the following way:
> 
>   1. As Remote Services is a significant Enterprise specification
> being produced by the EEG, it is expected that consumers of Aries will
> be looking for an implementation of this specification. CXF provides
> an implementation of this specification which already has a
> significant active community. The Aries project will make it easy for
> Aries consumers to consume the CXF Remote Services implementation,
> possibly by providing an instance of the application model that
> references the CXF Remote Services implementation. This would mean
> that end users will seamlessly pull in the required components from
> CXF by using the Aries-provided definition.
> 
> Apache ServiceMix - http://servicemix.apache.org/ Apache
> ServiceMix provides an ESB that combines the functionality of a
> Service Oriented Architecture (SOA) and Event Driven Architecture
> (EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
> source of the Apache Felix Karaf runtime. It can be a consumer of
> Aries applications and associated componentry as a natural evolution
> of its existing Karaf "feature" usage.
> 
> Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
> Java persistence project. It is related to Aries as a JPA persistence
> provider, including entity scanning and enhancement. The Aries project
> will make it easy for JPA persistence providers such as OpenJPA to be
> used in an OSGi environment and will provide container managed
> persistence for the Blueprint container.
> 
> Documentation
> 
> An early draft of OSGi v4.2 core and compendium specifications - which
> includes the Blueprint container specification - is available at:
> http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
> Initial Source
> 
>    * The Blueprint container impl from the Geronimo sandbox will be
> moved to the Aries project for further development:
> http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
>    * IBM will also contribute code for:
>          o container-managed JPA support in an OSGi environment.
>          o making OSGi services visible to Java EE components through JNDI.
>          o packaging web components as bundles and a URL handler for
> recognizing and converting non-bundled Web components
>    * We will also be soliciting implementations of other OSGi
> enterprise application-centric specifications.
> 
> External Dependencies
> 
>    * Apache Ant http://ant.apache.org Apache License
>    * Apache Commons http://commons.apache.org Apache License
>    * Junit (Java unit test framework) http://junit.sourceforge.net CPL
> v1.0 license: http://junit.sourceforge.net/cpl-v10.html
>    * Apache Felix (implementation of the OSGi Core and Compendium
> specifications - compliance level unknown) http://felix.apache.org
> Apache License (hosted by ASF).
>    * Eclipse Equinox (compliant implementation of the OSGi Core
> Specification and Compendium specifications)
> http://eclipse.org/equinox/ Eclipse Public License
>    * OpenJPA http://openjpa.apache.org Apache License
>    * Serp http://serp.sourceforge.net/ BSD
>    * Apache Geronimo http://geronimo.apache.org Apache License
> 
> Required Resources
> Mailing lists
> 
> aries-private (with moderated subscriptions)
> aries-dev
> aries-commits
> aries-user
> 
> Subversion Directory
> 
> http://svn.apache.org/repos/asf/incubator/aries
> 
> Issue Tracking
> 
> JIRA (ARIES)
> 
> Web Site
> 
> Confluence (Aries)
> 
> Initial Committers
> 
> Names of initial committers with affiliation and current ASF status:
> 
>    * Alasdair Nottingham (IBM)
>    * Andrew Osborne (IBM)
>    * Dan Kulp (Progress, ASF member)
>    * David Bosschaert (Progress, ASF committer)
>    * David Jencks (IBM, ASF member)
>    * Eoghan Glynn (Progress, ASF committer)
>    * Graham Charters (IBM)
>    * Guillaume Nodet (Progress, ASF member)
>    * Hiram Chirino (Progress, ASF member)
>    * Ian Robinson (IBM)
>    * James Strachan (Progress, ASF member)
>    * Jarek Gawor (IBM, ASF member)
>    * Jeremy Hughes (IBM, ASF committer)
>    * Joe Bohn (IBM, ASF committer)
>    * Lin Sun (IBM, ASF committer)
>    * Mark Nuttall (IBM)
>    * Oisin Hurley (Progress)
>    * Rick McGuire (IBM, ASF committer)
>    * Sergey Beryozkin (Progress, ASF committer),
>    * Timothy Ward (IBM)
>    * Valentin Mahrwald (IBM)
>    * Zoe Slattery (IBM)
> 
> Affiliations
> 
> The majority of the initial committers are employed by IBM corp or
> Progress Software. One objective of the incubator is to attract a
> diverse community of contributors and we anticipate future
> contributors to have other affiliations.
> 
> Sponsors
> Champions
> 
> Kevan Miller, Guillaume Nodet
> 
> Nominated Mentors
> 
> Guillaume Nodet, Davanum Srinivas (Dims)
> 
> Sponsoring Entity
> 
> The incubator. Successful graduation from Incubator should result in
> Aries becoming a new TLP.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Kevan Miller <ke...@gmail.com>.
On Sep 2, 2009, at 5:01 AM, Leo Simons wrote:

> On Tue, Sep 1, 2009 at 3:38 PM, Jeremy Hughes<hu...@apache.org>  
> wrote:
>> We appreciate any feedback and comments on the proposal.
>
> * Any chance of one or two of the other ASF members involved also
> stepping up as a mentor?

That would be very good. I left my name of the mentor list, hoping to  
encourage additional mentors...

>
> * Projects that consist of groups of components often have some
> problems maintaining sufficient cohesion as a community. I hope you
> guys will give that the specific attention it probably requires and
> tune the project charter appropriately.

I think there is more cohesion than simply an aggregation of  
components. Should be able to make this more obvious in the proposal.

>
> * I have no problems with having multiple OSGi projects at apache as
> long as they're all healthy communities and they play nice with each
> other.
>
> (...)
>
> Of course the "play nice" part is interesting here -- I'm frowning a
> bit at seeing this how-to-interact-with-felix discussion kick off with
> a pretty much finished proposal going to the incubator. Surely the
> conversation can go a bit differently? For example maybe you could've
> approached felix first and discussed seeding the project with some of
> the parts-of-felix (along with developers) that are argued to need an
> independent-from-felix re-brand? Maybe you can take a step back
> together even now and see if something like that might make sense? Or,
> maybe you can co-operate on a shared registry / website of the OSGi
> components in all the different projects so that people visiting
> apache.org are not confused? Or something like that?
>
> I hope you guys find a way to reduce the friction and co-operate;
> having what looks like battle lines being drawn up at the start of
> incubation is _not_ a good thing.

The only friction that I've seen is whether or not this work should be  
under/destined for a Felix umbrella. I'm not aware of any existing  
technical overlap, nor anything that would prevent extensive sharing/ 
cooperation (even if we end up with 2 TLPs)...

>
> I do expect to see that felix/aria conversation resolved clearly one
> way or another before the proposal goes up for a vote. Even if the
> resolution is "there will significant charter overlap and duplication
> of effort and code and probably little committer overlap between the
> communities because we disagree on how to do things" then I'd like to
> see that clearly spelled out.

Agreed.

--kevan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Donald Woods <dw...@apache.org>.
Since there have been several edits, can you repost the latest proposal?

Also, I'm looking forward to contribute and to help integrate any 
changes needed to support OpenJPA for RFC 143.


Thanks,
Donald


Jeremy Hughes wrote:
> 2009/9/2 Leo Simons <ma...@leosimons.com>:
>> On Tue, Sep 1, 2009 at 3:38 PM, Jeremy Hughes<hu...@apache.org> wrote:
>>> We appreciate any feedback and comments on the proposal.
> ...
>> * Projects that consist of groups of components often have some
>> problems maintaining sufficient cohesion as a community. I hope you
>> guys will give that the specific attention it probably requires and
>> tune the project charter appropriately.
> 
> I've modified the Community section of the proposal adding the section
> between *** this:
> 
> OSGi is a mature Java modularity technology that is well-used in many
> environments but, in the enterprise space, has more typically been
> exploited by the internals of the runtime infrastructure than the
> applications that run on it. This is primarily because of a lack of a
> clear enterprise OSGi application programming model and implementation
> of OSGi-enabled Java technology to support enterprise applications.
> There is a need for open source implementations of these technologies
> and there is currently no Apache project focused on the wider goal of
> delivering components for an enterprise OSGi application programming
> model. *** We recognise that projects comprising multiple components
> face challenges maintaining cohesion as a community but believe the
> common focus on the enterprise OSGi programming model is a strong
> theme that will guide the activities of the community as a whole. ***
> Aries aims to build a community of developers interested in the
> definition and delivery of software components that support an
> enterprise OSGi programming model and which can be integrated into a
> number of different runtime environments. By maintaining independence
> of both the target runtime and underlying OSGi framework it is our
> intention to build the broadest possible community of developers.
> 
> I hope this shows that this is on our radar.
> 
> Thanks,
> Jeremy
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
2009/9/2 Leo Simons <ma...@leosimons.com>:
> On Tue, Sep 1, 2009 at 3:38 PM, Jeremy Hughes<hu...@apache.org> wrote:
>> We appreciate any feedback and comments on the proposal.
...
>
> * Projects that consist of groups of components often have some
> problems maintaining sufficient cohesion as a community. I hope you
> guys will give that the specific attention it probably requires and
> tune the project charter appropriately.

I've modified the Community section of the proposal adding the section
between *** this:

OSGi is a mature Java modularity technology that is well-used in many
environments but, in the enterprise space, has more typically been
exploited by the internals of the runtime infrastructure than the
applications that run on it. This is primarily because of a lack of a
clear enterprise OSGi application programming model and implementation
of OSGi-enabled Java technology to support enterprise applications.
There is a need for open source implementations of these technologies
and there is currently no Apache project focused on the wider goal of
delivering components for an enterprise OSGi application programming
model. *** We recognise that projects comprising multiple components
face challenges maintaining cohesion as a community but believe the
common focus on the enterprise OSGi programming model is a strong
theme that will guide the activities of the community as a whole. ***
Aries aims to build a community of developers interested in the
definition and delivery of software components that support an
enterprise OSGi programming model and which can be integrated into a
number of different runtime environments. By maintaining independence
of both the target runtime and underlying OSGi framework it is our
intention to build the broadest possible community of developers.

I hope this shows that this is on our radar.

Thanks,
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Graham Charters <gc...@googlemail.com>.
I think it's important that Aries have its own identity independent
from a particular framework implementation (e.g. Felix or Equinox) or
Kernel (e.g. Karaf, Geronimo, etc.). Independence (both technical and
perception) will help make it equally consumable in each and increase
the likelihood of it being deployed in more environments.

I also believe Aries will attract a community which is sustainable and
different from those other projects.  Given the goal to have Aries
components work on and/or be consumed by those projects I would hope
that the Aries community would share members with Felix, Geronimo,
ServiceMix, etc..  This outcome would be highly desirable.  My hope is
that incubation will prove that Aries is indeed a sustainable
independent project and if that is found not to be the case, then that
is also a valid outcome.

Regards, Graham.

2009/9/3 Niclas Hedhman <ni...@hedhman.org>:
> On Thu, Sep 3, 2009 at 3:19 AM, William A. Rowe, Jr.<wr...@rowe-clan.net> wrote:
>
>> If Felix is looking at this as an opportunity, to attract more OSGi
>> activity at the foundation, expand its base of contributors (at least
>> to common underlying components) and demonstrate that the ASF encourages
>> creation of the best-of-breed solutions, I'd hope to see some Felix PMC
>> members step up to help mentor this effort and identify places where
>> the best choice between common code is a win for all efforts.
>
> +100, and IMHO not only as Mentors... I would be surprised (and very
> concerned) if the Aries folks wouldn't love to have a few Felix
> committers joining in.
> After all, it is easier to influence and discuss if you are on the
> same side of a fence...
>
>
> Cheers
> --
> Niclas Hedhman, Software Developer
> http://www.qi4j.org - New Energy for Java
>
> I  live here; http://tinyurl.com/2qq9er
> I  work here; http://tinyurl.com/2ymelc
> I relax here; http://tinyurl.com/2cgsug
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Karl Pauls <ka...@gmail.com>.
On Fri, Sep 4, 2009 at 3:53 PM, Daniel Kulp<dk...@apache.org> wrote:
> On Fri September 4 2009 9:27:23 am Graham Charters wrote:
>> Having read all the discussions, I still have concerns about the
>> suggestion to put all OSGi spec implementation under Felix.  I don't
>> see this approach being taken for other specification organizations
>> (JCP, OASIS, etc.) and I think that is to the benefit of Apache.  For
>> example, whilst a goal of Geronimo is JEE compliance it does not host
>> all the implementations of the JEE specifications.  Having OpenEJB,
>> OpenJPA, Tomcat, etc as separate projects allows them to evolve
>> independent communities, with cross-pollination.  The domains,
>> technologies and skills required to cover the entirety of JEE are
>> diverse and the same is true for OSGi.  To put these under one project
>> would lead to sub-groups of different interests under one disjoint
>> umbrella community.
>
> +1
>
> Geronimo is a perfect example.   Couldn't have said it better myself.   The
> community of the "experts" in the technology area should be the ones
> implementing those specs as part of their community.

Um, for me it is a perfect example for the opposite :-)

Geronimo is using the artifacts of other communities to create
something that is bigger than the sum of its parts. The parts in turn
are developed not within geronimo but (as you say yourself) by the
respective communities that are the "experts". For me this is a
perfect example of what we propose in this discussion. Let us develop
(and build the "expert" community around) the OSGi EE spec related
components at Felix and let Aries be the project that makes use of
them to create something that is bigger than the sum of its parts
namely, to explore how to build an enterprise component model on OSGi
and the other non-spec related topics.

regards,

Karl

> Dan
>>
>> I also worry about the practicalities of saying that all OSGi spec
>> implementations belong in Felix.  This is a moving target, both within
>> each specification, where extensions may be created and then
>> standardized and also at the spec level, where new concepts are
>> created and then standardized.  Must these then move under the Felix
>> umbrella, which will undoubtedly create a lot of churn for users of,
>> and contributors to, Aries?
>>
>> Thinking about the problem the way JEE is handled makes me wonder if
>> Felix could pull in spec implementations from Aries (and have
>> committers on Aries) and therefore still contribute to and provide the
>> distribution of the entire OSGi Service Platform.  Maybe this could be
>> done through Felix hosting a bundle repository (Felix commons?)?
>> Consumers of Felix would be able to get the OSGi Service Platform and
>> consumers of Aries would get the enterprise OSGi application portions.
>>
>> I'd like to emphasize that the desire to be separate from Felix is in
>> no way a criticism of that project.  I have a huge amount of respect
>> for what Richard et al continue to achieve and having experienced
>> first-hand the value the combination of Felix and Equinox bring to the
>> OSGi standards, I sincerely believe that OSGi is far stronger as a
>> result.
>>
>> The desire to remain separate is based purely on the belief that this
>> is the approach which will best serve the goals of evolving an
>> enterprise OSGi application programming model, and a community around
>> its definition.  This rationale is also the reason why Geronimo was
>> not suggested (an equally valid choice given the majority of the
>> Enterprise OSGi specifications leverage JEE technologies).  I guess
>> what I don't understand is why the Incubator would not prove or
>> disprove this belief, without making a prior decision?
>>
>> Regards, Graham.
>>
>> 2009/9/4 Daniel Kulp <dk...@apache.org>:
>> > As a point of note, not all OSGi spec implementations live in Felix even
>> > at Apache today.   The Remote Services/Distributed OSGi reference
>> > implementation is a sub project of CXF.     I think Tuscany has an
>> > implementation as well.
>> >
>> > So far, there hasn't been any discussion about moving those into Felix.
>> >  Your argument below makes it sound like they should be.
>> >
>> > Dan
>> >
>> > On Thu September 3 2009 1:33:04 pm Richard S. Hall wrote:
>> >> There was no attempt to contact the Felix PMC in general that I am aware
>> >> and I certainly didn't know about it in advance.
>> >>
>> >> And there seems to be a continued attempt to construe my original
>> >> criticisms as "all of Aries should go into Felix".
>> >>
>> >> I, personally, do not believe that all of Aries should go into Felix, I
>> >> too think it should have its own identity. I was always only ever
>> >> referring to the independent OSGi spec implementations. I was arguing
>> >> that Felix is a good place to work on them, since it is part of what it
>> >> is trying to achieve.
>> >>
>> >> Further, I don't really understand the implication that somehow the
>> >> burden is now on the Felix community to go and contribute to Aries on
>> >> OSGi spec implementations just because of this proposal, when there was
>> >> no attempt to work with the Felix community on creating OSGi spec
>> >> implementations in the first.
>> >>
>> >> The only conclusions I see being drawn by people who have invested very
>> >> little in Felix is that we should dismantle the Felix charter so that we
>> >> can accommodate the fact that some people don't want to play with us.
>> >>
>> >> At that rate, I stand by my previous "vote" and otherwise people can do
>> >> whatever they want in Aries.
>> >>
>> >> -> richard
>> >>
>> >> On 9/3/09 13:23, Niclas Hedhman wrote:
>> >> > Kevan,
>> >> >
>> >> > Was a contact with Felix made prior to dropping the proposal here? I
>> >> > got the impression that wasn't the case, which I find surprising... If
>> >> > I am wrong, what was the meat of such?
>> >> >
>> >> > I'm also less happy with the rhetoric here repeated over and over,
>> >> > seemingly uninterested in discussion of reaching a solution everyone
>> >> > can accept. (From both camps, btw)
>> >> >
>> >> > -- Niclas
>> >> >
>> >> > On Sep 4, 2009 12:53 AM, "Kevan Miller"<ke...@gmail.com>
>> >> >  wrote:
>> >> >
>> >> > On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:>  On Thu, Sep 3,
>> >> > 2009 at 3:19 AM, William A. Ro...
>> >> > Totally agree. Had certainly hoped that Felix committers would be
>> >> > interested in joining...
>> >> >
>> >> > --kevan
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: gene...
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> For additional commands, e-mail: general-help@incubator.apache.org
>> >
>> > --
>> > Daniel Kulp
>> > dkulp@apache.org
>> > http://www.dankulp.com/blog
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>



-- 
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me as well. Just to reiterate one more point, As with any
other podling, the destination of this podling is determined *when* we
graduate. If there is enough "help/guidance/participation" from folks
on dev@felix to the podling, then the podling will naturally gravitate
towards becoming a subproject of felix.

thanks,
dims

On Fri, Sep 4, 2009 at 9:53 AM, Daniel Kulp<dk...@apache.org> wrote:
> On Fri September 4 2009 9:27:23 am Graham Charters wrote:
>> Having read all the discussions, I still have concerns about the
>> suggestion to put all OSGi spec implementation under Felix.  I don't
>> see this approach being taken for other specification organizations
>> (JCP, OASIS, etc.) and I think that is to the benefit of Apache.  For
>> example, whilst a goal of Geronimo is JEE compliance it does not host
>> all the implementations of the JEE specifications.  Having OpenEJB,
>> OpenJPA, Tomcat, etc as separate projects allows them to evolve
>> independent communities, with cross-pollination.  The domains,
>> technologies and skills required to cover the entirety of JEE are
>> diverse and the same is true for OSGi.  To put these under one project
>> would lead to sub-groups of different interests under one disjoint
>> umbrella community.
>
> +1
>
> Geronimo is a perfect example.   Couldn't have said it better myself.   The
> community of the "experts" in the technology area should be the ones
> implementing those specs as part of their community.
>
> Dan
>
>
>
>>
>> I also worry about the practicalities of saying that all OSGi spec
>> implementations belong in Felix.  This is a moving target, both within
>> each specification, where extensions may be created and then
>> standardized and also at the spec level, where new concepts are
>> created and then standardized.  Must these then move under the Felix
>> umbrella, which will undoubtedly create a lot of churn for users of,
>> and contributors to, Aries?
>>
>> Thinking about the problem the way JEE is handled makes me wonder if
>> Felix could pull in spec implementations from Aries (and have
>> committers on Aries) and therefore still contribute to and provide the
>> distribution of the entire OSGi Service Platform.  Maybe this could be
>> done through Felix hosting a bundle repository (Felix commons?)?
>> Consumers of Felix would be able to get the OSGi Service Platform and
>> consumers of Aries would get the enterprise OSGi application portions.
>>
>> I'd like to emphasize that the desire to be separate from Felix is in
>> no way a criticism of that project.  I have a huge amount of respect
>> for what Richard et al continue to achieve and having experienced
>> first-hand the value the combination of Felix and Equinox bring to the
>> OSGi standards, I sincerely believe that OSGi is far stronger as a
>> result.
>>
>> The desire to remain separate is based purely on the belief that this
>> is the approach which will best serve the goals of evolving an
>> enterprise OSGi application programming model, and a community around
>> its definition.  This rationale is also the reason why Geronimo was
>> not suggested (an equally valid choice given the majority of the
>> Enterprise OSGi specifications leverage JEE technologies).  I guess
>> what I don't understand is why the Incubator would not prove or
>> disprove this belief, without making a prior decision?
>>
>> Regards, Graham.
>>
>> 2009/9/4 Daniel Kulp <dk...@apache.org>:
>> > As a point of note, not all OSGi spec implementations live in Felix even
>> > at Apache today.   The Remote Services/Distributed OSGi reference
>> > implementation is a sub project of CXF.     I think Tuscany has an
>> > implementation as well.
>> >
>> > So far, there hasn't been any discussion about moving those into Felix.
>> >  Your argument below makes it sound like they should be.
>> >
>> > Dan
>> >
>> > On Thu September 3 2009 1:33:04 pm Richard S. Hall wrote:
>> >> There was no attempt to contact the Felix PMC in general that I am aware
>> >> and I certainly didn't know about it in advance.
>> >>
>> >> And there seems to be a continued attempt to construe my original
>> >> criticisms as "all of Aries should go into Felix".
>> >>
>> >> I, personally, do not believe that all of Aries should go into Felix, I
>> >> too think it should have its own identity. I was always only ever
>> >> referring to the independent OSGi spec implementations. I was arguing
>> >> that Felix is a good place to work on them, since it is part of what it
>> >> is trying to achieve.
>> >>
>> >> Further, I don't really understand the implication that somehow the
>> >> burden is now on the Felix community to go and contribute to Aries on
>> >> OSGi spec implementations just because of this proposal, when there was
>> >> no attempt to work with the Felix community on creating OSGi spec
>> >> implementations in the first.
>> >>
>> >> The only conclusions I see being drawn by people who have invested very
>> >> little in Felix is that we should dismantle the Felix charter so that we
>> >> can accommodate the fact that some people don't want to play with us.
>> >>
>> >> At that rate, I stand by my previous "vote" and otherwise people can do
>> >> whatever they want in Aries.
>> >>
>> >> -> richard
>> >>
>> >> On 9/3/09 13:23, Niclas Hedhman wrote:
>> >> > Kevan,
>> >> >
>> >> > Was a contact with Felix made prior to dropping the proposal here? I
>> >> > got the impression that wasn't the case, which I find surprising... If
>> >> > I am wrong, what was the meat of such?
>> >> >
>> >> > I'm also less happy with the rhetoric here repeated over and over,
>> >> > seemingly uninterested in discussion of reaching a solution everyone
>> >> > can accept. (From both camps, btw)
>> >> >
>> >> > -- Niclas
>> >> >
>> >> > On Sep 4, 2009 12:53 AM, "Kevan Miller"<ke...@gmail.com>
>> >> >  wrote:
>> >> >
>> >> > On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:>  On Thu, Sep 3,
>> >> > 2009 at 3:19 AM, William A. Ro...
>> >> > Totally agree. Had certainly hoped that Felix committers would be
>> >> > interested in joining...
>> >> >
>> >> > --kevan
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: gene...
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >> For additional commands, e-mail: general-help@incubator.apache.org
>> >
>> > --
>> > Daniel Kulp
>> > dkulp@apache.org
>> > http://www.dankulp.com/blog
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>



-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Daniel Kulp <dk...@apache.org>.
On Fri September 4 2009 9:27:23 am Graham Charters wrote:
> Having read all the discussions, I still have concerns about the
> suggestion to put all OSGi spec implementation under Felix.  I don't
> see this approach being taken for other specification organizations
> (JCP, OASIS, etc.) and I think that is to the benefit of Apache.  For
> example, whilst a goal of Geronimo is JEE compliance it does not host
> all the implementations of the JEE specifications.  Having OpenEJB,
> OpenJPA, Tomcat, etc as separate projects allows them to evolve
> independent communities, with cross-pollination.  The domains,
> technologies and skills required to cover the entirety of JEE are
> diverse and the same is true for OSGi.  To put these under one project
> would lead to sub-groups of different interests under one disjoint
> umbrella community.

+1 

Geronimo is a perfect example.   Couldn't have said it better myself.   The 
community of the "experts" in the technology area should be the ones 
implementing those specs as part of their community.

Dan



> 
> I also worry about the practicalities of saying that all OSGi spec
> implementations belong in Felix.  This is a moving target, both within
> each specification, where extensions may be created and then
> standardized and also at the spec level, where new concepts are
> created and then standardized.  Must these then move under the Felix
> umbrella, which will undoubtedly create a lot of churn for users of,
> and contributors to, Aries?
> 
> Thinking about the problem the way JEE is handled makes me wonder if
> Felix could pull in spec implementations from Aries (and have
> committers on Aries) and therefore still contribute to and provide the
> distribution of the entire OSGi Service Platform.  Maybe this could be
> done through Felix hosting a bundle repository (Felix commons?)?
> Consumers of Felix would be able to get the OSGi Service Platform and
> consumers of Aries would get the enterprise OSGi application portions.
> 
> I'd like to emphasize that the desire to be separate from Felix is in
> no way a criticism of that project.  I have a huge amount of respect
> for what Richard et al continue to achieve and having experienced
> first-hand the value the combination of Felix and Equinox bring to the
> OSGi standards, I sincerely believe that OSGi is far stronger as a
> result.
> 
> The desire to remain separate is based purely on the belief that this
> is the approach which will best serve the goals of evolving an
> enterprise OSGi application programming model, and a community around
> its definition.  This rationale is also the reason why Geronimo was
> not suggested (an equally valid choice given the majority of the
> Enterprise OSGi specifications leverage JEE technologies).  I guess
> what I don't understand is why the Incubator would not prove or
> disprove this belief, without making a prior decision?
> 
> Regards, Graham.
> 
> 2009/9/4 Daniel Kulp <dk...@apache.org>:
> > As a point of note, not all OSGi spec implementations live in Felix even
> > at Apache today.   The Remote Services/Distributed OSGi reference
> > implementation is a sub project of CXF.     I think Tuscany has an
> > implementation as well.
> >
> > So far, there hasn't been any discussion about moving those into Felix.
> >  Your argument below makes it sound like they should be.
> >
> > Dan
> >
> > On Thu September 3 2009 1:33:04 pm Richard S. Hall wrote:
> >> There was no attempt to contact the Felix PMC in general that I am aware
> >> and I certainly didn't know about it in advance.
> >>
> >> And there seems to be a continued attempt to construe my original
> >> criticisms as "all of Aries should go into Felix".
> >>
> >> I, personally, do not believe that all of Aries should go into Felix, I
> >> too think it should have its own identity. I was always only ever
> >> referring to the independent OSGi spec implementations. I was arguing
> >> that Felix is a good place to work on them, since it is part of what it
> >> is trying to achieve.
> >>
> >> Further, I don't really understand the implication that somehow the
> >> burden is now on the Felix community to go and contribute to Aries on
> >> OSGi spec implementations just because of this proposal, when there was
> >> no attempt to work with the Felix community on creating OSGi spec
> >> implementations in the first.
> >>
> >> The only conclusions I see being drawn by people who have invested very
> >> little in Felix is that we should dismantle the Felix charter so that we
> >> can accommodate the fact that some people don't want to play with us.
> >>
> >> At that rate, I stand by my previous "vote" and otherwise people can do
> >> whatever they want in Aries.
> >>
> >> -> richard
> >>
> >> On 9/3/09 13:23, Niclas Hedhman wrote:
> >> > Kevan,
> >> >
> >> > Was a contact with Felix made prior to dropping the proposal here? I
> >> > got the impression that wasn't the case, which I find surprising... If
> >> > I am wrong, what was the meat of such?
> >> >
> >> > I'm also less happy with the rhetoric here repeated over and over,
> >> > seemingly uninterested in discussion of reaching a solution everyone
> >> > can accept. (From both camps, btw)
> >> >
> >> > -- Niclas
> >> >
> >> > On Sep 4, 2009 12:53 AM, "Kevan Miller"<ke...@gmail.com>
> >> >  wrote:
> >> >
> >> > On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:>  On Thu, Sep 3,
> >> > 2009 at 3:19 AM, William A. Ro...
> >> > Totally agree. Had certainly hoped that Felix committers would be
> >> > interested in joining...
> >> >
> >> > --kevan
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: gene...
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >
> > --
> > Daniel Kulp
> > dkulp@apache.org
> > http://www.dankulp.com/blog
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Graham Charters <gc...@googlemail.com>.
Having read all the discussions, I still have concerns about the
suggestion to put all OSGi spec implementation under Felix.  I don't
see this approach being taken for other specification organizations
(JCP, OASIS, etc.) and I think that is to the benefit of Apache.  For
example, whilst a goal of Geronimo is JEE compliance it does not host
all the implementations of the JEE specifications.  Having OpenEJB,
OpenJPA, Tomcat, etc as separate projects allows them to evolve
independent communities, with cross-pollination.  The domains,
technologies and skills required to cover the entirety of JEE are
diverse and the same is true for OSGi.  To put these under one project
would lead to sub-groups of different interests under one disjoint
umbrella community.

I also worry about the practicalities of saying that all OSGi spec
implementations belong in Felix.  This is a moving target, both within
each specification, where extensions may be created and then
standardized and also at the spec level, where new concepts are
created and then standardized.  Must these then move under the Felix
umbrella, which will undoubtedly create a lot of churn for users of,
and contributors to, Aries?

Thinking about the problem the way JEE is handled makes me wonder if
Felix could pull in spec implementations from Aries (and have
committers on Aries) and therefore still contribute to and provide the
distribution of the entire OSGi Service Platform.  Maybe this could be
done through Felix hosting a bundle repository (Felix commons?)?
Consumers of Felix would be able to get the OSGi Service Platform and
consumers of Aries would get the enterprise OSGi application portions.

I'd like to emphasize that the desire to be separate from Felix is in
no way a criticism of that project.  I have a huge amount of respect
for what Richard et al continue to achieve and having experienced
first-hand the value the combination of Felix and Equinox bring to the
OSGi standards, I sincerely believe that OSGi is far stronger as a
result.

The desire to remain separate is based purely on the belief that this
is the approach which will best serve the goals of evolving an
enterprise OSGi application programming model, and a community around
its definition.  This rationale is also the reason why Geronimo was
not suggested (an equally valid choice given the majority of the
Enterprise OSGi specifications leverage JEE technologies).  I guess
what I don't understand is why the Incubator would not prove or
disprove this belief, without making a prior decision?

Regards, Graham.

2009/9/4 Daniel Kulp <dk...@apache.org>:
>
> As a point of note, not all OSGi spec implementations live in Felix even at
> Apache today.   The Remote Services/Distributed OSGi reference implementation
> is a sub project of CXF.     I think Tuscany has an implementation as well.
>
> So far, there hasn't been any discussion about moving those into Felix.  Your
> argument below makes it sound like they should be.
>
> Dan
>
>
> On Thu September 3 2009 1:33:04 pm Richard S. Hall wrote:
>> There was no attempt to contact the Felix PMC in general that I am aware
>> and I certainly didn't know about it in advance.
>>
>> And there seems to be a continued attempt to construe my original
>> criticisms as "all of Aries should go into Felix".
>>
>> I, personally, do not believe that all of Aries should go into Felix, I
>> too think it should have its own identity. I was always only ever
>> referring to the independent OSGi spec implementations. I was arguing
>> that Felix is a good place to work on them, since it is part of what it
>> is trying to achieve.
>>
>> Further, I don't really understand the implication that somehow the
>> burden is now on the Felix community to go and contribute to Aries on
>> OSGi spec implementations just because of this proposal, when there was
>> no attempt to work with the Felix community on creating OSGi spec
>> implementations in the first.
>>
>> The only conclusions I see being drawn by people who have invested very
>> little in Felix is that we should dismantle the Felix charter so that we
>> can accommodate the fact that some people don't want to play with us.
>>
>> At that rate, I stand by my previous "vote" and otherwise people can do
>> whatever they want in Aries.
>>
>> -> richard
>>
>> On 9/3/09 13:23, Niclas Hedhman wrote:
>> > Kevan,
>> >
>> > Was a contact with Felix made prior to dropping the proposal here? I got
>> > the impression that wasn't the case, which I find surprising... If I am
>> > wrong, what was the meat of such?
>> >
>> > I'm also less happy with the rhetoric here repeated over and over,
>> > seemingly uninterested in discussion of reaching a solution everyone can
>> > accept. (From both camps, btw)
>> >
>> > -- Niclas
>> >
>> > On Sep 4, 2009 12:53 AM, "Kevan Miller"<ke...@gmail.com>  wrote:
>> >
>> > On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:>  On Thu, Sep 3, 2009
>> > at 3:19 AM, William A. Ro...
>> > Totally agree. Had certainly hoped that Felix committers would be
>> > interested in joining...
>> >
>> > --kevan
>> >
>> > --------------------------------------------------------------------- To
>> > unsubscribe, e-mail: gene...
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Stuart,

Thanks a ton. Please do join the aries mailing list(s) after we VOTE on (and hopefully accept) the proposal. All the 
action will shift there from this mailing list.

thanks,
dims

On 09/05/2009 11:08 PM, Stuart McCulloch wrote:
> 2009/9/5 Davanum Srinivas<da...@gmail.com>
>
>> One more question, Will there be a problem of folks on dev@felix not being
>> able or willing to participate in a new podling? (If the folks presenting
>> this proposal do wish to start off as a podling)
>>
>
> Personally speaking I'd be willing to help out where possible regardless of
> where it starts off.
> I doubt I'm experienced enough in the Apache Way to be a mentor, but having
> been on the
> OSGi Enterprise Expert Group in the past I am interested in seeing solutions
> in this space.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Stuart McCulloch <mc...@gmail.com>.
2009/9/5 Davanum Srinivas <da...@gmail.com>

> One more question, Will there be a problem of folks on dev@felix not being
> able or willing to participate in a new podling? (If the folks presenting
> this proposal do wish to start off as a podling)
>

Personally speaking I'd be willing to help out where possible regardless of
where it starts off.
I doubt I'm experienced enough in the Apache Way to be a mentor, but having
been on the
OSGi Enterprise Expert Group in the past I am interested in seeing solutions
in this space.

-- 
Cheers, Stuart

thanks,
> dims

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Let me clarify why i asked that question, When we started the Wink Podling there was strong recommendation that the 
incoming folks should work under CXF which already has a JAX-RS implementation. Once we did start the podling we have 
had guidance from just Dan Kulp from CXF and not from anyone else :(

thanks,
dims

On 09/04/2009 04:49 PM, Davanum Srinivas wrote:
> Richard,
>
> I see your viewpoint better now. Thanks.
>
> One more question, Will there be a problem of folks on dev@felix not
> being able or willing to participate in a new podling? (If the folks
> presenting this proposal do wish to start off as a podling)
>
> thanks,
> dims
>
> On 09/04/2009 04:31 PM, Richard S. Hall wrote:
>> On 9/4/09 16:10, Davanum Srinivas wrote:
>>> Richard,
>>>
>>> On 09/04/2009 03:49 PM, Richard S. Hall wrote:
>>>> So, no, I am not saying "everything should", but in general, it
>>>> would be
>>>> nice if the spec impls started there since we have a community of OSGi
>>>> users and OSGi experts who are very active and receptive, many of whom
>>>> also work in the EE space.
>>>
>>> Will the people mentioned not participate if Aries is a separate
>>> podling to start with? After all destination PMC can be determined
>>> during graduation process. Also the incubation process is to show new
>>> incoming team how Apache works etc..is that better done as a podling
>>> or as a felix sub project? If we continue the same thought process,
>>> will there every be any incubator podling with for any OSGi related
>>> activity?
>>
>> Yes, and I mentioned this, but that seems to get lost somehow.
>>
>>>> In short, it makes sense for spec impls tied to the Aries component
>>>> model (for example), to be hosted there, but there is little need to
>>>> create another project to incubate generic OSGi spec impls, since the
>>>> Felix community was set up for that. The reality is, most OSGi specs
>>>> are
>>>> not huge projects so we likely wouldn't want TLPs for all of them, but
>>>> nothing stops a subproject started at Felix from going TLP if it takes
>>>> on a life of its own.
>>>
>>> Choices are
>>>
>>> 1) Podling -> TLP
>>> 2) Podling -> Felix Sub project
>>> 3) Podling -> Felix Sub project -> TLP
>>> 4) Felix Sub project
>>> 5) Felix Sub project -> TLP
>>>
>>> The first 3 effectively uses incubator process(es) to educate the
>>> incoming folks and provides a strong grounding in ASF-land (at least
>>> that is what the intention is :)
>>>
>>> So, why should we bypass incubator?
>>
>> Again, there was already a project incubated to educate incoming folks
>> on how to create open source OSGi spec impls at Apache, so why do we
>> need to repeat that process?
>>
>> Your phrasing of this question implies we are trying to somehow skirt
>> the Apache way, but educating incoming people via contributions and
>> meritocracy to an existing project is not some shortcut.
>>
>> -> richard
>>
>>>
>>> thanks,
>>> dims
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Richard,

#2 - "Finished impls could quickly be released as non-incubator artifacts." is also something that i am not comfortable 
with, at least until the new committers get off the ground, attract a user community and show that they are able to 
follow the ASF way.

Ideally my hope is that dev@felix folks should guide the community being formed within the incubation podling process. 
If we can get anyone interested join in as a mentor and/or committer that would be wonderful.

thanks,
dims

On 09/04/2009 06:04 PM, Richard S. Hall wrote:
>
> On 9/4/09 16:49, Davanum Srinivas wrote:
>> Richard,
>>
>> I see your viewpoint better now. Thanks.
>>
>> One more question, Will there be a problem of folks on dev@felix not
>> being able or willing to participate in a new podling? (If the folks
>> presenting this proposal do wish to start off as a podling)
>
> Dims, since I don't speak for all Felix community members, I can't
> really answer that question. I imagine that interested parties would
> contribute, but certainly a benefit of at least doing any independent
> OSGi spec impls at Felix is you will automatically get the oversight of
> people who have been doing it for years, if not their contribution. The
> separation could possibly make life simpler too for those willing to
> help, since:
>
> 1. People interested only in the OSGi spec impls do not necessarily
> have to be involved on Aries mailing lists that will likely
> incorporate a lot of discussion about the Aries component model
> and related content.
> 2. Finished impls could quickly be released as non-incubator artifacts.
>
> -> richard
>
>>
>> thanks,
>> dims
>>
>> On 09/04/2009 04:31 PM, Richard S. Hall wrote:
>>> On 9/4/09 16:10, Davanum Srinivas wrote:
>>>> Richard,
>>>>
>>>> On 09/04/2009 03:49 PM, Richard S. Hall wrote:
>>>>> So, no, I am not saying "everything should", but in general, it
>>>>> would be
>>>>> nice if the spec impls started there since we have a community of OSGi
>>>>> users and OSGi experts who are very active and receptive, many of whom
>>>>> also work in the EE space.
>>>>
>>>> Will the people mentioned not participate if Aries is a separate
>>>> podling to start with? After all destination PMC can be determined
>>>> during graduation process. Also the incubation process is to show new
>>>> incoming team how Apache works etc..is that better done as a podling
>>>> or as a felix sub project? If we continue the same thought process,
>>>> will there every be any incubator podling with for any OSGi related
>>>> activity?
>>>
>>> Yes, and I mentioned this, but that seems to get lost somehow.
>>>
>>>>> In short, it makes sense for spec impls tied to the Aries component
>>>>> model (for example), to be hosted there, but there is little need to
>>>>> create another project to incubate generic OSGi spec impls, since the
>>>>> Felix community was set up for that. The reality is, most OSGi
>>>>> specs are
>>>>> not huge projects so we likely wouldn't want TLPs for all of them, but
>>>>> nothing stops a subproject started at Felix from going TLP if it takes
>>>>> on a life of its own.
>>>>
>>>> Choices are
>>>>
>>>> 1) Podling -> TLP
>>>> 2) Podling -> Felix Sub project
>>>> 3) Podling -> Felix Sub project -> TLP
>>>> 4) Felix Sub project
>>>> 5) Felix Sub project -> TLP
>>>>
>>>> The first 3 effectively uses incubator process(es) to educate the
>>>> incoming folks and provides a strong grounding in ASF-land (at least
>>>> that is what the intention is :)
>>>>
>>>> So, why should we bypass incubator?
>>>
>>> Again, there was already a project incubated to educate incoming folks
>>> on how to create open source OSGi spec impls at Apache, so why do we
>>> need to repeat that process?
>>>
>>> Your phrasing of this question implies we are trying to somehow skirt
>>> the Apache way, but educating incoming people via contributions and
>>> meritocracy to an existing project is not some shortcut.
>>>
>>> -> richard
>>>
>>>>
>>>> thanks,
>>>> dims
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 9/4/09 16:49, Davanum Srinivas wrote:
> Richard,
>
> I see your viewpoint better now. Thanks.
>
> One more question, Will there be a problem of folks on dev@felix not 
> being able or willing to participate in a new podling? (If the folks 
> presenting this proposal do wish to start off as a podling)

Dims, since I don't speak for all Felix community members, I can't 
really answer that question. I imagine that interested parties would 
contribute, but certainly a benefit of at least doing any independent 
OSGi spec impls at Felix is you will automatically get the oversight of 
people who have been doing it for years, if not their contribution. The 
separation could possibly make life simpler too for those willing to 
help, since:

   1. People interested only in the OSGi spec impls do not necessarily
      have to be involved on Aries mailing lists that will likely
      incorporate a lot of discussion about the Aries component model
      and related content.
   2. Finished impls could quickly be released as non-incubator artifacts.

-> richard

>
> thanks,
> dims
>
> On 09/04/2009 04:31 PM, Richard S. Hall wrote:
>> On 9/4/09 16:10, Davanum Srinivas wrote:
>>> Richard,
>>>
>>> On 09/04/2009 03:49 PM, Richard S. Hall wrote:
>>>> So, no, I am not saying "everything should", but in general, it 
>>>> would be
>>>> nice if the spec impls started there since we have a community of OSGi
>>>> users and OSGi experts who are very active and receptive, many of whom
>>>> also work in the EE space.
>>>
>>> Will the people mentioned not participate if Aries is a separate
>>> podling to start with? After all destination PMC can be determined
>>> during graduation process. Also the incubation process is to show new
>>> incoming team how Apache works etc..is that better done as a podling
>>> or as a felix sub project? If we continue the same thought process,
>>> will there every be any incubator podling with for any OSGi related
>>> activity?
>>
>> Yes, and I mentioned this, but that seems to get lost somehow.
>>
>>>> In short, it makes sense for spec impls tied to the Aries component
>>>> model (for example), to be hosted there, but there is little need to
>>>> create another project to incubate generic OSGi spec impls, since the
>>>> Felix community was set up for that. The reality is, most OSGi 
>>>> specs are
>>>> not huge projects so we likely wouldn't want TLPs for all of them, but
>>>> nothing stops a subproject started at Felix from going TLP if it takes
>>>> on a life of its own.
>>>
>>> Choices are
>>>
>>> 1) Podling -> TLP
>>> 2) Podling -> Felix Sub project
>>> 3) Podling -> Felix Sub project -> TLP
>>> 4) Felix Sub project
>>> 5) Felix Sub project -> TLP
>>>
>>> The first 3 effectively uses incubator process(es) to educate the
>>> incoming folks and provides a strong grounding in ASF-land (at least
>>> that is what the intention is :)
>>>
>>> So, why should we bypass incubator?
>>
>> Again, there was already a project incubated to educate incoming folks
>> on how to create open source OSGi spec impls at Apache, so why do we
>> need to repeat that process?
>>
>> Your phrasing of this question implies we are trying to somehow skirt
>> the Apache way, but educating incoming people via contributions and
>> meritocracy to an existing project is not some shortcut.
>>
>> -> richard
>>
>>>
>>> thanks,
>>> dims
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Richard,

I see your viewpoint better now. Thanks.

One more question, Will there be a problem of folks on dev@felix not being able or willing to participate in a new 
podling? (If the folks presenting this proposal do wish to start off as a podling)

thanks,
dims

On 09/04/2009 04:31 PM, Richard S. Hall wrote:
> On 9/4/09 16:10, Davanum Srinivas wrote:
>> Richard,
>>
>> On 09/04/2009 03:49 PM, Richard S. Hall wrote:
>>> So, no, I am not saying "everything should", but in general, it would be
>>> nice if the spec impls started there since we have a community of OSGi
>>> users and OSGi experts who are very active and receptive, many of whom
>>> also work in the EE space.
>>
>> Will the people mentioned not participate if Aries is a separate
>> podling to start with? After all destination PMC can be determined
>> during graduation process. Also the incubation process is to show new
>> incoming team how Apache works etc..is that better done as a podling
>> or as a felix sub project? If we continue the same thought process,
>> will there every be any incubator podling with for any OSGi related
>> activity?
>
> Yes, and I mentioned this, but that seems to get lost somehow.
>
>>> In short, it makes sense for spec impls tied to the Aries component
>>> model (for example), to be hosted there, but there is little need to
>>> create another project to incubate generic OSGi spec impls, since the
>>> Felix community was set up for that. The reality is, most OSGi specs are
>>> not huge projects so we likely wouldn't want TLPs for all of them, but
>>> nothing stops a subproject started at Felix from going TLP if it takes
>>> on a life of its own.
>>
>> Choices are
>>
>> 1) Podling -> TLP
>> 2) Podling -> Felix Sub project
>> 3) Podling -> Felix Sub project -> TLP
>> 4) Felix Sub project
>> 5) Felix Sub project -> TLP
>>
>> The first 3 effectively uses incubator process(es) to educate the
>> incoming folks and provides a strong grounding in ASF-land (at least
>> that is what the intention is :)
>>
>> So, why should we bypass incubator?
>
> Again, there was already a project incubated to educate incoming folks
> on how to create open source OSGi spec impls at Apache, so why do we
> need to repeat that process?
>
> Your phrasing of this question implies we are trying to somehow skirt
> the Apache way, but educating incoming people via contributions and
> meritocracy to an existing project is not some shortcut.
>
> -> richard
>
>>
>> thanks,
>> dims
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Sat, Sep 5, 2009 at 4:31 PM, Karl Pauls<ka...@gmail.com> wrote:

> Where in the above "but educating incoming people via contributions
> and meritocracy to an existing project is not some shortcut" do you
> find anything that would imply that the idea is to just accept a large
> number of people into a TLP?

Not sure what got you off, but if you want trial;

Incubator's Evidence A; 9 people on the roster are not ASF folks.

Incubator's Evidence B; Someone said that commit rights are needed for
practical reasons.

Incubator's Evidence C; Richard is contesting Dims' question "Why
should we bypass the Incubator?" from the "Choices List", with a
motivation that this can happen at Felix.

I leave it to the jury to draw the conclusion and not repeat myself.


> I think that we at Felix never did just
> vote in people on the basis "they will create...". Sometimes we do
> accept people new to the ASF on the basis "they donated..." but only
> if we are talking about individual (i.e., 1 or 2) contributors which
> either have been around for  a while or had somebody on the PMC who
> did speak up for them personally.

I am not referring to the past...


>> Hence, the group's decision to come to Incubator is a correct one.
>
> And nobody has been questioning that as far as I can see.
> This is different from saying that the group's
> decision to come to Incubator is an incorrect one...

I said it was a correct one!

>> Where it graduates to is a different story, and I can leave that
>> question for later. And the Felix community is encouraged to follow
>> and participate the Aries effort.
>
> As I'm sure at least some if not all of us will. The has never been a
> question either imo. The question in this regard was and is purely to
> what extend Felix people interested in the OSGi EE spec
> implementations only have to get involved in the (more general) Aries
> project and how quickly OSGi EE spec implementations can be released
> as none incubator artifacts.

Isn't it very simple? Work with the people over the year or two the
Incubation is bound to take, and influence them to understand what you
think is the best direction. Put that good Felix vibes in place and
make parts of the project to naturally graduate to Felix.

> And one more time (just in case it was missed earlier): let me point
> out that nobody is talking about Aries as a Felix "incubator" project
> nor (at least at this point in time) about a possible subproject of
> Felix after graduation. We are only talking about the OSGi EE spec
> implementations that are part of the proposed Aries scope.

Well, Felix is free to implement whatever specifications it wants. The
Incubator couldn't care less. So the issue is bigger than that. It is
about community. Felix want to 'adopt' people who wants to work on
these specs, and such 'adoption' may become an Incubator issue if it
is "as is the case" a whole bunch of people with ASF experience. If
you contest that let's say Apache Geronimo or Apache Cocoon are not
"allowed" to implement OSGi specs and that those efforts are the
"monopoly" of Felix, then you are on thin ice, as that is definitely
against the spirit of ASF. You can only influence them to move their
effort to Felix, but it is not a given. Unfortunately, the Felix
community has been coming on quite strongly and antagonistic, so there
is a lot of social skills required to mend that, but given the time
available, I don't see a real problem.


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
Hi Peter, thank you. Welcome to eveyone.

Cheers,
Jeremy

2009/9/14 Peter Peshev <pp...@gmail.com>:
> HI Jeremy,
>
> I have added seven names to the wiki as per your instructions :
>
> Bernd Kolb
> Dimo Stoilov
> Kiril Mitov
> Nikolai Tankov
> Peter Peshev
> Sabine Heider
> Violeta Georgieva
>
> The people have worked on various modules from SAP's Java EE certified
> server, from  SAP's SCA implentation as well as from SAP's Eclipse
> based Developer Studio. From a specification perspective that could be
> relevant to the project, there are experts with participation in
> various standards organisations  ( OSGi EEG,  JCP, OSOA, OASIS)
>
> Best Regards
> Peter
>
> On Fri, Sep 11, 2009 at 6:49 PM, Jeremy Hughes <hu...@apache.org> wrote:
>> As discussion is settling down, I'd like to aim for Tuesday next week
>> (15 Sept) to call a vote.
>>
>> Peter, does that give you time to supply your initial set of committers?
>>
>> Thanks,
>> Jeremy
>>
>> 2009/9/10 Jeremy Hughes <hu...@apache.org>:
>>> 2009/9/10 Peter Peshev <pp...@gmail.com>:
>>>> Hi Jeremy,
>>>>
>>>> Thanks , we would need a few more days to finalize all the
>>>> participants from our side, some people are on vacation this week .
>>>> Maybe it could be even a bigger number.
>>>
>>> Wow, sounds like you have a lot to contribute :-)
>>>
>>>>  Is there a deadline ?
>>>
>>> No, there's no deadline. When the discussion has settled down then
>>> we'll wait for a few days before calling for a vote to accept Aries as
>>> a podling. If the vote is successful then the podling is set up with
>>> (among other things) the set of initial committers and the mailing
>>> lists described in the proposal. The way we grow the (developer)
>>> community from there is to vote on making contributors into committers
>>> on the dev mailing list we would have set up. So there is plenty of
>>> opportunity to add committers - in fact, like any other Apache
>>> community, we absolutely rely on it to grow.
>>>
>>> Cheers,
>>> Jeremy
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Peter Peshev <pp...@gmail.com>.
HI Jeremy,

I have added seven names to the wiki as per your instructions :

Bernd Kolb
Dimo Stoilov
Kiril Mitov
Nikolai Tankov
Peter Peshev
Sabine Heider
Violeta Georgieva

The people have worked on various modules from SAP's Java EE certified
server, from  SAP's SCA implentation as well as from SAP's Eclipse
based Developer Studio. From a specification perspective that could be
relevant to the project, there are experts with participation in
various standards organisations  ( OSGi EEG,  JCP, OSOA, OASIS)

Best Regards
Peter

On Fri, Sep 11, 2009 at 6:49 PM, Jeremy Hughes <hu...@apache.org> wrote:
> As discussion is settling down, I'd like to aim for Tuesday next week
> (15 Sept) to call a vote.
>
> Peter, does that give you time to supply your initial set of committers?
>
> Thanks,
> Jeremy
>
> 2009/9/10 Jeremy Hughes <hu...@apache.org>:
>> 2009/9/10 Peter Peshev <pp...@gmail.com>:
>>> Hi Jeremy,
>>>
>>> Thanks , we would need a few more days to finalize all the
>>> participants from our side, some people are on vacation this week .
>>> Maybe it could be even a bigger number.
>>
>> Wow, sounds like you have a lot to contribute :-)
>>
>>>  Is there a deadline ?
>>
>> No, there's no deadline. When the discussion has settled down then
>> we'll wait for a few days before calling for a vote to accept Aries as
>> a podling. If the vote is successful then the podling is set up with
>> (among other things) the set of initial committers and the mailing
>> lists described in the proposal. The way we grow the (developer)
>> community from there is to vote on making contributors into committers
>> on the dev mailing list we would have set up. So there is plenty of
>> opportunity to add committers - in fact, like any other Apache
>> community, we absolutely rely on it to grow.
>>
>> Cheers,
>> Jeremy
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Peter Peshev <pp...@gmail.com>.
Hi Jeremy,

Yes, I would try to do that on Monday morning

Best Regards
Peter


On Fri, Sep 11, 2009 at 6:49 PM, Jeremy Hughes <hu...@apache.org> wrote:
> As discussion is settling down, I'd like to aim for Tuesday next week
> (15 Sept) to call a vote.
>
> Peter, does that give you time to supply your initial set of committers?
>
> Thanks,
> Jeremy
>
> 2009/9/10 Jeremy Hughes <hu...@apache.org>:
>> 2009/9/10 Peter Peshev <pp...@gmail.com>:
>>> Hi Jeremy,
>>>
>>> Thanks , we would need a few more days to finalize all the
>>> participants from our side, some people are on vacation this week .
>>> Maybe it could be even a bigger number.
>>
>> Wow, sounds like you have a lot to contribute :-)
>>
>>>  Is there a deadline ?
>>
>> No, there's no deadline. When the discussion has settled down then
>> we'll wait for a few days before calling for a vote to accept Aries as
>> a podling. If the vote is successful then the podling is set up with
>> (among other things) the set of initial committers and the mailing
>> lists described in the proposal. The way we grow the (developer)
>> community from there is to vote on making contributors into committers
>> on the dev mailing list we would have set up. So there is plenty of
>> opportunity to add committers - in fact, like any other Apache
>> community, we absolutely rely on it to grow.
>>
>> Cheers,
>> Jeremy
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
As discussion is settling down, I'd like to aim for Tuesday next week
(15 Sept) to call a vote.

Peter, does that give you time to supply your initial set of committers?

Thanks,
Jeremy

2009/9/10 Jeremy Hughes <hu...@apache.org>:
> 2009/9/10 Peter Peshev <pp...@gmail.com>:
>> Hi Jeremy,
>>
>> Thanks , we would need a few more days to finalize all the
>> participants from our side, some people are on vacation this week .
>> Maybe it could be even a bigger number.
>
> Wow, sounds like you have a lot to contribute :-)
>
>>  Is there a deadline ?
>
> No, there's no deadline. When the discussion has settled down then
> we'll wait for a few days before calling for a vote to accept Aries as
> a podling. If the vote is successful then the podling is set up with
> (among other things) the set of initial committers and the mailing
> lists described in the proposal. The way we grow the (developer)
> community from there is to vote on making contributors into committers
> on the dev mailing list we would have set up. So there is plenty of
> opportunity to add committers - in fact, like any other Apache
> community, we absolutely rely on it to grow.
>
> Cheers,
> Jeremy
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
2009/9/10 Peter Peshev <pp...@gmail.com>:
> Hi Jeremy,
>
> Thanks , we would need a few more days to finalize all the
> participants from our side, some people are on vacation this week .
> Maybe it could be even a bigger number.

Wow, sounds like you have a lot to contribute :-)

>  Is there a deadline ?

No, there's no deadline. When the discussion has settled down then
we'll wait for a few days before calling for a vote to accept Aries as
a podling. If the vote is successful then the podling is set up with
(among other things) the set of initial committers and the mailing
lists described in the proposal. The way we grow the (developer)
community from there is to vote on making contributors into committers
on the dev mailing list we would have set up. So there is plenty of
opportunity to add committers - in fact, like any other Apache
community, we absolutely rely on it to grow.

Cheers,
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Peter Peshev <pp...@gmail.com>.
Hi Jeremy,

Thanks , we would need a few more days to finalize all the
participants from our side, some people are on vacation this week .
Maybe it could be even a bigger number.  Is there a deadline ?

Best Regards
Peter

On Thu, Sep 10, 2009 at 12:46 PM, Jeremy Hughes <hu...@apache.org> wrote:
> Hi Peter,
>
> 2009/9/9 Peter Peshev <pp...@gmail.com>:
>> Hi Jeremy,
>>
>> We from SAP would like to join and nominate six people for the
>> proposed Aries project. What's the process - should I just add the six
>> names on the wiki ? Maybe we could discuss this offline to not spam
>> the whole mailing list.
>
> Great news! Welcome. I think just adding your names to the initial
> committer list in the proposal wiki is fine. As for any discussion
> about it, I think we should keep discussion on the list - it's the
> Apache Way :-)
>
>>
>> Unfortunately none of the suggested people from our side has
>> experience in Apache project , but I  hope that’s not an issue.
>
> This is one of the things incubation will help with. Kevan mentioned
> some starting points - there are many other good pages to read for
> those completely new to Apache. Here are some more :-)
>
> http://www.apache.org/foundation/how-it-works.html
> http://www.apache.org/foundation/getinvolved.html
> http://www.apache.org/foundation/voting.html
> http://www.apache.org/foundation/glossary.html
>
> Jeremy
>
>>
>> Best Regards
>> Peter Peshev
>>
>>
>>
>> On Mon, Sep 7, 2009 at 5:57 PM, Jeremy Hughes<hu...@apache.org> wrote:
>>> Cross-pollination and help from the Felix community have been talked
>>> about several times and I absolutely welcome that. As such, please
>>> would Felix committers willing to spend time helping the (proposed)
>>> Aries podling add their names to the initial committer list on the
>>> proposal wiki [1]. This naturally extends beyond Felix committers.
>>>
>>> Apologies for x-post to dev@felix ... I wanted to attract as many as
>>> possible :-)
>>>
>>> [1] http://wiki.apache.org/incubator/AriesProposal
>>>
>>> Thanks,
>>> Jeremy
>>>
>>> 2009/9/5 Davanum Srinivas <da...@gmail.com>:
>>>> Karl,
>>>>
>>>> Please don't get me wrong. Felix is choice for an excellent *destination*
>>>> TLP. The Incubator PMC itself was setup to take away the responsibility for
>>>> training incoming folks from existing TLP(s). So my gut feeling is that we
>>>> should allow the incubation process to go on and decide on destination and
>>>> scope once the project is ready to graduate. I am sure the folks on the
>>>> proposal would love to get any and every help they can get to graduate as
>>>> well as on the technical front. Please do continue to provide help and
>>>> guidance.
>>>>
>>>> thanks,
>>>> dims
>>>>
>>>> On 09/05/2009 10:29 AM, Karl Pauls wrote:
>>>>>
>>>>> On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivas<da...@gmail.com>
>>>>>  wrote:
>>>>>>
>>>>>> Karl,
>>>>>>
>>>>>> There are *many* TLP(s) with overlapping scope as James Strachan pointed
>>>>>> out
>>>>>> earlier in the thread.
>>>>>>
>>>>>>
>>>>>> I don't see the need to shoe horn a new community with new code into an
>>>>>> existing TLP just because of scope. For all you know by the time they get
>>>>>> out of the incubator their scope may change a bit (or more).
>>>>>
>>>>> I'm sorry if it looked like I wanted to shoe horn anything into felix.
>>>>> That wasn't my goal as for me it was a question of where I would like
>>>>> it to happen and as I said earlier already, not the end of the world
>>>>> if not.
>>>>>
>>>>> regards,
>>>>>
>>>>> Karl
>>>>>
>>>>>> thanks,
>>>>>> dims
>>>>>>
>>>>>> On 09/05/2009 04:31 AM, Karl Pauls wrote:
>>>>>>>
>>>>>>> The question
>>>>>>> is about the scope and goals of Aries and more specifically about the
>>>>>>> part where it is about being an umbrella for OSGi EE spec
>>>>>>> implementations where it has been argued that this could/should be
>>>>>>> done at felix
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
Hi Peter,

2009/9/9 Peter Peshev <pp...@gmail.com>:
> Hi Jeremy,
>
> We from SAP would like to join and nominate six people for the
> proposed Aries project. What's the process - should I just add the six
> names on the wiki ? Maybe we could discuss this offline to not spam
> the whole mailing list.

Great news! Welcome. I think just adding your names to the initial
committer list in the proposal wiki is fine. As for any discussion
about it, I think we should keep discussion on the list - it's the
Apache Way :-)

>
> Unfortunately none of the suggested people from our side has
> experience in Apache project , but I  hope that’s not an issue.

This is one of the things incubation will help with. Kevan mentioned
some starting points - there are many other good pages to read for
those completely new to Apache. Here are some more :-)

http://www.apache.org/foundation/how-it-works.html
http://www.apache.org/foundation/getinvolved.html
http://www.apache.org/foundation/voting.html
http://www.apache.org/foundation/glossary.html

Jeremy

>
> Best Regards
> Peter Peshev
>
>
>
> On Mon, Sep 7, 2009 at 5:57 PM, Jeremy Hughes<hu...@apache.org> wrote:
>> Cross-pollination and help from the Felix community have been talked
>> about several times and I absolutely welcome that. As such, please
>> would Felix committers willing to spend time helping the (proposed)
>> Aries podling add their names to the initial committer list on the
>> proposal wiki [1]. This naturally extends beyond Felix committers.
>>
>> Apologies for x-post to dev@felix ... I wanted to attract as many as
>> possible :-)
>>
>> [1] http://wiki.apache.org/incubator/AriesProposal
>>
>> Thanks,
>> Jeremy
>>
>> 2009/9/5 Davanum Srinivas <da...@gmail.com>:
>>> Karl,
>>>
>>> Please don't get me wrong. Felix is choice for an excellent *destination*
>>> TLP. The Incubator PMC itself was setup to take away the responsibility for
>>> training incoming folks from existing TLP(s). So my gut feeling is that we
>>> should allow the incubation process to go on and decide on destination and
>>> scope once the project is ready to graduate. I am sure the folks on the
>>> proposal would love to get any and every help they can get to graduate as
>>> well as on the technical front. Please do continue to provide help and
>>> guidance.
>>>
>>> thanks,
>>> dims
>>>
>>> On 09/05/2009 10:29 AM, Karl Pauls wrote:
>>>>
>>>> On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivas<da...@gmail.com>
>>>>  wrote:
>>>>>
>>>>> Karl,
>>>>>
>>>>> There are *many* TLP(s) with overlapping scope as James Strachan pointed
>>>>> out
>>>>> earlier in the thread.
>>>>>
>>>>>
>>>>> I don't see the need to shoe horn a new community with new code into an
>>>>> existing TLP just because of scope. For all you know by the time they get
>>>>> out of the incubator their scope may change a bit (or more).
>>>>
>>>> I'm sorry if it looked like I wanted to shoe horn anything into felix.
>>>> That wasn't my goal as for me it was a question of where I would like
>>>> it to happen and as I said earlier already, not the end of the world
>>>> if not.
>>>>
>>>> regards,
>>>>
>>>> Karl
>>>>
>>>>> thanks,
>>>>> dims
>>>>>
>>>>> On 09/05/2009 04:31 AM, Karl Pauls wrote:
>>>>>>
>>>>>> The question
>>>>>> is about the scope and goals of Aries and more specifically about the
>>>>>> part where it is about being an umbrella for OSGi EE spec
>>>>>> implementations where it has been argued that this could/should be
>>>>>> done at felix
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
2009/9/9 Niklas Gustavsson <ni...@protocol7.com>:
> On Wed, Sep 9, 2009 at 8:14 PM, Kevan Miller<ke...@gmail.com> wrote:
>> Cool! So, IMO would be best to post the names here on general@ and let
>> Jeremy update the Wiki.
>
> Since we're at it, I'd like to sign up as a committer as well (apache
> username ngn). Will be quite time constrained in the next two-three
> months but the areas deeply interests me so I'll chime in where
> possible.
>
> /niklas
Sure, welcome! Please go ahead and add yourself to the list of initial
committers on the proposal

http://wiki.apache.org/incubator/AriesProposal

Thanks,
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
Hi Raymond, welcome! I added you to the proposal.

Thanks,
Jeremy

2009/9/11 Raymond Feng <en...@gmail.com>:
> I'm also interested in the Aries project and would like to sign up as an
> initial committer, especially in the area of distributed OSGi. I have been
> the key contributor in Apache Tuscany project to enable the runtime with
> OSGi and implement the OSGi remote services (originally RFC 119) using SCA
> as the distribution provider. There are good opportunities ahead that
> Tuscany and Aries collaborate in supporting OSGi and SCA programming models.
>
> Raymond Feng
> rfeng@apache.org
> --------------------------------------------------
> From: "Guillaume Nodet" <gn...@gmail.com>
> Sent: Friday, September 11, 2009 1:47 AM
> To: "general" <ge...@incubator.apache.org>
> Subject: Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
>
>> I've added both Jean-Sebastien and you to the proposal.
>>
>> 2009/9/11 Carsten Ziegeler <cz...@apache.org>:
>>>
>>> Hi,
>>>
>>> sounds like interesting stuff. I would like to be added to the initial
>>> committer list as well :)
>>>
>>> Thanks
>>> Carsten
>>> --
>>> Carsten Ziegeler
>>> cziegeler@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Raymond Feng <en...@gmail.com>.
I'm also interested in the Aries project and would like to sign up as an 
initial committer, especially in the area of distributed OSGi. I have been 
the key contributor in Apache Tuscany project to enable the runtime with 
OSGi and implement the OSGi remote services (originally RFC 119) using SCA 
as the distribution provider. There are good opportunities ahead that 
Tuscany and Aries collaborate in supporting OSGi and SCA programming models.

Raymond Feng
rfeng@apache.org
--------------------------------------------------
From: "Guillaume Nodet" <gn...@gmail.com>
Sent: Friday, September 11, 2009 1:47 AM
To: "general" <ge...@incubator.apache.org>
Subject: Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

> I've added both Jean-Sebastien and you to the proposal.
>
> 2009/9/11 Carsten Ziegeler <cz...@apache.org>:
>> Hi,
>>
>> sounds like interesting stuff. I would like to be added to the initial
>> committer list as well :)
>>
>> Thanks
>> Carsten
>> --
>> Carsten Ziegeler
>> cziegeler@apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>
> -- 
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
I've added both Jean-Sebastien and you to the proposal.

2009/9/11 Carsten Ziegeler <cz...@apache.org>:
> Hi,
>
> sounds like interesting stuff. I would like to be added to the initial
> committer list as well :)
>
> Thanks
> Carsten
> --
> Carsten Ziegeler
> cziegeler@apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Carsten Ziegeler <cz...@apache.org>.
Hi,

sounds like interesting stuff. I would like to be added to the initial
committer list as well :)

Thanks
Carsten
-- 
Carsten Ziegeler
cziegeler@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jean-Sebastien Delfino <js...@apache.org>.
Niklas Gustavsson wrote:
> On Wed, Sep 9, 2009 at 8:14 PM, Kevan Miller<ke...@gmail.com> wrote:
>> Cool! So, IMO would be best to post the names here on general@ and let
>> Jeremy update the Wiki.
> 
> Since we're at it, I'd like to sign up as a committer as well (apache
> username ngn). Will be quite time constrained in the next two-three
> months but the areas deeply interests me so I'll chime in where
> possible.
> 
> /niklas
> 

Hi, I'd like to help and sign up as a committer too (apache user name 
jsdelfino). I have experience with Apache, SCA and OSGi as I did quite a 
bit of OSGi work in Apache Tuscany.

Jeremy, do you want me to add my name? or are you making all the updates 
to the Wiki page?

-- 
Jean-Sebastien

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Wed, Sep 9, 2009 at 8:14 PM, Kevan Miller<ke...@gmail.com> wrote:
> Cool! So, IMO would be best to post the names here on general@ and let
> Jeremy update the Wiki.

Since we're at it, I'd like to sign up as a committer as well (apache
username ngn). Will be quite time constrained in the next two-three
months but the areas deeply interests me so I'll chime in where
possible.

/niklas

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Kevan Miller <ke...@gmail.com>.
On Sep 9, 2009, at 1:57 PM, Davanum Srinivas wrote:

> Hi Peter,
>
> Excellent! I am hoping that the champions - in this case Kevan  
> Miller and Guillaume Nodet - will chime in on next steps.

Cool! So, IMO would be best to post the names here on general@ and let  
Jeremy update the Wiki. That seems to be preferred approach according  
to http://incubator.apache.org/guides/participation.html#committer also.

No problem with lack of Apache experience. You may want to look at the  
following:

http://incubator.apache.org/guides/committer.html
http://www.apache.org/dev/new-committers-guide.html

And you can submit an ICLA at any time -- http://www.apache.org/licenses/#clas 
  Scanning and emailing seems to be the most efficient method, these  
days, but others work also...

--kevan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Hi Peter,

Excellent! I am hoping that the champions - in this case Kevan Miller and Guillaume Nodet - will chime in on next steps.

thanks,
dims

On 09/09/2009 01:45 PM, Peter Peshev wrote:
> Hi Jeremy,
>
> We from SAP would like to join and nominate six people for the
> proposed Aries project. What's the process - should I just add the six
> names on the wiki ? Maybe we could discuss this offline to not spam
> the whole mailing list.
>
> Unfortunately none of the suggested people from our side has
> experience in Apache project , but I  hope that’s not an issue.
>
> Best Regards
> Peter Peshev
>
>
>
> On Mon, Sep 7, 2009 at 5:57 PM, Jeremy Hughes<hu...@apache.org>  wrote:
>> Cross-pollination and help from the Felix community have been talked
>> about several times and I absolutely welcome that. As such, please
>> would Felix committers willing to spend time helping the (proposed)
>> Aries podling add their names to the initial committer list on the
>> proposal wiki [1]. This naturally extends beyond Felix committers.
>>
>> Apologies for x-post to dev@felix ... I wanted to attract as many as
>> possible :-)
>>
>> [1] http://wiki.apache.org/incubator/AriesProposal
>>
>> Thanks,
>> Jeremy
>>
>> 2009/9/5 Davanum Srinivas<da...@gmail.com>:
>>> Karl,
>>>
>>> Please don't get me wrong. Felix is choice for an excellent *destination*
>>> TLP. The Incubator PMC itself was setup to take away the responsibility for
>>> training incoming folks from existing TLP(s). So my gut feeling is that we
>>> should allow the incubation process to go on and decide on destination and
>>> scope once the project is ready to graduate. I am sure the folks on the
>>> proposal would love to get any and every help they can get to graduate as
>>> well as on the technical front. Please do continue to provide help and
>>> guidance.
>>>
>>> thanks,
>>> dims
>>>
>>> On 09/05/2009 10:29 AM, Karl Pauls wrote:
>>>>
>>>> On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivas<da...@gmail.com>
>>>>   wrote:
>>>>>
>>>>> Karl,
>>>>>
>>>>> There are *many* TLP(s) with overlapping scope as James Strachan pointed
>>>>> out
>>>>> earlier in the thread.
>>>>>
>>>>>
>>>>> I don't see the need to shoe horn a new community with new code into an
>>>>> existing TLP just because of scope. For all you know by the time they get
>>>>> out of the incubator their scope may change a bit (or more).
>>>>
>>>> I'm sorry if it looked like I wanted to shoe horn anything into felix.
>>>> That wasn't my goal as for me it was a question of where I would like
>>>> it to happen and as I said earlier already, not the end of the world
>>>> if not.
>>>>
>>>> regards,
>>>>
>>>> Karl
>>>>
>>>>> thanks,
>>>>> dims
>>>>>
>>>>> On 09/05/2009 04:31 AM, Karl Pauls wrote:
>>>>>>
>>>>>> The question
>>>>>> is about the scope and goals of Aries and more specifically about the
>>>>>> part where it is about being an umbrella for OSGi EE spec
>>>>>> implementations where it has been argued that this could/should be
>>>>>> done at felix
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Peter Peshev <pp...@gmail.com>.
Hi Jeremy,

We from SAP would like to join and nominate six people for the
proposed Aries project. What's the process - should I just add the six
names on the wiki ? Maybe we could discuss this offline to not spam
the whole mailing list.

Unfortunately none of the suggested people from our side has
experience in Apache project , but I  hope that’s not an issue.

Best Regards
Peter Peshev



On Mon, Sep 7, 2009 at 5:57 PM, Jeremy Hughes<hu...@apache.org> wrote:
> Cross-pollination and help from the Felix community have been talked
> about several times and I absolutely welcome that. As such, please
> would Felix committers willing to spend time helping the (proposed)
> Aries podling add their names to the initial committer list on the
> proposal wiki [1]. This naturally extends beyond Felix committers.
>
> Apologies for x-post to dev@felix ... I wanted to attract as many as
> possible :-)
>
> [1] http://wiki.apache.org/incubator/AriesProposal
>
> Thanks,
> Jeremy
>
> 2009/9/5 Davanum Srinivas <da...@gmail.com>:
>> Karl,
>>
>> Please don't get me wrong. Felix is choice for an excellent *destination*
>> TLP. The Incubator PMC itself was setup to take away the responsibility for
>> training incoming folks from existing TLP(s). So my gut feeling is that we
>> should allow the incubation process to go on and decide on destination and
>> scope once the project is ready to graduate. I am sure the folks on the
>> proposal would love to get any and every help they can get to graduate as
>> well as on the technical front. Please do continue to provide help and
>> guidance.
>>
>> thanks,
>> dims
>>
>> On 09/05/2009 10:29 AM, Karl Pauls wrote:
>>>
>>> On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivas<da...@gmail.com>
>>>  wrote:
>>>>
>>>> Karl,
>>>>
>>>> There are *many* TLP(s) with overlapping scope as James Strachan pointed
>>>> out
>>>> earlier in the thread.
>>>>
>>>>
>>>> I don't see the need to shoe horn a new community with new code into an
>>>> existing TLP just because of scope. For all you know by the time they get
>>>> out of the incubator their scope may change a bit (or more).
>>>
>>> I'm sorry if it looked like I wanted to shoe horn anything into felix.
>>> That wasn't my goal as for me it was a question of where I would like
>>> it to happen and as I said earlier already, not the end of the world
>>> if not.
>>>
>>> regards,
>>>
>>> Karl
>>>
>>>> thanks,
>>>> dims
>>>>
>>>> On 09/05/2009 04:31 AM, Karl Pauls wrote:
>>>>>
>>>>> The question
>>>>> is about the scope and goals of Aries and more specifically about the
>>>>> part where it is about being an umbrella for OSGi EE spec
>>>>> implementations where it has been argued that this could/should be
>>>>> done at felix
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Ian Robinson <ia...@googlemail.com>.
Peter Peshev wrote:
> Anyway - after reading the proposal , my mental model for Aries is the
> following -   a group of bundles or web archives (here comes RFC 66 )
> are grouped via a new extended SCA component type (
> implementation.osgi_application)  or perhaps inherit from the
> implementation.jee that is in the spec.  
An SCA component type describing a collection of bundles is certainly 
what you'd want to see in the SCA services view of the world. There's 
probably a step before that though, for homogenous OSGi assemblies, that 
describes the modularity characteristics of a group of OSGi bundles in a 
more local OSGi dialect (perhaps in the form of a manifest for the group 
of bundles). In such a form that an SCA component type can be derived.
> Since big part of the
> enterprise scenarios are addressing already existing applications,
> there could be an existing code that  uses JMS resources.  I was kind
> of assuming that the definition for those would be  done via the
> standard SCA  binding.jms  -- the application developer should define
> in the SCA artifacts via binding.jms  the resources  used  from the
> code either via @Reference or via a pure JMS API call. So in a way
> Aries would be the glue code - reading the SCA xml-s and propagating
> to all the other involved parties what is needed. For the JMS broker
> case -- create the destinations and factories. For the OSGi runtime -
> provide the bundles.
>   
I can see (at least) 2 ways of looking at JMS: (i) where a component 
programmer wishes to use the JMS API and programing model. For example 
the Aries blueprint container should be able to provide a means for a 
component to declare a reference to a JMS provider (along with its 
configuration) which is resolved through the service registry and 
injected into the component. (ii) where the  component programmer 
doesn't much care about JMS but the deployer specifies JMS resources in 
a remote services binding. For an SCA component these definitions would 
be part of a binding.jms and I think there's potential for some 
Aries/Tuscany collaboration around this.


I'm sure there's plenty of further detail we can discuss around these 
ideas, although that might be better done on the Aries mailing list if 
the proposal is accepted for incubation.

Regards,
Ian Robinson

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Peter Peshev <pp...@gmail.com>.
Hi Jeremy,

No I don't feel strongly for this, I am not suggesting a change of the
proposal,  I am just trying to build a detailed picture for myself
(and perhaps for the community) what exactly some parts of Aries
project would look like.  I am not Apache experienced, so I am not
sure whether I should have the discusison here  or wait till the
proposal is voted and trigger it on the Aries mailing list if
accepted, since those are really technical details.  So please stop me
if you feel like it's not the right time

Anyway - after reading the proposal , my mental model for Aries is the
following -   a group of bundles or web archives (here comes RFC 66 )
are grouped via a new extended SCA component type (
implementation.osgi_application)  or perhaps inherit from the
implementation.jee that is in the spec.  Since big part of the
enterprise scenarios are addressing already existing applications,
there could be an existing code that  uses JMS resources.  I was kind
of assuming that the definition for those would be  done via the
standard SCA  binding.jms  -- the application developer should define
in the SCA artifacts via binding.jms  the resources  used  from the
code either via @Reference or via a pure JMS API call. So in a way
Aries would be the glue code - reading the SCA xml-s and propagating
to all the other involved parties what is needed. For the JMS broker
case -- create the destinations and factories. For the OSGi runtime -
provide the bundles.

It's a JMS scenario but the same model is valid  to the other stuff if
there is interest to integrate - JCA, web services, proprietary SCA
bindings for backend connectivity, etc..

Is this correct, or I am describing something totally new and
different than what you are proposing?


Best regards
Peter

On Thu, Sep 10, 2009 at 10:18 PM, Jeremy Hughes <hu...@apache.org> wrote:
> Sorry, I didn't mean we would exclude applications from using the JMS
> API. There are cases where a Blueprint component isn't concerned what
> async comms is being used, and there are times when that level of
> detail is needed. There are many use cases which of course we haven't
> thought about and that is a reason why we're coming to Apache - to
> explore that. So the proposal is the initial scope and the project
> will hopefully grow from there. If you feel strongly about it then we
> can add something to the proposal.
>
> Thanks,
> Jeremy
>
> 2009/9/10 Peter Peshev <pp...@gmail.com>:
>> Hi Jeremy,
>>
>> Well, I had some other use cases in mind besides "Message driven
>> Blueprint components"
>>
>> At least in my view JMS API is quite popular and  stable  so it's not
>> a rare case to be used from web applications as it is. An interesting
>> use case would be the resource provisioning. I would expect that
>> those "deployable units"  mentioned in the proposal could bring as
>> well metainformation about  JMS resources (connection factories,
>> destinations) that are going to be used from the application  and I
>> would expect the Aries would be the glue code between the resource
>> creation in the JMS broker and the deployment.
>>
>> Best regards
>> Peter
>>
>> On Thu, Sep 10, 2009 at 11:59 AM, Jeremy Hughes <hu...@apache.org> wrote:
>>> 2009/9/8 Peter Peshev <pp...@gmail.com>:
>>>> Hi Jeremy,
>>>>
>>>> Since you are asking about potential committers - at least to me a new
>>>> OSGi project focused on Java EE sounds quite interesting.
>>>>
>>>> Btw, when looking at the proposal I would  personally suggest even to
>>>> expand the scope and include other Java enterprise concepts - for
>>>> example integration with JMS (i.e. ActiveMQ) , JCA resource adapters ,
>>>> or addressing the usecase for integration of  non-Apache Java EE
>>>> components (EclipseLink, etc.). Would you consider these as in scope
>>>> for the project ?
>>>
>>> I think these are in scope. They're just not explicitly called out in
>>> the proposal. On the asynchronous messaging side, we do call out
>>> "Message driven Blueprint components" which would (potentially) use
>>> JMS to achieve that.
>>>
>>> Thanks,
>>> Jeremy
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
Sorry, I didn't mean we would exclude applications from using the JMS
API. There are cases where a Blueprint component isn't concerned what
async comms is being used, and there are times when that level of
detail is needed. There are many use cases which of course we haven't
thought about and that is a reason why we're coming to Apache - to
explore that. So the proposal is the initial scope and the project
will hopefully grow from there. If you feel strongly about it then we
can add something to the proposal.

Thanks,
Jeremy

2009/9/10 Peter Peshev <pp...@gmail.com>:
> Hi Jeremy,
>
> Well, I had some other use cases in mind besides "Message driven
> Blueprint components"
>
> At least in my view JMS API is quite popular and  stable  so it's not
> a rare case to be used from web applications as it is. An interesting
> use case would be the resource provisioning. I would expect that
> those "deployable units"  mentioned in the proposal could bring as
> well metainformation about  JMS resources (connection factories,
> destinations) that are going to be used from the application  and I
> would expect the Aries would be the glue code between the resource
> creation in the JMS broker and the deployment.
>
> Best regards
> Peter
>
> On Thu, Sep 10, 2009 at 11:59 AM, Jeremy Hughes <hu...@apache.org> wrote:
>> 2009/9/8 Peter Peshev <pp...@gmail.com>:
>>> Hi Jeremy,
>>>
>>> Since you are asking about potential committers - at least to me a new
>>> OSGi project focused on Java EE sounds quite interesting.
>>>
>>> Btw, when looking at the proposal I would  personally suggest even to
>>> expand the scope and include other Java enterprise concepts - for
>>> example integration with JMS (i.e. ActiveMQ) , JCA resource adapters ,
>>> or addressing the usecase for integration of  non-Apache Java EE
>>> components (EclipseLink, etc.). Would you consider these as in scope
>>> for the project ?
>>
>> I think these are in scope. They're just not explicitly called out in
>> the proposal. On the asynchronous messaging side, we do call out
>> "Message driven Blueprint components" which would (potentially) use
>> JMS to achieve that.
>>
>> Thanks,
>> Jeremy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Peter Peshev <pp...@gmail.com>.
Hi Jeremy,

Well, I had some other use cases in mind besides "Message driven
Blueprint components"

At least in my view JMS API is quite popular and  stable  so it's not
a rare case to be used from web applications as it is. An interesting
use case would be the resource provisioning. I would expect that
those "deployable units"  mentioned in the proposal could bring as
well metainformation about  JMS resources (connection factories,
destinations) that are going to be used from the application  and I
would expect the Aries would be the glue code between the resource
creation in the JMS broker and the deployment.

Best regards
Peter

On Thu, Sep 10, 2009 at 11:59 AM, Jeremy Hughes <hu...@apache.org> wrote:
> 2009/9/8 Peter Peshev <pp...@gmail.com>:
>> Hi Jeremy,
>>
>> Since you are asking about potential committers - at least to me a new
>> OSGi project focused on Java EE sounds quite interesting.
>>
>> Btw, when looking at the proposal I would  personally suggest even to
>> expand the scope and include other Java enterprise concepts - for
>> example integration with JMS (i.e. ActiveMQ) , JCA resource adapters ,
>> or addressing the usecase for integration of  non-Apache Java EE
>> components (EclipseLink, etc.). Would you consider these as in scope
>> for the project ?
>
> I think these are in scope. They're just not explicitly called out in
> the proposal. On the asynchronous messaging side, we do call out
> "Message driven Blueprint components" which would (potentially) use
> JMS to achieve that.
>
> Thanks,
> Jeremy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
2009/9/8 Peter Peshev <pp...@gmail.com>:
> Hi Jeremy,
>
> Since you are asking about potential committers - at least to me a new
> OSGi project focused on Java EE sounds quite interesting.
>
> Btw, when looking at the proposal I would  personally suggest even to
> expand the scope and include other Java enterprise concepts - for
> example integration with JMS (i.e. ActiveMQ) , JCA resource adapters ,
> or addressing the usecase for integration of  non-Apache Java EE
> components (EclipseLink, etc.). Would you consider these as in scope
> for the project ?

I think these are in scope. They're just not explicitly called out in
the proposal. On the asynchronous messaging side, we do call out
"Message driven Blueprint components" which would (potentially) use
JMS to achieve that.

Thanks,
Jeremy

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Peter Peshev <pp...@gmail.com>.
Hi Jeremy,

Since you are asking about potential committers - at least to me a new
OSGi project focused on Java EE sounds quite interesting.

Btw, when looking at the proposal I would  personally suggest even to
expand the scope and include other Java enterprise concepts - for
example integration with JMS (i.e. ActiveMQ) , JCA resource adapters ,
or addressing the usecase for integration of  non-Apache Java EE
components (EclipseLink, etc.). Would you consider these as in scope
for the project ?

Best Regards
Peter Peshev

On Mon, Sep 7, 2009 at 5:57 PM, Jeremy Hughes<hu...@apache.org> wrote:
> Cross-pollination and help from the Felix community have been talked
> about several times and I absolutely welcome that. As such, please
> would Felix committers willing to spend time helping the (proposed)
> Aries podling add their names to the initial committer list on the
> proposal wiki [1]. This naturally extends beyond Felix committers.
>
> Apologies for x-post to dev@felix ... I wanted to attract as many as
> possible :-)
>
> [1] http://wiki.apache.org/incubator/AriesProposal
>
> Thanks,
> Jeremy
>
> 2009/9/5 Davanum Srinivas <da...@gmail.com>:
>> Karl,
>>
>> Please don't get me wrong. Felix is choice for an excellent *destination*
>> TLP. The Incubator PMC itself was setup to take away the responsibility for
>> training incoming folks from existing TLP(s). So my gut feeling is that we
>> should allow the incubation process to go on and decide on destination and
>> scope once the project is ready to graduate. I am sure the folks on the
>> proposal would love to get any and every help they can get to graduate as
>> well as on the technical front. Please do continue to provide help and
>> guidance.
>>
>> thanks,
>> dims
>>
>> On 09/05/2009 10:29 AM, Karl Pauls wrote:
>>>
>>> On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivas<da...@gmail.com>
>>>  wrote:
>>>>
>>>> Karl,
>>>>
>>>> There are *many* TLP(s) with overlapping scope as James Strachan pointed
>>>> out
>>>> earlier in the thread.
>>>>
>>>>
>>>> I don't see the need to shoe horn a new community with new code into an
>>>> existing TLP just because of scope. For all you know by the time they get
>>>> out of the incubator their scope may change a bit (or more).
>>>
>>> I'm sorry if it looked like I wanted to shoe horn anything into felix.
>>> That wasn't my goal as for me it was a question of where I would like
>>> it to happen and as I said earlier already, not the end of the world
>>> if not.
>>>
>>> regards,
>>>
>>> Karl
>>>
>>>> thanks,
>>>> dims
>>>>
>>>> On 09/05/2009 04:31 AM, Karl Pauls wrote:
>>>>>
>>>>> The question
>>>>> is about the scope and goals of Aries and more specifically about the
>>>>> part where it is about being an umbrella for OSGi EE spec
>>>>> implementations where it has been argued that this could/should be
>>>>> done at felix
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
Cross-pollination and help from the Felix community have been talked
about several times and I absolutely welcome that. As such, please
would Felix committers willing to spend time helping the (proposed)
Aries podling add their names to the initial committer list on the
proposal wiki [1]. This naturally extends beyond Felix committers.

Apologies for x-post to dev@felix ... I wanted to attract as many as
possible :-)

[1] http://wiki.apache.org/incubator/AriesProposal

Thanks,
Jeremy

2009/9/5 Davanum Srinivas <da...@gmail.com>:
> Karl,
>
> Please don't get me wrong. Felix is choice for an excellent *destination*
> TLP. The Incubator PMC itself was setup to take away the responsibility for
> training incoming folks from existing TLP(s). So my gut feeling is that we
> should allow the incubation process to go on and decide on destination and
> scope once the project is ready to graduate. I am sure the folks on the
> proposal would love to get any and every help they can get to graduate as
> well as on the technical front. Please do continue to provide help and
> guidance.
>
> thanks,
> dims
>
> On 09/05/2009 10:29 AM, Karl Pauls wrote:
>>
>> On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivas<da...@gmail.com>
>>  wrote:
>>>
>>> Karl,
>>>
>>> There are *many* TLP(s) with overlapping scope as James Strachan pointed
>>> out
>>> earlier in the thread.
>>>
>>>
>>> I don't see the need to shoe horn a new community with new code into an
>>> existing TLP just because of scope. For all you know by the time they get
>>> out of the incubator their scope may change a bit (or more).
>>
>> I'm sorry if it looked like I wanted to shoe horn anything into felix.
>> That wasn't my goal as for me it was a question of where I would like
>> it to happen and as I said earlier already, not the end of the world
>> if not.
>>
>> regards,
>>
>> Karl
>>
>>> thanks,
>>> dims
>>>
>>> On 09/05/2009 04:31 AM, Karl Pauls wrote:
>>>>
>>>> The question
>>>> is about the scope and goals of Aries and more specifically about the
>>>> part where it is about being an umbrella for OSGi EE spec
>>>> implementations where it has been argued that this could/should be
>>>> done at felix
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
Cross-pollination and help from the Felix community have been talked
about several times and I absolutely welcome that. As such, please
would Felix committers willing to spend time helping the (proposed)
Aries podling add their names to the initial committer list on the
proposal wiki [1]. This naturally extends beyond Felix committers.

Apologies for x-post to dev@felix ... I wanted to attract as many as
possible :-)

[1] http://wiki.apache.org/incubator/AriesProposal

Thanks,
Jeremy

2009/9/5 Davanum Srinivas <da...@gmail.com>:
> Karl,
>
> Please don't get me wrong. Felix is choice for an excellent *destination*
> TLP. The Incubator PMC itself was setup to take away the responsibility for
> training incoming folks from existing TLP(s). So my gut feeling is that we
> should allow the incubation process to go on and decide on destination and
> scope once the project is ready to graduate. I am sure the folks on the
> proposal would love to get any and every help they can get to graduate as
> well as on the technical front. Please do continue to provide help and
> guidance.
>
> thanks,
> dims
>
> On 09/05/2009 10:29 AM, Karl Pauls wrote:
>>
>> On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivas<da...@gmail.com>
>>  wrote:
>>>
>>> Karl,
>>>
>>> There are *many* TLP(s) with overlapping scope as James Strachan pointed
>>> out
>>> earlier in the thread.
>>>
>>>
>>> I don't see the need to shoe horn a new community with new code into an
>>> existing TLP just because of scope. For all you know by the time they get
>>> out of the incubator their scope may change a bit (or more).
>>
>> I'm sorry if it looked like I wanted to shoe horn anything into felix.
>> That wasn't my goal as for me it was a question of where I would like
>> it to happen and as I said earlier already, not the end of the world
>> if not.
>>
>> regards,
>>
>> Karl
>>
>>> thanks,
>>> dims
>>>
>>> On 09/05/2009 04:31 AM, Karl Pauls wrote:
>>>>
>>>> The question
>>>> is about the scope and goals of Aries and more specifically about the
>>>> part where it is about being an umbrella for OSGi EE spec
>>>> implementations where it has been argued that this could/should be
>>>> done at felix
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Karl,

Please don't get me wrong. Felix is choice for an excellent *destination* TLP. The Incubator PMC itself was setup to 
take away the responsibility for training incoming folks from existing TLP(s). So my gut feeling is that we should allow 
the incubation process to go on and decide on destination and scope once the project is ready to graduate. I am sure the 
folks on the proposal would love to get any and every help they can get to graduate as well as on the technical front. 
Please do continue to provide help and guidance.

thanks,
dims

On 09/05/2009 10:29 AM, Karl Pauls wrote:
> On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivas<da...@gmail.com>  wrote:
>> Karl,
>>
>> There are *many* TLP(s) with overlapping scope as James Strachan pointed out
>> earlier in the thread.
>>
>>
>> I don't see the need to shoe horn a new community with new code into an
>> existing TLP just because of scope. For all you know by the time they get
>> out of the incubator their scope may change a bit (or more).
>
> I'm sorry if it looked like I wanted to shoe horn anything into felix.
> That wasn't my goal as for me it was a question of where I would like
> it to happen and as I said earlier already, not the end of the world
> if not.
>
> regards,
>
> Karl
>
>> thanks,
>> dims
>>
>> On 09/05/2009 04:31 AM, Karl Pauls wrote:
>>>
>>> The question
>>> is about the scope and goals of Aries and more specifically about the
>>> part where it is about being an umbrella for OSGi EE spec
>>> implementations where it has been argued that this could/should be
>>> done at felix
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Karl Pauls <ka...@gmail.com>.
On Sat, Sep 5, 2009 at 12:21 PM, Davanum Srinivas<da...@gmail.com> wrote:
> Karl,
>
> There are *many* TLP(s) with overlapping scope as James Strachan pointed out
> earlier in the thread.
>
>
> I don't see the need to shoe horn a new community with new code into an
> existing TLP just because of scope. For all you know by the time they get
> out of the incubator their scope may change a bit (or more).

I'm sorry if it looked like I wanted to shoe horn anything into felix.
That wasn't my goal as for me it was a question of where I would like
it to happen and as I said earlier already, not the end of the world
if not.

regards,

Karl

> thanks,
> dims
>
> On 09/05/2009 04:31 AM, Karl Pauls wrote:
>>
>> The question
>> is about the scope and goals of Aries and more specifically about the
>> part where it is about being an umbrella for OSGi EE spec
>> implementations where it has been argued that this could/should be
>> done at felix
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>



-- 
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Karl,

There are *many* TLP(s) with overlapping scope as James Strachan pointed out earlier in the thread.

I don't see the need to shoe horn a new community with new code into an existing TLP just because of scope. For all you 
know by the time they get out of the incubator their scope may change a bit (or more).

thanks,
dims

On 09/05/2009 04:31 AM, Karl Pauls wrote:
> The question
> is about the scope and goals of Aries and more specifically about the
> part where it is about being an umbrella for OSGi EE spec
> implementations where it has been argued that this could/should be
> done at felix

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Karl Pauls <ka...@gmail.com>.
On Sat, Sep 5, 2009 at 6:35 AM, Niclas Hedhman<ni...@hedhman.org> wrote:
> On Sat, Sep 5, 2009 at 4:31 AM, Richard S. Hall<he...@ungoverned.org> wrote:
>> On 9/4/09 16:10, Davanum Srinivas wrote:
>
>>> Choices are
>>>
>>> 1) Podling -> TLP
>>> 2) Podling -> Felix Sub project
>>> 3) Podling -> Felix Sub project -> TLP
>>> 4) Felix Sub project
>>> 5) Felix Sub project -> TLP
>>>
>>> So, why should we bypass incubator?
>
> No, AFAIK, that is not an option when a large bulk of the incoming
> community is new to ASF.
>
>> Again, there was already a project incubated to educate incoming folks on
>> how to create open source OSGi spec impls at Apache, so why do we need to
>> repeat that process?
>>
>> Your phrasing of this question implies we are trying to somehow skirt the
>> Apache way, but educating incoming people via contributions and meritocracy
>> to an existing project is not some shortcut.
>
> Yes, if you are accepting a large number of people into a TLP on the
> basis "they will create..." or "they donated...", then that PMC is
> "skirting the Apache way".

Where in the above "but educating incoming people via contributions
and meritocracy to an existing project is not some shortcut" do you
find anything that would imply that the idea is to just accept a large
number of people into a TLP? I think that we at Felix never did just
vote in people on the basis "they will create...". Sometimes we do
accept people new to the ASF on the basis "they donated..." but only
if we are talking about individual (i.e., 1 or 2) contributors which
either have been around for  a while or had somebody on the PMC who
did speak up for them personally.

> My stance has been that if a code donation
> include 1 or 2 new people, then that can be handled that way, but 9
> people on that basis will/should probably not fly. Considering the
> large number of ASF members and committers on the rooster, this is
> perhaps a border case, but since it is said that "not much code
> exist", then I also suspect that the rooster is 'rigged' with people
> in the organization that has a general interest and strong ASF
> affilliation and that the non-ASFers are those who are expected to do
> most of the work.

That still wouldn't prevent them from contributing to other projects
as you are probably well aware.

> Hence, the group's decision to come to Incubator is a correct one.

And nobody has been questioning that as far as I can see. The question
is about the scope and goals of Aries and more specifically about the
part where it is about being an umbrella for OSGi EE spec
implementations where it has been argued that this could/should be
done at felix while the more general part of building an enterprise
component model on top of OSGi could/should very well be a new
incubator project. This is different from saying that the group's
decision to come to Incubator is an incorrect one...

> Where it graduates to is a different story, and I can leave that
> question for later. And the Felix community is encouraged to follow
> and participate the Aries effort.

As I'm sure at least some if not all of us will. The has never been a
question either imo. The question in this regard was and is purely to
what extend Felix people interested in the OSGi EE spec
implementations only have to get involved in the (more general) Aries
project and how quickly OSGi EE spec implementations can be released
as none incubator artifacts.

And one more time (just in case it was missed earlier): let me point
out that nobody is talking about Aries as a Felix "incubator" project
nor (at least at this point in time) about a possible subproject of
Felix after graduation. We are only talking about the OSGi EE spec
implementations that are part of the proposed Aries scope.

regards,

Karl

> I think this discussion is more or less over.
>
> Unless it was missed earlier; My +1 for incubation.
>
>
> Cheers
> --
> Niclas Hedhman, Software Developer
> http://www.qi4j.org - New Energy for Java
>
> I  live here; http://tinyurl.com/2qq9er
> I  work here; http://tinyurl.com/2ymelc
> I relax here; http://tinyurl.com/2cgsug
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>



-- 
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Sat, Sep 5, 2009 at 4:31 AM, Richard S. Hall<he...@ungoverned.org> wrote:
> On 9/4/09 16:10, Davanum Srinivas wrote:

>> Choices are
>>
>> 1) Podling -> TLP
>> 2) Podling -> Felix Sub project
>> 3) Podling -> Felix Sub project -> TLP
>> 4) Felix Sub project
>> 5) Felix Sub project -> TLP
>>
>> So, why should we bypass incubator?

No, AFAIK, that is not an option when a large bulk of the incoming
community is new to ASF.

> Again, there was already a project incubated to educate incoming folks on
> how to create open source OSGi spec impls at Apache, so why do we need to
> repeat that process?
>
> Your phrasing of this question implies we are trying to somehow skirt the
> Apache way, but educating incoming people via contributions and meritocracy
> to an existing project is not some shortcut.

Yes, if you are accepting a large number of people into a TLP on the
basis "they will create..." or "they donated...", then that PMC is
"skirting the Apache way". My stance has been that if a code donation
include 1 or 2 new people, then that can be handled that way, but 9
people on that basis will/should probably not fly. Considering the
large number of ASF members and committers on the rooster, this is
perhaps a border case, but since it is said that "not much code
exist", then I also suspect that the rooster is 'rigged' with people
in the organization that has a general interest and strong ASF
affilliation and that the non-ASFers are those who are expected to do
most of the work.

Hence, the group's decision to come to Incubator is a correct one.
Where it graduates to is a different story, and I can leave that
question for later. And the Felix community is encouraged to follow
and participate the Aries effort.

I think this discussion is more or less over.

Unless it was missed earlier; My +1 for incubation.


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Karl Pauls <ka...@gmail.com>.
On Fri, Sep 4, 2009 at 10:31 PM, Richard S. Hall<he...@ungoverned.org> wrote:
> On 9/4/09 16:10, Davanum Srinivas wrote:
>>
>> Richard,
>>
>> On 09/04/2009 03:49 PM, Richard S. Hall wrote:
>>>
>>> So, no, I am not saying "everything should", but in general, it would be
>>> nice if the spec impls started there since we have a community of OSGi
>>> users and OSGi experts who are very active and receptive, many of whom
>>> also work in the EE space.
>>
>> Will the people mentioned not participate if Aries is a separate podling
>> to start with? After all destination PMC can be determined during graduation
>> process. Also the incubation process is to show new incoming team how Apache
>> works etc..is that better done as a podling or as a felix sub project? If we
>> continue the same thought process, will there every be any incubator podling
>> with for any OSGi related activity?
>
> Yes, and I mentioned this, but that seems to get lost somehow.

And as others have mentioned too there are already a couple like e.g.,
Sling (started in the incubator now a TLP) and Ace (recently accepted
to the incubator).

regards,

Karl

>>> In short, it makes sense for spec impls tied to the Aries component
>>> model (for example), to be hosted there, but there is little need to
>>> create another project to incubate generic OSGi spec impls, since the
>>> Felix community was set up for that. The reality is, most OSGi specs are
>>> not huge projects so we likely wouldn't want TLPs for all of them, but
>>> nothing stops a subproject started at Felix from going TLP if it takes
>>> on a life of its own.
>>
>> Choices are
>>
>> 1) Podling -> TLP
>> 2) Podling -> Felix Sub project
>> 3) Podling -> Felix Sub project -> TLP
>> 4) Felix Sub project
>> 5) Felix Sub project -> TLP
>>
>> The first 3 effectively uses incubator process(es) to educate the incoming
>> folks and provides a strong grounding in ASF-land (at least that is what the
>> intention is :)
>>
>> So, why should we bypass incubator?
>
> Again, there was already a project incubated to educate incoming folks on
> how to create open source OSGi spec impls at Apache, so why do we need to
> repeat that process?
>
> Your phrasing of this question implies we are trying to somehow skirt the
> Apache way, but educating incoming people via contributions and meritocracy
> to an existing project is not some shortcut.
>
> -> richard
>
>>
>> thanks,
>> dims
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>



-- 
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 9/4/09 16:10, Davanum Srinivas wrote:
> Richard,
>
> On 09/04/2009 03:49 PM, Richard S. Hall wrote:
>> So, no, I am not saying "everything should", but in general, it would be
>> nice if the spec impls started there since we have a community of OSGi
>> users and OSGi experts who are very active and receptive, many of whom
>> also work in the EE space.
>
> Will the people mentioned not participate if Aries is a separate 
> podling to start with? After all destination PMC can be determined 
> during graduation process. Also the incubation process is to show new 
> incoming team how Apache works etc..is that better done as a podling 
> or as a felix sub project? If we continue the same thought process, 
> will there every be any incubator podling with for any OSGi related 
> activity?

Yes, and I mentioned this, but that seems to get lost somehow.

>> In short, it makes sense for spec impls tied to the Aries component
>> model (for example), to be hosted there, but there is little need to
>> create another project to incubate generic OSGi spec impls, since the
>> Felix community was set up for that. The reality is, most OSGi specs are
>> not huge projects so we likely wouldn't want TLPs for all of them, but
>> nothing stops a subproject started at Felix from going TLP if it takes
>> on a life of its own.
>
> Choices are
>
> 1) Podling -> TLP
> 2) Podling -> Felix Sub project
> 3) Podling -> Felix Sub project -> TLP
> 4) Felix Sub project
> 5) Felix Sub project -> TLP
>
> The first 3 effectively uses incubator process(es) to educate the 
> incoming folks and provides a strong grounding in ASF-land (at least 
> that is what the intention is :)
>
> So, why should we bypass incubator?

Again, there was already a project incubated to educate incoming folks 
on how to create open source OSGi spec impls at Apache, so why do we 
need to repeat that process?

Your phrasing of this question implies we are trying to somehow skirt 
the Apache way, but educating incoming people via contributions and 
meritocracy to an existing project is not some shortcut.

-> richard

>
> thanks,
> dims
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Richard,

On 09/04/2009 03:49 PM, Richard S. Hall wrote:
> So, no, I am not saying "everything should", but in general, it would be
> nice if the spec impls started there since we have a community of OSGi
> users and OSGi experts who are very active and receptive, many of whom
> also work in the EE space.

Will the people mentioned not participate if Aries is a separate podling to start with? After all destination PMC can be 
determined during graduation process. Also the incubation process is to show new incoming team how Apache works etc..is 
that better done as a podling or as a felix sub project? If we continue the same thought process, will there every be 
any incubator podling with for any OSGi related activity?

> In short, it makes sense for spec impls tied to the Aries component
> model (for example), to be hosted there, but there is little need to
> create another project to incubate generic OSGi spec impls, since the
> Felix community was set up for that. The reality is, most OSGi specs are
> not huge projects so we likely wouldn't want TLPs for all of them, but
> nothing stops a subproject started at Felix from going TLP if it takes
> on a life of its own.

Choices are

1) Podling -> TLP
2) Podling -> Felix Sub project
3) Podling -> Felix Sub project -> TLP
4) Felix Sub project
5) Felix Sub project -> TLP

The first 3 effectively uses incubator process(es) to educate the incoming folks and provides a strong grounding in 
ASF-land (at least that is what the intention is :)

So, why should we bypass incubator?

thanks,
dims

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 9/4/09 9:05, Daniel Kulp wrote:
> As a point of note, not all OSGi spec implementations live in Felix even at
> Apache today.   The Remote Services/Distributed OSGi reference implementation
> is a sub project of CXF.     I think Tuscany has an implementation as well.
>
> So far, there hasn't been any discussion about moving those into Felix.  Your
> argument below makes it sound like they should be.
>    

Actually, I had conversations with the CXF/DOSGi team at IONA during its 
development. We discussed the technological approach as well as the 
potential home. My position was/is:

   1. If it is tied to CXF and it not generally useful without it, then
      it is reasonable for it to be hosted at CXF.
   2. If it is completely general and of interest to a general user, not
      just a CXF user, then it is reasonable for it to be hosted at Felix.

Since they felt it was fairly specific to CXF, that's where it ended up.

So, no, I am not saying "everything should", but in general, it would be 
nice if the spec impls started there since we have a community of OSGi 
users and OSGi experts who are very active and receptive, many of whom 
also work in the EE space.

In short, it makes sense for spec impls tied to the Aries component 
model (for example), to be hosted there, but there is little need to 
create another project to incubate generic OSGi spec impls, since the 
Felix community was set up for that. The reality is, most OSGi specs are 
not huge projects so we likely wouldn't want TLPs for all of them, but 
nothing stops a subproject started at Felix from going TLP if it takes 
on a life of its own.

-> richard

> Dan
>
>
> On Thu September 3 2009 1:33:04 pm Richard S. Hall wrote:
>    
>> There was no attempt to contact the Felix PMC in general that I am aware
>> and I certainly didn't know about it in advance.
>>
>> And there seems to be a continued attempt to construe my original
>> criticisms as "all of Aries should go into Felix".
>>
>> I, personally, do not believe that all of Aries should go into Felix, I
>> too think it should have its own identity. I was always only ever
>> referring to the independent OSGi spec implementations. I was arguing
>> that Felix is a good place to work on them, since it is part of what it
>> is trying to achieve.
>>
>> Further, I don't really understand the implication that somehow the
>> burden is now on the Felix community to go and contribute to Aries on
>> OSGi spec implementations just because of this proposal, when there was
>> no attempt to work with the Felix community on creating OSGi spec
>> implementations in the first.
>>
>> The only conclusions I see being drawn by people who have invested very
>> little in Felix is that we should dismantle the Felix charter so that we
>> can accommodate the fact that some people don't want to play with us.
>>
>> At that rate, I stand by my previous "vote" and otherwise people can do
>> whatever they want in Aries.
>>
>> ->  richard
>>
>> On 9/3/09 13:23, Niclas Hedhman wrote:
>>      
>>> Kevan,
>>>
>>> Was a contact with Felix made prior to dropping the proposal here? I got
>>> the impression that wasn't the case, which I find surprising... If I am
>>> wrong, what was the meat of such?
>>>
>>> I'm also less happy with the rhetoric here repeated over and over,
>>> seemingly uninterested in discussion of reaching a solution everyone can
>>> accept. (From both camps, btw)
>>>
>>> -- Niclas
>>>
>>> On Sep 4, 2009 12:53 AM, "Kevan Miller"<ke...@gmail.com>   wrote:
>>>
>>> On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:>   On Thu, Sep 3, 2009
>>> at 3:19 AM, William A. Ro...
>>> Totally agree. Had certainly hoped that Felix committers would be
>>> interested in joining...
>>>
>>> --kevan
>>>
>>> --------------------------------------------------------------------- To
>>> unsubscribe, e-mail: gene...
>>>        
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>      
>    

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Daniel Kulp <dk...@apache.org>.
As a point of note, not all OSGi spec implementations live in Felix even at 
Apache today.   The Remote Services/Distributed OSGi reference implementation 
is a sub project of CXF.     I think Tuscany has an implementation as well.

So far, there hasn't been any discussion about moving those into Felix.  Your 
argument below makes it sound like they should be.

Dan


On Thu September 3 2009 1:33:04 pm Richard S. Hall wrote:
> There was no attempt to contact the Felix PMC in general that I am aware
> and I certainly didn't know about it in advance.
> 
> And there seems to be a continued attempt to construe my original
> criticisms as "all of Aries should go into Felix".
> 
> I, personally, do not believe that all of Aries should go into Felix, I
> too think it should have its own identity. I was always only ever
> referring to the independent OSGi spec implementations. I was arguing
> that Felix is a good place to work on them, since it is part of what it
> is trying to achieve.
> 
> Further, I don't really understand the implication that somehow the
> burden is now on the Felix community to go and contribute to Aries on
> OSGi spec implementations just because of this proposal, when there was
> no attempt to work with the Felix community on creating OSGi spec
> implementations in the first.
> 
> The only conclusions I see being drawn by people who have invested very
> little in Felix is that we should dismantle the Felix charter so that we
> can accommodate the fact that some people don't want to play with us.
> 
> At that rate, I stand by my previous "vote" and otherwise people can do
> whatever they want in Aries.
> 
> -> richard
> 
> On 9/3/09 13:23, Niclas Hedhman wrote:
> > Kevan,
> >
> > Was a contact with Felix made prior to dropping the proposal here? I got
> > the impression that wasn't the case, which I find surprising... If I am
> > wrong, what was the meat of such?
> >
> > I'm also less happy with the rhetoric here repeated over and over,
> > seemingly uninterested in discussion of reaching a solution everyone can
> > accept. (From both camps, btw)
> >
> > -- Niclas
> >
> > On Sep 4, 2009 12:53 AM, "Kevan Miller"<ke...@gmail.com>  wrote:
> >
> > On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:>  On Thu, Sep 3, 2009
> > at 3:19 AM, William A. Ro...
> > Totally agree. Had certainly hoped that Felix committers would be
> > interested in joining...
> >
> > --kevan
> >
> > --------------------------------------------------------------------- To
> > unsubscribe, e-mail: gene...
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Fri, Sep 4, 2009 at 12:48 PM, Kevan Miller<ke...@gmail.com> wrote:

> Perhaps could have been handled differently. However, in the end, I much
> prefer holding a public discussion rather than over a private@ list.

Well, the leads to the sense of "exclusion" instead of "inclusion"
which we very much prefer.

> Hoping we can move the conversation forward...

I don't know the technical status of this, but I can't for my life see
that it should pose a problem for Aries if the OSGi spec
implementations are going under the Felix hood. That would make
Richard happy, and if that there is entangled code where some bits
definitely should end up in the spec impl part, then ask Felix
committers to stop demanding and come in and help do the separation.
If they are not available to do so (for whatever reason), then you
have the right to tell them to shut up on the basis of "He who does,
decides." and you guys have done your part.

All this can happen while in incubation, and again, if Felix guys
think that they don't have the time, the energy or just "why should
we...", then the issue is in my book solved by default.


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Kevan,

On Sep 4, 2009, at 6:48 , Kevan Miller wrote:

> On Sep 3, 2009, at 1:23 PM, Niclas Hedhman wrote:
>
>> Was a contact with Felix made prior to dropping the proposal here?  
>> I got the
>> impression that wasn't the case, which I find surprising... If I am  
>> wrong,
>> what was the meat of such?
>
> No. There were some internal sensitivities to the timing of the  
> proposal (given the code donation and other rigamarole). Contacting  
> the Felix PMC prior to proposal submission would have required  
> additional approval... Perhaps could have been handled differently.  
> However, in the end, I much prefer holding a public discussion  
> rather than over a private@ list.


I agree with you that a private@ list discussion would not have been  
the best way, but I don't see why that discussion could not have  
happened on the dev@ list. Anyway, it's in the past now, we should  
look forward and look for ways help each other.

Greetings, Marcel


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Kevan Miller <ke...@gmail.com>.
On Sep 3, 2009, at 1:23 PM, Niclas Hedhman wrote:

> Kevan,
>
> Was a contact with Felix made prior to dropping the proposal here? I  
> got the
> impression that wasn't the case, which I find surprising... If I am  
> wrong,
> what was the meat of such?

No. There were some internal sensitivities to the timing of the  
proposal (given the code donation and other rigamarole). Contacting  
the Felix PMC prior to proposal submission would have required  
additional approval... Perhaps could have been handled differently.  
However, in the end, I much prefer holding a public discussion rather  
than over a private@ list.

>
> I'm also less happy with the rhetoric here repeated over and over,  
> seemingly
> uninterested in discussion of reaching a solution everyone can  
> accept. (From
> both camps, btw)

That's totally valid criticism, IMO, and I've had the same reaction...  
Hoping we can move the conversation forward...

--kevan 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
On 9/3/09 14:37, Ian Robinson wrote:
> The discussion on this part of the proposal reflects the origins of it 
> - people with an interest in AppServers and integration runtimes that 
> are looking to the new EEG specs to provide additional capability in 
> their world so that existing applications can begin to take advantage 
> of OSGi with minimum barrier to entry. There will be tensions in 
> implementing the specs to work in a way that reflects how these apps 
> are built today vs how we'd start afresh given that opportunity. When 
> the question "why do we need to accomodate the baggage of XYZ in the 
> servlet/JNDI/JTA/JMX/JPA/... spec comes up it will be the AppServer 
> and integration runtime folks who have the need for accomodating the 
> quirkier corners of "legacy" Java EE behaviour. They are going to have 
> a perspective that is a little different from one whose success 
> criteria is OSGi spec compliance without a need to additionally 
> accomodate some of the warts, or integrate with some of the other 
> features, of Java EE. Given this slightly different perspective (and 
> the warts) it is perhaps understandable that a community with this 
> interest might see value in developing its own culture within the laws 
> of the (Apache) land, while living in peace with its neighbours.

Agreed it is important goal for your spec impls to support legacy, but 
you seem to have some misconception about the amount of top-down control 
exerted on Felix subprojects. Each subproject is pretty much free to do 
whatever it wants as far as the implementation approach is concerned, 
which is why we allow competing implementations within Felix.

-> richard

>
> Ian Robinson
>
> Richard S. Hall wrote:
>> There was no attempt to contact the Felix PMC in general that I am 
>> aware and I certainly didn't know about it in advance.
>>
>> And there seems to be a continued attempt to construe my original 
>> criticisms as "all of Aries should go into Felix".
>>
>> I, personally, do not believe that all of Aries should go into Felix, 
>> I too think it should have its own identity. I was always only ever 
>> referring to the independent OSGi spec implementations. I was arguing 
>> that Felix is a good place to work on them, since it is part of what 
>> it is trying to achieve.
>>
>> Further, I don't really understand the implication that somehow the 
>> burden is now on the Felix community to go and contribute to Aries on 
>> OSGi spec implementations just because of this proposal, when there 
>> was no attempt to work with the Felix community on creating OSGi spec 
>> implementations in the first.
>>
>> The only conclusions I see being drawn by people who have invested 
>> very little in Felix is that we should dismantle the Felix charter so 
>> that we can accommodate the fact that some people don't want to play 
>> with us.
>>
>> At that rate, I stand by my previous "vote" and otherwise people can 
>> do whatever they want in Aries.
>>
>> -> richard
>>
>> On 9/3/09 13:23, Niclas Hedhman wrote:
>>> Kevan,
>>>
>>> Was a contact with Felix made prior to dropping the proposal here? I 
>>> got the
>>> impression that wasn't the case, which I find surprising... If I am 
>>> wrong,
>>> what was the meat of such?
>>>
>>> I'm also less happy with the rhetoric here repeated over and over, 
>>> seemingly
>>> uninterested in discussion of reaching a solution everyone can 
>>> accept. (From
>>> both camps, btw)
>>>
>>> -- Niclas
>>>
>>> On Sep 4, 2009 12:53 AM, "Kevan Miller"<ke...@gmail.com>  wrote:
>>>
>>> On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:>  On Thu, Sep 3, 
>>> 2009 at
>>> 3:19 AM, William A. Ro...
>>> Totally agree. Had certainly hoped that Felix committers would be 
>>> interested
>>> in joining...
>>>
>>> --kevan
>>>
>>> --------------------------------------------------------------------- To 
>>>
>>> unsubscribe, e-mail: gene...
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Ian Robinson <ia...@googlemail.com>.
The discussion on this part of the proposal reflects the origins of it - 
people with an interest in AppServers and integration runtimes that are 
looking to the new EEG specs to provide additional capability in their 
world so that existing applications can begin to take advantage of OSGi 
with minimum barrier to entry. There will be tensions in implementing 
the specs to work in a way that reflects how these apps are built today 
vs how we'd start afresh given that opportunity. When the question "why 
do we need to accomodate the baggage of XYZ in the 
servlet/JNDI/JTA/JMX/JPA/... spec comes up it will be the AppServer and 
integration runtime folks who have the need for accomodating the 
quirkier corners of "legacy" Java EE behaviour. They are going to have a 
perspective that is a little different from one whose success criteria 
is OSGi spec compliance without a need to additionally accomodate some 
of the warts, or integrate with some of the other features, of Java EE. 
Given this slightly different perspective (and the warts) it is perhaps 
understandable that a community with this interest might see value in 
developing its own culture within the laws of the (Apache) land, while 
living in peace with its neighbours.

Ian Robinson

Richard S. Hall wrote:
> There was no attempt to contact the Felix PMC in general that I am 
> aware and I certainly didn't know about it in advance.
>
> And there seems to be a continued attempt to construe my original 
> criticisms as "all of Aries should go into Felix".
>
> I, personally, do not believe that all of Aries should go into Felix, 
> I too think it should have its own identity. I was always only ever 
> referring to the independent OSGi spec implementations. I was arguing 
> that Felix is a good place to work on them, since it is part of what 
> it is trying to achieve.
>
> Further, I don't really understand the implication that somehow the 
> burden is now on the Felix community to go and contribute to Aries on 
> OSGi spec implementations just because of this proposal, when there 
> was no attempt to work with the Felix community on creating OSGi spec 
> implementations in the first.
>
> The only conclusions I see being drawn by people who have invested 
> very little in Felix is that we should dismantle the Felix charter so 
> that we can accommodate the fact that some people don't want to play 
> with us.
>
> At that rate, I stand by my previous "vote" and otherwise people can 
> do whatever they want in Aries.
>
> -> richard
>
> On 9/3/09 13:23, Niclas Hedhman wrote:
>> Kevan,
>>
>> Was a contact with Felix made prior to dropping the proposal here? I 
>> got the
>> impression that wasn't the case, which I find surprising... If I am 
>> wrong,
>> what was the meat of such?
>>
>> I'm also less happy with the rhetoric here repeated over and over, 
>> seemingly
>> uninterested in discussion of reaching a solution everyone can 
>> accept. (From
>> both camps, btw)
>>
>> -- Niclas
>>
>> On Sep 4, 2009 12:53 AM, "Kevan Miller"<ke...@gmail.com>  wrote:
>>
>> On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:>  On Thu, Sep 3, 
>> 2009 at
>> 3:19 AM, William A. Ro...
>> Totally agree. Had certainly hoped that Felix committers would be 
>> interested
>> in joining...
>>
>> --kevan
>>
>> --------------------------------------------------------------------- To
>> unsubscribe, e-mail: gene...
>>
>>    
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
For things that come from ServiceMix, I think the story is really
different.   ServiceMix TLP charter is the following:  "an extensible
messaging bus for service integration, mediation and composition and its
related components".   So clearly, Karaf, as an enhanced OSGi runtime
distribution, does not really fit in ServiceMix.

However, the ASF has never prevented two projects to have overlapping
charters.  And the scope of Aries is much more narrow than Felix to avoid
becoming an umbrella project with lots of disjoint communities.


On Fri, Sep 4, 2009 at 15:03, Karl Pauls <ka...@gmail.com> wrote:

> Let me point out one more time: Nobody is talking about Aries as a
> Felix "incubator" project. We are only talking about the OSGi EE spec
> implementations that are part of the proposed Aries scope.
>
> I'd be more then happy to see the rest of the proposal (namely, to
> explore how to build an enterprise component model on OSGi and the
> other non-spec related topics) become a reality by means of a new
> incubator project. Whether that ends-up as a felix sub-project or as a
> sub-project or TLP in the end we don't have to discuss right now.
>
> In regard to the other half of the proposal I do think you would be
> better off to develop them over at Felix and I'm sure we would be more
> then happy to support you and find solutions to any issues you might
> have (as we recently did with karaf). Not the end of the world if not
> but not what I would prefer nor see as the best solutions for neither
> Felix nor Aries.
>
> regards,
>
> Karl
>
> On Fri, Sep 4, 2009 at 1:51 PM, Guillaume Nodet<gn...@gmail.com> wrote:
> > There are a few things I don't understand well.   I thought the ASF over
> the
> > past years was trying to discourage umbrella projects.   I also thought
> that
> > overlap between the projects was indeed accepted (we already have
> multiple
> > JAX-WS or JAX-RS implementations in various TLPs / podlings).
> > That was rather clear in my mind, so I must have missed something.
> >
> > But let's try to be constructive ...
> >
> > Given the state and objectives of Aries (which means there's not much
> code
> > right now), I don' think it's wise to start splitting now between pure
> OSGi
> > specs implementations and other extensions, especially because some of
> the
> > possible specs mentionned are not yet spec, and Aries would become an
> input
> > / feedback source for creating those specifications.
> >
> > That said, we need to find a home for this proposal.   It seems Felix
> might
> > be a good place, so this basically means incubating Aries inside a Felix
> as
> > a subproject (I still think this is the role of the incubator, but let's
> put
> > that aside).
> > It means creating a subproject in Felix in a sandbox opened to all ASF
> > committers, and having a very low entry barrier for people that are not
> ASF
> > committers yet but want to contribute to Aries (as I said, it's difficult
> to
> > contribute patches when the code is inexistant at this point).   Another
> > thing to help creating a community around Aries would be to have the
> > possibility to have dedicated mailing lists and web site as a lot of TLP
> do
> > for their subprojects.  Plus, there are some code donations, so we also
> need
> > to take care of the IP clearance.  Binding votes would be those of the
> Felix
> > PMC of course.  Then, when the pseudo-incubation is completed, Aries
> could
> > either become a real Felix subproject, its own TLP, or be split.
> >
> > I really don't  see the value in that, as it seems I've just described
> what
> > the Incubator has been set up for afaik.  And as any new podling
> proposal,
> > any ASF committer is free to join at this point.  So there's really not
> much
> > difference between every people from felix joining aries podling.  But I
> > really don't want to fight for that and I'd personally be ok if the Felix
> > PMC wants to become an incubator for Aries.
> >
> >
> > On Fri, Sep 4, 2009 at 11:29, Bertrand Delacretaz <
> bdelacretaz@apache.org>wrote:
> >
> >> On Fri, Sep 4, 2009 at 7:50 AM, Niclas Hedhman<ni...@hedhman.org>
> wrote:
> >> > On Fri, Sep 4, 2009 at 1:23 PM, Kevan Miller<ke...@gmail.com>
> >> wrote:
> >> >
> >> >>... What would be the
> >> >> benefit for the Aries community of developing these spec
> implementations
> >> at
> >> >> Felix?
> >> >
> >> > Ideally, you have more people taking care of any issues. More
> >> > importantly, you need to think outside the project and ask "What would
> >> > be the benefit for ASF...?", and IMHO having a complete spec suite
> >> > from one place benefits ASF as a whole....
> >>
> >> Very much agree with that. Being able to say "OSGi spec
> >> implementations happen at Felix, and
> >> customizations/application-specific stuff/extensions etc. usually
> >> happen in other projects" leads to a clear picture for "customers" of
> >> Apache OSGi stuff (and BTW the incubation proposal forgot about Sling
> >> apparently - we might use Aries' stuff as well in there).
> >>
> >> I don't like the idea of having part of the OSGi specs scattered
> >> around several projects - as a general rule. Several modules are now
> >> at Felix that were initially developed by the communities of other
> >> projects (ServiceMix, Slng, ACE), and moved to Felix once recognized
> >> as being "of general interest to OSGi users" - I think that's a very
> >> good model both for ASF insiders and outsiders.
> >>
> >> Several projects in the history of the ASF have granted commit access
> >> to committers of other projects on parts of their codebase. That
> >> wouldn't be a new thing. Forrest committers, for example, have commit
> >> rights on Cocoon, but they're expected to ask before changing stuff in
> >> there, to make sure Cocoon folks know what's going on.
> >>
> >> That works well, IMHO, and maybe Felix could similarly open parts of
> >> their codebase to other OSGi-related projects, with the same
> >> convention of "just let us know before making changes in there" and
> >> "make sure you're following our dev list".
> >>
> >> I know such issues can be discussed during incubation, not necessarily
> >> before the podling is accepted, but the fact that (AFAIK) no contact
> >> was made with the Felix project before creating the Aries proposal is
> >> very disturbing - so IMHO we should rather clarify this before
> >> accepting the podling.
> >>
> >> Maybe simply saying "modules that implement OSGi specs, or that are of
> >> general interest to OSGi users, will be moved to the Felix project, as
> >> much as possible" in the Aries proposal would help. That should be
> >> true for any project doing OSGi at Apache anyway, and I think the
> >> other projects mentioned above are working like that, which is a Good
> >> Thing,
> >>
> >> I'm very happy to see Guillaume as a mentor for Aries, that will
> >> hopefully help in building bridges between Felix and Aries.
> >>
> >> -Bertrand
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> > ------------------------
> > Open Source SOA
> > http://fusesource.com
> >
>
>
>
> --
> Karl Pauls
> karlpauls@gmail.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Karl Pauls <ka...@gmail.com>.
Let me point out one more time: Nobody is talking about Aries as a
Felix "incubator" project. We are only talking about the OSGi EE spec
implementations that are part of the proposed Aries scope.

I'd be more then happy to see the rest of the proposal (namely, to
explore how to build an enterprise component model on OSGi and the
other non-spec related topics) become a reality by means of a new
incubator project. Whether that ends-up as a felix sub-project or as a
sub-project or TLP in the end we don't have to discuss right now.

In regard to the other half of the proposal I do think you would be
better off to develop them over at Felix and I'm sure we would be more
then happy to support you and find solutions to any issues you might
have (as we recently did with karaf). Not the end of the world if not
but not what I would prefer nor see as the best solutions for neither
Felix nor Aries.

regards,

Karl

On Fri, Sep 4, 2009 at 1:51 PM, Guillaume Nodet<gn...@gmail.com> wrote:
> There are a few things I don't understand well.   I thought the ASF over the
> past years was trying to discourage umbrella projects.   I also thought that
> overlap between the projects was indeed accepted (we already have multiple
> JAX-WS or JAX-RS implementations in various TLPs / podlings).
> That was rather clear in my mind, so I must have missed something.
>
> But let's try to be constructive ...
>
> Given the state and objectives of Aries (which means there's not much code
> right now), I don' think it's wise to start splitting now between pure OSGi
> specs implementations and other extensions, especially because some of the
> possible specs mentionned are not yet spec, and Aries would become an input
> / feedback source for creating those specifications.
>
> That said, we need to find a home for this proposal.   It seems Felix might
> be a good place, so this basically means incubating Aries inside a Felix as
> a subproject (I still think this is the role of the incubator, but let's put
> that aside).
> It means creating a subproject in Felix in a sandbox opened to all ASF
> committers, and having a very low entry barrier for people that are not ASF
> committers yet but want to contribute to Aries (as I said, it's difficult to
> contribute patches when the code is inexistant at this point).   Another
> thing to help creating a community around Aries would be to have the
> possibility to have dedicated mailing lists and web site as a lot of TLP do
> for their subprojects.  Plus, there are some code donations, so we also need
> to take care of the IP clearance.  Binding votes would be those of the Felix
> PMC of course.  Then, when the pseudo-incubation is completed, Aries could
> either become a real Felix subproject, its own TLP, or be split.
>
> I really don't  see the value in that, as it seems I've just described what
> the Incubator has been set up for afaik.  And as any new podling proposal,
> any ASF committer is free to join at this point.  So there's really not much
> difference between every people from felix joining aries podling.  But I
> really don't want to fight for that and I'd personally be ok if the Felix
> PMC wants to become an incubator for Aries.
>
>
> On Fri, Sep 4, 2009 at 11:29, Bertrand Delacretaz <bd...@apache.org>wrote:
>
>> On Fri, Sep 4, 2009 at 7:50 AM, Niclas Hedhman<ni...@hedhman.org> wrote:
>> > On Fri, Sep 4, 2009 at 1:23 PM, Kevan Miller<ke...@gmail.com>
>> wrote:
>> >
>> >>... What would be the
>> >> benefit for the Aries community of developing these spec implementations
>> at
>> >> Felix?
>> >
>> > Ideally, you have more people taking care of any issues. More
>> > importantly, you need to think outside the project and ask "What would
>> > be the benefit for ASF...?", and IMHO having a complete spec suite
>> > from one place benefits ASF as a whole....
>>
>> Very much agree with that. Being able to say "OSGi spec
>> implementations happen at Felix, and
>> customizations/application-specific stuff/extensions etc. usually
>> happen in other projects" leads to a clear picture for "customers" of
>> Apache OSGi stuff (and BTW the incubation proposal forgot about Sling
>> apparently - we might use Aries' stuff as well in there).
>>
>> I don't like the idea of having part of the OSGi specs scattered
>> around several projects - as a general rule. Several modules are now
>> at Felix that were initially developed by the communities of other
>> projects (ServiceMix, Slng, ACE), and moved to Felix once recognized
>> as being "of general interest to OSGi users" - I think that's a very
>> good model both for ASF insiders and outsiders.
>>
>> Several projects in the history of the ASF have granted commit access
>> to committers of other projects on parts of their codebase. That
>> wouldn't be a new thing. Forrest committers, for example, have commit
>> rights on Cocoon, but they're expected to ask before changing stuff in
>> there, to make sure Cocoon folks know what's going on.
>>
>> That works well, IMHO, and maybe Felix could similarly open parts of
>> their codebase to other OSGi-related projects, with the same
>> convention of "just let us know before making changes in there" and
>> "make sure you're following our dev list".
>>
>> I know such issues can be discussed during incubation, not necessarily
>> before the podling is accepted, but the fact that (AFAIK) no contact
>> was made with the Felix project before creating the Aries proposal is
>> very disturbing - so IMHO we should rather clarify this before
>> accepting the podling.
>>
>> Maybe simply saying "modules that implement OSGi specs, or that are of
>> general interest to OSGi users, will be moved to the Felix project, as
>> much as possible" in the Aries proposal would help. That should be
>> true for any project doing OSGi at Apache anyway, and I think the
>> other projects mentioned above are working like that, which is a Good
>> Thing,
>>
>> I'm very happy to see Guillaume as a mentor for Aries, that will
>> hopefully help in building bridges between Felix and Aries.
>>
>> -Bertrand
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>



-- 
Karl Pauls
karlpauls@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
There are a few things I don't understand well.   I thought the ASF over the
past years was trying to discourage umbrella projects.   I also thought that
overlap between the projects was indeed accepted (we already have multiple
JAX-WS or JAX-RS implementations in various TLPs / podlings).
That was rather clear in my mind, so I must have missed something.

But let's try to be constructive ...

Given the state and objectives of Aries (which means there's not much code
right now), I don' think it's wise to start splitting now between pure OSGi
specs implementations and other extensions, especially because some of the
possible specs mentionned are not yet spec, and Aries would become an input
/ feedback source for creating those specifications.

That said, we need to find a home for this proposal.   It seems Felix might
be a good place, so this basically means incubating Aries inside a Felix as
a subproject (I still think this is the role of the incubator, but let's put
that aside).
It means creating a subproject in Felix in a sandbox opened to all ASF
committers, and having a very low entry barrier for people that are not ASF
committers yet but want to contribute to Aries (as I said, it's difficult to
contribute patches when the code is inexistant at this point).   Another
thing to help creating a community around Aries would be to have the
possibility to have dedicated mailing lists and web site as a lot of TLP do
for their subprojects.  Plus, there are some code donations, so we also need
to take care of the IP clearance.  Binding votes would be those of the Felix
PMC of course.  Then, when the pseudo-incubation is completed, Aries could
either become a real Felix subproject, its own TLP, or be split.

I really don't  see the value in that, as it seems I've just described what
the Incubator has been set up for afaik.  And as any new podling proposal,
any ASF committer is free to join at this point.  So there's really not much
difference between every people from felix joining aries podling.  But I
really don't want to fight for that and I'd personally be ok if the Felix
PMC wants to become an incubator for Aries.


On Fri, Sep 4, 2009 at 11:29, Bertrand Delacretaz <bd...@apache.org>wrote:

> On Fri, Sep 4, 2009 at 7:50 AM, Niclas Hedhman<ni...@hedhman.org> wrote:
> > On Fri, Sep 4, 2009 at 1:23 PM, Kevan Miller<ke...@gmail.com>
> wrote:
> >
> >>... What would be the
> >> benefit for the Aries community of developing these spec implementations
> at
> >> Felix?
> >
> > Ideally, you have more people taking care of any issues. More
> > importantly, you need to think outside the project and ask "What would
> > be the benefit for ASF...?", and IMHO having a complete spec suite
> > from one place benefits ASF as a whole....
>
> Very much agree with that. Being able to say "OSGi spec
> implementations happen at Felix, and
> customizations/application-specific stuff/extensions etc. usually
> happen in other projects" leads to a clear picture for "customers" of
> Apache OSGi stuff (and BTW the incubation proposal forgot about Sling
> apparently - we might use Aries' stuff as well in there).
>
> I don't like the idea of having part of the OSGi specs scattered
> around several projects - as a general rule. Several modules are now
> at Felix that were initially developed by the communities of other
> projects (ServiceMix, Slng, ACE), and moved to Felix once recognized
> as being "of general interest to OSGi users" - I think that's a very
> good model both for ASF insiders and outsiders.
>
> Several projects in the history of the ASF have granted commit access
> to committers of other projects on parts of their codebase. That
> wouldn't be a new thing. Forrest committers, for example, have commit
> rights on Cocoon, but they're expected to ask before changing stuff in
> there, to make sure Cocoon folks know what's going on.
>
> That works well, IMHO, and maybe Felix could similarly open parts of
> their codebase to other OSGi-related projects, with the same
> convention of "just let us know before making changes in there" and
> "make sure you're following our dev list".
>
> I know such issues can be discussed during incubation, not necessarily
> before the podling is accepted, but the fact that (AFAIK) no contact
> was made with the Felix project before creating the Aries proposal is
> very disturbing - so IMHO we should rather clarify this before
> accepting the podling.
>
> Maybe simply saying "modules that implement OSGi specs, or that are of
> general interest to OSGi users, will be moved to the Felix project, as
> much as possible" in the Aries proposal would help. That should be
> true for any project doing OSGi at Apache anyway, and I think the
> other projects mentioned above are working like that, which is a Good
> Thing,
>
> I'm very happy to see Guillaume as a mentor for Aries, that will
> hopefully help in building bridges between Felix and Aries.
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Stuart McCulloch <mc...@gmail.com>.
2009/9/4 Guillaume Nodet <gn...@gmail.com>

> On Fri, Sep 4, 2009 at 07:50, Niclas Hedhman <ni...@hedhman.org> wrote:
>
> > On Fri, Sep 4, 2009 at 1:23 PM, Kevan Miller<ke...@gmail.com>
> > wrote:
> >
> > > So, let's assume that one or more OSGi spec implementations are a core
> > part
> > > of Aries -- with specific features/customization for Aries. Personally,
> > it
> > > seems reasonable that an Aries project would want these customized spec
> > > implementations close at hand -- within their project.
> >
> > I would like to draw attention to "Pax Web", which is both a OSGi Http
> > Service implementation as well as many extensions, such as war, jsp,
> > filter support. Yet it is done in a way of a custom extension
> > mechanism (Pax Web Extender), so that if you only use Pax Web, you
> > only get the basic spec implementation, nothing more, nothing less. I
> > am sure a similar approach could be made here, where the clean spec
> > part is at one place and the customizations are "close at hand".
> >
>
> My real problem is not the location, but really the fact that we'd split
> things.
> Do you really see how easy it would be if pax-web was developed at apache
> and pax-web-extender in ops4j ?
>

Well if one module was implementing the defined spec and the other was
building
on top of it, using some sort of extender approach, then that might work
quite well.

At least it would be clear what was standard, and what wasn't.

The two are somewhat tied together, and the value for having pax-web
> somewhere else is much lessened by the problems it would bring (it would be
> much more difficult to keep both in sync, meaning the communities have to
> be
> roughly the same, and what about the release process which would be much
> more difficult too).
>

OSGi is supposed to be about introducing modularity, so I would hope that it
would be possible for different teams to develop against an agreed /
standard
API without having too much trouble keeping in sync - once the initial API
is
defined you can release more or less independently, and let the framework
wire things up at deployment time.

Both teams would need to agree on how the common API developed over
time, but you might actually end up with a better, leaner API that way.

Me personally - I would prefer to see the spec implementations hosted at
Felix,
but if that's not possible then that's ok. Either way I would try to help
out where
possible (time permitting of course!).

But I do think it would be ironic if two OSGi related projects couldn't work
together, or even share bundles, because that really would be a bad advert
for modularization - let's try to move away from the old approach of silo'd
communities and "release trains" and embrace modularity.

Then in the end it doesn't really matter where the bundles come from...

--
Cheers, Stuart

For Aries, I would see the same problem.  That might be even worse given
> some of the things that are supposed to be done don't exist yet.   So when
> you have an existing code base, you can envision splitting it into two when
> it's mature enough.   Another thing, is that some things are not yet OSGi
> spec, but might become so in the future (such as application metadata and
> such), so it might be difficult to choose a destination right now.  For
> blueprint, some aspects are not yet standardized (such as custom
> namespaces), so they are tightly bound to the implementation.   I don't
> think it would make much sense to split that either.
>
> Let's try to find a solution to this problem.
>
>
> >
> > > What would be the
> > > benefit for the Aries community of developing these spec
> implementations
> > at
> > > Felix?
> >
> > Ideally, you have more people taking care of any issues. More
> > importantly, you need to think outside the project and ask "What would
> > be the benefit for ASF...?", and IMHO having a complete spec suite
> > from one place benefits ASF as a whole.
> >
> > >> The only conclusions I see being drawn by people who have invested
> very
> > >> little in Felix is that we should dismantle the Felix charter so that
> we
> > can
> > >> accommodate the fact that some people don't want to play with us.
> > >
> > > I don't know why anybody would want to "dismantle the Felix charter".
> I'm
> > > not sure why Aries would impact that one way or another...
> >
> > Richard is over-reacting, and statements like that should be left for
> > it is; an attempt to blow things out of proportion to gain sympathy,
> > possibly out of frustration.
> >
> >
> > Cheers
> > --
> > Niclas Hedhman, Software Developer
> > http://www.qi4j.org - New Energy for Java
> >
> > I  live here; http://tinyurl.com/2qq9er
> > I  work here; http://tinyurl.com/2ymelc
> > I relax here; http://tinyurl.com/2cgsug
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by da...@apache.org.
Being a fan and a regular contributor of Felix I still don't see why
Felix should have the monopoly on OSGi spec implementations.

If there is a group of people who would like to build a community
*specifically* around enterprise OSGi components, then why not let
them do that? If some of these things implement an OSGi specification,
that's even better! Why would they be allowed to implement only things
that don't happen to be an OSGi spec? That would produce a very
fragmented community.

I don't understand the need to decide from high up: projext X cannot
do some of the thing that project Y is already doing. Maybe it needs
to be clearly spelled out in the proposal that there is overlap with
other projects, but still I don't see why overlap would be an issue.

David Bosschaert
http://osgithoughts.blogspot.com/

2009/9/4 Bertrand Delacretaz <bd...@apache.org>:
> On Fri, Sep 4, 2009 at 7:50 AM, Niclas Hedhman<ni...@hedhman.org> wrote:
>> On Fri, Sep 4, 2009 at 1:23 PM, Kevan Miller<ke...@gmail.com> wrote:
>>
>>>... What would be the
>>> benefit for the Aries community of developing these spec implementations at
>>> Felix?
>>
>> Ideally, you have more people taking care of any issues. More
>> importantly, you need to think outside the project and ask "What would
>> be the benefit for ASF...?", and IMHO having a complete spec suite
>> from one place benefits ASF as a whole....
>
> Very much agree with that. Being able to say "OSGi spec
> implementations happen at Felix, and
> customizations/application-specific stuff/extensions etc. usually
> happen in other projects" leads to a clear picture for "customers" of
> Apache OSGi stuff (and BTW the incubation proposal forgot about Sling
> apparently - we might use Aries' stuff as well in there).
>
> I don't like the idea of having part of the OSGi specs scattered
> around several projects - as a general rule. Several modules are now
> at Felix that were initially developed by the communities of other
> projects (ServiceMix, Slng, ACE), and moved to Felix once recognized
> as being "of general interest to OSGi users" - I think that's a very
> good model both for ASF insiders and outsiders.
>
> Several projects in the history of the ASF have granted commit access
> to committers of other projects on parts of their codebase. That
> wouldn't be a new thing. Forrest committers, for example, have commit
> rights on Cocoon, but they're expected to ask before changing stuff in
> there, to make sure Cocoon folks know what's going on.
>
> That works well, IMHO, and maybe Felix could similarly open parts of
> their codebase to other OSGi-related projects, with the same
> convention of "just let us know before making changes in there" and
> "make sure you're following our dev list".
>
> I know such issues can be discussed during incubation, not necessarily
> before the podling is accepted, but the fact that (AFAIK) no contact
> was made with the Felix project before creating the Aries proposal is
> very disturbing - so IMHO we should rather clarify this before
> accepting the podling.
>
> Maybe simply saying "modules that implement OSGi specs, or that are of
> general interest to OSGi users, will be moved to the Felix project, as
> much as possible" in the Aries proposal would help. That should be
> true for any project doing OSGi at Apache anyway, and I think the
> other projects mentioned above are working like that, which is a Good
> Thing,
>
> I'm very happy to see Guillaume as a mentor for Aries, that will
> hopefully help in building bridges between Felix and Aries.
>
> -Bertrand
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Fri, Sep 4, 2009 at 7:50 AM, Niclas Hedhman<ni...@hedhman.org> wrote:
> On Fri, Sep 4, 2009 at 1:23 PM, Kevan Miller<ke...@gmail.com> wrote:
>
>>... What would be the
>> benefit for the Aries community of developing these spec implementations at
>> Felix?
>
> Ideally, you have more people taking care of any issues. More
> importantly, you need to think outside the project and ask "What would
> be the benefit for ASF...?", and IMHO having a complete spec suite
> from one place benefits ASF as a whole....

Very much agree with that. Being able to say "OSGi spec
implementations happen at Felix, and
customizations/application-specific stuff/extensions etc. usually
happen in other projects" leads to a clear picture for "customers" of
Apache OSGi stuff (and BTW the incubation proposal forgot about Sling
apparently - we might use Aries' stuff as well in there).

I don't like the idea of having part of the OSGi specs scattered
around several projects - as a general rule. Several modules are now
at Felix that were initially developed by the communities of other
projects (ServiceMix, Slng, ACE), and moved to Felix once recognized
as being "of general interest to OSGi users" - I think that's a very
good model both for ASF insiders and outsiders.

Several projects in the history of the ASF have granted commit access
to committers of other projects on parts of their codebase. That
wouldn't be a new thing. Forrest committers, for example, have commit
rights on Cocoon, but they're expected to ask before changing stuff in
there, to make sure Cocoon folks know what's going on.

That works well, IMHO, and maybe Felix could similarly open parts of
their codebase to other OSGi-related projects, with the same
convention of "just let us know before making changes in there" and
"make sure you're following our dev list".

I know such issues can be discussed during incubation, not necessarily
before the podling is accepted, but the fact that (AFAIK) no contact
was made with the Felix project before creating the Aries proposal is
very disturbing - so IMHO we should rather clarify this before
accepting the podling.

Maybe simply saying "modules that implement OSGi specs, or that are of
general interest to OSGi users, will be moved to the Felix project, as
much as possible" in the Aries proposal would help. That should be
true for any project doing OSGi at Apache anyway, and I think the
other projects mentioned above are working like that, which is a Good
Thing,

I'm very happy to see Guillaume as a mentor for Aries, that will
hopefully help in building bridges between Felix and Aries.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
On Fri, Sep 4, 2009 at 07:50, Niclas Hedhman <ni...@hedhman.org> wrote:

> On Fri, Sep 4, 2009 at 1:23 PM, Kevan Miller<ke...@gmail.com>
> wrote:
>
> > So, let's assume that one or more OSGi spec implementations are a core
> part
> > of Aries -- with specific features/customization for Aries. Personally,
> it
> > seems reasonable that an Aries project would want these customized spec
> > implementations close at hand -- within their project.
>
> I would like to draw attention to "Pax Web", which is both a OSGi Http
> Service implementation as well as many extensions, such as war, jsp,
> filter support. Yet it is done in a way of a custom extension
> mechanism (Pax Web Extender), so that if you only use Pax Web, you
> only get the basic spec implementation, nothing more, nothing less. I
> am sure a similar approach could be made here, where the clean spec
> part is at one place and the customizations are "close at hand".
>

My real problem is not the location, but really the fact that we'd split
things.
Do you really see how easy it would be if pax-web was developed at apache
and pax-web-extender in ops4j ?
The two are somewhat tied together, and the value for having pax-web
somewhere else is much lessened by the problems it would bring (it would be
much more difficult to keep both in sync, meaning the communities have to be
roughly the same, and what about the release process which would be much
more difficult too).

For Aries, I would see the same problem.  That might be even worse given
some of the things that are supposed to be done don't exist yet.   So when
you have an existing code base, you can envision splitting it into two when
it's mature enough.   Another thing, is that some things are not yet OSGi
spec, but might become so in the future (such as application metadata and
such), so it might be difficult to choose a destination right now.  For
blueprint, some aspects are not yet standardized (such as custom
namespaces), so they are tightly bound to the implementation.   I don't
think it would make much sense to split that either.

Let's try to find a solution to this problem.


>
> > What would be the
> > benefit for the Aries community of developing these spec implementations
> at
> > Felix?
>
> Ideally, you have more people taking care of any issues. More
> importantly, you need to think outside the project and ask "What would
> be the benefit for ASF...?", and IMHO having a complete spec suite
> from one place benefits ASF as a whole.
>
> >> The only conclusions I see being drawn by people who have invested very
> >> little in Felix is that we should dismantle the Felix charter so that we
> can
> >> accommodate the fact that some people don't want to play with us.
> >
> > I don't know why anybody would want to "dismantle the Felix charter". I'm
> > not sure why Aries would impact that one way or another...
>
> Richard is over-reacting, and statements like that should be left for
> it is; an attempt to blow things out of proportion to gain sympathy,
> possibly out of frustration.
>
>
> Cheers
> --
> Niclas Hedhman, Software Developer
> http://www.qi4j.org - New Energy for Java
>
> I  live here; http://tinyurl.com/2qq9er
> I  work here; http://tinyurl.com/2ymelc
> I relax here; http://tinyurl.com/2cgsug
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Fri, Sep 4, 2009 at 1:23 PM, Kevan Miller<ke...@gmail.com> wrote:

> So, let's assume that one or more OSGi spec implementations are a core part
> of Aries -- with specific features/customization for Aries. Personally, it
> seems reasonable that an Aries project would want these customized spec
> implementations close at hand -- within their project.

I would like to draw attention to "Pax Web", which is both a OSGi Http
Service implementation as well as many extensions, such as war, jsp,
filter support. Yet it is done in a way of a custom extension
mechanism (Pax Web Extender), so that if you only use Pax Web, you
only get the basic spec implementation, nothing more, nothing less. I
am sure a similar approach could be made here, where the clean spec
part is at one place and the customizations are "close at hand".

> What would be the
> benefit for the Aries community of developing these spec implementations at
> Felix?

Ideally, you have more people taking care of any issues. More
importantly, you need to think outside the project and ask "What would
be the benefit for ASF...?", and IMHO having a complete spec suite
from one place benefits ASF as a whole.

>> The only conclusions I see being drawn by people who have invested very
>> little in Felix is that we should dismantle the Felix charter so that we can
>> accommodate the fact that some people don't want to play with us.
>
> I don't know why anybody would want to "dismantle the Felix charter". I'm
> not sure why Aries would impact that one way or another...

Richard is over-reacting, and statements like that should be left for
it is; an attempt to blow things out of proportion to gain sympathy,
possibly out of frustration.


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Kevan Miller <ke...@gmail.com>.
On Sep 3, 2009, at 1:33 PM, Richard S. Hall wrote:

> There was no attempt to contact the Felix PMC in general that I am  
> aware and I certainly didn't know about it in advance.
>
> And there seems to be a continued attempt to construe my original  
> criticisms as "all of Aries should go into Felix".

Apologies, if I've been guilty of this.

> I, personally, do not believe that all of Aries should go into  
> Felix, I too think it should have its own identity. I was always  
> only ever referring to the independent OSGi spec implementations. I  
> was arguing that Felix is a good place to work on them, since it is  
> part of what it is trying to achieve.

So, let's assume that one or more OSGi spec implementations are a core  
part of Aries -- with specific features/customization for Aries.  
Personally, it seems reasonable that an Aries project would want these  
customized spec implementations close at hand -- within their project.  
What would be the benefit for the Aries community of developing these  
spec implementations at Felix? Perhaps you can help me understand...  
Likewise, I'm not sure I understand how these implementations would  
harm Felix.

> Further, I don't really understand the implication that somehow the  
> burden is now on the Felix community to go and contribute to Aries  
> on OSGi spec implementations just because of this proposal, when  
> there was no attempt to work with the Felix community on creating  
> OSGi spec implementations in the first.

I think the intent was to look for opportunities to bridge a gap. If  
this doesn't help, I'm willing to try and work on alternatives...

> The only conclusions I see being drawn by people who have invested  
> very little in Felix is that we should dismantle the Felix charter  
> so that we can accommodate the fact that some people don't want to  
> play with us.

I don't know why anybody would want to "dismantle the Felix charter".  
I'm not sure why Aries would impact that one way or another...

--kevan



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
Richard,

By having the "why should Felix..."-attitude, you solidify a stalemate
stance. It creates a "why should Aries..."-attitude on the other side, for
instance pointing out "there are many examples of multiple spec
implementations at ASF".

I'm not suggesting that Felix should bend over backwards, but instead of
putting up demands, join and influence from the inside. If Felix shows
humility and willingness to come to a solution, then I expect the Aries
group to do the same...

-- Niclas

On Sep 4, 2009 1:33 AM, "Richard S. Hall" <he...@ungoverned.org> wrote:

There was no attempt to contact the Felix PMC in general that I am aware and
I certainly didn't know about it in advance.

And there seems to be a continued attempt to construe my original criticisms
as "all of Aries should go into Felix".

I, personally, do not believe that all of Aries should go into Felix, I too
think it should have its own identity. I was always only ever referring to
the independent OSGi spec implementations. I was arguing that Felix is a
good place to work on them, since it is part of what it is trying to
achieve.

Further, I don't really understand the implication that somehow the burden
is now on the Felix community to go and contribute to Aries on OSGi spec
implementations just because of this proposal, when there was no attempt to
work with the Felix community on creating OSGi spec implementations in the
first.

The only conclusions I see being drawn by people who have invested very
little in Felix is that we should dismantle the Felix charter so that we can
accommodate the fact that some people don't want to play with us.

At that rate, I stand by my previous "vote" and otherwise people can do
whatever they want in Aries.

-> richard

On 9/3/09 13:23, Niclas Hedhman wrote: > > Kevan, > > Was a contact with
Felix made prior to dropp...

--------------------------------------------------------------------- To
unsubscribe, e-mail: genera...

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "Richard S. Hall" <he...@ungoverned.org>.
There was no attempt to contact the Felix PMC in general that I am aware 
and I certainly didn't know about it in advance.

And there seems to be a continued attempt to construe my original 
criticisms as "all of Aries should go into Felix".

I, personally, do not believe that all of Aries should go into Felix, I 
too think it should have its own identity. I was always only ever 
referring to the independent OSGi spec implementations. I was arguing 
that Felix is a good place to work on them, since it is part of what it 
is trying to achieve.

Further, I don't really understand the implication that somehow the 
burden is now on the Felix community to go and contribute to Aries on 
OSGi spec implementations just because of this proposal, when there was 
no attempt to work with the Felix community on creating OSGi spec 
implementations in the first.

The only conclusions I see being drawn by people who have invested very 
little in Felix is that we should dismantle the Felix charter so that we 
can accommodate the fact that some people don't want to play with us.

At that rate, I stand by my previous "vote" and otherwise people can do 
whatever they want in Aries.

-> richard

On 9/3/09 13:23, Niclas Hedhman wrote:
> Kevan,
>
> Was a contact with Felix made prior to dropping the proposal here? I got the
> impression that wasn't the case, which I find surprising... If I am wrong,
> what was the meat of such?
>
> I'm also less happy with the rhetoric here repeated over and over, seemingly
> uninterested in discussion of reaching a solution everyone can accept. (From
> both camps, btw)
>
> -- Niclas
>
> On Sep 4, 2009 12:53 AM, "Kevan Miller"<ke...@gmail.com>  wrote:
>
> On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:>  On Thu, Sep 3, 2009 at
> 3:19 AM, William A. Ro...
> Totally agree. Had certainly hoped that Felix committers would be interested
> in joining...
>
> --kevan
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: gene...
>
>    

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
Kevan,

Was a contact with Felix made prior to dropping the proposal here? I got the
impression that wasn't the case, which I find surprising... If I am wrong,
what was the meat of such?

I'm also less happy with the rhetoric here repeated over and over, seemingly
uninterested in discussion of reaching a solution everyone can accept. (From
both camps, btw)

-- Niclas

On Sep 4, 2009 12:53 AM, "Kevan Miller" <ke...@gmail.com> wrote:

On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote: > On Thu, Sep 3, 2009 at
3:19 AM, William A. Ro...
Totally agree. Had certainly hoped that Felix committers would be interested
in joining...

--kevan

--------------------------------------------------------------------- To
unsubscribe, e-mail: gene...

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Kevan Miller <ke...@gmail.com>.
On Sep 3, 2009, at 12:53 AM, Niclas Hedhman wrote:

> On Thu, Sep 3, 2009 at 3:19 AM, William A. Rowe, Jr.<wrowe@rowe-clan.net 
> > wrote:
>
>> If Felix is looking at this as an opportunity, to attract more OSGi
>> activity at the foundation, expand its base of contributors (at least
>> to common underlying components) and demonstrate that the ASF  
>> encourages
>> creation of the best-of-breed solutions, I'd hope to see some Felix  
>> PMC
>> members step up to help mentor this effort and identify places where
>> the best choice between common code is a win for all efforts.
>
> +100, and IMHO not only as Mentors... I would be surprised (and very
> concerned) if the Aries folks wouldn't love to have a few Felix
> committers joining in.
> After all, it is easier to influence and discuss if you are on the
> same side of a fence...

Totally agree. Had certainly hoped that Felix committers would be  
interested in joining...

--kevan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Niclas Hedhman <ni...@hedhman.org>.
On Thu, Sep 3, 2009 at 3:19 AM, William A. Rowe, Jr.<wr...@rowe-clan.net> wrote:

> If Felix is looking at this as an opportunity, to attract more OSGi
> activity at the foundation, expand its base of contributors (at least
> to common underlying components) and demonstrate that the ASF encourages
> creation of the best-of-breed solutions, I'd hope to see some Felix PMC
> members step up to help mentor this effort and identify places where
> the best choice between common code is a win for all efforts.

+100, and IMHO not only as Mentors... I would be surprised (and very
concerned) if the Aries folks wouldn't love to have a few Felix
committers joining in.
After all, it is easier to influence and discuss if you are on the
same side of a fence...


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Leo Simons wrote:
> On Tue, Sep 1, 2009 at 3:38 PM, Jeremy Hughes<hu...@apache.org> wrote:
>> We appreciate any feedback and comments on the proposal.
> 
> * Any chance of one or two of the other ASF members involved also
> stepping up as a mentor?

If Felix is looking at this as an opportunity, to attract more OSGi
activity at the foundation, expand its base of contributors (at least
to common underlying components) and demonstrate that the ASF encourages
creation of the best-of-breed solutions, I'd hope to see some Felix PMC
members step up to help mentor this effort and identify places where
the best choice between common code is a win for all efforts.

> maybe you can co-operate on a shared registry / website of the OSGi
> components in all the different projects so that people visiting
> apache.org are not confused? Or something like that?
> 
> I hope you guys find a way to reduce the friction and co-operate;
> having what looks like battle lines being drawn up at the start of
> incubation is _not_ a good thing.

+1, and I put the onus equally on felix and aries contributors to make
that happen, if it can.

> I do expect to see that felix/aria conversation resolved clearly one
> way or another before the proposal goes up for a vote. Even if the
> resolution is "there will significant charter overlap and duplication
> of effort and code and probably little committer overlap between the
> communities because we disagree on how to do things" then I'd like to
> see that clearly spelled out.

+1

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Leo Simons <ma...@leosimons.com>.
On Tue, Sep 1, 2009 at 3:38 PM, Jeremy Hughes<hu...@apache.org> wrote:
> We appreciate any feedback and comments on the proposal.

* Any chance of one or two of the other ASF members involved also
stepping up as a mentor?

* Projects that consist of groups of components often have some
problems maintaining sufficient cohesion as a community. I hope you
guys will give that the specific attention it probably requires and
tune the project charter appropriately.

* I have no problems with having multiple OSGi projects at apache as
long as they're all healthy communities and they play nice with each
other.

(...)

Of course the "play nice" part is interesting here -- I'm frowning a
bit at seeing this how-to-interact-with-felix discussion kick off with
a pretty much finished proposal going to the incubator. Surely the
conversation can go a bit differently? For example maybe you could've
approached felix first and discussed seeding the project with some of
the parts-of-felix (along with developers) that are argued to need an
independent-from-felix re-brand? Maybe you can take a step back
together even now and see if something like that might make sense? Or,
maybe you can co-operate on a shared registry / website of the OSGi
components in all the different projects so that people visiting
apache.org are not confused? Or something like that?

I hope you guys find a way to reduce the friction and co-operate;
having what looks like battle lines being drawn up at the start of
incubation is _not_ a good thing.

I do expect to see that felix/aria conversation resolved clearly one
way or another before the proposal goes up for a vote. Even if the
resolution is "there will significant charter overlap and duplication
of effort and code and probably little committer overlap between the
communities because we disagree on how to do things" then I'd like to
see that clearly spelled out.


cheers,


- Leo

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Fwd: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Guillaume Nodet <gn...@gmail.com>.
This might be interesting to Geronimo and Felix communities.
Any further discussion should happen on general@incubator.apache.org

---------- Forwarded message ----------
From: Jeremy Hughes <hu...@apache.org>
Date: Tue, Sep 1, 2009 at 16:38
Subject: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
To: general@incubator.apache.org


Hi, we would like to propose a new incubator podling called Aries.

http://wiki.apache.org/incubator/AriesProposal

Here is a quick summary of the proposal

The Aries project will deliver a set of pluggable Java components
enabling an enterprise OSGi application programming model. This
includes implementations and extensions of application-focused
specifications defined by the OSGi Alliance Enterprise Expert Group
(EEG) and an assembly format for multi-bundle applications, for
deployment to a variety of OSGi based runtimes.

Aries aims to build a community of developers interested in the
definition and delivery of software components that support an
enterprise OSGi programming model and which can be integrated into a
number of different runtime environments.

We appreciate any feedback and comments on the proposal.

Here is a plain text copy of the whole proposal:

Apache Aries
Abstract

The Aries project will deliver a set of pluggable Java components
enabling an enterprise OSGi application programming model. This
includes implementations and extensions of application-focused
specifications defined by the OSGi Alliance Enterprise Expert Group
(EEG) and an assembly format for multi-bundle applications, for
deployment to a variety of OSGi based runtimes.
Proposal

It is a goal of the Aries project to provide a natural home for open
source implementations of current and future OSGi EEG specifications,
including the opportunity for the collaborative development of
compliance tests, and an environment to demonstrate the composition of
these technologies and to explore areas where EEG specifications lack
coverage. A further goal of this project is to leverage experience
gained from it to inform contributions to OSGi EEG requirements and
specification documents.

Aries will offer an enterprise OSGi application programming model that
enables applications to leverage Java EE and other enterprise
technologies and to benefit from the modularity, dynamism and
versioning capabilities of OSGi. A significant feature of Aries will
be a container for OSGi Blueprint components - an implementation of
the new OSGi v4.2 Blueprint component model that defines a standard
dependency injection mechanism for Java components, which is derived
from the Spring framework and extended for OSGi to declaratively
register component interfaces as services in the OSGi service
registry.

In addition, the Aries project will develop a model for assembling an
application/subsystem into a deployable unit, consisting of multiple
bundles, as an archive which may include metadata that describes the
version and external location of the application's constituent bundles
or which may contain the bundles directly.

The Aries project will deliver run-time componentry that supports
applications, running in an OSGi framework, exploiting enterprise Java
technologies common in web applications and integration scenarios
including web application bundles, remote services integration and
JPA. The project is not expected to deliver a complete application or
integration server runtime but will instead deliver enterprise
application componentry that can be integrated into such runtimes. The
project will develop extensions that go beyond the OSGi EEG
specifications to provide a more complete integration of OSGi
modularity with Java enterprise technologies, in particular delivering
support that includes but is not restricted to:

   * isolated enterprise applications composed of multiple, versioned
bundles with dynamic lifecycle.
   * declarative transactions and security for Blueprint components
   * Container-managed JPA for Blueprint components
   * Message-driven Blueprint components
   * Configuration of resource references in module blueprints.
   * Annotation-based Blueprint configuration
   * Federation of lookup mechanisms between local JNDI and the OSGi
service registry.
   * Fully declarative application metadata to enable reflection of
an SCA component type definition.

In order to maximise the potential scope of Aries adoption it is
anticipated the project will remain agnostic of a number of
complementary technologies and projects. It is the expectation that
Aries will therefore not be delivering components such as: an
application or integration server runtime kernel; a persistence
provider; distribution provider; a deployment provider or a Web
container. Aries will instead seek to enable the use of such
components from other projects.
Background

OSGi is a mature and Java modularity technology that is well-used in
many environments but, in the enterprise space, has more typically
been exploited by the internals of the runtime infrastructure than the
applications that run on it. This is primarily because of a lack of a
clear enterprise OSGi application programming model and implementation
of OSGi-enabled Java technology to support enterprise applications.
OSGi specifications are specified and maintained by the OSGi Alliance
which recognized this state of affairs several years ago and
established the Enterprise Expert Group within the Alliance to focus
specifically on the needs of enterprise applications. The objective of
this project is to deliver open source implementations of these
application-centric technologies to enable the development of
application components, benefiting from the modularity of OSGi
combined with standards-based programming models, which can be
deployed to a variety of target runtimes.
Rationale

Aries aims to build a community of developers interested in the
delivery of software components that support an enterprise OSGi
programming model and which can be integrated into a number of
different runtime environments. Apache hosts the Felix project which
provides an OSGi framework implementation and a variety of projects
which provide technologies exploited by enterprise application
components as well as projects which provide runtimes to host
application components. There is currently no Apache project focussed
on OSGi enterprise applications that is independent from both the OSGi
framework and the enterprise runtime environment in which application
components are hosted. By maintaining independence of both the target
runtime and underlying OSGi framework it is our intention to build the
broadest possible community of developers for Aries, and to maximize
the potential environments where Aries componentry can be used.
Initial Goals

We will initially focus on the Blueprint container and extend this
with enterprise features such as support for container managed JPA and
container managed transactions. Another initial focus area will be the
contribution of code to support the assembly of isolated, multi-bundle
applications that can be deployed as a unit.
Current Status
Meritocracy

The Aries contributors recognize the desirability of running the
project as a meritocracy. We are eager to engage other members of the
community and operate to the standard of meritocracy that Apache
emphasizes; we believe this is the most effective method of growing
our community and enabling widespread adoption.
Community

OSGi is a mature Java modularity technology that is well-used in many
environments but, in the enterprise space, has more typically been
exploited by the internals of the runtime infrastructure than the
applications that run on it. This is primarily because of a lack of a
clear enterprise OSGi application programming model and implementation
of OSGi-enabled Java technology to support enterprise applications.
There is a need for open source implementations of these technologies
and there is currently no Apache project focused on the wider goal of
delivering components for an enterprise OSGi application programming
model. Aries aims to build a community of developers interested in the
definition and delivery of software components that support an
enterprise OSGi programming model and which can be integrated into a
number of different runtime environments. By maintaining independence
of both the target runtime and underlying OSGi framework it is our
intention to build the broadest possible community of developers.
Alignment

The purpose of Aries is to develop implementations of
application-centric enterprise OSGi technologies that run on an OSGi
framework, but not a specific one, and are used by application
components deployed into a variety of runtime environments without
being tied to any specific environment. For this reason we believe
Aries is a project whose community would be best served if it could
leverage but be independent from the communities that provide
underlying OSGi framework technology and enterprise application server
and integration bus technologies, all of which exist as open source
efforts within Apache and elsewhere. We expect, for example, that some
code developed in Aries will run directly on top of an OSGi framework
such as Felix and that applications exploiting Aries technologies
could be deployed to runtimes such as ServiceMix and Geronimo.
Avoiding the Warning Signs
Orphaned products

The contributors are leading vendors of OSGi-based technologies and
have a long standing in the OSGi Alliance whose application-centric
specifications this project will implement. There is minimal risk of
this work becoming non-strategic and the contributors are confident
that a larger community will form within the project in a relatively
short space of time.
Inexperience with Open Source

Many of the committers have experience working in one or more open
source projects including Apache Geronimo, Felix, ServiceMix, OpenEJB,
and CXF.

Homogeneous Developers

The list of initial committers, geographically distributed across the
U.S. and Europe, consists of developers from two companies - IBM and
Progress software - with similar goals but for different scenarios.
Many of these developers are experienced Apache committers already and
all are experienced with working in distributed development
communities. It is our hope that, through the incubator, further
contributors with a broad background of experience but common interest
in enterprise OSGi technologies will become involved with this
project.

Relationships with Other Apache Projects

Aries will have a potential relationship with the Apache projects
listed in this section. These projects all serve different purposes
from Aries and have their own communities. It is hoped that each of
these communities will become involved with Aries and help to build a
diverse but independent Aries community.

Apache Felix Karaf -
http://felix.apache.org/site/apache-felix-karaf.html Apache Felix
Karaf is an OSGi based runtime which provides a lightweight container
onto which various components and applications can be deployed. It is
related to Aries:

  1. as a target OSGi based runtime to which Aries applications can
be deployed. In this role, Karaf is a consumer of Aries technology.

Apache Felix - http://felix.apache.org/site/index.html Apache
Felix is primarily a core OSGi framework implementation. It is related
to Aries:

  1. as an underlying OSGi framework implementation and potentially
other extensions that can be used both by Aries run-time components
and the applications which use them.

Apache Geronimo - http://geronimo.apache.org/ Apache Geronimo is
a server runtime framework and fully certified Java EE 5 application
server runtime. It is related to Aries in two ways:

  1. as a target runtime to which Aries applications can be deployed.
In this role, Geronimo is a consumer of Aries technology.
  2. the Geronimo blueprint sandbox -
http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint/ - contains
an implementation of the OSGi Blueprint container which will be moved
to Aries.

Apache Tuscany - http://tuscany.apache.org/ Apache Tuscany
provides a comprehensive infrastructure for SOA development and
management that is based on Service Component Architecture (SCA)
standard. It can be a consumer of Aries technology to provide an Aries
SCA implementation type for composing Aries applications in coarse
grained and potentially heterogeneous service assemblies.

Apache CXF - http://cxf.apache.org/ Apache CXF provides a Java
Web Services framework for distributed computing and remote service
realization and invocation using API's such as JAX-WS and JAX-RS. It
also provides the OSGi Remote Services (OSGi RFC 119) reference
implementation in a subproject:
http://cxf.apache.org/distributed-osgi.html. It is related to Aries in
the following way:

  1. As Remote Services is a significant Enterprise specification
being produced by the EEG, it is expected that consumers of Aries will
be looking for an implementation of this specification. CXF provides
an implementation of this specification which already has a
significant active community. The Aries project will make it easy for
Aries consumers to consume the CXF Remote Services implementation,
possibly by providing an instance of the application model that
references the CXF Remote Services implementation. This would mean
that end users will seamlessly pull in the required components from
CXF by using the Aries-provided definition.

Apache ServiceMix - http://servicemix.apache.org/ Apache
ServiceMix provides an ESB that combines the functionality of a
Service Oriented Architecture (SOA) and Event Driven Architecture
(EDA) to create an agile ESB. ServiceMix runs on OSGi and was the
source of the Apache Felix Karaf runtime. It can be a consumer of
Aries applications and associated componentry as a natural evolution
of its existing Karaf "feature" usage.

Apache OpenJPA - http://openjpa.apache.org/ Apache OpenJPA is a
Java persistence project. It is related to Aries as a JPA persistence
provider, including entity scanning and enhancement. The Aries project
will make it easy for JPA persistence providers such as OpenJPA to be
used in an OSGi environment and will provide container managed
persistence for the Blueprint container.

Documentation

An early draft of OSGi v4.2 core and compendium specifications - which
includes the Blueprint container specification - is available at:
http://www.osgi.org/download/osgi-4.2-early-draft3.pdf
Initial Source

   * The Blueprint container impl from the Geronimo sandbox will be
moved to the Aries project for further development:
http://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
   * IBM will also contribute code for:
         o container-managed JPA support in an OSGi environment.
         o making OSGi services visible to Java EE components through JNDI.
         o packaging web components as bundles and a URL handler for
recognizing and converting non-bundled Web components
   * We will also be soliciting implementations of other OSGi
enterprise application-centric specifications.

External Dependencies

   * Apache Ant http://ant.apache.org Apache License
   * Apache Commons http://commons.apache.org Apache License
   * Junit (Java unit test framework) http://junit.sourceforge.net CPL
v1.0 license: http://junit.sourceforge.net/cpl-v10.html
   * Apache Felix (implementation of the OSGi Core and Compendium
specifications - compliance level unknown) http://felix.apache.org
Apache License (hosted by ASF).
   * Eclipse Equinox (compliant implementation of the OSGi Core
Specification and Compendium specifications)
http://eclipse.org/equinox/ Eclipse Public License
   * OpenJPA http://openjpa.apache.org Apache License
   * Serp http://serp.sourceforge.net/ BSD
   * Apache Geronimo http://geronimo.apache.org Apache License

Required Resources
Mailing lists

aries-private (with moderated subscriptions)
aries-dev
aries-commits
aries-user

Subversion Directory

http://svn.apache.org/repos/asf/incubator/aries

Issue Tracking

JIRA (ARIES)

Web Site

Confluence (Aries)

Initial Committers

Names of initial committers with affiliation and current ASF status:

   * Alasdair Nottingham (IBM)
   * Andrew Osborne (IBM)
   * Dan Kulp (Progress, ASF member)
   * David Bosschaert (Progress, ASF committer)
   * David Jencks (IBM, ASF member)
   * Eoghan Glynn (Progress, ASF committer)
   * Graham Charters (IBM)
   * Guillaume Nodet (Progress, ASF member)
   * Hiram Chirino (Progress, ASF member)
   * Ian Robinson (IBM)
   * James Strachan (Progress, ASF member)
   * Jarek Gawor (IBM, ASF member)
   * Jeremy Hughes (IBM, ASF committer)
   * Joe Bohn (IBM, ASF committer)
   * Lin Sun (IBM, ASF committer)
   * Mark Nuttall (IBM)
   * Oisin Hurley (Progress)
   * Rick McGuire (IBM, ASF committer)
   * Sergey Beryozkin (Progress, ASF committer),
   * Timothy Ward (IBM)
   * Valentin Mahrwald (IBM)
   * Zoe Slattery (IBM)

Affiliations

The majority of the initial committers are employed by IBM corp or
Progress Software. One objective of the incubator is to attract a
diverse community of contributors and we anticipate future
contributors to have other affiliations.

Sponsors
Champions

Kevan Miller, Guillaume Nodet

Nominated Mentors

Guillaume Nodet, Davanum Srinivas (Dims)

Sponsoring Entity

The incubator. Successful graduation from Incubator should result in
Aries becoming a new TLP.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org




-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Jeremy,

Thanks! I'm still considering if it makes sense to add my name to the  
list of initial committers to help out with this, but I will  
definitely be following what's going on at Aries.

Greetings, Marcel

On Sep 9, 2009, at 13:09 , Jeremy Hughes wrote:

> Hi Marcel, I agree it was an oversight. I added the following to the
> "Relationship with Other Apache Projects" section:
>
> Apache Ace - http://incubator.apache.org/ace Apache ACE is a software
> distribution framework that allows you to centrally manage and
> distribute software components, configuration data and other artifacts
> to target systems. It is built using OSGi and can be deployed in
> different topologies. The target systems are usually also OSGi based,
> but don't have to be.
>
>   1. As a mechanism to distribute and configure the runtime
> components (those implementing the enterprise OSGi application
> programming model).
>   2. To distribute and configure enterprise OSGi application
> components implemented to the enterprise OSGi application programming
> model.
>
> Thanks,
> Jeremy
>
> 2009/9/6 Marcel Offermans <ma...@luminis.nl>:
>> It probably got swamped in the discussion, but, on Sep 1, 2009, at  
>> 22:20 ,
>> Marcel Offermans wrote:
>>
>>> On Sep 1, 2009, at 16:38 , Jeremy Hughes wrote:
>>>
>>>> Relationships with Other Apache Projects
>>>
>>> I know ACE is only in incubation, but is there a reason for not  
>>> mentioning
>>> it in this list? To me it makes sense to also consider technology  
>>> to deploy
>>> and update OSGi components and I think ACE could fit in there  
>>> nicely.
>>
>> Does anybody want to comment on this? I would definitely like to  
>> collaborate
>> on making ACE work well with anything Aries produces (since you  
>> were hinting
>> it's not a single project but more a series of components).
>>
>> Greetings, Marcel
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Jeremy Hughes <hu...@apache.org>.
Hi Marcel, I agree it was an oversight. I added the following to the
"Relationship with Other Apache Projects" section:

Apache Ace - http://incubator.apache.org/ace Apache ACE is a software
distribution framework that allows you to centrally manage and
distribute software components, configuration data and other artifacts
to target systems. It is built using OSGi and can be deployed in
different topologies. The target systems are usually also OSGi based,
but don't have to be.

   1. As a mechanism to distribute and configure the runtime
components (those implementing the enterprise OSGi application
programming model).
   2. To distribute and configure enterprise OSGi application
components implemented to the enterprise OSGi application programming
model.

Thanks,
Jeremy

2009/9/6 Marcel Offermans <ma...@luminis.nl>:
> It probably got swamped in the discussion, but, on Sep 1, 2009, at 22:20 ,
> Marcel Offermans wrote:
>
>> On Sep 1, 2009, at 16:38 , Jeremy Hughes wrote:
>>
>>> Relationships with Other Apache Projects
>>
>> I know ACE is only in incubation, but is there a reason for not mentioning
>> it in this list? To me it makes sense to also consider technology to deploy
>> and update OSGi components and I think ACE could fit in there nicely.
>
> Does anybody want to comment on this? I would definitely like to collaborate
> on making ACE work well with anything Aries produces (since you were hinting
> it's not a single project but more a series of components).
>
> Greetings, Marcel
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Graham,

ACE only just started, so no problem! :) I'm looking forward to  
working with Aries on making this happen. I agree with your analysis  
so far.

Greetings, Marcel


On Sep 6, 2009, at 22:32 , Graham Charters wrote:

> Hi Marcel,
>
> Not mentioning ACE was an oversight.  I think there are two potential
> roles for ACE in relation Aries:
> 1. To distribute and configure the runtime components (those
> implementing the enterprise OSGi application programming model).
> 2. To distribute and configure enterprise OSGi application components
> implemented to the enterprise OSGi application programming model.
>
> Regards, Graham.
>
> 2009/9/6 Davanum Srinivas <da...@gmail.com>:
>> Marcel,
>>
>> I believe it was an oversight to have missed mentioning ACE.  
>> Hopefully one
>> of the proposed committers will comment on this aspect.
>>
>> thanks,
>> dims
>>
>> On 09/06/2009 08:29 AM, Marcel Offermans wrote:
>>>
>>> It probably got swamped in the discussion, but, on Sep 1, 2009, at  
>>> 22:20
>>> , Marcel Offermans wrote:
>>>
>>>> On Sep 1, 2009, at 16:38 , Jeremy Hughes wrote:
>>>>
>>>>> Relationships with Other Apache Projects
>>>>
>>>> I know ACE is only in incubation, but is there a reason for not
>>>> mentioning it in this list? To me it makes sense to also consider
>>>> technology to deploy and update OSGi components and I think ACE  
>>>> could
>>>> fit in there nicely.
>>>
>>> Does anybody want to comment on this? I would definitely like to
>>> collaborate on making ACE work well with anything Aries produces  
>>> (since
>>> you were hinting it's not a single project but more a series of
>>> components).
>>>
>>> Greetings, Marcel
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Graham Charters <gc...@googlemail.com>.
Hi Marcel,

Not mentioning ACE was an oversight.  I think there are two potential
roles for ACE in relation Aries:
1. To distribute and configure the runtime components (those
implementing the enterprise OSGi application programming model).
2. To distribute and configure enterprise OSGi application components
implemented to the enterprise OSGi application programming model.

Regards, Graham.

2009/9/6 Davanum Srinivas <da...@gmail.com>:
> Marcel,
>
> I believe it was an oversight to have missed mentioning ACE. Hopefully one
> of the proposed committers will comment on this aspect.
>
> thanks,
> dims
>
> On 09/06/2009 08:29 AM, Marcel Offermans wrote:
>>
>> It probably got swamped in the discussion, but, on Sep 1, 2009, at 22:20
>> , Marcel Offermans wrote:
>>
>>> On Sep 1, 2009, at 16:38 , Jeremy Hughes wrote:
>>>
>>>> Relationships with Other Apache Projects
>>>
>>> I know ACE is only in incubation, but is there a reason for not
>>> mentioning it in this list? To me it makes sense to also consider
>>> technology to deploy and update OSGi components and I think ACE could
>>> fit in there nicely.
>>
>> Does anybody want to comment on this? I would definitely like to
>> collaborate on making ACE work well with anything Aries produces (since
>> you were hinting it's not a single project but more a series of
>> components).
>>
>> Greetings, Marcel
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Davanum Srinivas <da...@gmail.com>.
Marcel,

I believe it was an oversight to have missed mentioning ACE. Hopefully one of the proposed committers will comment on 
this aspect.

thanks,
dims

On 09/06/2009 08:29 AM, Marcel Offermans wrote:
> It probably got swamped in the discussion, but, on Sep 1, 2009, at 22:20
> , Marcel Offermans wrote:
>
>> On Sep 1, 2009, at 16:38 , Jeremy Hughes wrote:
>>
>>> Relationships with Other Apache Projects
>>
>> I know ACE is only in incubation, but is there a reason for not
>> mentioning it in this list? To me it makes sense to also consider
>> technology to deploy and update OSGi components and I think ACE could
>> fit in there nicely.
>
> Does anybody want to comment on this? I would definitely like to
> collaborate on making ACE work well with anything Aries produces (since
> you were hinting it's not a single project but more a series of
> components).
>
> Greetings, Marcel
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Marcel Offermans <ma...@luminis.nl>.
It probably got swamped in the discussion, but, on Sep 1, 2009, at  
22:20 , Marcel Offermans wrote:

> On Sep 1, 2009, at 16:38 , Jeremy Hughes wrote:
>
>> Relationships with Other Apache Projects
>
> I know ACE is only in incubation, but is there a reason for not  
> mentioning it in this list? To me it makes sense to also consider  
> technology to deploy and update OSGi components and I think ACE  
> could fit in there nicely.

Does anybody want to comment on this? I would definitely like to  
collaborate on making ACE work well with anything Aries produces  
(since you were hinting it's not a single project but more a series of  
components).

Greetings, Marcel


Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi

Posted by Marcel Offermans <ma...@luminis.nl>.
On Sep 1, 2009, at 16:38 , Jeremy Hughes wrote:

> It is a goal of the Aries project to provide a natural home for open
> source implementations of current and future OSGi EEG specifications,
> including the opportunity for the collaborative development of
> compliance tests, and an environment to demonstrate the composition of
> these technologies and to explore areas where EEG specifications lack
> coverage. A further goal of this project is to leverage experience
> gained from it to inform contributions to OSGi EEG requirements and
> specification documents.

Just reading this paragraph my initial reaction is that this is very  
much aligned with the Felix project. Felix's goals are basically to  
provide a full OSGi implementation of both the framework and  
compendium services whilst also providing a home for extensions to the  
specification that make sense. In that sense Aries sounds like a  
subset of Felix's goal, targetting the enterprise specifications.

> The Aries project will deliver run-time componentry that supports
> applications [...] The project is not expected to deliver a complete  
> application or
> integration server runtime but will instead deliver enterprise
> application componentry that can be integrated into such runtimes.

This makes a lot of sense. Any project building on a component  
architecture should be setup in such a way that many of the individual  
components can be combined and reused in different deployment scenarios.

> There is currently no Apache project focussed
> on OSGi enterprise applications that is independent from both the OSGi
> framework

This is a really interesting topic, and others have commented on this:  
the perception that bundles in the Felix project only run on Felix. Of  
course anybody who makes an effort to understand OSGi quickly learns  
that the whole purpose of the spec is to have bundles that can run on  
any implementation and from years of experience of doing OSGi  
projects, I must say that every project I did, did in fact use bundles  
from Felix, Knopflerfish, Eclipse, Pax, various other sources as well  
as project specific bundles.

My view is that we should really try to fix this misconception instead  
of using it as a reason to start new projects.

> For this reason we believe
> Aries is a project whose community would be best served if it could
> leverage but be independent from the communities that provide
> underlying OSGi framework technology

If you look at the OSGi specification as a whole, it consists of two  
parts: the framework and the compendium. In fact, with the different  
expert groups, you could say there is more than one compendium as each  
expert group usually adds a compendium of their own. Anyway, OSGi is  
more than just the framework alone, and Felix already supplies an  
implementation of the whole spec, so there currently is no community  
that provide just the OSGi framework (also look at Knopflerfish and  
Equinox, both of which also provide compendium implementations).

> Relationships with Other Apache Projects

I know ACE is only in incubation, but is there a reason for not  
mentioning it in this list? To me it makes sense to also consider  
technology to deploy and update OSGi components and I think ACE could  
fit in there nicely.

> The incubator. Successful graduation from Incubator should result in
> Aries becoming a new TLP.

As others mentioned, this is perhaps an issue that should be addressed  
when leaving the incubator. As I explained above, my personal view is  
that this would fit nicely within the Felix TLP, especially since  
there seems to be a lot of focus on implementing the OSGi Enterprise  
"compendium" which is part of the OSGi specifications. On the other  
hand, if you guys really want to work outside of Felix then of course  
that's an option too. I do think it's great that there is a group of  
people wanting to implement these enterprise specs and explore related  
options! Let's just try and leverage each others' work as much as  
possible!

Greetings, Marcel