From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] About user support and the mailing list
Date: Tue, 15 Oct 2013 15:16:23 +0200 (CEST) [thread overview]
Message-ID: <872799982.8879164.1381842983831.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <CAAXf6LXWKnMXXb1HP+-7rXPgtaiWN3no2=hyGcFdSkXJqu+NAw@mail.gmail.com>
>
> 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'.
>
hmm, compared to most FOSS projects I know buildroot is a bit special...
There is no clear separation between users and developers as far as
knowledge is concerned. All users should be able to compile stuff
know about cross compilers and installing firmwares. So doing a
separate -user vs -dev mailing list makes less sense her.
However I would like to have a separate -discuss an -patch mailing
list, one of them being for patch+reviews+commit messages and the
other one being for actual discussions.
That would separate the high traffic/fast reading parts from the
low traffic/philosophical discussion parts.
The important part is that mose people (everybody?) should logically
subscribe to both, but mail filtering etc... would be much simpler.
next prev parent reply other threads:[~2013-10-15 13:16 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 [this message]
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
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=872799982.8879164.1381842983831.JavaMail.root@openwide.fr \
--to=jeremy.rosen@openwide.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox