The developer boards that Scott and Fitz designed have arrived!
We'll be having our regular hacknight at sudo room tonight.
We'll be soldering components and testing if the boards works. We'll send
some to NZ folks and order more assuming it all checks out.
We'll also be working on writeups, the website + finalizing the video
script and scheduling upcoming video shoots.
--
marc/juul
Perhaps we should apply for this? Might be more relevant for People's Open
Network.
https://www.ripe.net/support/cpf
Deadline: 24 November 2017
Via cel on scuttlebutt.
Also: Hacknight tonight at sudo room as always.
Greetings meshers,
Am posting this off-list as there are ~250 people on the sudomesh mailing
list and many of them will likely be competing for the same grant. Also, I
made a mailing list for Disaster Radio folks
<https://sudoroom.org/lists/listinfo/disasterradio> as a supplement to
#disasterradio channel in Patchwork. Those who were on the conference call
last month have already been added, but feel free to join if you'd like.
Also started a hackpad for the Peoples Open Network submission
<https://hackmd.io/BwQwZgJiBMEGwFoDMSDGB2BAWArCAjAsAAzDAL4BGIAnCaiMcQKbFA==#>,
plz add to it!
--
Timeline for the NSF/Mozilla WINS grant below, followed by action items
(plz read those if you intend to participate in either the Disaster Radio
or People's Open submissions):
*Intent to Apply (Oct 15th):*
I checked back on the 'Intent to Apply' form, which is due *October 15th*,
and noted that the only info they required was a contact name, org name,
org status, and which challenge the org is applying for - 'Both' is an
option, and I'm 100% confident that's what I submitted back in August.
According to the challenge rules, "Teams may submit Submissions to both
Challenges and may submit more than one Submission per Challenge." So we're
good on the Intent to Apply for both People's Open and Disaster Radio.
*1023 Nonprofit Application (mid-October):*
The next deadline is self-imposed, and that's getting Sudo Mesh's 501c3
application in the mail ASAP - I am hoping by early next week, but may be
the following week since I'd like Jesse to review it and sign the Power of
Attorney form. It only took the IRS ~2-3 months to send both Omni's and
Sudo's exemption letters, so hopefully we'd get ours by January, when the
Stage 1 prizes are announced. I'll include a letter for expedited treatment
in the application, which lives currently in the Sudo Mesh google drive and
is nearly complete:
https://drive.google.com/open?id=0B4_Q7DQvNFT-MWx5bkI5MXVUYkU
*Design Concept Submission (Nov. 15):*
All submissions must first apply to the Design Concept Stage, for which we
need to submit mockups, hardware & network diagrams, and written
documentation. Prizes (for $60K, $40K, $30K, and $10K[x7]) and projects
eligible to move on to the Working Prototype Stage will be announced
in *January
2018*.
*Working Prototype Submission (June 22):*
If Mozilla deems our submission(s) eligible, we then need to submit working
proofs-of-concept by *June 22, 2018*. For this they suggest the following
forms of documentation: Network test data, Video demos, Photographic
documentation, Software code, and Hardware schematics. "Finalists during
the Working Prototype Stage may be required to provide live demos for
judges and/or a public audience at a Challenges Showcase in *Summer 2018*."
*"Prizes will be announced in or around August 2018. Finalists during the
Working Prototype Stage may be required to provide live demos for judges
and/or a public audience at a Challenges Showcase in Summer 2018."*
*Action Items:*
1. Define teams: While we have a defined team for the Disaster Radio
project (for which we're applying to the Off-the-Grid Internet Challenge
<https://wirelesschallenge.mozilla.org/_assets/NSF-OffTheGrid.pdf>), we
need to define a team for submission for the People's Open Network (for
which we're applying to the Smart Community Networks Challenge
<https://wirelesschallenge.mozilla.org/_assets/NSF-SmartCommunity.pdf>).
Let's discuss who wants to participate in the PON team at next Tuesday's
meeting. Any participant can be on multiple teams. I started a hackpad for
the PON submission here:
https://hackmd.io/BwQwZgJiBMEGwFoDMSDGB2BAWArCAjAsAAzDAL4BGIAnCaiMcQKbFA==#
2. Choose Team Leaders: Both projects will also need to consent to someone
who can serve as the Team Leader, essentially the point of contact between
Mozilla and the project. This is ideally someone highly responsive to
emails, organized and able to stay on top of the various elements of the
submissions. Happy to play this role for either or both, and can think of a
number of folks who'd make excellent points of contact - just think it over
and volunteer if you have the spoons!
3. Sudo Mesh board members - namely *Jake, Lesley, Marc, Andrew, and
Jorritt* - please write up 1-2 sentences describing your 'qualifications'
(eg degrees, work experience, notable projects) into the spreadsheet I sent
you yesterday
<https://docs.google.com/spreadsheets/d/1IwaVw_9gMHnDutAMEKnM0G0Pq7NbRENkVjs…>
- it's a requirement of the 1023 application.
4. Everyone working on the grant team(s) should read through the Application
Submission Guide
<https://assets.mofoprod.net/nsf/NSFWINSapplicationguide.pdf> to get a
sense of what kind of questions we need to respond to and documentation
we'll need to write up. Consider your strengths and interests and what role
you'd like to play - code dev, written documentation, use cases / user
stories, design, website, some combo of the above, etc. We've already
sorted roles for Disaster Radio - but *add yourself here if you'd like to
work on the Peoples Open submission as well:*
https://hackmd.io/BwQwZgJiBMEGwFoDMSDGB2BAWArCAjAsAAzDAL4BGIAnCaiMcQKbFA==#
--
I'll propose we sesh on the Peoples Open grant submission as a breakout
session for next Tuesday's meeting and see if folks are down to have an
extended hackathon on it sometime in the next two weeks.
And a reminder that Disaster Radio hacks on Monday evenings and to register
for Science Hack Day
<https://www.eventbrite.com/e/science-hack-day-san-francisco-2017-registrati…>
for the weekend after this!
<3
Jenny
Help open a people-powered common space in Oakland, California!
https://omnicommons.org/donate
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"Technology is the campfire around which we tell our stories."
-Laurie Anderson
"Storytelling reveals meaning without committing the error of defining it."
-Hannah Arendt
"To define is to kill. To suggest is to create."
-Stéphane Mallarmé
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
Hi everyone!
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
communicate.
# 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:
https://viewer.scuttlebot.io/%253FWrhMwaxZ6q0Xk4sHIt4pdQD%2FuDT06lns170Jl5U…
# People
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)
* mixmix: Javascript. Scuttlebutt integration. New Zealand based.
* dominictarr: Javascript. Scuttlebutt integration. New Zealand based.
* 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).
* cel: Javascript. Scuttlebutt integration. Focus on offline and low power
operation. Nomad (currently Hawaii based I think).
* noffle: Javascript. Peer to peer offline and web-based mapping.
* tunabananas: Team coordination. Writing / documentation. 501c3
application.
* 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
learn KiCad.
* 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
production.
* 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:
https://github.com/sudomesh/disaster-radio
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
nearly done.
# Communication
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
public places.
We have several comms channels:
* *Scuttlebutt*: General discussion
-- The #DisasterRadio channel. NOT the #disaster-radio channel (that was a
mistake)
* *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.
-- https://github.com/sudomesh/disaster-radio/issues
* *Github wiki*: Documenting our research and designs
-- https://github.com/sudomesh/disaster-radio/wiki
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:
https://github.com/ssbc/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:
https://sudoroom.org/pipermail/disasterradio/2017-October/000001.html
--
marc/juul
Reposted from #disasterradio on Patchwork, originally published on Sep 28th:
--
\o/ back on patchwork, and very happy to be here!
I said I would share some of sudoroom / sudomesh's governance docs, so
here's a breakdown of the basic agreements / governance structure we could
adopt. Based on feedback to this post, I can turn these into some draft
documents up for consensus.
Here's a current draft of Sudo Mesh's bylaws, based on bylaws of the Omni
Commons:
Sudo Mesh Bylaws
<https://docs.google.com/document/d/1g1aK1S301NBtbGVIQn-zY-fLPWw8pyHNHvaBTVb…>
I'm thinking that formally, Disaster Radio would be a fiscally-sponsored
project of the Sudo Mesh 501c3 with a designated committee of all those who
participated in our first call. I can draft a fiscal sponsorship agreement
based on those we've written for Omni's fiscally-sponsored projects [1].
That committee would have full control of any funds designated as "Disaster
Radio, a Project of Sudo Mesh" in a subaccount of Sudo Mesh's bank account.
Initially transferring funds into a subaccount of Sudo Mesh's bank account
is necessary if we're using Sudo Mesh's 501c3 org status, because those
funds need to be allocated and tracked by the 501c3 and documented in the
annual 990 federal tax forms. Typically, a sponsoring nonprofit charges
5-15% of money raised by the project because of the administrative overhead
necessary (tracking expenses, writing receipts, annual accounting & taxes).
I would suggest the minimum 5%, which will in all likelihood end up going
to recurring server / bandwidth costs anyway [2], or perhaps that reserve
could go toward paying an accountant or lawyer.
New potential members of the project would be agreed upon by consensus of
the full committee, so long as a quorum of members (2/3?) are able to weigh
in. Decisions can be made electronically (see Sec. 16: Action by Unanimous
Written Consent Without Meeting) - perhaps we could implement a Loom.io
instance or some such for consensus proposals?
Financial decisions could be made by consensus of the whole committee -
however, it may be prudent to designate a sub-committee that focuses on
budgeting, accounting, and handling financial proposals / budget requests.
To that end, other subcommittees / working groups might include hardware
design, software development, community outreach, etc - with each working
group empowered to make certain kinds of decisions, rather than requiring
full committee consensus at each step, twist and turn :). Working Groups
would be required to be fully transparent and open to any committee members
to join [3]
The following is probably more proposals for Sudo Mesh the umbrella org,
which informs the overarching values and policies of its projects:
- For resolving conflicts, I'd like to propose we adopt sudo/omni's
Conflict Resolution Policy [4, 5] or some variant.
- In terms of values, I'd like to propose adopting a Statement of
Solidarity to articulate a commitment to prioritizing the needs of the
marginalized and oppressed [6], as well as a Safer Space Policy to
articulate commitment to a nurturing, harassment-free space (online and in
meatspace) [7].
This is probably enough for one post... thoughts / feedback welcome!!
--
*REFERENCES:*
[1] Sudo Room's Fiscal Sponsorship Agreement w/ Omni Commons (set
$2000/month contribution toward rent/mortgage):
Sudo_FS_Agreement_2017.pdf
<https://drive.google.com/file/d/0B4_Q7DQvNFT-N3BKaDAzb0t0akU/view?usp=drive…>
[2] Real Vegan Cheese's Fiscal Sponsorship Agreement w/ Omni Commons
(similar model Disaster Radio would have, 5% of income paid out to sponsor):
RVS_FS_Agreement_2017.pdf
<https://drive.google.com/file/d/0B4_Q7DQvNFT-R2lUaXkwRVNXRUE/view?usp=drive…>
[3] Omni's Protocols re: Working Groups:
https://omnicommons.org/wiki/Working_Groups
[4] Conflict Resolution Process for Omni, adopted from Sudo Room's:
https://omnicommons.org/wiki/Conflict_Resolution_Policy
[5] A visual schematic of decision-making processes:
https://sudoroom.org/wiki/File:SudoRoom.png
[6] Omni's Statement of Solidarity:
https://omnicommons.org/wiki/Founding_Document#Statement_of_Solidarity
[7] Omni's Safer Space Policy:
https://omnicommons.org/wiki/Safer_Space_Policy
--
Jenny
Help open a people-powered common space in Oakland, California!
https://omnicommons.org/donate
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"Technology is the campfire around which we tell our stories."
-Laurie Anderson
"Storytelling reveals meaning without committing the error of defining it."
-Hannah Arendt
"To define is to kill. To suggest is to create."
-Stéphane Mallarmé
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
