ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Jordahl <tjord...@adobe.com>
Subject RE: Mailing list changes.....
Date Mon, 18 Oct 2010 19:52:22 GMT
> This should probably be moved over to the Axis TLP:
>    "ws-axis-tck"

I think we can just remove this one as I do not believe there is anyone still running the
JAX-RPC TCK on axis 1.x any more (the original use of that list was for folks to talk about
TCK issues there).

Tom Jordahl


-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org] 
Sent: Monday, October 18, 2010 11:04 AM
To: general@ws.apache.org
Subject: Re: Mailing list changes.....


To followup some more,  according to infra and suc, the following mailing 
lists are still "active":
    "ws-private"
    "ws-announce"
    "ws-axis-user-ja"
    "ws-axis-cvs"
    "ws-axis-tck"
    "ws-commons-dev"
    "ws-general"
    "ws-jaxme-dev
    "ws-kandula-dev"
    "ws-muse-dev"
    "ws-muse-user"
    "ws-muse-commits"
    "ws-rampart-dev"
    "ws-rampart-c-dev"
    "ws-sandesha-dev"
    "ws-savan-dev"
    "ws-woden-dev"
    "ws-wsif-dev"
    "ws-wsif-user"
    "ws-wss4j-dev"
    "ws-xmlrpc-auto"
    "ws-xmlrpc-dev

>From that list, I think we also need to instruct infra to close down:
    "ws-axis-user-ja"
    "ws-axis-cvs"
    "ws-kandula-dev"
    "ws-rampart-dev"
    "ws-rampart-c-dev"
    "ws-sandesha-dev"
    "ws-savan-dev"
as those should already have been moved/merged into the Axis TLP.

These should be shutdown as the projects are "attic" material:
    "ws-muse-dev"
    "ws-muse-user"
    "ws-muse-commits"
    "ws-wsif-dev"
    "ws-wsif-user"

This should probably be moved over to the Axis TLP:
    "ws-axis-tck"

That leaves just:
    "ws-announce"

Should that one remain or just merge that into users@ws?









On Sunday 17 October 2010 11:01:09 pm Glen Daniels wrote:
> +1 to these changes, and thanks for pushing this forward, Dan.  I added
> myself as a requested moderator on the issue.
> 
> Especially since everything is going to be combined, I'd probably suggest
> we set up commits@ to cut down a bit on traffic.  But IMO, Hudson
> notifications should go to dev@ so that build breaks are less likely to
> fall through the cracks.
> 
> --Glen
> 
> On 10/15/2010 10:35 AM, Daniel Kulp wrote:
> > I've filed:
> > https://issues.apache.org/jira/browse/INFRA-3073
> > 
> > 
> > Couple things I think still need discussing:
> > 
> > 1) Do we want additional lists for commits and/or issues (JIRA notices)
> > or do we want said emails to just go to the dev list?
> > 
> > 2) Do we want a notification list for Hudson notifications  or just to
> > the dev list?
> > 
> > 3) Moderators - I signed up to be a moderator, but ideally there should
> > be a couple more.   Volunteers?   It's really not much work or many spam
> > messages to deal with.   I have maybe 10 a day total between all the
> > CXF, Santuario, Stonehenge, and a few other lists.
> > 
> > Dan
> > 
> > On Thursday 14 October 2010 10:20:36 am Daniel Kulp wrote:
> >> Everyone seems fairly possitive about making this change.  If no one
> >> objects by tomorrow, I'll file a INFRA issue to go ahead and do this.
> >> 
> >> For dev@, it would be merging:
> >> general
> >> commons-dev
> >> xmlrpc-dev
> >> woden-dev
> >> wss4j-dev
> >> jaxme-dev
> >> 
> >> users@ would, at this point, just be
> >> xmlrpc-user
> >> 
> >> I THINK all the other lists at:
> >> http://mail-archives.apache.org/mod_mbox/#ws
> >> are either already moved on to other TLP's (juddi/axis) or retired to
> >> the attic.    Can someone double check that?  I'm not familliar with
> >> all the names for the various Axis modules that would have been merged
> >> already and such so I'd like to be sure about it.
> >> 
> >> Thanks!
> >> Dan
> >> 
> >> On Tuesday 12 October 2010 5:10:29 pm Daniel Kulp wrote:
> >>> I'd like to make a proposal that I think would the WS community and
> >>> would like peoples thoughts on the matter:
> >>> 
> >>> I think it would be good for the community to combine all the *-dev@ws
> >>> mailing lists (and likely general@ as well) in to a single
> >>> dev@ws.apache.org. Likewise, combine all the *-user@ws lists into a
> >>> single users@.   Probably a single commits list as well.
> >>> 
> >>> I really think having separate lists has caused the community to
> >>> fracture into small little eco systems with very little knowledge of
> >>> what is happening in the rest of the community propogating from
> >>> project to project.  Doing releases is hard as the other PMC members
> >>> may not be following the other projects at all.   By combining them
> >>> back into a few, broader lists, that should make it easier to follow
> >>> what the entire community is doing.    Once everyone really gets a
> >>> feel for things and are communicating with each other, I think it will
> >>> be easier to figure out what can/should be spun off, retired to attic,
> >>> etc...
> >>> 
> >>> Also, I'd like the new lists changed to be moderated lists.   Moderated
> >>> lists are much easer for new people to get involved in, especially
> >>> through places like nabble.
> >>> 
> >>> Thoughts?

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

Mime
View raw message