All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot talk at ELCE
Date: Fri, 25 Oct 2013 10:00:59 +0200	[thread overview]
Message-ID: <526A253B.20003@mind.be> (raw)
In-Reply-To: <87d2mt6avi.fsf@dell.be.48ers.dk>

On 25/10/13 09:57, Peter Korsgaard wrote:
>>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>   >  slide 4: No single company steering: actually, no company at all is
>   > steering - though most of us use buildroot professionally, our
>   > buildroot work is mostly on a volunteer basis. Right?
>
> Yes, in the sense that no company mgmt is telling us in what direction
> Buildroot need to move, but a lot of us are using Buildroot in the
> context of our work, so there will always be some influence ..

  Yeah, but in Tizen for instance, there is also no single company 
steering - there are two :-) So I think it's important to make that 
distinction.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-10-25  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25  7:14 [Buildroot] Buildroot talk at ELCE Peter Korsgaard
2013-10-25  7:29 ` Baruch Siach
2013-10-25  7:41   ` Peter Korsgaard
2013-10-25  7:42 ` Thomas De Schampheleire
2013-10-25  7:47   ` Peter Korsgaard
2013-10-25  7:53 ` Arnout Vandecappelle
2013-10-25  7:57   ` Peter Korsgaard
2013-10-25  8:00     ` Arnout Vandecappelle [this message]
2013-10-25  8:02   ` Thomas De Schampheleire

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=526A253B.20003@mind.be \
    --to=arnout@mind.be \
    --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.