On Sun, 2010-11-21 at 20:49 +0930, Michael Wheatland wrote: > In addition to this we can build a 'exhibition system' which would > allow people outside of the design team to see examples of projects > that the design team have completed, but that is the next step, we > need to build the groundwork first.
I don't think you have to make ongoing projects inaccessible to the public. It would increase hurdles, encourage an "Us vs Them" mentality and reduce chances of inspiring people. You just need to be very clear about the project status. It might happen that some not fully thought-through concept will be reported about in a misleading way, then. Seen stuff like that happen, it is very annoying at first, but usually 2 weeks later it shows to not really matter at all. > See the design workflow summary here: > http://wiki.documentfoundation.org/Website/Drupal/Design > > Can you please make any comments regarding the appropriateness of the > workflow and project states. Any additional functionality of the > Request-Develop-Feedback-Approve-Launch sequence and inputs and > outputs to the system should be built now. > I hope this satisfies all those designers out there who are hungry for > a taste of what is to come. I have my troubles with reading that diagram. However, "Request-Develop-Feedback-Approve-Launch" sounds good. Does "brainstorm system" refer to something like http://www.ideatorrent.org/? Especially when dealing with visual design, it is critical to get past simple "I like / I don't like it" reactions. As far as a kind of voting is required, I would try to ask something along the lines of: "In how far does the proposal meet the briefing/requirements"? With maximally 5 values from "not at all" to "most excellently so!" -- Thorsten Wilms thorwil's design for free software: http://thorwil.wordpress.com/ -- Unsubscribe instructions: E-mail to marketing+h...@libreoffice.org List archive: http://www.libreoffice.org/lists/marketing/ *** All posts to this list are publicly archived for eternity ***
