I agree, if we are able to have the firmware and tests ready before battle mesh, we will have a big improvment. Maybe we can try to do it. I know you have a big experience with openwrt, and I could help too. We could start creating a new mailing list, something like: wbm-firmware or wbm-work or whatever. And discuss there how to organize it and what is needed for the next firmware.<br>
<br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">Adding more hardware won't solve anything.<br clear="all"></blockquote><div>I don't agree. I'm not saying just add more hardware. I'm speaking about "to change" the actual hardware to a new one which let us more possiblities.<br>
</div><br>--<br>./p4u<br><br>
<br><br><div class="gmail_quote">2011/9/22 Nico <span dir="ltr"><<a href="mailto:nico@openwrt.org">nico@openwrt.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Pau,<br><br><div class="gmail_quote"><div class="im">On Thu, Sep 22, 2011 at 2:20 PM, Pau <span dir="ltr"><<a href="mailto:hakais@gmail.com" target="_blank">hakais@gmail.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>I'm also a newcomer at WBM, the last one was my first one. Before I went there, I thought that this was an event where the main objective was to test mesh protocols and put them in battle. But after, my thought was that this is an event to meet people and speak about some geek topics.<br>
</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">For me that is good, but maybe to push the original objective a little more would be nice.<br>One of the main restrictions I found is the hardware. Fonera is a very limited device and when you are running 4 or 5 protocols, it can do some strange things, and the tests become unreliable. Maybe we should put some efforts in to have another kind of hardware, we can find some sponsors who can give us some hardware. Or maybe we can put a special tax for spending on hardware (10€ per person = 600€ = 10 new devices).<br>
</blockquote><div><br></div></div><div>We can (and always tried to in the past) do both : gather people and have them exchange on these "geek" topics *and* do some real tests. The hardest part has always been to have everybody agree on what to test and how, and get everything ready to do it. If we can manage to agree on test scenarios and objectives and have routing protocols, hardware devices and firmwares ready before the event would actually start, that would be a massive improvement. Adding more hardware won't solve anything.</div>
<div class="im">
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">About the sponsors searching, what can we offer them?<br></blockquote><div><br></div></div><div>I don't know... visibility ?</div>
<div> </div><div>Cheers,</div><div>--</div><font color="#888888"><div>-{Nico}</div></font><div><div></div><div class="h5"><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><div class="gmail_quote">
2011/9/22 Marek Lindner <span dir="ltr"><<a href="mailto:lindner_marek@yahoo.de" target="_blank">lindner_marek@yahoo.de</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Thursday, September 22, 2011 06:52:22 Andrew Parnell wrote:<br>
> One thing I would like to suggest is to have a more formalised<br>
> arrangement for the test network that we will use for WBMv5. Though I<br>
> am a newcomer to this, one thing that I couldn't help but notice was<br>
> that many of us were there for 5-6 days before we were actually<br>
> deploying the Foneras and building a test mesh. It seems that this is<br>
> not the most efficient use of our time. Perhaps we could find a way<br>
> to require that each team/group who wishes to submit code for testing<br>
> must have this ready to go /before/ the event begins. This way, a<br>
> firmware image can be prepared in advance, and once people begin to<br>
> arrive, we can set up the mesh immediately and have much more time for<br>
> testing. We would probably also want to have another deadline(s)<br>
> sometime in the middle of the event perhaps, where updates can be<br>
> provided and a new firmware image(s) compiled. Hopefully this would<br>
> allow us to use the short time we have to the maximum benefit, and we<br>
> could really get some good tests/statistics compiled as a result.<br>
<br>
</div>It is not that we did not try in the past. We had deadlines / teams / etc but<br>
clearly lacked direction imposed by a "test leader" or "test group". The<br>
misery starts when you ask the question: What are we going to test ? You will<br>
find people chiming in that are fairly silent most of the time but feel they<br>
have to "defend" their protocol.<br>
In short: As long as we don't have someone (preferrably a protocol neutral<br>
person) who takes matters into his hands I don't expect any improvement this<br>
year either.<br>
<br>
Regards,<br>
<font color="#888888">Marek<br>
</font><div><div></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><br>_______________________________________________<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>
<br></blockquote></div></div></div><br>
<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>