How about using prefixes for each project and then adding filters in the mail clients, just like how we used to do in Axis2 as well as in ws-commons.
thanks, Thilina On Thu, Nov 4, 2010 at 4:26 AM, Jochen Wiedmann <[email protected]>wrote: > On Thu, Nov 4, 2010 at 1:11 AM, Daniel Kulp <[email protected]> wrote: > > > The BEST model to look at is the commons project at Apache. They have a > very > > diverse set of sub projects and have been very successful at being able > to > > provide adequate oversight on all the projects. How do they do it: they > > MANDATE that there are not separate dev lists for each project. > > > It is also the best example of a mailing list with an extremely bad > ratio between noise and content, at least for me. > > > > > If the traffic about a particulare subproject grows enough to overwelm > the > > rest of the projects, that's usually a sign that it's ready to spin out. > > Thus, if you don't like it, start participating with XML-RPC, submit > patches, > > foster ideas, etc.... and help it grow to a point where it's ready to > > graduate. > > XML-RPC is most likely not a project which will grow. It is in > maintenance mode and has been just that for a couple of years. It is > extremely unlikely that you have a chance to attract interest for the > ws project under its contributors / users, unless they move their > professional interest, which would be an event unrelated to either > projects. > > Jochen > > -- > I Am What I Am And That's All What I Yam (Popeye) > -- http://thilinag.blogspot.com https://www.cs.indiana.edu/~tgunarat/ http://www.linkedin.com/in/thilina
