I'm at UDS, and after speaking with kwwii, and _MMA_, I have written a
few notes, as well as some personal thoughts. This is mostly for the
planning process itself, but I am sending it to the list so everyone
is clued in as well :).
Things we discussed:
Dark theme, and incompatibilities from programs with hard coded
values. In terms of this, the current plan is to push a dark theme
into Ibex ASAP so people can begin to file bugs against the
applications in question.
The largest problem at the moment, is Icons. In order to create an
entirely cohesive theme we need to completely create our own set to
fit. However, there have been concerns raised about those icons that
don't match. This is especially accentuated by the fact that one of
the current proposals are the etched solid icons. However, this will
always happen: and in order to ever break out of Tango we need to
start somewhere. Tango is off the table--however, those that Human
currently doesn't fill since its been commissioned (in Dapper?) will
show up as Tango. In terms of where we need to go: 1. We need to
decide on a direction, 2. We have to lock down the minimum number of
worthwhile stable contributors. 3, and go from there. One item that
was raised was whether Canonical will purchase a new icon set. It
would certainly be easier on our man hours. Hopefully, if this
happens, the commission agreement will demand that the contracted
company supply Free artwork and make the sources available.
Icon themes: Besides the dark theme, etched glass etc: Perhaps we
should revamp Human, and extend it as well? I haven't tested whether
Human is mostly compatible with dark themes as it currently stands,
and I will look into that.
There is also the option of looking into a variety of other already
available gpl themes. We can customise and extend those.
Dark Theme
Dark Theme: If we do this, would we have to produce a companion light
theme as well? Or is the carryover from the last release sufficient
for those who prefer or need to work with something lighter. There is
also the question where people will accept a dark theme in which some
applications with hardcoded values produce some undesired results. I
think this is mostly a nonissue, as long as we can file bugs for the
major apps like FF. If we can pull off something that looks
impressive, or even just great looking-- people will be satisfied. In
art, the big picture always matters the most. It doesn't matter how
wonderful an eye, or finger is, if everything else is executed poorly.
In the same aspect it doesn't matter whether your icons are
jawdroppingly beautiful or your windows decorations if all else is
not. If things are cohesive, they don't have to be amazing looking.
Even if they are just quite good by themselves--when combined it can
make for an experience most impressive. It is the whole of the work
that applies.
Developers, and Packaging
One major concern is that we have no developers really interested in
developing for us--but the larger issue is that we still have to find
packagers. Hopefully, we can do that here at UDS. However, MMA has
informed me that the launchpad bzr can produce .debs, so this may be
somewhat mitigated. However, afaik (feel free to correct me) the
community theme package has still thus far not been produced? I'll
talk more about the community theme package and its importance later
in this psuedo-essay.
Infrastructure:
We also need to reduce the mess and make everything easily viewable.
This may come from ubuntu-art.org giving us a category or it may come
from a set of guidelines following along the lines of Fedora. One idea
was that people need to successfully contribute something in order to
post about the project. This would definitely reduce the amount of
naysayers and those with mouths that run, but feet that do not walk.
We have to decide whether these restrictions are necessary if we use a
gatekeeper as described lower.
--- My Thoughts:
What We Need
In terms of being even relatively successful, we need to do something
artistically strong and distinct. What does it mean to be 'strong'?
This means something that is cohesive and presents the same look and
feel. This means something conceptual behind it, even if it is
something simple. Why do we need a concept? This is the only way to
unify many disparate parts, especially in terms of working with
multiple contributors. I think, an important part of this, to be
successful, is a _gatekeeper_. This may be someone at UDS, but mostly
likely will be the concept or mockup originator.
What makes something artistically strong.
To be artistically strong-- this means we have to have defined our
vision greatly, in VISUAL terms. Which means supplying our references,
studies, and notes. However, the visual component is the most
important. Any competent artist, the ones we're interested in, will be
able to pick up the major elements and most probably bring an
interesting twist to it as well.
I think that the artwork 'team',
