Since some new folks have started contributing to the project since our
last meeting I wanted to write a quick intro of who's who and how we can
# Next call
We're trying to schedule the next team call for tomorrow (Wednesday).
Please fill out this doodle: https://beta.doodle.com/poll/pvauhsfkb89sthqx
If you cannot make the call then don't despair. We will take notes and also
relay updates in person at sudo room.
Here is noffle's post about it from scuttlebutt:
Current team and what they are working on or have stated they want to work
on. (from memory, please let me know if I forgot you or got something wrong)
* piet: Extensive hardware design/implementation experience. New Zealand
based. Waiting for us to give him more details and send version 0 hardware
prototypes (ETA 3 weeks).
operation. Nomad (currently Hawaii based I think).
* tunabananas: Team coordination. Writing / documentation. 501c3
* jorrit: Software. Mesh protocol development and simulation.
* muxlux: Circuit board layout.
* nanomonkey: Circuit board design/implementation.
* fitz: Circuit board design/implementation. Radio expertise. Helping scott
* nic: Design and prototyping of node enclosure and mounting system. May be
bringing someone else on board to help with automated drone node-mounting.
* leez: Solar li-ion charging and power management.
* juul: Firmware and web app dev. Hardware research/prototyping. Video
* grant: Firmware development. Pre-circuit-board-layout hardware prototyping
* sierk: Public facing website development and vector map tile generation
I am trying to on-board another person who has experience designing on-pcb
high gain panel antennas, which is currently a missing area of expertise.
# Software, Hardware, Designs and Writings
We use this github repo to share what we make:
Currently it contains firmware, web app and some circuit board design files.
For the software we have been writing a simulator so folks can develop the
front-end without having the hardware hooked up to their computer. This is
Note that we want to operate in the open but we have competition that does
not operate in the open, e.g. the for-profit GoTenna company is apparently
entering the competition. Luckily their product is proprietary, over-priced
and doesn't actually mesh. Given this state of affairs, all our comms are
still public but please don't link to our discussions unnecessarily in
We have several comms channels:
* *Scuttlebutt*: General discussion
-- The #DisasterRadio channel. NOT the #disaster-radio channel (that was a
* *Mailing list*: General discussion. Several folks have encountered bugs
in the Patchwork scuttlebutt client so we set up a mailing list.
Unfortunately a couple of folk don't like email. People will cross-post
important things between the Scuttlebutt and this list so just use
whichever one you're more comfortable with but do make an attempt to
cross-post if something is urgent.
-- You have already been subscribed (I hope that's ok)
-- Archives: https://sudoroom.org/pipermail/disasterradio/
* *Github issues*: We're trying to move discussions and updates about
ongoing sub-projects here. Please start a new issue for each sub-project
you're working on or if you feel the need, start a whole new github
repository. If you don't have admin access for the sudomesh group then let
me know and give me your github user name.
* *Github wiki*: Documenting our research and designs
To get on Scuttlebutt it's probably best just to show up on a Monday or
Tuesday evening and talk to someone. There are a few different clients and
they each have their oddnesses. The most full-featured one is Patchwork:
If you received this email then you are subscribed to the DisasterRadio
mailing list. I hope that's ok.
# Upcoming deadlines
If you weren't already on the mailing list when it went our, you might want
to read the outline tunabanans sent of the deadlines and action items that
are directly related to the NSF/Mozilla challenge: