On Fri, Jun 19, 2015 at 3:55 AM, Carsten Haitzler <ras...@rasterman.com> wrote: > After some prodding we now have the following at the bottom of:
Hello raster, [snip] > Any comments? I think the following in Boost policy is very useful to have and be used in the guidelines(Do a mental s/Boost/Enlightenment/): <snipet> * Guidelines for Effective Discussions Apply social engineering to prevent heated technical discussion from degenerating into a shouting match, and to actively encourage the cooperation upon which Boost depends. Questions help. If someone suggests something that you don't think will work, then replying with a question like "will that compile?" or "won't that fail to compile, or am I missing something?" is a lot smoother than "That's really stupid - it won't compile." Saying "that fails to compile for me, and seems to violate section n.n.n of the standard" would be yet another way to be firm without being abrasive. If most of the discussion has been code-free generalities, posting a bit of sample code can focus people on the practical issues. If most of the discussion has been in terms of specific code, try to talk a bit about hidden assumptions and generalities that may be preventing discussion closure. Taking a time-out is often effective. Just say: "Let me think about that for a day or two. Let's take a time-out to digest the discussion so far." </snipet> The "Questions help" really changes the mood of discussions and make for a more amicable and affectionate relationship between members. Kind regards, -- Felipe Magno de Almeida ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
