<div class="gmail_quote">Do we have a sumup? A more "final" version of the text in order for us the late birds to contribute to it? (feel a litlle lost)</div><div class="gmail_quote"><br></div><div class="gmail_quote">
On Mon, Apr 2, 2012 at 12:52 PM, Michel de Geofroy <span dir="ltr"><<a href="mailto:micheldegeofroy@gmail.com">micheldegeofroy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I read over and tried to synthesize<div><br></div><div>My 5 cents</div><div><br></div><div>Independently self organized by its participants, the Battlemesh is an annual friendly meetup with a bottom’s up approach where individuals share and compare ideas.Its focal point consists of hands on comparative tests of mesh routing protocols and associated technologies. Join Us! </div>
<div><br></div><div><br></div><div>Michel</div><div class="HOEnZb"><div class="h5"><div><br></div><div> <br><br><div class="gmail_quote">On Mon, Apr 2, 2012 at 11:05 AM, Mitar <span dir="ltr"><<a href="mailto:mitar@tnode.com" target="_blank">mitar@tnode.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<div><br>
> On Sun, Apr 1, 2012 at 11:52 PM, Juliusz Chroboczek <<a href="mailto:jch@pps.jussieu.fr" target="_blank">jch@pps.jussieu.fr</a>>wrote:<br>
</div><div>> NO, battlemesh is not only about routing protocols.<br>
<br>
</div>Agreed.<br>
<div><br>
> hmm imho "talks" sounds better as "happenings".<br>
<br>
</div>Yes, but it is much more than just talks: workshops, round tables, ...<br>
<div><br>
> "While BattleMesh is no conference, there are typically some short talks<br>
> per day, to allow people to present and get feedback for their ideas,<br>
> stories and experiences related to community mesh networks."<br>
<br>
</div>I would leave *short* out.<br>
<div><br>
> but afair the intention of the text was to say what battlemesh is or what<br>
> we want to have there, and not what is NOT or we do NOT want there,..<br>
> (but its not always easy with a strict "positive only" approach)<br>
<br>
</div>Exactly this was the main idea. To encourage the proper idea, not to<br>
list some rules what it is and what is not. But to somehow tell what is<br>
the spirit.<br>
<div><br>
> i think staying a bit vague, was an important achievement of this text.<br>
<br>
</div>Exactly. We do not want to define things too precisely.<br>
<div><br>
> "open-source" and "community" are likely the most important words of this<br>
> text!<br>
<br>
</div>And they are vague enough to cover all different aspects we want to<br>
cover. Why do not use vague words when they exactly tell what we want?<br>
<div><br>
> and imho avoiding terms like "open-source" and "community", and replacing<br>
> them with e.g. "fun", is ....<br>
<br>
</div>:-)<br>
<span><font color="#888888"><br>
<br>
Mitar<br>
</font></span><div><div>_______________________________________________<br>
Battlemesh mailing list<br>
<a href="mailto:Battlemesh@ml.ninux.org" target="_blank">Battlemesh@ml.ninux.org</a><br>
<a href="http://ml.ninux.org/mailman/listinfo/battlemesh" target="_blank">http://ml.ninux.org/mailman/listinfo/battlemesh</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Battlemesh mailing list<br>
<a href="mailto:Battlemesh@ml.ninux.org">Battlemesh@ml.ninux.org</a><br>
<a href="http://ml.ninux.org/mailman/listinfo/battlemesh" target="_blank">http://ml.ninux.org/mailman/listinfo/battlemesh</a><br>
<br></blockquote></div><br>