<br><br><div><span class="gmail_quote">On 3/4/06, <b class="gmail_sendername">Pascal Klein</b> <<a href="mailto:4pascal@tpg.com.au">4pascal@tpg.com.au</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, 2 Mar 2006 17:01:19 -0600<br>"Matthew Nuzum" <<a href="mailto:mattnuzum@gmail.com">mattnuzum@gmail.com</a>> wrote:<br><br>> On 3/2/06, Pascal Klein <<a href="mailto:4pascal@tpg.com.au">4pascal@tpg.com.au
</a>> wrote:<br>> > On Thu, 2 Mar 2006 10:46:57 +0000<br>> > Who <<a href="mailto:mailforwho@googlemail.com">mailforwho@googlemail.com</a>> wrote:<br>> ><br>> > > Hi, and hello list!<br>
> > ><br>> > > I thought, given what Mark has said recently about getting some high<br>> > > quality, polished themes into the repositories soon, that we ought to get<br>> > > straight to discussing which themes will be 'operated on'.
<br>> > ><br>><br>> Pascal,<br>><br>> I will not be able to attend the meeting this weekend, but let me<br>> contribute some food for thought.<br>><br>> The art-list until now has been a place where people tossed out ideas
<br>> and art they have done. This is fine, but if the goal is to get art<br>> into Universe so that it can be considered for inclusion into main,<br>> maybe there should be a discussion as to what the decision makers want
<br>> to see.<br>><br>> It is much easier to hit the target when you can see the target.<br>> Blindly shooting arrows into the sky may result in a direct hit, but<br>> it's not likely. I'm still using Breezy and Hoary, so I can't see what
<br>> graphical elements have been proposed for Dapper and therefore can't<br>> make direct suggestions, but here is what might be asked and therefore<br>> decided upon:<br>><br>> - what colors should be used?
<br>> - is there a theme that should underlie the artwork? (for example,<br>> when RH released blue curve, there was a definite theme and coherency<br>> to the artwork)<br>> - what are our greatest needs?<br>
> - the difference between a slick, polished, enterprise grade<br>> application and something that looks like it was hobbled together is<br>> the attention to detail. Therefore, identify areas of the interface<br>
> that look 'fine' or 'not bad' but don't have the professional 'shine'<br>> that we want to be represented in the Linux community for the next 5<br>> years (the expected support life span of dapper).<br>><br>
> Dapper is going to be around a while, and if anyone on the art-list<br>> wants to be relevant to the upcoming project, they need to think<br>> long-term when they think about this release.<br>><br>> Five years from now there will be people saying, "Well... it's about
<br>> time we upgrade those old Dapper computers..." Their thoughts about<br>> the look and feel could be one of the following:<br>> - "Remember when these came out? They really set the bar for the next
<br>> few generations of desktops."<br>> or<br>> - "Wow, can you believe someone thought this looked good?"<br>><br>> This weekend's meeting can decide what people will be saying when that<br>
> day comes.<br>> --<br>> Matthew Nuzum<br>> <a href="http://www.bearfruit.org">www.bearfruit.org</a><br>><br>><br><br><br>Very true. I think a wiki page for this would be good. I'll add it to<br>my to-do. :) I'd very much appreciate any input anyone could supply in
<br>regard to Matthew's ideas especially for the wiki page.<br><br>Cheers.</blockquote><div><br>
Pascal,<br>
What sort of thing were you expecting that the wikipage would cover -
could we add something to the additional themes page (which people are
using now!)<br>
<br>
I can add some details about what needs to be decided on for a theme -
I thought maybe making an 'Addirional theme template' that people had
to fill in for a theme (one for each of the three themes we decide on)
would force people to think about all the aspects Mathew talked about
(eg colour, bg, gdm etc...)<br>
</div><br>
See you all in IRC - this will be my first time, so go easy :P<br></div>