Hey Mike, It depends on what type of dev related traffic. If it’s JIRA, SVN or Git bots, etc, then that traffic can be split onto e.g., an *-issues or *-commit list, or *-git list, etc. In general, though I tend to agree with Greg Stein, who has told me this several times [1] (you have to read down to see his quote) that basically splitting devs and users during Incubation makes it more difficult since the users and devs should be in lock step during that time. Dev discussions should be architectural; nuanced and non-bot emails and so forth, so users of the newly Incubating Apache project can be part of the community from the get go. If, over time, the users are burdened by the dev traffic, and want another option, it can be done then. For example with Apache OODT, we started out with dev and users and then found over time it made most sense to simply shut down the users list, which we did recently [2].
HTH, Chris [1] http://s.apache.org/Qmz [2] http://s.apache.org/zgz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Mike Carey <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Monday, April 20, 2015 at 2:19 AM To: "[email protected]" <[email protected]> Subject: Re: users and dev lists >For our pre-ASF lists, we split them for the opposite reason - because >there was so much dev-related traffic and we didn't want to burden our >non-dev users with all of that noise. Thoughts on that? > >On 4/19/15 5:03 PM, Mattmann, Chris A (3980) wrote: >> My advice, based on past experience, is to not split the lists >> initially upon Incubation. It splinters the community. If you need >> to split it b/c there is so much user related traffic later, I would >> do it then. >> >> Cheers, >> Chris >> >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Chief Architect >> Instrument Software and Science Data Systems Section (398) >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 168-519, Mailstop: 168-527 >> Email: [email protected] >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Associate Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> >> >> >> >> -----Original Message----- >> From: Till Westmann <[email protected]> >> Reply-To: "[email protected]" >> <[email protected]> >> Date: Sunday, April 19, 2015 at 7:16 PM >> To: "[email protected]" >> <[email protected]> >> Subject: users and dev lists >> >>> Hi, >>> >>> we currently have users and dev lists for AsterixDB (outside of the >>>ASF) >>> and we actually have users that are not developers on the users list. >>> At the ASF we currently don’t have a users-list and I’m wondering if we >>> should leave it that way or if we should add a users lists to >>>(hopefully) >>> migrate our current users to. >>> >>> Thoughts/Preferences? >>> >>> Thanks, >>> Till >
