<div dir="ltr"> <div class="gmail_quote">2008/9/11 Cory K. <<a href="mailto:coryisatm@ubuntu.com">coryisatm@ubuntu.com</a>> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">Dylan McCall wrote: >> Odysseus Flappington wrote: >> >>> I think just by slotting in the word 'community' into the definition, >>> you're already implying that you aren't affiliated with Ubuntu >>> officially, and have no decision making power in regards to the >>> default theme. >>> >> Is this a problem for you or anyone? >> > > I do find this a bit of a problem. I like the idea (no, /love/ the > idea!) of a diverse community themes pack. I also think that people > should create a lot of high quality themes for that package and not > always aim at taking top slot as default theme. Of course, community > themes are still Ubuntu themes so would ideally follow the palette. > </div>Agreed. But, I would not be opposed to say a great blue theme if it was of quality and a big push from the community. <div class="Ih2E3d"> > With lots of open source projects, I get the distinct impression that > artwork is based on a totally different set of rules than code. </div>I would say very much so. But there are, or can be common framework. <div class="Ih2E3d"> > Case > in point, Mozilla and that Iceweasel fiasco -- largely because Debian > wanted to use completely free artwork. > </div>Nothing wrong with that. Just a pain. <div class="Ih2E3d"> > Over here in Ubuntu, I think it is an issue that the theme work and > theme decision making is very quiet. I'm not saying that it isn't > open, because Ken does just fine answering questions. (Besides that, > it ultimately boils down to - paraphrasing - "nobody can explain it, > but Mark just has naturally good taste in colours"). However, when > people think of the official theme as detached from the community > here, we run the risk of a situation developing just like Mozilla's. > With art, the community contributes ideas, and -- just like with code > -- those ideas occasionally find their way into official work when the > maintainers like them. The difference here is that those ideas tend to > be just ideas rather than measurable "things" (eg: specific changes to > an options dialog). > > It would help if the folks behind the default theme were a little bit > more inclusing visible about their own work there, just like the > different groups working on community themes. That would help reduce > some confusion here with regards to what is being done, it would be > more productive and it would give the art development that touch of > openness it needs. "The default theme" would stop being some kind of > looming Goliath figure and simply be a part amongst us mortals. </div>Well Ken W and Mark says what's default. Ken is pretty open about what he is doing. It's usually in a PPA or development version of Ubuntu. The problem is that it's not been clearly communicated that default is not this teams target. That's what I'm hoping to do with this current discussion. Come to some kinda consensus as to the description so it can be clearly posted on LP and the wiki. Then, move on with what we actually want to achieve in a given cycle, as a team. </blockquote></div> What is the artwork team? 'A transient group of disparate individuals chirping away in a mailing list, and finding that it is all in vain anyway, only to stop posting to the list having achieved little before eventually unsubscribing.' A perfect example of this is Salane Ashcroft I believe his name was, who was all over the mailing list a few months back, anyone who would have joined the list back then would have thought he was artwork community leader. From Cory's posts in the last few days it looks as if he is trying to gain some kind of order, and a bid for community leader for himself, I don't post to this list often but I do try to keep up to date with the happenings, and I have to say this is probably exactly what is needed. The Artwork Team is a misnomer, it is not a team in any definition of the word, it should follow a development cycle, have submission deadlines. If Cory has a plan to transform this list into a real community team, just appoint him community-leader and focus on how the development cycle should be arranged for 9.04. He is the only possible candidate anyway and its damn obvious this community needs someone like him to kick some ass and get it working like it should be. Michael </div>