Mirek, *, Regards para 1): why would there need to be a developer already in agreement to start the process? It would be nice if one, or more, were already on board, but much of the argument for implementation actually comes from fleshing out the details of what the enhancement should be.
Admittedly a developer's understanding of the structure of the program and cross platform implementation early in the process improves feasibility of implementation and can provide reasonable bounds to the design. But, waiting for developers to appear and take an interest otherwise stifles design. On the other hand, if there is a reasonable flow of good designs from the Design process that result in implementation then that flow becomes the norm. More developers will "check-in" to see what needs to be worked on, and I'd expect that a fair number would actually make design contributions. As is now many do their own design work while implementing their code. Stuart -- View this message in context: http://nabble.documentfoundation.org/Revisiting-our-project-workflow-tp4114936p4114974.html Sent from the Design mailing list archive at Nabble.com. -- 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
