<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title><![CDATA[Helping with art in Ubuntu is not accessible]]></title>
    <link>http://brainstorm.ubuntu.com/item/19139/</link>
    <description><![CDATA[I'm an artist and I'd really like to help with some of the Ubuntu art projects, problem is I had to visit around 3 different sites clicking on some 8 different links to get there and then I had to subscribe to a mailing list<br />
<br />


<b>[431 votes] Solution #1: Make it easier to submit to Ubuntu</b>
<br />

<br />
<br />



<b>[131 votes] Solution #2: point 5.  of Solution#1</b>
<br />

<br />
<br />



<b>[75 votes] Solution #3: Export/import</b>
<br />

<br />
<br />



<b>[-30 votes] Solution #4: Export to gnome-look</b>
<br />

<br />
<br />



<b>[89 votes] Solution #5: Constant Artwork Competition</b>
<br />

<br />
<br />



<b>[36 votes] Solution #6: Use Launchpad</b>
<br />

<br />
<br />



]]></description>

    <language>en-us</language>
    <pubDate>Fri, 10 Apr 2009 15:35:00 +0000</pubDate>
    <lastBuildDate>Tue, 05 May 2009 23:53:17 +0000</lastBuildDate>
    <generator>QAPoll module</generator>
    <guid isPermaLink="true">http://brainstorm.ubuntu.com/idea/19139/</guid>
        <item>
  <title>Comment from sayakb</title>
  <description><![CDATA[Design page points to the artwork team wikipage: https://wiki.ubuntu.com/Artwork<br /><br />If you feel that the page lacks relevant information, you may also contact the team directly at #ubuntu-artwork and request addition of the same.]]></description>
  <pubDate>Fri, 10 Apr 2009 16:14:19 +0000</pubDate>
</item>
        <item>
  <title>Comment from fred_t</title>
  <description><![CDATA[As an Industrial Designer wanting to help, I faced the same problem. I agree with you. I think Ubuntu is probably losing very good design concepts due to the lack of accessibility. I personally tried twice to participate by communicating my desire to help, but nobody paid attention. ]]></description>
  <pubDate>Fri, 10 Apr 2009 23:38:21 +0000</pubDate>
</item>
        <item>
  <title>Comment from Endolith</title>
  <description><![CDATA[Helping with anything in open source is not accessible.  There are five million hoops to jump through just to get a spelling error fixed in an application.]]></description>
  <pubDate>Sat, 11 Apr 2009 03:07:22 +0000</pubDate>
</item>
        <item>
  <title>Comment from baldurpet</title>
  <description><![CDATA[@ Endolith<br />Well why should it be that hard? Are you saying it's good that people jump through 5m hoops to help??<br /><br />Are you saying losing valuable workers because of a difficult process is a good thing?]]></description>
  <pubDate>Sat, 11 Apr 2009 18:28:02 +0000</pubDate>
</item>
        <item>
  <title>Comment from Endolith</title>
  <description><![CDATA[Where did I say it was good?  :)  I'm saying that this applies to much more than just art.  Anyone who wants to contribute to any part of open source has to do a lot of work just in preparation.  We need to lower the barriers.]]></description>
  <pubDate>Sun, 12 Apr 2009 02:48:47 +0000</pubDate>
</item>
        <item>
  <title>Comment from baldurpet</title>
  <description><![CDATA[Oops, right you are. You never said it was a good thing, I should really read comments before I start my little rants =D<br /><br />Yes, absolutely. My mom is a programmer, but she's very impatient and wants things to work right away or else she'll lose interest. Every time I think "is this accessible enough?" I ask myself whether my mom would bother with it]]></description>
  <pubDate>Sun, 12 Apr 2009 04:44:01 +0000</pubDate>
</item>
        <item>
  <title>Comment from KhaaL</title>
  <description><![CDATA[it would be cool if launchpad would have this functionality. You can already administrate bugs and translations there, so why not art too?]]></description>
  <pubDate>Sun, 12 Apr 2009 10:46:26 +0000</pubDate>
</item>
        <item>
  <title>Comment from baldurpet</title>
  <description><![CDATA[@ KhaaL<br />Oh that's a very good idea! Keeping everything related to Ubuntu at the same place and making it easy to improve..<br />I'm sure that it would pay off in a few months.<br /><br />I just want to add that when I say "issue commands" I was talking about telling the participant what is needed.<br /><br />If we go back to KhaaL's idea then think of it this way; Launchpad has a 'to-do' list of strings that need to be translated for every language and a 'to-do' list of bugs that need to be fixed- I would like to see Launchpad store a list of artwork (icons, wallpapers, logos etc.) that need to be drawn and it is imperative that suggesting ideas be as easy as translating or submitting bug reports to Launchpad!]]></description>
  <pubDate>Sun, 12 Apr 2009 12:09:33 +0000</pubDate>
</item>
        <item>
  <title>Comment from Basem</title>
  <description><![CDATA[The problem with exporting to GnomeLook is that Gnome look will eventually contain alot of semi finished uncompleted looks...<br />The purpose of exporting and importing is to be able to backup ur look and restore it later...or maybe simply sharing it with friends...]]></description>
  <pubDate>Tue, 14 Apr 2009 07:00:27 +0000</pubDate>
</item>
        <item>
  <title>Comment from baldurpet</title>
  <description><![CDATA[Yeah, I pointed it out in solution #4 but I wanted to submit it anyway to see what people thought]]></description>
  <pubDate>Tue, 14 Apr 2009 16:06:03 +0000</pubDate>
</item>
        <item>
  <title>Comment from Endolith</title>
  <description><![CDATA[<i>The problem with exporting to GnomeLook is that Gnome look will eventually contain alot of semi finished uncompleted looks...</i><br /><br />That wouldn't be so bad if there were a way for each to be part of a revision tree.  Like you take the default Human theme and modify it, and it shows up as a variant of Human, then someone else modifies yours, and it shows up in the tree below that...<br /><br />There could be voting on which variants are high quality to separate the good from the bad, etc.  <br /><br />Probably not something GnomeLook is capable of, though.  Maybe it needs a new website specifically for this.]]></description>
  <pubDate>Tue, 14 Apr 2009 16:23:19 +0000</pubDate>
</item>
        <item>
  <title>Comment from baldurpet</title>
  <description><![CDATA[@ Endolith<br />That is actually a good idea!<br />It might be a little difficult to implement but other than that it sounds, then if one theme e.g. has a lot of branches you can tell that it must be a pretty good theme (just like Ubuntu has around 20-30 branches so there must be something people like about it)]]></description>
  <pubDate>Tue, 14 Apr 2009 17:33:50 +0000</pubDate>
</item>
        <item>
  <title>Comment from Endolith</title>
  <description><![CDATA[<i>then if one theme e.g. has a lot of branches you can tell that it must be a pretty good theme</i><br /><br />Maybe.  :)  Really, it would just show that lots of people have it.  Obviously Human would have tons of branches since it's the default, for instance.  My idea was that this would:<br /><br />1. Reduce the number of themes you have to look through.  They'd all be "variants" of a base theme, so there would just be a list of base themes to navigate through, instead of a list of thousands of themes that only vary slightly from each other.<br />2. Show relationships between themes, instead of just arbitrary rankings.  So if everyone likes theme A, but then someone makes an improved version theme B, and everyone who downloads B likes it better than A, then the site should show this somehow.  It should hide A and only display B as an updated version of A.<br /><br />Like on Slashdot, there are huge discussion threads with many branches, and they use an algorithm to only display the best comments and hide the rest.  If you're interested in a certain comment that you see in this "wide" view, you can then drill down and view the discussion surrounding it that was previously hidden.<br /><br />Similarly, if you like a certain theme, you can drill down and view others that are related to it.<br /><br />I'm just trying to think of a way to separate the good from the bad.<br /><br />I made a similar proposal for <a href="http://getsatisfaction.com/mozilla/topics/ubiquity_commands_should_have_ancestors_and_descendants">similar proposal for Mozilla Ubiquity</a>.]]></description>
  <pubDate>Wed, 15 Apr 2009 14:55:38 +0000</pubDate>
</item>
        <item>
  <title>Comment from philip</title>
  <description><![CDATA[It makes sense to have a general system to accommodate bug reports, enhancement requests, code patches and artwork]]></description>
  <pubDate>Tue, 05 May 2009 23:53:17 +0000</pubDate>
</item>
      </channel>
</rss>
