All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] About user support and the mailing list
Date: Wed, 16 Oct 2013 18:00:54 +0200	[thread overview]
Message-ID: <20131016180054.610acf12@skate> (raw)
In-Reply-To: <CAAXf6LXWKnMXXb1HP+-7rXPgtaiWN3no2=hyGcFdSkXJqu+NAw@mail.gmail.com>

Dear Thomas De Schampheleire,

On Tue, 15 Oct 2013 15:04:44 +0200, Thomas De Schampheleire wrote:

> > Yes and no. Our mailing list is now having a *huge* traffic, mainly
> > developer-oriented (patches and related discussions). For the user just
> > starting up with Buildroot, not very familiar of open-source
> > communities, not feeling necessarily at ease with subscribing to a
> > 50-100 e-mails/day mailing list, searching other forms of support seems
> > natural to me.
> >
> > Maybe it's a sign that we should have a more "user-oriented" support
> > channel. A dedicated mailing list? An publicized usage of Stack
> > Overflow or some other similar stuff? Not sure exactly about this, but
> > might be worth a chat at the next Buildroot meeting, I believe.
> 
> The amount of traffic on the mailing list has indeed increased a lot.
> On a previous Buildroot meeting, we talked about a split of the
> mailing lists. At that time, we decided not to do this (yet).
> 
> One of the advantages of a unified list is that new users also are
> 'exposed' to development, and are hopefully more likely to contribute
> too. There is no 'development elite' in this model.
> At the same time, a unified list also encourages developers to help
> users. It's not possible to subscribe to 'only the developer list'.

Agreed.

> A split mailing list model is mainly advantageous for users that only
> want to subscribe to a low-volume list, but other than that I don't
> yet see big advantages. If you have more, please let me know.

That's mainly what I was concerned about. Subscribing to a 50-100
mails/day mailing list might be problematic for people who just want to
use Buildroot, even though I agree that the boundary between "users"
and "developers" is a lot less cut in Buildroot than it is for other
software.

> Thomas: you seem to be active on StackOverflow. Can you give some more
> background how this would work for us? I've only used stackoverflow in
> a read-only mode, when googling a specific question.

I'm not so much active on stackoverflow actually. In fact I just
subscribed to the tag "buildroot" so that whenever a Buildroot related
question is asked, I receive an e-mail. I generally find Stack Overflow
a bit better than web forums thanks to the scoring system which ensures
"good" answers are the one getting the highest visibility. Stack
Overflow also generally has a very high Google rank, so whenever you
search something programming-related on Google, there's a high chance
of having a hit on Stack Overflow.

In this discussion, I don't really have one good solution to suggest,
I'm merely interested in discussing the fact that the mailing list
traffic has increased, which on one side is really great (the project
is active) but on the other side may be problematic for users who just
want to have a little bit of support.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2013-10-16 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-12 10:15 [Buildroot] [PATCH] package: fix 'local' site method for host packages Thomas Petazzoni
2013-10-14 19:59 ` Peter Korsgaard
2013-10-15  8:25   ` [Buildroot] About user support and the mailing list Thomas Petazzoni
2013-10-15 13:04     ` Thomas De Schampheleire
2013-10-15 13:16       ` Jeremy Rosen
2013-10-15 14:30         ` Ryan Barnett
2013-10-15 16:07           ` Peter Korsgaard
2013-10-15 19:44             ` Thomas De Schampheleire
2013-10-16 21:56               ` Arnout Vandecappelle
2013-10-16 16:00       ` Thomas Petazzoni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131016180054.610acf12@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.