[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Small KOffice interaction design meeting in middle november?
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2006-11-03 18:53:01
Message-ID: 200611031153.01282.aseigo () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 02 November 2006 16:02, Sebastian Sauer wrote:
> On Thursday 02 November 2006 23:22, Thomas Zander wrote:
> > On Thursday 02 November 2006 23:03, Sebastian Sauer wrote:
> > > I don't see
> > > how that could solve the in my eyes somewhat bigger prob of
> > > "everything is part of the whole coperate KDE-desktop". E.g. KOffice
> > > is KDE's office-suite, but is that true?
> >
> > Yes, its true.
>
> So, KOffice makes only sense in KDE-desktop environments (that is if a user
> runs the KDE-desktop - or as Aaron named it pretty good; things like
> kicker+kwin+etc.) ?

bug: confusion of KDE's workspace with the KDE brand.

> Do we really like to be recognized as "the Office-suite for the
> KDE-desktop" (please note the limitation the sentence imply) or as "the
> Office-suite".

bug: confusion of KDE's workspace with the KDE brand.

> > We already have seen that the lines to Qt are getting a bit longer then
> > we like, having the effect that its harder to get patches and features
> > in. Do we really want the same thing in KDE?
>
> eh, we don't talk here about refactoring code or something like this. It's
> all about presentation of the result. While the "coperate desktop" image
> makes a lot of sense for KDE imho it does not for KOffice except the
> target-group are KDE-users only.

bug: misidentifying KDE's image as "the corporate desktop". this is ONE image.

> > On the technical and the social as well as the political aspects I feel
> > like I'm part of KDE. And your email leaves me very confused as to
> > where our difference in opinion stems from.
>
> For sure KO is and will stay forever part of KDE. But that's not the
> question since we don't deal with black and white here. ppl need to
> recognize FIRST that KOffice is a office.suite and SECOND or THEIRD that
> it's part of KDE and not the other way around.

i think even this is the wrong granularity. people should identify with the 
applications first and foremost. why? because the applications are hugely 
varied in scope (imagery, presentations, project management, 
word/spreadsheet, reporting) and are not uniformly mature as they should be 
if truly part of a suite.

the app is a part of the KOffice brand which is a KDE brand.

> > So, can we work with the board and solve any issues that make you state
> > that KOffice has no identity?
>
> Okeli dokeli... let's propably start with a small list;
> 1. we need an own icon (top priority :)

yes, to be a brand you need a logo (not an icon; base the icon off the logo)

> 2. for the next gsoc we should imho participate as "KOffice organization"

i'm not sure what the obsession over this is since it really matters zero n 
the large scheme of marketing or brand foundations and KOffice is not 
interesting to Google due to project attributes.

> and earn that way at least the same number of "summer-devels" like abiword
> and gnumeric

this would be nice to do achieve; does it matter if its under the KDE umbrella 
or not though?

> 3. get koffice-libs ready for reuse once ko2 is "stable" as discussed at
> aKademy.

yes!

> 4. seek for sponsors any may it only to start our own "summer of code"

cool idea

> 5. PR, PR, PR...

i'd love to see the KOffice PR coordinate thematically with KDE4 PR.

> 6.
> 7. rule the world

=)

> to bad that I forgot what step 6 was :-/

undulate your wantonness

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)

[Attachment #5 (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]