Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

Hi Marc, Thorsten, *

Marc Paré schrieb:
Le 2010-11-21 11:23, Thorsten Wilms a écrit :
Design vs Marketing, yes.

If you apply some of the broader definitions, you can both conclude that
Design touches everything and also that Marketing touches everything.
Originally marketing may have been all about selling and design all
about look and haptics, but both are starting positions where you end up
covering the entire system if you run long enough.

But you don't need to run that far....

Of course there are inter-dependencies between marketing and design - quite similar to the links between development and QA or development and UX.

But this doesn't mean to make any unsolvable problems.

What if we try to avoid both terms?
(if not combined with a more specific field)

I think they cover quite clearly what they want to say, so I'd keep them.

Nevertheless we can think of different sub-segments as working fields for specified teams, but I think most of them can be easily subsumed under one of the categories (especially if we think of the Design sub-categories Visual Design and UX Design).

* Steering (mission statement and strategy go here)
Much broader than marketing and design - it covers the central points of branding and needs to be discussed in the entire community.

* Visual Identity (starting from the logo)
Design (Visual D)

* Market Research

* Promotion (bound to have overlap with Visual Identity, sadly)
Marketing, by using resources from Design (Visual D)

* Relations (could have an internal partner, called Community)
Marketing (I'd like to see strengthening and broadening our community a central task for our marketing)

* Services (to outside the project)
not really clear to me what you mean: Product / user service? Marketing contacts? Links to software support providers?

* Documentation
Independent, but using Visual Design elements

* Infrastructure (contains website, similar to Services, but inside)
What does this contain besides website? Native-lang teams will have their own structure - I could imagine a place where they work together not only on L10N, but on infrastructure / NGO and other topics as well. If this would be inside the marketing area depends on what they want to achieve.

* UX Design (solely for the product)
UX is broader - covers product and website. Even Design might be too small, as it reaches to all the development and coding areas.

But in Design it is easy to find.

> [...] The wiki worskpace should then be in <-- this is where
you pronounce the reasons of Design

I don't think that creating very long lines of sub-categories will help us a lot. Therefore I already proposed as part of the Marketing category

We might think of
but I'd prefer
with Category:Design

Then presumably if there were any pages to for Design purposes the wiki
pages would be created here:

How does this sound?

Much too long paths!

Imagine we create one or two more sub-levels....

Only if the path is important to understand the topic of the page a sub-level should be created.

In all other circumstances categorizing the page in the relevant category leads to a better structure - and if a page covers two or more categories, sub-levels are no more applicable at all.

Best regards


Unsubscribe instructions: E-mail to
List archive:
*** All posts to this list are publicly archived for eternity ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.