From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [Fwd: [FOSDEM] Your devroom request has not been accepted]
Date: Mon, 01 Dec 2008 07:51:12 -0500 [thread overview]
Message-ID: <4933DDC0.5000701@balister.org> (raw)
In-Reply-To: <493386A1.9090503@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 2473 bytes --]
Robert Schuster wrote:
> Hi,
> summary: There won't be a special for OpenEmbedded only. There will be
> an 'Embedded devroom' and if we ask we may get some hours for OE
> specific talks.
Thanks for trying! I still think an OE room would be useful at FOSDEM,
but they have space limitations :(
We need to keep our eyes open for the Embedded devroom call for
presentations. I think there are several OE related ones that would be
good fits. They would probably need to be interesting to a general
embedded audience. Having several really cool projects presented (that
happened to use OE) would be really good for OE.
Philip
>
> Regards
> Robert
>
>
> ------------------------------------------------------------------------
>
> Subject:
> [FOSDEM] Your devroom request has not been accepted
> From:
> Pascal Bleser <loki@fosdem.org>
> Date:
> Mon, 01 Dec 2008 01:42:16 +0100
> To:
> r.schuster@tarent.de, glp@openwrt.org
>
> To:
> r.schuster@tarent.de, glp@openwrt.org
> CC:
> FOSDEM DevRooms <devrooms@fosdem.org>, Philippe De Swert
> <philippedeswert@scarlet.be>
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> We're sorry to give you bad news, but your developer room request for
> FOSDEM 2009 has not been accepted.
>
> We realize that this must be disappointing news, but unfortunately we
> don't have a sufficient number of rooms to our disposal to cover all
> requests.
> Just to clarify: your request is perfectly valid, but we had to pick.
>
> Given the domain of your respective projects, we would recommend to get
> in touch with Philippe De Swert (in CC:), who is organizing the schedule
> of the Embedded devroom.
>
> Thanks for your interest in FOSDEM, nevertheless.
>
> - --
> -o) Pascal Bleser <loki@fosdem.org> http://www.fosdem.org
> /\\ FOSDEM 2009 :: 7 + 8 February 2009 in Brussels
> _\_v Free and Opensource Software Developers European Meeting
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
>
> iD8DBQFJMzLor3NMWliFcXcRAgeDAKCdJBs9oFsjkDIvKIObM091i2CHiACgv4zw
> kDRPorAX+ivqujzzJFuavKk=
> =6Zyd
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-12-01 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 6:39 [Fwd: [FOSDEM] Your devroom request has not been accepted] Robert Schuster
2008-12-01 12:51 ` Philip Balister [this message]
2008-12-01 14:13 ` Koen Kooi
-- strict thread matches above, loose matches on Subject: below --
2008-12-01 6:42 Robert Schuster
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=4933DDC0.5000701@balister.org \
--to=philip@balister.org \
--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.