----- Original Message -----
> 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.
agree. that's why choice #2 best reflect reality. since all users are
potential developers, and since we want to grow that group, users should...
users should....
dang. i want to change my vote.
>
> 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]
