There are senior ASF members who say that the "community" is the set of active committers, since these individuals are the ones that create and maintain the software. Users are simply our way of creating more committers. :) If that is so, then separating *only* the user lists won't divide the core community. So long as we have a single dev@, we will have a unified *development* community, which, arguably, is the one that counts.
I'd also agree that until there is a PMC-sanctioned release, the best place for Shale posts is the [EMAIL PROTECTED] We've always said the user list is for released software, and Shale has no release. -Ted. http://www.husted.com/poe/ On 8/26/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > I agree with Craig about this potentially dividing the community up. > While many prefer to work exclusively in one camp or another there are > plenty of people who want to stay on top of what's happening in both > camps. > > Since "shale" is not a word most of us use in everyday conversation > (except when talking about *the shale* subproject) I think a simple > key word filter would work even if the user did not mention [shale] in > the subject line. > > sean > > ps. I've been limiting my shale questions to the dev list since its > not even 1.0 yet and the community is still growing. Hopefully this > is ok. > > > On 8/26/05, Ted Husted <[EMAIL PROTECTED]> wrote: > > Moving to dev@ ... > > > > On 8/25/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > > On 8/25/05, Rick Reumann <[EMAIL PROTECTED]> wrote: > > > > > > > > Would starting up a separate shale mailing list be a bad idea? I only > > > > ask because the number of struts posts is quite heavy and if someone > > > > posts a Shale question withough an approriate [shale] intro, I might > > > > miss the post and end up deleting it if I get busy and it ends up buried > > > > between the other struts posts? > > > > > > Experience across all of Apache is that splitting up mailing lists > > > tends not to accomplish the desired purpose (redirecting the traffic). > > > More importantly, the cases where it has happened caused existing > > > communities to divide instead of unite, to their ultimate detriment, > > > and indeed in some cases has engendered conflict. That's not what > > > Apache is about. > > > > > > -1 on separate lists for *any* Struts subprojects (including Shale). > > > > Another approach that is working for some projects is to have separate > > user lists, but a single dev list. I'd be -1 on separate dev lists, > > but +0 on separate user lists for at least some of the subprojects, > > where the traffic boundaries are obvious. > > > > -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
