Hi guys, One of the things we badly need is a good decision-making workflow. We've discussed this on the last IRC chat [1] and that lead to my rough draft:
1) A problem is presented, either on the ux-advise mailing list or on the design list. Feedback and possible solutions are collected on the relevant Bugzilla page or, if a Bugzilla page doesn't make sense for the problem, on the design mailing list. 2) The topic is discussed at the following IRC chat [4]. Proposals that don't adhere to our guidelines and principles or are infeasible are discarded. 3) If all attendees as well as all the design team experts (contacted separately if not present) unanimously agree on a certain proposal, it is chosen as the solution. 4) If they don't, the user testing expert conducts a test of the possible solutions. 5) If a test is inconclusive, proves inaccurate, or can't be held, the proposed solutions are voted on. "None of the proposed solutions are satisfactory" is always an option. The vote is announced at least on the design mailing list. 6) The whole process is repeated until a satisfactory solution is found. Let's test this workflow by applying it here. Please give feedback and/or propose a different workflow in this thread. [1] https://wiki.documentfoundation.org/Design/Meetings/2014-06-29 [2] https://wiki.documentfoundation.org/Design/Meetings -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
