public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [rfc] Rendering the official Gentoo logo / Blender 2.04, Python 2.2
Date: Thu, 05 May 2011 04:31:10 +0200	[thread overview]
Message-ID: <4DC20BEE.6050904@gentoo.org> (raw)
In-Reply-To: <20110501080634.2eb18ab3@pomiocik.lan>

On 05/01/2011 08:06 AM, Michał Górny wrote:
> Isn't it possible to create a better SVG then?

It may be.  Of the three variants trying to match the Blender version
that I have seen so far, none is a replacement of equal quality on the
bling scale to my impression.  They feel like tradeoffs, not like the
real thing.  Maybe they try to come too close to the ray-traced
rendering, but I'm not sure if I really want to propose a different
direction either.


> I think such a variant
> would be much more portable and reproducible than blender files.

What I dislike about the idea of moving to a new logo is that we would
give up part of our culture just because we were unable to move it from
past to present to future.  Imagine this dialog:

 A: "Hey guys, I noticed you have a new logo?"
 B: "Yeah, blender rendering changed - so we dropped it."

I don't really want to be B in that dialog.  I see the pragmatic aspect
of moving to SVG but it also has the taste of giving up to me.  To
vercome that taste, a very strong replacement would be needed.

If we replace the Blender "g" we may also need a substitute for the
red-white Blender "gentoo" as seen at
http://sources.gentoo.org/cgi-bin/viewvc.cgi/*docroot*/images/gentoo-new.gif
if just for the sake of consistency.

I am wondering what effect the Blender nature of a logo does have on the
capability and will of people to create fan art based on it compared to
an SVG version.  It seems like there is only a handful of 3D Gentoo
wallpapers but does that mean it would have been more with an SVG
version, instead?  On what levels could SVG work as a catalyst?

If we ported the logo to Blender 2.57 now: what can we do to not be
running after Blender rendering changes for all time or to reduce their
impact on us?  Is this a natural cost or an evil one?

Just my 2 cents.

Best,



Sebastian



  reply	other threads:[~2011-05-05  2:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29  0:29 [gentoo-dev] [rfc] Rendering the official Gentoo logo / Blender 2.04, Python 2.2 Sebastian Pipping
2011-04-29  5:46 ` Michał Górny
2011-05-01  4:10   ` [gentoo-dev] " Ulrich Mueller
2011-05-01  6:06     ` Michał Górny
2011-05-05  2:31       ` Sebastian Pipping [this message]
2011-05-05  5:48         ` Michał Górny
2011-05-05  1:53     ` Sebastian Pipping
2011-05-05  5:36     ` Sebastian Pipping
2011-05-05 13:44       ` Marijn
2011-05-05 16:47         ` Sebastian Pipping
2011-05-05 17:04           ` Matthew Summers
2015-02-23 22:11       ` Sebastian Pipping
2015-02-23 22:29         ` Diego Elio Pettenò
2015-02-23 22:34           ` Daniel Campbell
2015-03-02 17:05             ` Sebastian Pipping
2011-06-07  9:15 ` [gentoo-dev] [rfc] Rendering the official Gentoo logo / Blender,2.04, " Mario Bodemann
2011-06-12 17:14   ` David Abbott
2015-03-25 15:12   ` Sebastian Pipping

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=4DC20BEE.6050904@gentoo.org \
    --to=sping@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox