From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: Alex J Lennon <ajlennon@dynamicdevices.co.uk>,
"paul@paulbarker.me.uk" <paul@paulbarker.me.uk>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Yocto Project and OpenEmbedded Logos
Date: Fri, 31 Jan 2014 10:24:31 +0000 [thread overview]
Message-ID: <CF112A01.3BFDB%belen.barros.pena@intel.com> (raw)
In-Reply-To: <52EADD1C.3050900@dynamicdevices.co.uk>
Sent them off list. I'll try to get them on the website.
Cheers
Belén
On 30/01/2014 23:15, "Alex J Lennon" <ajlennon@dynamicdevices.co.uk> wrote:
>
>
>
>Hi Paul,
>
>I had similar trouble today. I couldn't for the life of me find a nice
>SVG of the Yocto logo,
>although I did scan through the brand guidelines pdf. They seem to point
>to the website
>but in the end I just scaled up the PDF and grabbed a capture from that...
>
>https://www.yoctoproject.org/sites/yoctoproject.org/files/yoctoproject_sty
>leguide.pdf
>
>I was looking for an OpenEmbedded logo for FOSDEM 2012 and Philip
>Balister kindly pointed me to this one,
>
>http://git.openembedded.org/openembedded/tree/contrib/artwork/oe.svg
>
>I hope that's of use, cheers,
>
>Alex
>
>On 30/01/2014 21:53, Paul Barker wrote:
>
>
>Hi, sorry this is a last-minute question.
>
>I'm throwing together slides for my talk at FOSDEM on Sunday and I
>could do with decent copies of the Yocto Project and OpenEmbedded
>logos to include where appropriate. I think having good images of the
>correct logos when I'm talking about OE/Yocto will help to show it off
>to possible users.
>
>I've got a Yocto Project logo off Google Image Search but I can't find
>a good OpenEmbedded logo that isn't a badly-JPEG-compressed image. If
>someone could link me to something better I'd really appreciate that.
>
>Also, the "Yocto Project Brand Guidelines" link on
>https://www.yoctoproject.org/about/trademark-policy points to the page
>https://www.yoctoproject.org/ecosystem/branding-compliance-guidelines.
>That page doesn't seem to contain any info.
>
>Cheers,
>
>
>
>
>--
> <http://www.dynamicdevices.co.uk/>
>Alex J Lennon/
>Director
>1 Queensway, Liverpool L22 4RA
>mobile: +44 (0)7956 668178
>
>
> <http://www.linkedin.com/in/alexjlennon> <skype:alexjlennon?add>
>This e-mail message may contain confidential or legally privileged
>information and is intended only for the use of the intended
>recipient(s). Any unauthorized disclosure, dissemination, distribution,
>copying or the taking of any action in reliance on the information
> herein is prohibited. E-mails are not secure and cannot be guaranteed to
>be error free as they can be intercepted, amended, or contain viruses.
>Anyone who communicates with us by e-mail is deemed to have accepted
>these risks. Company Name is not responsible
> for errors or omissions in this message and denies any responsibility
>for any damage arising from the use of e-mail. Any opinion and other
>statement contained in this message and any attachment are solely those
>of the author and do not necessarily represent
> those of the company.
>
>
next prev parent reply other threads:[~2014-01-31 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 21:53 Yocto Project and OpenEmbedded Logos Paul Barker
2014-01-30 23:15 ` Alex J Lennon
2014-01-31 10:24 ` Barros Pena, Belen [this message]
2014-01-31 9:39 ` Philip Balister
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=CF112A01.3BFDB%belen.barros.pena@intel.com \
--to=belen.barros.pena@intel.com \
--cc=ajlennon@dynamicdevices.co.uk \
--cc=paul@paulbarker.me.uk \
--cc=yocto@yoctoproject.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.