On Mon, 2010-11-22 at 01:28 +0100, Bernhard Dippold wrote:
I think they cover quite clearly what they want to say, so I'd keep them.
If they would, there would be no question whether design should sit
below marketing or not. There would be no questions if the logo or a
brochure belongs to marketing or 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.
Yes. Mentioned it for completeness and to have a section that clearly
* Visual Identity (starting from the logo)
Design (Visual D)
It's design and marketing considerations. Visual Identity avoids the
blurriness of either term.
I would have proposed Corporate Identity as a more common term, that
could cover both Steering and Visual Design, but there's no corporation
* 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)
These 3 are indeed meant to be aspects of marketing taken apart. Making
it explicit what goes where. Allowing you to pick according to your
needs and interests.
* Services (to outside the project)
not really clear to me what you mean: Product / user service? Marketing
contacts? Links to software support providers?
Any service that is not targeted at the project itself. I would
anticipate mainly support.
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
It may be unlikely that anything comes up here that doesn't happen
online, but the term allows it. Website, wiki, bug tracker, source
repositories, IM and IRC channels ...
* 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.
I'm well aware that UX design can be applied to every area. This is
meant to be UX for just the product. So call it "Product UX Design" to
There could also be Infrastructure or Project UX Design.
We might think of
but I'd prefer
I'd prefer the last, too. Even more with "Visual Identity" instead of
thorwil's design for free software:
Unsubscribe instructions: E-mail to email@example.com
List archive: http://www.libreoffice.org/lists/marketing/
*** All posts to this list are publicly archived for eternity ***
Re: [libreoffice-marketing] [Design] Design team needs and Drupal site development · Christoph Noack
- Re: [libreoffice-marketing] [Design] Design team needs and Drupal site development (continued)
Impressum (Legal Info)
: 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