[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-promo
Subject: Re: [kde-promo] Changing how we market the workspace
From: "Wade Olson" <wade () corefunction ! com>
Date: 2008-10-15 15:05:40
Message-ID: a42b7670810150805k379d9fb3y6b5a31e8798224c9 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Mon, Oct 13, 2008 at 2:32 PM, Aaron J. Seigo <aseigo@kde.org> wrote:
> On Sunday 12 October 2008, Cornelius Schumacher wrote:
> > On Thursday 09 October 2008 03:52:21 Aaron J. Seigo wrote:
> > > the Apache Apache webserver. that's not something to emulate, indeed.
> of
> > > course, we already have KDE KDE. ;)
> >
> > That sounds like a straw man argument. Nobody says "Apache Apache" or
> "KDE
> > KDE". The Apache community creates the Apache HTTP server, just like the
> > KDE community creates the KDE platform and the KDE applications. Of
> > course "Apache" is often used to refer to the HTTP server because it's
>
> which is the entire point, leading to the sorts of unfortunate confusion
> regarding the Apache brand that people such as Stephen Kelly go through.
>
> using the term "Apache Apache" is meant to highlight the problem in clear
> terms: because there is no "Apache Apache", people just say "Apache" when
> really they mean the "Apache HTTP server" leading to the limiting of
> perception to "Apache" being "that http daemon" and nothing else, or that
> Apache products require "that http daemon they make".
>
> so "Apache Apache" is not a straw man, it's illustrative. just as nobody
> really says "KDE KDE" though we've used that exact phrase to explain the
> challenges we face.
>
> > concise and easily understood, just like "KDE" is used and understood to
> > refer to the platform and core set of applications we release as "KDE".
>
> obviously, and this leads to market confusion. we get it, the rest of the
> world tends not to and for very understandable reasons.
>
> haven't we already gone through all of this several times?
>
> > There are plenty of examples where the name of the creator and the name
> of
> > the product are the same. What's wrong, if "I use KDE" sounds like "I
> drive
> > a Porsche"?
>
> because Porsche actually wants you to primarily associate their brand with
> the
> car line, and because saying "I have a Porsche handbag" or "I have a
> Porsche
> laptop" doesn't cause people to think "You probably have to use that in a
> Porsche car" and therefore prevent people from purchasing Porsche branded
> products just because they don't have a Porsche car.
>
> the two examples are therefore not comparable in this situation.
>
> In reading this discussion, I think it's important to explicitly state one
milestone to gain perspective.
Based on all the text refining exercises, distill what KDE is down to the
purest level.
It's either:
"Software created by people." or "People that make software." Then we go
from there. I tend to believe that over the past couple of years the
predominant thinking has slowly shifted from the former to the latter. And
that's good.
If you want to talk marketing: realize what the assets are and what the
Competitive Advantage and the Unique Selling Proposition is. It's a metric
shitload of great, smart people that get along just well enough to do great
things together. Hence my first image was about different people but same
vision.
I only bring this up now to "level set". It's fundamental before building
on it, and some of the posts seem to get distracted then when discussing how
to frame other aspects of KDE (such as releases). This stance is really at
the root of every forking conversation: if KDE community goes away, KDE
withers. If the code goes away, who cares, KDE could just make more and
better code.
So if we take this pure, atomic statement of "People that make software"
then we can build on it, which is exactly what Aaron did a little while ago
in the rephrasing "KDE is an international technology team that creates Free
Software..."
Sorry if this has been covered already in some thread I haven't yet read.
If everyone in this thread shares this stance, we'll have better luck with
framing out ideas like "KDE releases KDE KDE..."
[Attachment #5 (text/html)]
<div dir="ltr"><br><br><div class="gmail_quote">On Mon, Oct 13, 2008 at 2:32 PM, \
Aaron J. Seigo <span dir="ltr"><<a \
href="mailto:aseigo@kde.org">aseigo@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Sunday 12 October 2008, \
Cornelius Schumacher wrote:<br> > On Thursday 09 October 2008 03:52:21 Aaron J. \
Seigo wrote:<br> > > the Apache Apache webserver. that's not something to \
emulate, indeed. of<br> > > course, we already have KDE KDE. ;)<br>
><br>
> That sounds like a straw man argument. Nobody says "Apache Apache" or \
"KDE<br> > KDE". The Apache community creates the Apache HTTP server, \
just like the<br> > KDE community creates the KDE platform and the KDE \
applications. Of<br> > course "Apache" is often used to refer to the \
HTTP server because it's<br> <br>
</div>which is the entire point, leading to the sorts of unfortunate confusion<br>
regarding the Apache brand that people such as Stephen Kelly go through.<br>
<br>
using the term "Apache Apache" is meant to highlight the problem in \
clear<br>
terms: because there is no "Apache Apache", people just say \
"Apache" when<br> really they mean the "Apache HTTP server" \
leading to the limiting of<br> perception to "Apache" being "that http \
daemon" and nothing else, or that<br> Apache products require "that http \
daemon they make".<br> <br>
so "Apache Apache" is not a straw man, it's illustrative. just as \
nobody<br> really says "KDE KDE" though we've used that exact phrase to \
explain the<br> challenges we face.<br>
<div class="Ih2E3d"><br>
> concise and easily understood, just like "KDE" is used and understood \
to<br> > refer to the platform and core set of applications we release as \
"KDE".<br> <br>
</div>obviously, and this leads to market confusion. we get it, the rest of the<br>
world tends not to and for very understandable reasons.<br>
<br>
haven't we already gone through all of this several times?<br>
<div class="Ih2E3d"><br>
> There are plenty of examples where the name of the creator and the name of<br>
> the product are the same. What's wrong, if "I use KDE" sounds like \
"I drive<br> > a Porsche"?<br>
<br>
</div>because Porsche actually wants you to primarily associate their brand with \
the<br> car line, and because saying "I have a Porsche handbag" or "I \
have a Porsche<br> laptop" doesn't cause people to think "You probably \
have to use that in a<br> Porsche car" and therefore prevent people from \
purchasing Porsche branded<br> products just because they don't have a Porsche \
car.<br> <br>
the two examples are therefore not comparable in this situation.<br>
<div><div></div><div class="Wj3C7c"><br></div></div></blockquote><div>In reading this \
discussion, I think it's important to explicitly state one milestone to gain \
perspective.<br><br>Based on all the text refining exercises, distill what KDE is \
down to the purest level.<br> <br>It's either:<br><br>"Software created by \
people." or "People that make software." Then we go from \
there. I tend to believe that over the past couple of years the predominant \
thinking has slowly shifted from the former to the latter. And that's \
good.<br> <br>If you want to talk marketing: realize what the assets are and what the \
Competitive Advantage and the Unique Selling Proposition is. It's a metric \
shitload of great, smart people that get along just well enough to do great things \
together. Hence my first image was about different people but same vision.<br> \
<br>I only bring this up now to "level set". It's fundamental \
before building on it, and some of the posts seem to get distracted then when \
discussing how to frame other aspects of KDE (such as releases). This stance is \
really at the root of every forking conversation: if KDE community goes away, KDE \
withers. If the code goes away, who cares, KDE could just make more and better \
code.<br> <br>So if we take this pure, atomic statement of "People that make \
software" then we can build on it, which is exactly what Aaron did a little \
while ago in the rephrasing "<a name="cp-content">KDE is an international \
technology team that creates Free Software..."<br> <br>Sorry if this has been \
covered already in some thread I haven't yet read. If everyone in this \
thread shares this stance, we'll have better luck with framing out ideas like \
"KDE releases KDE KDE..."<br> </a></div></div></div>
_______________________________________________
This message is from the kde-promo mailing list.
Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on \
or temporarily stop your subscription.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic