Seems like a solid idea to me, and I can't really see any drawbacks for not doing it.<br><br clear="all">-Matthew Lye<br><br>You can do anything you set your mind to when you have vision, determination, and and endless supply of expendable labor.<br>
<No tree's were harmed during this transmission. However, a great number of electrons were terribly inconvenienced><br>
<br><br><div class="gmail_quote">On Mon, Mar 30, 2009 at 3:54 AM, John Baer <span dir="ltr"><<a href="mailto:baerjj@gmail.com">baerjj@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I see Community Themes as a great opportunity which adds value in many<br>
ways.<br>
<br>
1. IMO folks want to contribute to Ubuntu in meaningful ways. Community<br>
themes can be a driver for that desire and a place for effort that<br>
measures up.<br>
<br>
2. Community themes adds value to Canonical as a testing ground for<br>
effort being considered for default.<br>
<br>
3. Community themes adds value to the creation of community artwork. New<br>
effort is added and old removed every release cycle. It also provides an<br>
opportunity to validate all of the "i" 's have been dotted, and the "t"<br>
's crossed (e.g. no copy righted material, agreed architecture, etc).<br>
<br>
Just my thoughts ...<br>
<br>
John<br>
<font color="#888888"><br>
<br>
<br>
--<br>
ubuntu-art mailing list<br>
<a href="mailto:ubuntu-art@lists.ubuntu.com">ubuntu-art@lists.ubuntu.com</a><br>
<a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-art" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-art</a><br>
</font></blockquote></div><br>