Minutes from People's Open Network Weekly Meeting - 13 February 2018
7:30pm-9pm
- https://omnicommons.org/wiki/Safer_Space_Policy
Contents
- 1 Agenda <https://sudoroom.org/wiki/Mesh/13_Feb_2018#Agenda>
- 2 Introductions
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Introductions>
- 3 Meeting Roles
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Meeting_Roles>
- 4 Check in on previous action items
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Check_in_on_previous_action_items>
- 5 Updates & Reportbacks
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Updates_.26_Reportbacks>
- 5.1 Bugs/Technical
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Bugs.2FTechnical>
- 5.2 Node Mounts & Outreach
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Node_Mounts_.26_Outreach>
- 5.3 Communications & Events
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Communications_.26_Events>
- 5.4 Internal Logistics / Finance
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Internal_Logistics_.2F_Finance>
- 6 Sundays <https://sudoroom.org/wiki/Mesh/13_Feb_2018#Sundays>
- 6.1 Node Mount
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Node_Mount>
- 6.2 Office Hours
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Office_Hours>
- 7 Proposal: Alameda Open Network
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Proposal:_Alameda_Open_Network>
- 8 Proposal: Semi-synchronous Chat Options
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Proposal:_Semi-synchronous_Chat_…>
- 9 Discussion: Preparation for People's Open Strategic Plan Meeting
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Discussion:_Preparation_for_Peop…>
- 10 Discussion: PON Home Node and Exit Node Management
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Discussion:_PON_Home_Node_and_Ex…>
- 11 related topic: makenode documentation/deprecation
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#related_topic:_makenode_document…>
- 12 Action Items
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Action_Items>
- 13 Breakout Groups
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Breakout_Groups>
- 14 Last Meeting Notes
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#Last_Meeting_Notes>
- 15 End of Meeting
<https://sudoroom.org/wiki/Mesh/13_Feb_2018#End_of_Meeting>
Agenda
- Introductions and Meeting Roles (10 mins)
- Check in on previous action items (5 mins)
- Updates & Reportbacks (20 mins)
- Sundays (5 mins)
- Proposal: Alameda Open Network Proposal (15 mins)
- Proposal: Semi-synchronous Chat Options (10 mins)
- Discussion: Preparation for the stategic plan meeting (10 mins)
- Discussion: PON Home Node and Exit Node Management (20 mins)
- Action Items (5 mins)
- Breakout Groups
Introductions
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF
Announcements
- Icebreaker question: Favorite candy
- mai - she/they, favorite candy kit-kat, no announcements
- jorrit - he/him, flashback to when he was 8, winegums? and Coke.
- bengo - he him, they/them, special edition Y2K sweethearts
- JJ - he/him - candied ginger
- benny - he/they, likes sour patch watermelon gummie
- sierk - chocolate cookies
- Robb - he/him/they - candied ginger, SKOR bar
- Grant - he /they - mentos -
- jenny - she/her, not a candy person, dark chocolate, any annoucments,
nope
- Ben - he/they, dark chocolate, go to meet with Jeff tomorrow at 1pm (s
of campus)
- jehan - he/him - jelly beans, wants to help with tunnel
Meeting Roles
- Facilitator/s: Mai
- Stacktaker: Robb
- Notetaker/s: Benny, Grant, Jenny
- URL of this pad: https://peoplesopen.net/notes
- Next meeting's facilitator(s):
Check in on previous action items
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes
and past action items below:
- create meeting agenda template (eg
https://omnicommons.org/wiki/Delegates_Meeting_Notes_Template ) and
archive nov-feb notes - jenny
- see https://sudoroom.org/wiki/Mesh/Mesh_Meeting_Notes_Template and
https://sudoroom.org/wiki/Mesh/Minutes
- re-ping lolspace & respond to julia (AJ+ contact) - jenny
- pinged devie a couple of days ago to see if they would be
interested, requested to check back in March, location is close
to village,
sped up timeline to be part of al jazeera feature
- got positive reponse from AJ+, hoping to hear back from lolspace
- jorrit - thanks, for listening to comments from last weeks meeting
despite not being here
- no reply from Devi yet (lolspace) - forwarded Julia's response to
sudomesh signal group (folks seemed positive)
- nyc mesh meetup - jehan
- the meetup was in a bar, back patio, apparently their meetup
schedule is not that regular, they have some but they are for particular
purposes, this was a more general public meetup. The event started small,
but grew and then turned into a panel discussion with the members of
NYCmesh, they have a lot of inbound interest, a lot more than
they can deal
with. They don't look at individuals, but try to hook up entire
building by
talking to landlords. They are using a firmware, old custom build of QMP?
SO they have trouble updating it, but it does work. They don't pay for
bandwidth, they have a gigabit, average 50mbps with peak of 300mbps. They
have ~1/3 or ~1/5 chance that people could get internet access. Using
primarily Ubiquiti AirGrids
Also hungout with some people in brooklyn who's internet access is through
NYCmesh. Bandwidth just from one node in Manhattan. 5-8 inbounds a week ->
5-8 inbounds a day after press.
-
- jorrit - what wold you copy that they do there?
- jehan - could be wrong about assessment, but having a high up node
that can be connected to easily seems to have been very helpful to them.
everyone who mails in, they reply, can you see the verizon building from
your apartment? okay we can do it. [we have a harder process]
- mai - do they have any mesh service?
- jehan - there's a guy running a wiki from his house
- previous meeting w/ nycmesh:
https://sudoroom.org/wiki/Mesh/05_July_2016
- send out doodle for budget/strategy meeting - mai
- https://doodle.com/poll/ni5vmu5nvsdxpqip
- mai - decided on 2pm on Saturday, Feb 17th
Updates & Reportbacks Bugs/Technical
Priority bugs we need help with are located at:
http://peoplesopen.net/helpwanted - For a high-level overview of recent
Github activity, see the Trello:
https://trello.com/invite/b/r9l5ouQ4/3b2eecd83bb9e7a57a339cf1ee038288/sudo-…
- see helpwanted link
- bug #8 - debugging exit node,
- jorrit - seems to have figured out how to set up an exit node (in
Germany!) poked around the actual exit node, saw some stuff that could be
fixed
- jorrit - feel like I'm looking at a house burning down
- jorrit - will talk more about operations later
- to fix bug #1, need to fix bug #8. made a quick script for
creating exit node, want to explain to 3-4 other people. wants to do a
breakout.
-
- grant - I really like "setting up an exitnode" as a sunday skill
share. props! wondering--if a node is already up and never gets
reset, how
can you get root access once it's on their private internet?
- jorrit - need to reproduce it
- jenny - yar(sp?) says jorrit *does* have root access to the mesh
exit node
-
- Bengo - are the trello links supposed to be closed?
- jenny - invite only yeah, pasting link.
-
- jorrit and Bengo [exit node explanation]
- jorrit - want to dispute netflix idea that netflix is blocking
peoples open traffic
-
- grant - idea: other bugs, #2 and #13, can be fixed by documenting
makenode
- robb - recalls someone mentioning netflix doesn't allow vpn traffic
- jorrit - need to test
- jehan - no im positive that's it
- jorrit - wants to see proof
- jehan - could ask netflix, hey this is not a vpn ur confused; work
with us
Node Mounts & Outreach
Node Mounts Trello:
https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-…
- ben - going to jeff's place tomorrow, if anyone would like to do a
weekday mount?
- sierk - grant and I are gonna do a survey at Ed's place. Also found
another location within LOS to Driveway Follies, also talking with
Biblioteca near LOLspace/Village
-
Communications & Events
Comms Trello:
https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-…
// Events Trello:
https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peopl…
- mai - AJ+ already discussed
- jenny - january 11th, people wanting to start mesh network in LA. who
wants to follow up?
- sierk - i could follow up--asked the person who asked me about it to
e-mail, but they never got in touch
Internal Logistics / Finance
Internal Logistics & Bureaucracy Trello:
https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/inter…
- INSURANCE: Will & Jenny have been trying to get a quote for Directors
& Officers insurance. Last reply was 1/25 from Tracy @ Brignole & Ghiri: "I
have not been successful in obtaining a quote for the Directors & Officers
Liability coverage. I have either been declined by markets due to the
business operations or a minimum premium of $15,000. I do have a request
for the following:
- Please forward your financials. If financials are not available do
you have a budget? (Estimation of revenues and expenses)."
- Budget Draft:
https://docs.google.com/spreadsheets/d/1QJetruKfHrO5bpaLDk_smXYpLSvGlzytda_…
- "What is your business plan. "
- Biz Plan Draft:
https://docs.google.com/document/d/1H8x3JnbGEkoeE3CwMzrCC0MD1tIAhb6O8JjLsiC…
- jenny - biz plan and budget draft just need to show that we've
given them thought--doesn't have to be final
- HELP WANTED on the above!
- GOVT FILINGS:
- Jenny sending CT-1 initial reg form to the Attorney General tmrw.
Once approved we get a # and then have to file RRF-1s probably for
2014-2017.
- Business Tax exemption - jnny can't remember if she did it form
mesh when she did it for omni & sudo. will show up on the radar
if/when we
start making $$. will x-check
- FINANCE: $1,187 in bank acct.
- Mozilla requesting a W-9 - jenny will send tmrw w/ CT-1.
- Still requesting equipment budget requests! Please add to the notes.
- Setting up proper accounting this year - ping jnny if you're
interested in helping/learning.
- jenny - needs dollar amount from jorrit for cow/chicken
reimbursement
- bengo - what's better than a spreadsheet
- jenny - would like to setup a quickbooks online
- jorrit - what's your plan to help others to help you? Oracle of All
Things Complicated
- jenny - could send out a doodle
- mai - something we could discuss on Saturday (strategic planning
meeting)
Sundays Node Mount
We try to arrange a rooftop node mount every Sunday afternoon. Ongoing
spreadsheet is located at: https://peoplesopen.net/sundays
- Next Sunday's mount:
Office Hours
We host office hours every Sunday from 1-2pm in Sudo Room. To sign up for a
shift, fill in your name here: https://ethercalc.org/byoi_office_hours
- Next Sunday's volunteer: Benny,
- Notes from this past Sunday's session:
- Created new "Workshop" landing page for PeoplesOpen.net about BYOI
https://peoplesopen.net/workshop.html
- Cleaned up and added to Mounting Guide
https://github.com/sudomesh/mounting
- Creation of People's Open Network and Sudo Room pages on Wikipedia:
https://en.wikipedia.org/wiki/People%27s_Open_Network
- Attempt at cleaning up SudoMesh wiki
https://peoplesopen.net/pad/p/wiki_cleanup help needed!
- sierk wants to help out with wiki cleanup
- Benny - is inserting peoplesopen site into disaster radio template
Proposal: Alameda Open Network
grant talked with Amos White this afternoon https://about.me/amoswhite
- he is proposing to head up a large-scale, pratical roll out of a
People's Open Network in Alameda and would like to hold workshop(s) very
soon (he suggested starting Sat. Mar. 3) on how to go about doing this.
could sync up well with on-going outreach in East Oakland and
-
- grant explained current state of the Oakland PON and various
considerations he would have to think about (cost, LOS, volunteers, etc)
- see email chain here
https://trello.com/c/OLMqxcph/91-alameda-open-network
- grant - I wanna know what people think of doing Alameda workshops
with amos--practical stuff, getting/setting up antennas
- jorrit - as you were talking, I was seeing them coming here to get
trained (as opposed to us going there). can slowly segue into bigger event.
- mai - do they have an internet access point? were they hoping we would
provide that?
- grant - i explained that he would have to look into what places in
Oakland he had LOS to
- robb - diane's has a perfect shot at alameda and richmond
- jenny - still need to power the node
- mai - is there anything we can do regarding the richmond tower?
- jenny - the holdup is only that we need to coordinate with Jonah(sp?),
probably buy new equipment to put up there, and do a site survey. they have
a second tower that might have better LOS to the south. I've been putting
in on the agenda, but I wasn't here for a bit.
- mai - I think this would be a great thing to discuss at the strategic
plan discussion. It's a great path forward.
- jenny - I brought up determining a peering agreement to solidify our
partnership--his only concern was that he didn't want to get tied into
anything too serious in case they have to back out of the agreement
- jorrit - we had a long discussion about that, and i think we decided
that there would be no (peering) agreement
-
- Agreement was to not have any formal agreement
- jorrit - re: Amos, first thing is to get him familiar with how
stuff works. that can happen right away. e.g. by the time he has two nodes
up and running, our exit node should be resolved.
- robb - they should do a BYOI (in alameda)
- jehan - if they can/want to pay for an uplink, they might be able to
get an uplink through digital realty
- right across from Digital Realty which is part of SFMIX (SF
metropolitan internet exchange)
- jorrit - i want to make sure we don't scare anyone away with our own
fears (e.g. bugs we are fixing that they may never have to face)
- ben - [questions about whether trees are blocking LOS from Diane ->
Alameda]
- mai - agree w/ jorrit that best way forward is to invite Amos to BYOI
office hours. It's awesome that he sounds so enthusiastic.
- grant - I also suggested office hours! (high five). I also liked
robb's suggestion to get Alameda people organized. I tried to make it clear
that we can't just hop on over and set everything up. But we can provide
tools and knowledge so you can hold your own workshop. Can organize people
in Alameda who are interested, bring them here, and we can train them about
how to have their own workshops.Going to shoot him an e-mail tomorrow. Will
reference notes.
- jehan - is it safe to delete the peoplesopen.network email server?
- jenny - that's the contact info for mozilla
Proposal: Semi-synchronous Chat Options
- Rocket.Chat at http://peoplesopen.net:3000 (NOT YET SECURE and maybe
up/down, but will have demo running Tuesday night)
- daniel & grant worked on it a bunch on sat, trying to set it up on
a raspi
- now set up on a DO droplet running ubuntu.
- Let's Chat - had trouble running on sudomesh server
- Mattermost - haven't tried
- Matrix - haven't tried
- sierk - what will it replace?
- jenny - IRC, info@ emails
- jehan - how does it compare to matrix?
- grant - dunno--rocketchat had clear docs.
- ben - am happy w/ mattermost at my home. it seems pretty similar.
- x - also recommends Discord, for voicechat
- Consenso? Do we wanna go ahead with another chat platform?
- benny: get it minimally solid for us to try out
- sierk: try it for a few months then we know what features are
missing
- we're-a test it out for awhile "get on there"
- "if you don't wanna try it maybe you can get in there & let us
know" - jehan
Discussion: Preparation for People's Open Strategic Plan Meeting
- How should we get input from people who can't attend the meeting? In
order to also inform what our community would like to see out of PON.
- Suggestions: Send out a survey before Saturday
- proposal: mai - draft a form to send out tomorrow afternoon
- inviting suggestions for what should be on survey, will post to
signal group
Discussion: PON Home Node and Exit Node Management
Discuss/share current state of, and ideas regarding: patching home nodes,
maintaining exit nodes and monitoring network health
- jorrit - the reason for bringing this up is to get some ideas from the
group on how to move forward on managing the network we love so much
- there are two bits to it, the managment of the deployed nodes (home
and extender) and management of the exit node
- would like to first share how we do it today, right now we have one
active person who has access to ssh and patch nodes
- some months ago there was a the KRACK attack, that one person
jumped up and fixed all the nodes
- the exit node, there is are maybe one of two who are familiar with,
jehan is one, no he isn't, ok there is one. Yar has access, but doesn't
know what is running.
- mai - was the propsal at the last update that you would spread that
knowledge?
- jorrit -that was the technical part, this is the organizational part
- sierk - very relevant, mentioned something similar to grant, we get
to the state that we have a lot to maintian and that people rely
on, have a
few volunteers who are active maintainers of services and repos.
suggest we
discuss this on saturday - point people for specific aspects
- jorrit - for this discussion I wanna talk specifically about a plan
of action once the old exit node goes up--do we patch the existing nodes?
- jehan - we have nothing to lose
- jorrit - but the one person who has acces to do it.
- jenny - it's obviously problematic to have only one person with
access to do this. it's currently the case because earlier,
there was only
one person sufficiently paranoid, competent, and gung-ho to do
this. now we
probably have more people who can have this responsibility. we
need to come
up with personal security protocols for system administration.
- jorrit - what I'm hearing from you is that we're okay with remote
management of home nodes (if people consent)
- grant - current state of network is remote patching with
opt-out--you need to know that you can opt-out before you can
opt-out. this
is a bug in previous firmware. i vote for, with new firmware, you need to
opt-in to being open to remote fixes/updates.
- jorrit - what I'm hearing from grant is that you want explicit
opt-in.
- jenny - I also like this.
- jehan - right now there are people out there w/ open wifi hotspots
that are using their home internet connection. we should
definitely remote
in to fix this.
- grant - this is related to the "document makenode" issue. I'm
documenting makenode right now so it will be easier to make
these firmware
changes we're talking about.
- mai - seems like if we have a mailing list of people who have
nodes, then we should let them know about the bug (if they're providing
open wifi access to their internet) for the sake of transparency. in that
same e-mail, we should let them know that we're working on this
issue, and
we can help them fix it themselves, or we can fix it for them remotely.
Reaching out to them is in the nature and spirit of this project. Letting
them be empowered to fix it themselves, or choose to let us do
it for them.
That's my communication suggestion.
- sierk - Similar to Mai, but more long term--are we going to discuss
this elsewhere, because there are some details... it will take some time.
new mailing list?
- mai - definitely should discuss on saturday
- ben - very little to lose by giving other people agency about the
bug. more of a problem if people don't know and something happens.
- jenny - only issue i see is that we do not have a mailing list of
node operators.
- jorrit - sounds like we have consensus about what to communicate
but not how. I stil want to get consensus on whether we should
proactively
remotely patch things if we can.
- grant - bug number 1? yes we should remote patch. but we should
discuss whether to remote patch all other bugs.
- mai - are we going to say that we're going to fix it proactively?
- jorrit - i want to separate (1) that we are going to proactively
patch and (2) that we are going to send an e-mail to operators
- grant - we did this in september--marc got some, didn't get others.
in the past i have sent an e-mail to the list.
- Possible Plan: Get exit node up, fix the code, update firmware on
existing nodes,, then:
- update firmware with opt-in process for remote maintenance
- establish protocol for those with remote access
Should we remote-patch Bug #1?
- Mai: Does this entail we let them know beforehand?
- Jorrit: No, we'd just patch it. Send an email.
- Aye: Grant, Jenny ??? we are evidently unable to move onto
decision-making-moment :P :)
- Nay:
- Abstain:
-
- ben - how long does a mount take?
- robb - it's usually like 6 hours. could probably do it in 3.
related topic: makenode documentation/deprecation
(announcement): Anyone wanna help document makenode? see
https://peoplesopen.net/pad/p/makenode - also
https://sudoroom.org/wiki/Mesh/Makenode
Action Items
- Send CT-1 and W-9 - Jenny
- Follow up on D&O Insurance - Jenny, ?
- Reply to Julia / AJ+ - Jenny
- Move peoplesopen.network emails to new Migadu server - Jenny/Jehan
- Get rocket.chat secure and persistent on sudomesh server - grant
- Draft group consensus and send to Amos White - grant
- Send survey to mailing list ahead of strategic meeting - mai
- Weekday node mount with Jeff 12pm Wednesday - Ben, mai, grant
Breakout Groups
At the end of the meeting, break out into small groups to hack on or
discuss specific topics.
- Exit Node Debug: Jorrit, mai, grant, bengo, benny
Last Meeting Notes
https://sudoroom.org/wiki/Mesh/06_Feb_2018
End of Meeting
- please archive these meeting notes by copying the entire pad contents
onto the sudomesh wiki
- then please erase the contents of this pad
- then please cut & paste a blank template from here:
https://sudoroom.org/mediawiki/index.php?title=Mesh/Mesh_Meeting_Notes_Temp…
- previous meeting notes are archived here:
https://sudoroom.org/wiki/Mesh/Minutes
Hey y'all,
I'm currently running the localization via wifi as a service on my rpi:
100.65.27.66/
Let me know what you think. (It's a super ugly design, but it's a start.
This is my first time doing anything like this)
My guess is that for most people, the intersection between the BSSIDs they
can see and those in the database will be empty, but let me know if this is
not the case.
best,
Arthur
PS. It's pretty straighforward to find nearby BSSIDs and RSSIs on mac and
linux. See
https://github.com/aetilley/wifi_localization/blob/master/localize_from_nea…
Hello friendly meshers!
The next Build Your Own Internet office hours* is this Sunday February 18th
from 1pm to late afternoon in SudoRoom
<https://sudoroom.org/wiki/Directions>.
Last week, folks did all kinds of awesome things, including (but not
limited to!):
- making rad signage
- creating a new BYOI workshop landing page
<https://peoplesopen.net/workshop.html>
- cleaning up and adding to the Mounting Guide
<https://github.com/sudomesh/mounting>
- creating People's Open Network
<https://en.wikipedia.org/wiki/People%27s_Open_Network> and Sudo Room
<https://en.wikipedia.org/wiki/Sudo_Room> pages on Wikipedia [ack! they are
now candidates for deletion! let's research
<https://en.wikipedia.org/wiki/Wikipedia:Notability_%28organizations_and_com…>
this
weekend and respond.]
- beginning the daunting process of cleaning up the SudoMesh wiki
<https://peoplesopen.net/pad/p/wiki_cleanup>
- beginning to add templating back to the peoplesopen.netwebsite source code
- debugging the subtle but infamous exit node outage
This week's theme is *Protocols: who needs 'em anyway? certainly not me.
i'm through with protocols !*
It'll be a great time to continue all the awesome work listed above, start
a new project, or get newly acquainted with the mesh, this time (casually)
through the lens of protocols.
Some questions I have about protocols are: What are wikipedia's protocols
about article deletion and noteworthiness? How does the "babel" protocol,
currently in use by our mesh network, work? What social protocols do we use
at sudomesh to coordinate all of these awesome efforts?
🐴🐙🐨
As always, we'll be there to answer questions and learn from each other
about cable crimping, node flashing and mounting, as well as other aspects
of the project.
Hope to see you there!
--Benny
Hi!
Freifunk has been accepted to Google Summer of Code this year again.
GSoC is Google's program where students can get around $5000 for work on
an open source project over the summer. Freifunk serves as an umbrella
organization for many mesh/community networks/projects.
Maybe you have some ideas what students could work on? If so, consider
adding them to existing list:
https://projects.freifunk.net/
(PRs: https://github.com/freifunk/projects.freifunk.net-contents)
Maybe some of existing ideas would be something you would also care
about: maybe find a mentor from your network and volunteer to help guide
the student.
Or, maybe some of you are students who are already involved with the
project. This is also great: you could work through Google Summer of
Code this summer.
Mitar
--
http://mitar.tnode.com/https://twitter.com/mitar_m
this is beyond excellent, robb!
Jenny
Help open a professional kitchen at the Omni Commons in Oakland!
https://omnicommons.org/kitchen
`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
"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é
"Anything done for the first time unleashes a demon."
--Dave Sim, "Cerebus the Aardvark"
~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
---------- Forwarded message ----------
From: robb <sf99er(a)gmail.com>
Date: Mon, Feb 5, 2018 at 2:15 AM
Subject: [sudo-discuss] byoi video on google drive
To: Sudo-discuss <sudo-discuss(a)lists.sudoroom.org>
i uploaded an edited h.265 encoding of byoiv4 to google drive
https://drive.google.com/file/d/1KV3OAG_P63mZ_wK_nqSjNDgpRnTLaQvS/view?usp=
sharing
~r
_______________________________________________
sudo-discuss mailing list
sudo-discuss(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/sudo-discuss
Here are the SudoMesh meeting minutes from Tues, 6 Feb 2018:
Viewable online here:
https://sudoroom.org/wiki/Mesh/06_Feb_2018
-----
Peoples Open Meeting: Feb 6, 2018 19:30 - 21:30
* facilitator - blake
* stack taker: grant
* note taker: benny, juul + others
= previous action items =
* nycmesha meet-up summary / possible inspiration for community support -
jehan in absentia
* proposal for reorganize meetings
* node mount teaching session Sunday at 1pm - grant, jorrit
* byoi debrief
= agenda items =
(add your item below, with a time limit)
= intros: (5 min) =
* how you'd like to be addressed and favorite sport, n why we're here
* blake - skateboarding
* sierk - working on web app for disaster.radio and make it work with
firmware, puppy bowl
* jorrit - any sport that people actively do, here today to be here, learn
about what other people did and share
* grant - table tennis, ping pong, here to take notes
* benny - non competitive touch footbal, here to see what the meetings are
like, listen
* carl - drunken chess, here to see what's going on
* marc/juul - sportsball
* jenny, basketball, not actually there
* Tommy - likes to sleep
* jeff - ultimate
* lesley - I've never understood how people feel watching sports, except
for maybe the lee sedol vs. alpha go tournament.
= updates & reportbacks =
* SudoPad documentation (1 min) -
** grant - in progress, almost done - https://sudoroom.org/wiki/Mesh/SudoPad
- also added to https://sudoroom.org/wiki/Mesh/Distributed_Services
** grant - suggests we could turn it into an ansible playbook
** sierk - use ansible to document what is run on the sudomesh server
** grant - long-term action item: document what is running on the sudomesh
server
* (brief announce) - Jenny scheduled a CORE I training @ Omni for March
8th, 6-8pm: http://www2.oaklandnet.com/government/o/OFD/s/CORE/index.htm
** City of Oakland provides free trainings to neighborhood groups for how
to organize disaster recovery community response. good learnings for mesh &
disaster radio and opportunity for local outreach
* node mount (10 min)
** outreach email template (please hack) -
https://peoplesopen.net/pad/p/outreach_email
** jnny: AJ+ (see below) wants to film a mount in the next 2 weeks. suggest
richmond tower if we can get equipment in time? also repinging lolspace
(they'd ask me to circle back in march but may be interested in
participating in the docu short. for feb 18?
* jorrit: thought folks were very engaged. started making a mounting guide.
took photos of the things you need. created a signal group specifically for
people to get familiar with how to prepare for a node mount.
https://github.com/sudomesh/mounting
** blake: do you think we should continue to do these things
**grant: yeah it's good to formalize and make the sundays open to the
public. i'd like to see people sign up to volunteer to be there and talk to
people. Would be nice to be able to coordinate node mounts there and to
teach people how to mount nodes.
** jorrit: we should make sure people get there early to set up.
** grant: it's a good idea to have someone to talk to for new people.
** jorrit: needs a big group of volunteers to do because otherwise people
are going to burn out.
** mai: does it make sense to have it every week? or alternate node mount
with office hours
** jorrit: we should decouple office hours and node mounts.
** mai: i feel like the peple who are able to do node mounts and the people
who can run office hours, there's a lot of overlap. we should be aware of
our bandwidth. this sunday i plan to be there and i don't know how to do a
node mount.
** jorrit: we need more people to get familiar with node mounts.
** grant: the person who's the volunteer dosn't need to know how to mount
nodes. very minimal requirements.
** jorrit: i'd be ok volunteering for office hours but not organizing a
node mount
** mai: i can be there. what does organizing office hours entail?
** jorrit: announcing it.
https://ethercalc.org/byoi_office_hourshttps://gist.github.com/otakup0pe/b960646d3f6b41927dbab2f00a6bb24a
* meeting re-org (5 min)
** blake: we're trying to make the meetings go a bit more smoothly but
having an agenda and specified times for different sections. I will send
out the notes from the meeting re-org discussion
** grant: one of the things we discussed was putting safer space policy or
similar at the top of the meeting notes to make it explicit.
** blake: want to give the meetings better structure to make them go more
smoothly.
* bug/help wanted review (2 mins) - https://peoplesopen.net/helpwanted
** jorrit: i created a redirect for /helpwanted. first one is tunnelbroker.
the exit node has been down for ~5 days. three people complained. been
trying to build this thing called tunneldigger-lab. marc has been
troubleshooting. yar has been troubleshooting. i'll briefly touch on the
others. daniel reported that we should disable remote logging. there's the
can't watch netflix movie issue. one is a featur request to decide how to
allocate bandwidth. last one is a bug that has been fixed but not rolled
out.
* discuss why donation and sunday mount documents were open for anyone to
edit (https://peoplesopen.net/donation / https://peoplesopen.net/sundays )
and how to avoid this in the future (5 mins)
** jenny: don't see a problem with having transparent finances. not sure
about the sundays spreadsheet but i probably am to blame. it's invite-only
now. apologies!!
** grant: lol, fianances sure, but people's personal addresses? i said
sorry! ;P
** jorrit: finances ok read-only, but editing should be restricted in my
opinion - its bookkeeping
** grant: second the read-only part
** looks like marc already made it invite-only
** not marc, but someone else did
* PON outages (a) DMCA take down, followed by (b) tunneldigger broker
failure, exit node status (see issue
https://github.com/sudomesh/bugs/issues/8 ), troubleshooting (10 min)
** proposal: investigate/share root cause of DMCA take down and come up
with ways to avoid in the future
*** jenny: finish setting up server @ hurricane electric and switch exit
node to that
** proposal: "who are admins of what" list
** proposal: train 3-4 people on how to operate , monitor and administer
the exit node using https://github.com/sudmesh/tunneldigger-lab or similar
doc
Communications (10 mins)
grant:, yeah, just notes for discussion
** alternatives to signal/IRC/mailing-list for troubleshooting and support
*** rough sketch of ideas (expand in a breakout group?)
*** signal etiquette - for privacy/encryption/timeout messages, day-of
comms (synchronous only)
*** IRC - create setup instructions or agree on alternative support channel
(semi-synchronous)
*** mailing list - larger updates, schedule meetings (assume async)
*** who moderates / monitors / replies to public email addresses
info(a)peoplesopen.net / nodemount(a)peoplesopen.net / info(a)sudomesh.org ?
(jorrit - unclear to me which email has been replied to and which one needs
attention, cc-to-self when replying would clarify this situation; many
possible unanswered info emails remain)
*** grant - i'll check migadu server to see if there are any settings like
"force cc-to-self"?
*** grant - couldn't find any options for info or nodemounts aliases, not
sure if jenny or any one else might have an idea how to deal with with this?
****jenny - info@peoplesopen is in the migadu acct -> domains ->
peoplesopen.net -> aliases -> info. currently sends to jorrit, jehan, will,
juul, mai, grant, me, and scott
***** nodemount goes to grant, jehan, mai, juul, scott, and me
***** info@sudomesh and all other emails @sudomesh are defined in the
etc/postfix/virtual file on the peoplesopen server. can move that over to
migadu as well
*** proposal - send out meeting notes to mesh list after meeting to inform
+ archive
**** just needs someone to do it again (sending to list). archives are
here: https://sudoroom.org/wiki/Mesh/Minutes
** see also Comms Trello:
https://trello.com/b/f3ugMPNU/sudo-mesh-communications ("emails" list is
automated, all emails i label "mesh inquiry" in my gmail are forwarded to
here. been playing with zapier)
** sierk - we're using IRC/Signal for conversations, and mailing
lists/github for bugs and issues. what we're currently doing doesn't scale
however, should we deal with it when it's an issue or figure something out
now?
** juul - mailing lists work. Signal is terrible and it's giving us more
problems then its solving.
** grant - when we get something on the mailing list we just need to make
sure to reply-all so it's more like a chat-like support channel
** sierk - there's still an issue of scaling. It sorta works now but it
won't work in the future. I'll send this issue to the mailing list — there
are solutions to this.
** jenny: i liked jehan's suggestion to use matrix: https://matrix.org/ -
persistant chat history, web-based and mobile clients
** mai - I'm also interested in trying matrix. It's important to have a
systematic way to deal with bugs and community issues and to have ways for
people involved to have casual conversations and share news — these
interactions build trust and community
** juul: rocket chat is also an option -- ooh, videoconferencing, screen &
filesharing??
* (maybe) byoi as more focused do-athon with a specific and well-defined
goal (judy talking to mai)
* zines (judy)
* discuss need for dedicated meeting re: SudoMesh strategic plan and budget
— will be more necessary *if* we get the Mozilla/NSF Grant (10 min)
** mai - we should have a meeting about funding and what our plans are for
the next several months, especially if we get the Mozilla/NSF grant
** leslie - Mozilla/NSF grant outline of "prototype" is something we've
already built. Providing more coverage and used connection is what we need
to build. Getting more nodes out there should be our #1 goal. +1
** mai - regardless of whether we get the Mozilla/NSF funding, we should
have a discussion about our budget and our strategic plan for the next few
months to few years. Discussing how we spend $ and how much we raise is one
point of entry to this discussion, but the larger conversation should be
what our goals/objectives are.
** jorrit: i want to second mai's comment that it should be disconnected
from nsf grant. i also want to applaud jenny's efforts with regards to 5
year plan and think we can lern a lot from her efforst toward getting 501c3
status.
*** jnny- aw tx. and good reminder i need to make those more sharable, wiki
prolly?
** sierk - i see this money and money in june to accelerate what we would
already be doing, under the imopression that the money now would speed us
up and get us ready for june, what's the plan for the next six months,
before allocate any money
** blake - this discussion is whether we should have a meeting about
budgetting and strategic plan and when
** grant: i think mai volunteered to draft a doodle. who should be invited?
** mai: i think anyone shold be invited but there should be an expectation
that you help.
* AJ+ (Al Jazeera) wants to do a feature on People's Open! (10 mins)
** Welcoming suggestions from the hivemind, this is the gist:
** They'd like to film a Sunday node mount, sometime in the next two weeks.
Jenny suggested the following possibilities: Richmond Tower to Diane's,
LOLspace/EastSide Arts Alliance to the Village, Laney College where Village
is building site #2 for unhoused students
** They also want to talk with someone directly impacted by the network.
Jenny suggested possibly one of our nodes in Richmond, hooking up Omni's
neighbor Araya (elderly disabled Eritrean man who asks me every time I see
him tho I haven't seen him in recent months), or yar's neighbors who rely
on yar's house's node for access
** "The story would be filmed for AJ+'s series with Dena Takruri. (
https://www.youtube.com/playlist?list=PLZd3QRtSy5LOWaQBH1fLN2etOO9pCAxaJ )
The idea is to be able to get an inside look to a story, with Dena leading
the experience. As you can see from her past stories, she has lots of
experience interviewing people in complicated and often intense
environments. Throughout the day, we would film the events taking place,
aka you and the team setting up the node, as well as hear from you and
others what inspired you to create and/or take part of the project. Our
hope is to get to the sociopolitical importance of the story. We would also
like to interview some residents that are affected by/benefit from the
nodes/internet in order to get a full scope of the benefits and potential
of the project. "
** mai - We should maybe hold off on putting ourselves in the spotlight. It
seems like we don't have many strong examples of people who rely on the
mesh network. We don't really have a way to scale right now, let alone a
strategic plan to figure out how we want to build and grow more
intentionally. It's not that we're not a success, we're just still growing
and personally feels uncomfortable putting ourselves out there until we can
deal with attracting so much attention.
** jorrit - I second Mai--if I'm not comfortable selling peoples open to my
neighbor, I'm not going to be comfortable selling to AJ. It's not stable
yet. I wouldn't want to be the person in front of the camera.
** juul - i have no problem lying to the media, they are mostly care about
the technology and not about what we are actually doing, but thinks we can
share what we are doing without misrepresenting
** blake - they will spin the story however they want.
** jorrit - I have a problem with lying. I don't want to deploy the same
techniques, "fake it until you make it". That's not why I joined this group.
** mai - I agree. That's the aspect of silicon valley that I hate. Talking
up their potential before they've even talked to a potential customer base.
It's exactly the kind of lack of reflective growth that I feel like is
really necessary if we want to build this really intentionally. I think if
we just let them film us and run the story--I don't even know if I'm fine
with that. One scenario--they film us, it looks like a huge success, then
30 people come to the tuesday meeting, and we don't have a plan to deal
with them. Then people have a negative reaction to how unprepare we are.
Alternative scenario, we do it when we're ready to deal with all the
inbound attention. Would rather not create impression that we're way more
put together than we are.
** blake - Steer discussion to how to communicate with Al Jazeera.
** leslie - I think they're comfortable with where we're at
** jorrit - what's the story we're giving to AJ? If the story is that we're
building this community network from the grassroots that's still very much
in experimentation, that's fine and I would happily share that story. But
if the story is that we're trying to build an alternative to AT&T then I'm
not comfortable with that.
** sierk - if we do it, we would be talking about community mesh networks.
we're a work in progress. if we tell the story that way, I'm totally fine
with talking to them about community mesh networks. but I don't we're ready
to talk about Peoples' Open, canceling comcast, etc. If we're clear about
that, I'm all in favor of helping spread the word about community mesh
networks.
** blake - Jenny wanted suggestions about how to talk to AJ. This is all
good feedback. People should continue to talk to AJ and the people
coordinating with AJ with their concerns.
** jenny - i was honest about where we're at w/ julia, and i'm guessing
marc was too. i told her i'd send a summary of peoples' concerns / ideas
after this meeting, appreciate all these points <3
** juul - Marvin Minsky quote, "Get people excited, and they'll teach
themselves." Been dealing w/ similar media things on real vegan cheese .
People who are interested will come, most people won't. People who like us
will stay. Even if you undersell yourself to the media, they will make you
look incredible. The job of the media tis to generate excitement (which is
what we want).
** mai - thumbs up to jenny and marc. We should think about how to let
people can get involved in various ways if it does lead to a lot of
attention and a large influx of interested people in the bay area.
* equipment budget requests (3 mins)
** what do we need? add to notes & jenny will purchase.
** usb to ethernet adapters
** second pair of EZ ethernet crimpers
** cow & chicken reimbursement - jorrit - 2x old raspberry pi (model b), 1x
8GB SDcard, 2x n600 nodes, 2x usb power cables
*** jenny: jorrit, send me receipts (if you didn't yet) & i can cut a check
from our online banking backend.
* proposal: table & workshop at Allied Media Conference, June 14-17 (3 mins)
** jenny is definitely going, proposing a table for omni as well
** tables are $100: https://www.alliedmedia.org/amc/table
** call for sessions is now open. we're probably a good fit for the
"digital futures of consent" track:
https://www.alliedmedia.org/amc2018/digital-futures-of-consent-track - DUE
DATE: March 16
** mai - an awesome conference multicultural, multigenerational conference
that goes on in Detroit, has been going on for ten years, not sure if it is
connected to DDJC, talks a lot about making media more accesible and
empowering marginalized voices. I'm interested to go.
** blake - interested to go.
* node scouting
** jeff - talked to ben (elam), we've been talking about connecting to
internet archive, is it a omni-directional link, or do we need a
directional poin-to-point link,
** marc - not sure, have to go there and check
** jeff - we can't see it from where I am in Berkeley,
** jenny: their 2.4GHZ link is open, but the 5.3GHz has a password
** marc - we are allowed to mount our gear on their tower
** jeff - a radio station at Ashby and I-80, got bought by someone, maybe
we could mount some gear on it
*** marc - what radio station
**** jeff - the one in American Graffiti?
= breakout groups =
* BYOI debrief (20 min)
= action items =
* see also comms trello:
https://trello.com/b/f3ugMPNU/sudo-mesh-communications // logistics &
bureaucracy trello:
https://trello.com/b/LzVQlW3X/internal-logistics-bureaucracy-brainstorms
/// github/code trello: https://trello.com/b/r9l5ouQ4/sudo-mesh-github-repos
// events trello: https://trello.com/b/Y3XfDK85/peoples-open-events
* create meeting agenda template (eg
https://omnicommons.org/wiki/Delegates_Meeting_Notes_Template ) and archive
nov-feb notes - jenny
* re-ping lolspace & respond to julia (AJ+ contact) - jenny
* send out doodle for budget/strategy meeting - mai
* long term - document what is running on the sudomesh server - sierk, grant
Hey there,
This is your (new) weekly reminder to add any topics you'd like to be
discussed to the SudoMesh meeting agenda before Tuesday:
https://peoplesopen.net/pad/p/notes
>> Add your bit where it says "Example Discussion Item"
If you do add something, we expect you to come to the meeting to give some
context and lead that discussion.
Thanks!
Mai
Hey fellow mesh enthusiasts,
We will be continuing our Build Your Own Internet office hours* this Sunday
February 11th from 1pm to late afternoon in SudoRoom.
This week's ~theme~ is *Documentation/Research Jam*!
It'll be a time to review and update our own documentation. And we can
research other examples of community/mesh networks, see how they make their
projects happen and add what we find to the sudomesh wiki
<https://sudoroom.org/wiki/Mesh> (or edit Wikipedia articles!). This is all
about tuning up our own docs, researching, and working on our knowledge
commons with information on how we can build a decentralized, democratic
networks.
We'll also be there to answer questions and learn from each other about
cable crimping, node flashing and mounting, as well as other aspects of the
project. We especially encourage those who were at the last BYOI or the
office hours last week to come and teach others. They say the best way to
truly learn is by teaching others, right? :]
Hope to see ya there.
Mai
---
** What are BYOI office hours? It serves two purposes:*
*1. A jumping off point for people interested helping with a scheduled
Sunday node mount, but who are not able to attend a Tuesday night meeting
or are not "in the know."*
*2. A friendly, non-confrontational time for new people to get oriented to
the project or just ask general questions about networking, the internet,
and their service provider.*
*We may also use the time to hold training sessions on a topic of choice,
conduct outreach to potential node locations, address finances and
purchasing, or tackle any other outstanding issues.*
Hey fellow mesh enthusiasts,
On Tuesday we agreed to have a dedicated strategy and budget meeting for
People's Open, where we'd set some long term goals and decide concrete
objectives for the project. We're also doing this to figure out what to do
in case some funding comes through, and decide how we'd apply those funds
towards achieving our objectives.
*This meeting is especially for people who plan to be involved in building
out the People's Open Network over the next few months to a year.* It may
take more than one meeting to do this, but at least we can get a start on
our plan with a 2.5 hour meeting.
Please fill out the doodle poll below by **end of day Monday Feb 12** so we
can set a time that works best for the most people. We'll discuss the
format of it at Tuesday's regular weekly SudoMesh meeting.
>>> https://doodle.com/poll/ni5vmu5nvsdxpqip <<<
Thanks!
best,
Mai
