Bernhard Dippold wrote: > We need a central list for general discussions between developers and > non-coders. IMHO neither [EMAIL PROTECTED] nor [EMAIL PROTECTED] suite for > this purpose > as the work there has a different orientation.
I think we can achieve the goal in a different way. Developers can be reached at their dev-lists. So if somebody has a particular interest in something there is always a place where the discussion can happen. To give people a chance to become involved in planned work we could just put all information into a wiki page (like in case of the feature that started this discussion) and additionally announce this on a central (read only) mailing list so that interested people can become aware of the work before it actually starts and have a chance to get involved. The discussion about the feature should happen on a selected list where everybody interested can join. How should we treat "non-code" issues? I don't see a reason why we shouldn't discuss this on the project dev lists also. So in case of general aspects of templates the framework project seems to be appropriate, that more or less covers most of the topics that are not application specific. If the template *repository* is the topic then the extensions project seems to be the better place. But it should be the decision of the contributors where they want the discussion to happen as longa as the announcements are sent to the central list. I also think that the discuss list is problematic. A useful discussion about work in OpenOffice.org needs some dedication to the project and the will to focus on results. I'm not sure that these expectations are met by all subscribers of the discuss list. OTOH discussions like this one also shouldn't happen on a native-lang list (IMHO). I understand that it happened because many of the participants are used to use this list. But OTOH this is the same behavior that you criticize when shown by developers: staying in their own world and not looking for a broader audience. That's no offense, just an observation. When I think about reasons for this behavior I agree to Bernhard and others: we miss a discussion platform that is open for all but doesn't suffer from noise. I hope that my idea can help to solve this problem at least for some aspects of OpenOffice.org. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
