mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 00/12] add PNG support
Date: Fri, 7 Sep 2012 00:25:59 +0200	[thread overview]
Message-ID: <20120906222559.GK26594@pengutronix.de> (raw)
In-Reply-To: <20120906215050.GK20330@game.jcrosoft.org>

On Thu, Sep 06, 2012 at 11:50:50PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 18:03 Thu 06 Sep     , Sascha Hauer wrote:
> > The discussion in this thread makes it clear that there are two problems
> > with this logo, one technical and one political.
> > 
> > The technical problem:
> > 
> > From a technical pov it makes no sense to put big image binaries into
> > the repository when a small svg image would be sufficient to generate
> > all other images.
> > 
> > The political problem:
> > 
> > For an open source project a closed image is a no go. We (and by we I
> > mean we as the community, not we as Pengutronix) must for example be
> > able to:
> > 
> > - generate versions with different colors, sizes, dimensions
> > - generate a logo without text
> > - modify the image and to redistribute without limitations
> > - add a journal to the logo and use it for bwn.org (barebox weekly news) ;)
> As on Linux, Meego , Mozilla, Coreboot and others Logo are copyrighted and protected

From http://commons.wikimedia.org/wiki/File:Tux.svg:

| The copyright holder of this file allows anyone to use it for any
| purpose, provided that the copyright holder is properly attributed.
| Redistribution, derivative work, commercial use, and all other use is
| permitted.

So the Linux logo can explicitely be modified (derivative work)

You mentioned that:
> It's free to USE without modification for the Barebox Project
                   ^^^^^^^^^^^^^^^^^^^^

Whereas is coreboot we have (from http://www.coreboot.org/Logo):

| This logo or a modified version may be used by anyone to refer to the
| coreboot project

btw, the mentioned projects do not seem to have a problem with svg
files:

http://upload.wikimedia.org/wikipedia/commons/1/14/MeeGo_logo.svg
http://commons.wikimedia.org/wiki/File:Tux.svg
http://upload.wikimedia.org/wikipedia/en/7/74/Mozilla_Foundation_logo.svg
http://upload.wikimedia.org/wikipedia/de/e/ec/Coreboot_logo.svg

> 
> This is a standard for project image protection
> 
> Modify the image means the image is not Barebox Logo
> (Modify in the limit of the Licence)

Does this mean it can be modified or exactly the opposite?

Could you send a license text?

Thanks
 Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-09-06 22:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  6:00 Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04 ` [PATCH 01/12] add barebox logo Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04   ` [PATCH 02/12] bmp: rename it to splash Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04   ` [PATCH 03/12] bmp: split bmp rending in lib/bmp.c Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04   ` [PATCH 04/12] introduce image_renderer framework Jean-Christophe PLAGNIOL-VILLARD
2012-09-06 10:42     ` Jan Lübbe
2012-09-06  6:04   ` [PATCH 05/12] filetype: add BMP support Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04   ` [PATCH 06/12] splash/bmp: switch to image_renderer Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04   ` [PATCH 07/12] splash: add support to set a background color Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04   ` [PATCH 08/12] Introduce graphic utils Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04   ` [PATCH 09/12] graphic_utils: add rgba support Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04   ` [PATCH 10/12] filetype: add PNG support Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:04   ` [PATCH 11/12] " Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  6:05   ` [PATCH 12/12] png: add picoPNG lib support Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  8:56     ` Antony Pavlov
2012-09-06 10:37   ` [PATCH 01/12] add barebox logo Jan Lübbe
2012-09-06 10:44     ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-06 12:00       ` Eric Bénard
2012-09-06 12:16   ` Sascha Hauer
2012-09-06  7:37 ` [PATCH 00/12] add PNG support Eric Bénard
2012-09-06  8:55   ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  9:10     ` Eric Bénard
2012-09-06  9:47       ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-06  9:55         ` Eric Bénard
2012-09-06 10:03           ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-06 10:12             ` Eric Bénard
2012-09-06 10:29               ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-06 11:59                 ` Eric Bénard
2012-09-06 16:03 ` Sascha Hauer
2012-09-06 21:50   ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-06 22:25     ` Sascha Hauer [this message]
2012-09-07  0:18       ` Jean-Christophe PLAGNIOL-VILLARD

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=20120906222559.GK26594@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=plagnioj@jcrosoft.com \
    /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