All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <thebohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: FOSDEM 2012 - stand organization thread
Date: Mon, 23 Jan 2012 12:54:00 +0100	[thread overview]
Message-ID: <4F1D4A58.9090209@gmx.net> (raw)
In-Reply-To: <CAA5cW2zfJx9zWdx8VdDmxrG=U_xwiNJZYAy9Drkt-SCb8yVT5w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]

Hi Radoslav,

Am 21.01.2012 16:40, schrieb Radoslav Kolev:
> Hey guys,
> 
> It's my first time going to FOSDEM, so I don't know how it works out
> exactly. I'm not an Openembedded "master", but have been using it for
> a while and can try to explain to people what it is and why it's
> useful. So, hopefully I can help a bit with the stand too.
That's great and you surely can help. I am also not using OE daily but I
was working long enough for it to be able to tell conference attendees
what it can ( and why its way cooler than the competition. :P ).

As it is your first time visit I honestly ask you not to spend too much
time at our booth (a few hours is fine though) as FOSDEM is a really
intense and vibrant event. That does not mean we don't want your help
(quite the contrary) but I want to prevent that you'll get the feeling
of having missed something. FOSDEM has a lot of superb presentations,
interesting people you'd like to talk to etc.

Fair enough, meeting us OE people is probably also part of the bill. :)

> As for bringing hardware, what is usually needed here? I have some
> evaluation boards with different ARM SoCs, some with an LCD and touch
> screen that can run Angstrom and QT embedded demo apps, but nothing
> very impressive to show. Would that be useful?
A good idea for a device might be:
 - looks interesting
 - you can tell about the device/OS
 - it can withstand transport (not too fragile)

All the best,
Robert

> Regards and I hope to see you there,
> Radoslav
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 270 bytes --]

  parent reply	other threads:[~2012-01-23 12:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 14:38 FOSDEM 2012 - stand organization thread Robert Schuster
2012-01-16  9:00 ` Marcin Juszkiewicz
2012-01-19 13:40 ` Robert Schuster
2012-01-19 15:17   ` Frans Meulenbroeks
2012-01-19 15:17   ` Paul Eggleton
2012-01-20 19:19   ` Denis 'GNUtoo' Carikli
2012-01-21  0:11     ` Philip Balister
2012-01-24 11:43   ` Florian Boor
2012-01-24 19:29   ` Marco Cavallini
2012-02-01 10:39     ` Alex J Lennon
2012-02-01 13:18       ` Robert Schuster
2012-02-01 13:52         ` Alex J Lennon
2012-02-01 17:14           ` Robert Schuster
2012-02-01 17:24             ` Alex J Lennon
2012-02-01 17:54             ` Philip Balister
2012-02-01 17:55       ` Philip Balister
2012-01-21 15:40 ` Radoslav Kolev
2012-01-22  2:43   ` Khem Raj
2012-01-23 11:54   ` Robert Schuster [this message]
2012-01-23 11:43 ` Robert Schuster
2012-01-23 12:04   ` Alex J Lennon

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=4F1D4A58.9090209@gmx.net \
    --to=thebohemian@gmx.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.