[Buildroot] Splitting this list

[Buildroot] Splitting this list

[Bryce Schober]

It seems to me that this list could benefit from a split to buildroot-user
& buildroot-dev. There's an awful lot of developer "noise" for those trying
to get off the ground and get working. Just a thought...

<><  <><  <><
Bryce Schober
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120917/a7ef66a7/attachment.html>

[Buildroot] Splitting this list

[Peter Korsgaard]

>>>>> "Bryce" == Bryce Schober <bryce.schober@gmail.com> writes:

 Bryce> It seems to me that this list could benefit from a split to
 Bryce> buildroot-user & buildroot-dev. There's an awful lot of
 Bryce> developer "noise" for those trying to get off the ground and get
 Bryce> working. Just a thought...

We've considered it in the past, but so far the feeling among the main
developers favors a single list.

Another proposal than -user / -dev was to move the git commit mails to a
seperate list, which was brought up recently.

But splitting the list can also bring disadvantages, so I would prefer
to keep it like it is, unless a lot of people think elsewise?

-- 
Bye, Peter Korsgaard

[Buildroot] Splitting this list

[Thomas Petazzoni]

Dear Peter Korsgaard,

On Tue, 18 Sep 2012 08:21:09 +0200, Peter Korsgaard wrote:
> >>>>> "Bryce" == Bryce Schober <bryce.schober@gmail.com> writes:
> 
>  Bryce> It seems to me that this list could benefit from a split to
>  Bryce> buildroot-user & buildroot-dev. There's an awful lot of
>  Bryce> developer "noise" for those trying to get off the ground and get
>  Bryce> working. Just a thought...
> 
> We've considered it in the past, but so far the feeling among the main
> developers favors a single list.
> 
> Another proposal than -user / -dev was to move the git commit mails to a
> seperate list, which was brought up recently.
> 
> But splitting the list can also bring disadvantages, so I would prefer
> to keep it like it is, unless a lot of people think elsewise?

For a program such as Buildroot, there is really a continuum between
"user" and "developer": most users need at some point to become
developers, since to effectively use Buildroot you most likely need to
create packages for your own applications, create configurations for
your board, etc. Therefore, I don't think that splitting the
mailing-lists, and therefore splitting the communities is a good idea.

That said, if at some point the amount of traffic of the list starts to
discourage too many users from being on the list, we should probably
take action and do something. Maybe keep buildroot@ as it is, and
create a separate support at buildroot.org mailing list, only for user
support?

Regarding git commits, I definitely think they should remain on the
main developer mailing list. Having them encourages review, and allows
developers to remain aware of what's being merged.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com