I Agree<br><br><div class="gmail_quote">On Tue, Apr 3, 2012 at 6:21 PM, Benjamin Henrion <span dir="ltr"><<a href="mailto:bh@udev.org">bh@udev.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, Apr 3, 2012 at 6:03 PM, Gabriel Kerneis <<a href="mailto:kerneis@pps.jussieu.fr">kerneis@pps.jussieu.fr</a>> wrote:<br>
</div><div><div class="h5">> On Tue, Apr 03, 2012 at 02:17:21PM +0800, Yeoh Chun-Yeow wrote:<br>
>> I think that we need to ensure our binary images ready before the<br>
>> event. Off course, we need identify the hardware platform earlier.<br>
><br>
> Sadly, this is hardly surprising. For instance, six months ago, on this<br>
> mailing-list:<br>
><br>
> On Thu, Sep 22, 2011 at 02:20:52PM +0200, Pau wrote:<br>
>> 2011/9/22 Marek Lindner <<a href="mailto:lindner_marek@yahoo.de">lindner_marek@yahoo.de</a>><br>
>> > 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 arrangement<br>
>> > > for the test network that we will use for WBMv5. Though I am a newcomer<br>
>> > > to this, one thing that I couldn't help but notice was that many of us<br>
>> > > were there for 5-6 days before we were actually deploying the Foneras and<br>
>> > > building a test mesh. It seems that this is not the most efficient use of<br>
>> > > our time. Perhaps we could find a way to require that each team/group who<br>
>> > > wishes to submit code for testing must have this ready to go /before/ the<br>
>> > > event begins. This way, a firmware image can be prepared in advance, and<br>
>> > > once people begin to arrive, we can set up the mesh immediately and have<br>
>> > > much more time for testing. We would probably also want to have another<br>
>> > > deadline(s) sometime in the middle of the event perhaps, where updates can<br>
>> > > be 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>
>> > It is not that we did not try in the past. We had deadlines / teams / etc<br>
>> > but 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<br>
>> > will find people chiming in that are fairly silent most of the time but feel<br>
>> > they have to "defend" their protocol. In short: As long as we don't have<br>
>> > someone (preferrably a protocol neutral person) who takes matters into his<br>
>> > hands I don't expect any improvement this year either.<br>
>> ><br>
>> I'm also a newcomer at WBM, the last one was my first one. Before I went<br>
>> there, I thought that this was an event where the main objective was to test<br>
>> mesh protocols and put them in battle. But after, my thought was that this<br>
>> is an event to meet people and speak about some geek topics.<br>
>> For me that is good, but maybe to push the original objective a little more<br>
>> would be nice.<br>
>> One of the main restrictions I found is the hardware. Fonera is a very<br>
>> limited device and when you are running 4 or 5 protocols, it can do some<br>
>> strange things, and the tests become unreliable. Maybe we should put some<br>
>> efforts in to have another kind of hardware, we can find some sponsors who<br>
>> can give us some hardware. Or maybe we can put a special tax for spending on<br>
>> hardware (10€ per person = 600€ = 10 new devices).<br>
><br>
> Proposing and discussing some test scenarios in advance is definitely an<br>
> improvement, but it turned out to be useless without a reliable mesh setup to<br>
> perform the actual measurements.<br>
<br>
</div></div>Investing in a permanent testbed would not hurt.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Benjamin Henrion <bhenrion at <a href="http://ffii.org" target="_blank">ffii.org</a>><br>
FFII Brussels - <a href="tel:%2B32-484-566109" value="+32484566109">+32-484-566109</a> - <a href="tel:%2B32-2-3500762" value="+3223500762">+32-2-3500762</a><br>
"In July 2005, after several failed attempts to legalise software<br>
patents in Europe, the patent establishment changed its strategy.<br>
Instead of explicitly seeking to sanction the patentability of<br>
software, they are now seeking to create a central European patent<br>
court, which would establish and enforce patentability rules in their<br>
favor, without any possibility of correction by competing courts or<br>
democratically elected legislators."<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br>