Fwd: pruning projects @ ws

[Davanum Srinivas <da...@gmail.com>]

Folks,

OOPS! forwarding again with correct bcc's.

These are my thoughts...what do you all think? We are spreading our
efforts too thin and we need to seriously think about down-sizing a
bit and focusing our efforts. Feel free to start a separate thread for
a specific project(s) that you are interested in keeping alive.

Addressing: Not much traffic/activity. Can we collapse this into Axis
1.X since it is specific to that version
EWS       : Not much traffic/activity. Archive it?
Mirae     : Not much traffic/activity. Archive it?
Muse      : Not much recent activity. Can we do one single project
with Muse/Pubscribe/WSRF
Pubscribe : Not much recent activity. Can we do one single project
with Muse/Pubscribe/WSRF
WSRF      : Not much recent activity. Can we do one single project
with Muse/Pubscribe/WSRF
Scout     : Donate to Geronimo?
SOAP      : Time to pull the plug? Archive it?
TSIK      : Not much traffic/activity. Think about stopping incubation?
WSIF      : Last legs? Time to pull the plug?

Of course, if any project (not just the ones listed above) wants to
become a separate TLP, that's another option as well.

Thanks,
dims

--
Davanum Srinivas : http://wso2.com/blogs/

Re: Fwd: pruning projects @ ws

[Guillaume Sauthier <gu...@apache.org>]

Fernando Nasser wrote:

> Happy New Year everyone!
>
> Davanum Srinivas wrote:
>
>> Folks,
>>
>> OOPS! forwarding again with correct bcc's.
>>
>> These are my thoughts...what do you all think? We are spreading our
>> efforts too thin and we need to seriously think about down-sizing a
>> bit and focusing our efforts.
>
>
> This is the best New year's resolution ever! I have been asking for 
> this, not only for Apache but for the Open Source community at large. 
> Lets stop duplication efforts and concentrate on the best options we 
> have.
>
> Feel free to start a separate thread for
>
>> a specific project(s) that you are interested in keeping alive.
>>
>
>> EWS : Not much traffic/activity. Archive it?
>
>
> Haven't Geronimo folks wrote an equivalent piece?

I think they "generate" on the fly implementation of web services 
interfaces using cglib.
They don't use EWS AFAIK

>
> Either drop EWS or import the Geronimo version and convince them to 
> get it from here?
>
> But there is now 'ews-mapper'. That is used in JOnAS.

Yep.
EWS seems to be pretty stable. I don't have to work often on bug fixes.

But as long as JOnAS use it, I want to be able to make changes in EWS 
(who knows, maybe sometime in the future I will need to update that 
thing :) ).
So if we decide to archive it (does it mean : no more commits ?) I will 
have to move that piece of code in another repository (objectweb's repo).

So I agree that there is not uch activity on this project, but I have to 
maintain it (at least the mapper part).

>
> What to do with it?
>
>
> Regards to all.
>
> Fernando
>

Re: Fwd: pruning projects @ ws

[Fernando Nasser <fn...@redhat.com>]

Happy New Year everyone!

Davanum Srinivas wrote:
> Folks,
> 
> OOPS! forwarding again with correct bcc's.
> 
> These are my thoughts...what do you all think? We are spreading our
> efforts too thin and we need to seriously think about down-sizing a
> bit and focusing our efforts.

This is the best New year's resolution ever!  I have been asking for 
this, not only for Apache but for the Open Source community at large. 
Lets stop duplication efforts and concentrate on the best options we have.

  Feel free to start a separate thread for
> a specific project(s) that you are interested in keeping alive.
> 

> EWS       : Not much traffic/activity. Archive it?

Haven't Geronimo folks wrote an equivalent piece?

Either drop EWS or import the Geronimo version and convince them to get 
it from here?

But there is now 'ews-mapper'.  That is used in JOnAS.

What to do with it?


Regards to all.

Fernando

---------------------------------------------------------------------
To unsubscribe, e-mail: ews-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: ews-dev-help@ws.apache.org

Re: pruning projects @ ws

[Jochen Wiedmann <jo...@gmail.com>]

Hi,

I always had the impression that JaxMe and XML-RPC were the most 
inactive projects in the Apache world ... after browsing the mailing 
list archives of the listed projects, I do no longer think so.

I am unable to express opinions on any of these projects, though. 
Preferrably the project teams should decide, if possible. However, the 
following question is raised for me: How come, that so many projects are 
inactive?

I can think of many reasons for inactivity, not all of which are 
negative. For example, if a projects purpose is the implementation of a 
certain specification, then there may be a point, when the work is done. 
This may well happen for some project. In the case of SOAP, there 
obviosuly are successors. But still: Why so many?

It might help, if people with more insight than me could write some 
words on the particular projects. If so, we could possibly derive 
guidelines for the policy: When to establish a new project? When not?

Some things I could think of:

- JSR implementations might possibly be located under a new umbrella
   project for specifications. (See the thread on "Starting a java specs
   project" on general@incubator from last month.) That umbrella project
   (if it will be established) will most definitely have a different
   characteristic than ws and be used to mostly inactive subprojects.

- We should ask ourselves, how new subprojects are created. For example,
   a better idea might be to create a sandbox. New subprojects could be
   established in the sandbox. At some point, they might leave the
   sandbox. (This approach has worked well for Jakarta, I believe.)


Jochen