<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 30 Sep 2014, at 23:02, Simon Poole <<a href="mailto:simon@poole.ch">simon@poole.ch</a>> wrote:</div><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF"><div class="moz-cite-prefix"><br>
You simply can not assume that you are getting the full picture
and are participating on a single continuous thread of
communication between all participants.<br>
<br>
Nothing we can do about this, but I suspect the utility of
osmf-talk as a semi-private mailing list has outlived itself given
that the model actively provokes parallel comms. I would suggest
either doing away with it completely or scoping it strictly to
OSMF business. <br></div></div></blockquote><br></div>We can at least try to do something about this broken communication model. Someone suggested written code of conduct in OSM lists. What about stating there, that highjacking a thread or topic to another channel is forbidden? Commenting OSM list topics things in twitter etc, so the original posters quite probably do not see it, is not “parallel comms”, it is talking behind one's back, which is in my own culture is regarded as very bad manners, something what "only put-your-least-favorite-social-group-here do” and which smells very bad. Maybe the new multi-channel social media has new rules about it, if so then I’m too old for this.<div><br></div><div>Jaak</div></body></html>