[RESULT][VOTE] Create new subproject Aries Remote Service Admin with initial code from CXF DOSGi

2016-03-10 Thread Christian Schneider 

This vote passes with 5 binding +1 votes and no other votes.
I will create the repo and migrate the code base as described below.

Christian

On 07.03.2016 17:06, Christian Schneider wrote:
In my previous mail I started a discussion about moving the CXF DOSGi 
code to Aries.
As there was no negative feedback I am starting a vote to create a new 
subproject and move the non CXF specific code over to aries.


I propose the name Aries Remote Service Admin (aries-rsa) as a name.

The goal of the project is to implement the remote service admin spec 
in a very slim way with as few external dependencies as possible.
A secondary goal is to provide an API for providers that allows to 
implement new transports and serializations in a very simple way.


An initial code structure could look like this:
/rsa
/parent
/core
/topology-manager
/provider-api
/rsa-core
/discovery
/local
/zookeeper
/provider
/rmi
/itests
/features
/examples

The CXF specific provider will remain at CXF.
I think we do not need to provide a full distribution like in CXF-DOSGi.
A karaf feature should make sense though.

To make it easy for current developers of CXF DOSGi to participate in 
the new development I propose that we keep the barrier low when voting 
for an aries committer if he is committer in CXF

and already involved in CXF DOSGi.

Please vote
  [  ] +1 Create Aries Remote Service Admin subproject
  [  ] -1 Do not

Here is my
+1

Christian




--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: [VOTE] Create new subproject Aries Remote Service Admin with initial code from CXF DOSGi

2016-03-10 Thread Jean-Baptiste Onofré 
OK for this name, even it's maybe not obvious for "external" people. 
Maybe aries-remote ...


Else, aries-rsa is fine for me.

Regards
JB

On 03/10/2016 03:06 PM, Christian Schneider wrote:

I would like to start the new project on git right aways.
The advantage would be that I can push the full history of cxf dosgi so
it remains visible.
Of course the access should be open for all aries committers.

I propose the name aries-rsa.

Is that ok for everyone?

Christian

On 07.03.2016 17:06, Christian Schneider wrote:

In my previous mail I started a discussion about moving the CXF DOSGi
code to Aries.
As there was no negative feedback I am starting a vote to create a new
subproject and move the non CXF specific code over to aries.

I propose the name Aries Remote Service Admin (aries-rsa) as a name.

The goal of the project is to implement the remote service admin spec
in a very slim way with as few external dependencies as possible.
A secondary goal is to provide an API for providers that allows to
implement new transports and serializations in a very simple way.

An initial code structure could look like this:
/rsa
/parent
/core
/topology-manager
/provider-api
/rsa-core
/discovery
/local
/zookeeper
/provider
/rmi
/itests
/features
/examples

The CXF specific provider will remain at CXF.
I think we do not need to provide a full distribution like in CXF-DOSGi.
A karaf feature should make sense though.

To make it easy for current developers of CXF DOSGi to participate in
the new development I propose that we keep the barrier low when voting
for an aries committer if he is committer in CXF
and already involved in CXF DOSGi.

Please vote
  [  ] +1 Create Aries Remote Service Admin subproject
  [  ] -1 Do not

Here is my
+1

Christian






--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [VOTE] Create new subproject Aries Remote Service Admin with initial code from CXF DOSGi

2016-03-10 Thread Christian Schneider 

I would like to start the new project on git right aways.
The advantage would be that I can push the full history of cxf dosgi so 
it remains visible.

Of course the access should be open for all aries committers.

I propose the name aries-rsa.

Is that ok for everyone?

Christian

On 07.03.2016 17:06, Christian Schneider wrote:
In my previous mail I started a discussion about moving the CXF DOSGi 
code to Aries.
As there was no negative feedback I am starting a vote to create a new 
subproject and move the non CXF specific code over to aries.


I propose the name Aries Remote Service Admin (aries-rsa) as a name.

The goal of the project is to implement the remote service admin spec 
in a very slim way with as few external dependencies as possible.
A secondary goal is to provide an API for providers that allows to 
implement new transports and serializations in a very simple way.


An initial code structure could look like this:
/rsa
/parent
/core
/topology-manager
/provider-api
/rsa-core
/discovery
/local
/zookeeper
/provider
/rmi
/itests
/features
/examples

The CXF specific provider will remain at CXF.
I think we do not need to provide a full distribution like in CXF-DOSGi.
A karaf feature should make sense though.

To make it easy for current developers of CXF DOSGi to participate in 
the new development I propose that we keep the barrier low when voting 
for an aries committer if he is committer in CXF

and already involved in CXF DOSGi.

Please vote
  [  ] +1 Create Aries Remote Service Admin subproject
  [  ] -1 Do not

Here is my
+1

Christian




--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: [VOTE] Create new subproject Aries Remote Service Admin with initial code from CXF DOSGi

2016-03-08 Thread Sergey Beryozkin 

+1

Sergey
On 07/03/16 16:06, Christian Schneider wrote:

In my previous mail I started a discussion about moving the CXF DOSGi
code to Aries.
As there was no negative feedback I am starting a vote to create a new
subproject and move the non CXF specific code over to aries.

I propose the name Aries Remote Service Admin (aries-rsa) as a name.

The goal of the project is to implement the remote service admin spec in
a very slim way with as few external dependencies as possible.
A secondary goal is to provide an API for providers that allows to
implement new transports and serializations in a very simple way.

An initial code structure could look like this:
/rsa
 /parent
 /core
 /topology-manager
 /provider-api
 /rsa-core
 /discovery
 /local
 /zookeeper
 /provider
 /rmi
 /itests
 /features
 /examples

The CXF specific provider will remain at CXF.
I think we do not need to provide a full distribution like in CXF-DOSGi.
A karaf feature should make sense though.

To make it easy for current developers of CXF DOSGi to participate in
the new development I propose that we keep the barrier low when voting
for an aries committer if he is committer in CXF
and already involved in CXF DOSGi.

Please vote
   [  ] +1 Create Aries Remote Service Admin subproject
   [  ] -1 Do not

Here is my
+1

Christian




--
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Re: [VOTE] Create new subproject Aries Remote Service Admin with initial code from CXF DOSGi

2016-03-08 Thread Guillaume Nodet 
+1

2016-03-07 17:06 GMT+01:00 Christian Schneider :

> In my previous mail I started a discussion about moving the CXF DOSGi code
> to Aries.
> As there was no negative feedback I am starting a vote to create a new
> subproject and move the non CXF specific code over to aries.
>
> I propose the name Aries Remote Service Admin (aries-rsa) as a name.
>
> The goal of the project is to implement the remote service admin spec in a
> very slim way with as few external dependencies as possible.
> A secondary goal is to provide an API for providers that allows to
> implement new transports and serializations in a very simple way.
>
> An initial code structure could look like this:
> /rsa
> /parent
> /core
> /topology-manager
> /provider-api
> /rsa-core
> /discovery
> /local
> /zookeeper
> /provider
> /rmi
> /itests
> /features
> /examples
>
> The CXF specific provider will remain at CXF.
> I think we do not need to provide a full distribution like in CXF-DOSGi.
> A karaf feature should make sense though.
>
> To make it easy for current developers of CXF DOSGi to participate in the
> new development I propose that we keep the barrier low when voting for an
> aries committer if he is committer in CXF
> and already involved in CXF DOSGi.
>
> Please vote
>   [  ] +1 Create Aries Remote Service Admin subproject
>   [  ] -1 Do not
>
> Here is my
> +1
>
> Christian
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>


-- 

Guillaume Nodet

Red Hat, Open Source Integration

Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Re: [VOTE] Create new subproject Aries Remote Service Admin with initial code from CXF DOSGi

2016-03-07 Thread David Bosschaert 
Hi Christan,

Looks good!
+1 from me.

David

On 7 March 2016 at 16:06, Christian Schneider 
wrote:

> In my previous mail I started a discussion about moving the CXF DOSGi code
> to Aries.
> As there was no negative feedback I am starting a vote to create a new
> subproject and move the non CXF specific code over to aries.
>
> I propose the name Aries Remote Service Admin (aries-rsa) as a name.
>
> The goal of the project is to implement the remote service admin spec in a
> very slim way with as few external dependencies as possible.
> A secondary goal is to provide an API for providers that allows to
> implement new transports and serializations in a very simple way.
>
> An initial code structure could look like this:
> /rsa
> /parent
> /core
> /topology-manager
> /provider-api
> /rsa-core
> /discovery
> /local
> /zookeeper
> /provider
> /rmi
> /itests
> /features
> /examples
>
> The CXF specific provider will remain at CXF.
> I think we do not need to provide a full distribution like in CXF-DOSGi.
> A karaf feature should make sense though.
>
> To make it easy for current developers of CXF DOSGi to participate in the
> new development I propose that we keep the barrier low when voting for an
> aries committer if he is committer in CXF
> and already involved in CXF DOSGi.
>
> Please vote
>   [  ] +1 Create Aries Remote Service Admin subproject
>   [  ] -1 Do not
>
> Here is my
> +1
>
> Christian
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>

[VOTE] Create new subproject Aries Remote Service Admin with initial code from CXF DOSGi

2016-03-07 Thread Christian Schneider 
In my previous mail I started a discussion about moving the CXF DOSGi 
code to Aries.
As there was no negative feedback I am starting a vote to create a new 
subproject and move the non CXF specific code over to aries.


I propose the name Aries Remote Service Admin (aries-rsa) as a name.

The goal of the project is to implement the remote service admin spec in 
a very slim way with as few external dependencies as possible.
A secondary goal is to provide an API for providers that allows to 
implement new transports and serializations in a very simple way.


An initial code structure could look like this:
/rsa
/parent
/core
/topology-manager
/provider-api
/rsa-core
/discovery
/local
/zookeeper
/provider
/rmi
/itests
/features
/examples

The CXF specific provider will remain at CXF.
I think we do not need to provide a full distribution like in CXF-DOSGi.
A karaf feature should make sense though.

To make it easy for current developers of CXF DOSGi to participate in 
the new development I propose that we keep the barrier low when voting 
for an aries committer if he is committer in CXF

and already involved in CXF DOSGi.

Please vote
  [  ] +1 Create Aries Remote Service Admin subproject
  [  ] -1 Do not

Here is my
+1

Christian

--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com