Discussion

Differences between revisions 12 and 13
Revision 12 as of 2009-04-13 15:24:26
Size: 3168
Editor: p5089689E
Comment:
Revision 13 as of 2009-04-13 17:18:09
Size: 2899
Editor: p5089689E
Comment: Principles now included in Documentation/Process
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:


== Principles ==

Decisions based on facts are best. Decisions based on assumptions are better than random decisions.

Strict and tight requirements help us, because they restrict the otherwise infinite space of possibilities in design and make it manageable.

Ideas, Opinions, Collaboration

The Ubuntu artwork community at times sufferes from an influx of random ideas and random opinions. It is often unclear what people are trying to achieve with their ideas. Assumptions are made, but not communicated. There's no basis for discussion and teamwork, if the intentions and assumptions are unknown.

Opinions often come down to a "I like this" or "I don't like that". The value of such opinions brought forward on the list, IRC channel, forum and many other places are overestimated by some. Just because someone is vocal doesn't mean that they have any insight or can speak for others. We must assume that we do not hear from the majority of users.

Opinions without reason and context are not helpful. There are so many and often conflicting ones. It is not that interesting what our artwork means to a single random person, of whom we might not even have background information. We have to ask what it is likely to mean to our audience in the context of what we want to achieve.

We need to pull hidden assumptions into the light to either share or drop them. We need a tool to overcome personal taste, something that can be used as measure for all efforts. A central set of goals is required to get people to work together in a meaningful way. This falls in line with the needs of this design process itself.

Education and Competency

There's a lack of skilled and trained artists and designers in the Free Software world. A highly visible and structured ongoing design process should have educational value. It can serve as introduction and training ground for newcomers. Showing competency might attract skilled and knowledgeable people who would otherwise worry about being met with ignorance.

Discussing Artwork

If you present an idea or artwork, you should state

  • what you are trying to achieve with it.
  • who should be the audience.
  • the relevant assumptions you made.

If you want to criticise artwork, you should know about the above. But if you do or don't, it can be rewarding to express what you would think the artwork implies by itself.

It is often enlightening for the artist to have his work described by others.

You should not try to make people feel good about their art regardless of actually perceived quality. While no one should be discouraged from being creative, people need honest feedback to improve and to know where they stand. For some, this might not be the right venue at all. However, make a practice out of looking for and listing not only bad aspects, but also good aspects.

Consider the amount of work that was likely required to create what you are criticising. Adjust your own effort and care accordingly.

Artwork/Documentation/Discussion (last edited 2009-04-17 12:16:30 by p508965B5)