Hi Jani <div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">wouldn't it work faster and get more feedback if instead of a spec the site itself was prototyped? Take the ubuntu drupal theme, and with maybe minor CSS+art changes and the main (not archives) content of <a href="http://xubuntu.org">xubuntu.org</a> put it up somewhere. If you have access to <a href="http://xubuntu.org"> xubuntu.org</a> do you have enough rights to set up a subdomain for it (<a href="http://beta.xubuntu.org">beta.xubuntu.org</a>)</blockquote><div> If you don't use spec how do you thing work in a prototype ? What do you prototype ? </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Then people can get real feedback and proceed with improving it in small steps. Writing a spec is as you say boring, and I think it has the effect of demotivating people working on it, whereas a live site would get more contributors excited and be visible progress.</blockquote><div> I agree in the small steps are great because you can see the progress and that write spec is boring but I think is a must. </div></div> I first steps should be spec and the art. if you spend time in these boring topic the site is going to be create in a fast way. Because you don't think about what now just work follow a plan. I agree with you that the process is slow but depend on us to work to break this issue. All of us wish a nice site but The first step should be the goals what we want to reach. You can have a very good looking site but without the correct information don't make sense to change the site.