[Commotion-dev] Fwd: Re: Requesting you to help the middle-east response

Tue Feb 1 05:50:13 UTC 2011

Heya all,

For the list archives.  This was an earlier conversation on a basic dev
plan.

In summary, two groups. One group working to update the olsr ports
(http://www.olsr.org/?q=download) for windows, os x, iphone and android.
 The second group to work on improving the OpenWRT commotion custom
build (http://wiki.ucimc.org/bin/view/Tech/WirelessDocs).  I suspect
more threads and conversations for each group to follow.

Cheers,
--
Dan

-------- Original Message --------
Message-ID: <4D478629.9070308 at newamerica.net>
Date: Mon, 31 Jan 2011 23:03:53 -0500
From: Dan Meredith <meredith at newamerica.net>

Heya all,

Apologies for these messages.  Last one then, I am going to bed. One
Peter Folk who owns a rocking ISP in Illinois that's been rocking
OpenWRT *forever*.  He's down to help kick into geear the commOTIon
OpenWRT build Josh King is leading.  If others are interested in OpenWRT
hacking, post here and Josh will get you repository access to that one.

Just to be clear:
Aaron can facilitate git access to olsr where folks will work to upgrade
the Windows client.
Josh can facilitate git access to commOTIon where folks can rock the
OpenWRT firmware.

If you have friends who want to get into this, please bring them into
the conversation.

There is also an irc channel we've all be kicking it in:
#oswc on irc.freenode.net
http://webchat.freenode.net/?channels=#oswc

Alright ya all, thanks again and catch up with you in the morning.

Thanks!
--
Dan

On 01/31/2011 10:49 PM, Dan Meredith wrote:
> Heya all,
> 
> I want to introduce you all to Nick Stott.  Nick's a long time friend of
> mine who's background is all over the place.  Nick, please scroll down
> to catch up.  At this point, we're hoping Aaron will hook us up with
> repository access soon.  There is the public
> http://olsr.org/git/?p=olsrd.git;a=tree that folks can start digging
> through.  If anyone feels comfortable enough jumping to organize folks
> till Aaron can make it back, feel free.
> 
> Thanks!
> --
> Dan
> 
> On 01/31/2011 10:42 PM, Dan Meredith wrote:
>> Heya all,
>>
>> Meet Ben Chadoroff, Ben West, and Tim Yardley.  Ben's are doing rad work
>> deploying mesh in the U.S.  Ben C in Detroit and Ben W in St. Louis and
>> abroad.  Tim is doing some insane crazy probably secret distributed
>> silly large scale computing nonsense for a large U.S. university.  All
>> would like to get in on the impending code sprint.  Ben's, Tim, Brian
>> and Chris are also going to help rock it.  Aaron is going to facilitate
>> repository access for everyone.
>>
>> The goal at this point is to simply upgrade the Windows port of olsr
>> (http://www.olsr.org/?q=download) to 0.6.0 from 0.5.6.  Secondary goal
>> is to upgrade the GUI to something prettier and easier.  Next goals are
>> to duplicate this for the OS X, the iPhone (the most popular non
>> blackberry smartphone there), then Android
>>
>> Rocking!
>> --
>> Dan
>>
>> On 01/31/2011 10:10 PM, Dan Meredith wrote:
>>> Heya all,
>>>
>>> Meet Chris Reed, a cat I've been talking with over the last couple days
>>> who's willing to jump into the windows port as well.  I will leave it up
>>> to you all to introduce yourselves.  Aaron can facilitate repository
>>> access.  Brian and Chris, I will leave it to you two to sort out who's
>>> to do what.
>>>
>>> Thanks and good luck!
>>> --
>>> Dan
>>>
>>> On 01/31/2011 09:59 PM, Dan Meredith wrote:
>>>> Aaron, can we get Brian an account on any svn as well? In the spirit
>>>> collaboration, there may be others who want to help upgrade these client
>>>> ports.
>>>>
>>>> On 01/31/2011 06:46 PM, Brian Duggan wrote:
>>>>> Sounds like fun :)
>>>>>
>>>>> Aaron, thanks for the status update. Is there a test suite for olsrd?
>>>>> Did it pass last time you built it? If no, where can I find definitive
>>>>> criteria for "working"? :)
>>>>>
>>>>> I can build & test on Windows XP, Vista and 7. I can probably succeed in
>>>>> creating a .msi that packages olsrd and dependencies fairly quickly.
>>>>>
>>>>> Writing a UI will take me longer since I haven't done a Windows GUI before.
>>>>>
>>>>> I'll have an opportunity to set up my environment tonight and get
>>>>> cracking. Looking forward to more updates from you, Aaron :)
>>>>>
>>>>> Brian
>>>>>
>>>>> On 1/31/11 4:39 PM, L. Aaron Kaplan wrote:
>>>>>
>>>>>> On Jan 31, 2011, at 11:35 PM, Dan Meredith wrote:
>>>>>
>>>>>>> Heya Aaron,
>>>>>>>
>>>>>>> On 01/31/2011 05:33 PM, L. Aaron Kaplan wrote:
>>>>>>>>
>>>>>>>> On Jan 31, 2011, at 10:23 PM, Dan Meredith wrote:
>>>>>>>>
>>>>>>>>> Heya Brian,
>>>>>>>>>
>>>>>>>>> Awesome man.  Can you begin looking into the state of the Windows olsr
>>>>>>>>> port?  I've CC'd Aaron who would know where best to begin.  I am hoping
>>>>>>>>
>>>>>>>> essentially , what you need for a windows "port" is to install cygwin, flex, bison, gcc
>>>>>>>> and git and download the olsr code and just "make"
>>>>>>>>
>>>>>>> Whew, not going to cut it for your average user.
>>>>>
>>>>>> Agreed
>>>>>
>>>>>>>
>>>>>>>> Please note that we often don't test the windows version thoroughly . So there might be some bugs in the current version. But the last time I tried it, it compiled just fine and worked.
>>>>>>>>
>>>>>>>>> to drum up support for a code sprint on that port to improve the UI and
>>>>>>>>> bring it up to the current stable version.
>>>>>>>>>
>>>>>>>> Yes, the windows version does not have a proper UI.
>>>>>>>> It would be great if someone got motivated to create a windows UI for olsr.
>>>>>>>>
>>>>>>> Do you have a best guess the amount of time in developer hours that
>>>>>>> would be required to update the port (guess 1)
>>>>>
>>>>>> I dont know. If everything works out, it will be a couple of hours, maybe 1 day to compile and test all important versions of Windows.
>>>>>> In case we find some bugs with the current version, it could take longer . Hard to estimate in this case.
>>>>>
>>>>>>> and a more friendly UI
>>>>>>> (guess 2)?
>>>>>>>
>>>>>> Hm... let me cross check with Markus and Henning to give you a better answer on (2)
>>>>>
>>>>>> a.
>>>>>>>
>>>>>
>>>>>