On Aug 23, 2013, at 2:12 PM, Rob Godfrey <[email protected]> wrote:
> [X] 2. Keep the dev list but only for traffic not relevant to users of the > code > > > On 23 August 2013 17:07, Robbie Gemmell <[email protected]> wrote: > >> The 'our users are developers' thing is true of many (most?) of the >> projects at the ASF, however they still typically have separate user and >> dev lists. I think the real issue here is how we use them rather than >> whether they both exist. >> >> > > Exactly... To be honest I don't think it is the fact that we have 2 > mailing lists that is the primary issue that we need to work on... much > more of an issue to my mind is the mindset of us - the committers - in > terms of our use of lists and our engagement with the user community. ++1 > Gordon shows us all up here with his continued exemplary display on the > users list... continually responding to and addressing questions that occur > there. I think if all of us were to follow his example and to act in more > inclusive ways in our discussion of future roadmaps / feature development, > etc... then we would be providing a much better service for our users than > simply adding all the JIRA notifications and code review requests to the > users list (which would seem to me to be the primary result of closing the > dev list and moving its traffic to users). > > -- Rob > > >> Robbie >> >> On 23 August 2013 15:58, Darryl L. Pierce <[email protected]> wrote: >> >>> On Fri, Aug 23, 2013 at 01:50:12PM +0100, Gordon Sim wrote: >>>> Please indicate your preference: >>>> >>>> 1. Remove the dev list entirely >>> >>> +1 I'm actually inclined towards this. >>> >>> With an application's mailing list you'd want to have one place for >>> users to discuss using the application and another list for the >>> developers who write the code. >>> >>> But with something like Qpid, there's not so clear a separation between >>> developers and users; i.e., users ARE developers and are more directly >>> interested in the implementation details of Qpid, those things that are >>> discussed in the dev list. >>> >>> Except for such things as setting up or configuring the broker, pretty >>> much all traffic concerns development. >>> >>>> 2. Keep the dev list but only for traffic not relevant to users of the >>> code >>>> >>>> 3. Keep dev list for some wider set of traffic (please specify >>>> criteria you believe applies if selecting this option) >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> -- >>> Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. >>> Delivering value year after year. >>> Red Hat ranks #1 in value among software vendors. >>> http://www.redhat.com/promo/vendor/ >>> >>> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
