<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://sudoroom.org/mediawiki/index.php?action=history&amp;feed=atom&amp;title=Mesh%2F21_March_2017</id>
	<title>Mesh/21 March 2017 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://sudoroom.org/mediawiki/index.php?action=history&amp;feed=atom&amp;title=Mesh%2F21_March_2017"/>
	<link rel="alternate" type="text/html" href="https://sudoroom.org/mediawiki/index.php?title=Mesh/21_March_2017&amp;action=history"/>
	<updated>2026-06-20T09:56:01Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.37.2</generator>
	<entry>
		<id>https://sudoroom.org/mediawiki/index.php?title=Mesh/21_March_2017&amp;diff=10515&amp;oldid=prev</id>
		<title>Tunabananas: Created page with &quot;Sudomesh meeting - 21 March 2017  = attendees = * jenny, juul, jorrit, daniel, grant, andy, ian  ian: I am a techie. Was not at the event. Not a people person.   = sesh on fir...&quot;</title>
		<link rel="alternate" type="text/html" href="https://sudoroom.org/mediawiki/index.php?title=Mesh/21_March_2017&amp;diff=10515&amp;oldid=prev"/>
		<updated>2017-03-29T15:31:44Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Sudomesh meeting - 21 March 2017  = attendees = * jenny, juul, jorrit, daniel, grant, andy, ian  ian: I am a techie. Was not at the event. Not a people person.   = sesh on fir...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Sudomesh meeting - 21 March 2017&lt;br /&gt;
&lt;br /&gt;
= attendees =&lt;br /&gt;
* jenny, juul, jorrit, daniel, grant, andy, ian&lt;br /&gt;
&lt;br /&gt;
ian: I am a techie. Was not at the event. Not a people person. &lt;br /&gt;
&lt;br /&gt;
= sesh on first ever BYOI internet event =&lt;br /&gt;
&lt;br /&gt;
== what did you like about it==&lt;br /&gt;
* Daniel - lots of enthusiasm, participation, motivated sudomesh crew excited to make it happen. people excited about crimping cables! at one point 7-8 people around the table practicing&lt;br /&gt;
** Didn't think people would be interested in learning crimping but many people were and even asked questions that Daniel had too look up the answer to&lt;br /&gt;
* liked the visual display of the link propagation&lt;br /&gt;
* jorrit: I was sitting at sign-in table. Liked handing out paperclips and things and liked telling the story &amp;quot;this is what you need to build your own internet&amp;quot;. It was nice to be able to give something that you can put in your wallet (some people clipped the laminated ethernet crimping diagrams to their clothes with the router-resetting-paperclips)&lt;br /&gt;
** asked people how they learned about the event - some saw it at the bus stop - flyering actually works!, saw on fb, word of mouth, one person from manylabs, &lt;br /&gt;
** asked people if they found what they were looking for en route out - someone helping to run a library in marin (ivan!), wants to help work with oak libraries. teacher from CCA asking if we could give a lecture to her class - said &amp;quot;what's in it for us?&amp;quot; maybe have your students write the curriculum of what they want to learn about. sign-in table is v effective!&lt;br /&gt;
** impressed by the talks and how it all came together. good to have even a slim structure to help with organizing people.&lt;br /&gt;
* andy: crimping station and node mounting station got a lot of activity&lt;br /&gt;
* grant: people receptive and talkative, engaged. lots of good questions, some of which i didn't know how to answer. &lt;br /&gt;
** jenny: maybe we should have a live roleplay of how packets are transferred in a mesh network &lt;br /&gt;
* grant: have people put stickers on a map&lt;br /&gt;
** jenny: mesh speed dating&lt;br /&gt;
** jenny: could have nametags that use color coding &lt;br /&gt;
*jenny: great crowd. &lt;br /&gt;
* &amp;quot;non-technical roles: community organizing, documentarians, educators, legal hackers, people who like to climb tall buildings...&lt;br /&gt;
* didn't put in much effort, was very effective - don't want to see this balloon into an intensive project that takes a lot of effort&lt;br /&gt;
* eve: really liked daniel's station and being walked through setting up the access point. could be a good demo, maybe projected on the wall. Will gave a really good talk. Pleasantly surprised by turnout and likes all the ideas that she's heard&lt;br /&gt;
&lt;br /&gt;
== learnings for next time ==&lt;br /&gt;
* Daniel: need to have flyers and swag ready at least one day beforehand; help with proofreading (make how-to sheets more collaboratively-produced); wants to add photos to the how-to guides&lt;br /&gt;
* jorrit: more of a process to see how people fit in - eg, learn the protocol, neighborhood outreach, etc&lt;br /&gt;
** jenny: like a skills and interests assessment...&lt;br /&gt;
* jenny: someone whose role is to document / take photos / take video&lt;br /&gt;
*grant: handouts for each station?&lt;br /&gt;
* andy: maybe make sense to have more talks. getting into firmware and radio propagation. but do them as breakout talks. use the main stage for general information and present the schedules.&lt;br /&gt;
** grant: it'd be better since then we wouldn't have to repeat ourselves. had to repeat my intro to the babeld lab several times, maybe having a few set times in which a given station is intro'd&lt;br /&gt;
** jenny: maybe two staggered times for different &amp;quot;tracks&amp;quot;&lt;br /&gt;
* grant - wish i had something more comprehensive to hand to people in paper form&lt;br /&gt;
** difficult to assess given number of people how many talks to have&lt;br /&gt;
* jenny: maybe a more engineered flow. e.g. after they crimp the cable they should be able to plug it in and see it work.&lt;br /&gt;
* daniel: screen was too small for people in the back. bring chairs to front or use bigger screen. or instead of having stage then have every station talk one at a time (with mic and amp) and have entire group move from station to station.&lt;br /&gt;
* andy: de-emphasize the lecture aspect and emphasize the workshop aspect.&lt;br /&gt;
* jenny: we should have given a brief &amp;quot;history of peoplesopen.net&amp;quot; to contextualize. how the group operates and the ethos of the project.&lt;br /&gt;
* andy: one station just to answer question about security/practicality &amp;quot;don't trust the network&amp;quot; and &amp;quot;we run a vpn&amp;quot;&lt;br /&gt;
* grant: we should have community outreach station that demo'd more of the comminications &lt;br /&gt;
* jenny: we should practice (have a rehearsal) for at least the talks beforehand&lt;br /&gt;
* leslie: would include more of an overview at the beginning - detailing the different stations available etc&lt;br /&gt;
* daniel: assign people random numbers and make links ad hoc&lt;br /&gt;
* jorrit: table for handing out routers &lt;br /&gt;
** jenny: (maybe discount if they successfully flash their own router?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= next workshop =&lt;br /&gt;
&lt;br /&gt;
* July 1st 2-5 pm&lt;br /&gt;
&lt;br /&gt;
eve: Should we say &amp;quot;come back and it will be more in-depth&amp;quot; or something&lt;br /&gt;
&lt;br /&gt;
= outreach =&lt;br /&gt;
* ping Ivan about the library project, invite him to next meeting&lt;br /&gt;
* get back to lady from CCA asking for an example curriculum - interested in &lt;br /&gt;
* check in with jehan about stickers for the routers, work on a basic guide for setting up your node. &lt;br /&gt;
&lt;br /&gt;
= we need emojis =&lt;br /&gt;
* you should be able to easily explain exactly which emoji in e.g. 10 words or less&lt;br /&gt;
* it should be reasonably unoffensive&lt;br /&gt;
&lt;br /&gt;
= should the SSID change when no internet present? =&lt;br /&gt;
* marc: if there are two nodes or more they can connect. but otherwise people will connect and not get internet and it's bad advertising. change the ssid automatically when there's no internet&lt;br /&gt;
* jorrit: sounds like a problem we'd like to have... &amp;quot;peoplesopen doesn't work&amp;quot; and people actually log in and file an issue. &lt;br /&gt;
** marc: could have a peoplesopen node that doesn't connect to the internet and that's what was intended.. &lt;br /&gt;
*** jenny: longer-term may be a good way of promoting an oakland-based, independent internet with local services and alternatives to large corporate cloud providers, eg google&lt;br /&gt;
* marc: may be intentional, or it's down because the neighboring node is down, &lt;br /&gt;
&lt;br /&gt;
= battlemesh =&lt;br /&gt;
* email the list if you wanna come / coordinate!&lt;br /&gt;
* marc, jenny &amp;amp; jehan going so far&lt;br /&gt;
* Vienna, June 5-11&lt;br /&gt;
&lt;br /&gt;
= NPR interview update =&lt;br /&gt;
* marc was supposed to do it today, but the reporter stopped responding&lt;br /&gt;
* when/if it does air, we'll get a lot of media attention&lt;br /&gt;
** jenny: should ensure we have our legal ducks in a row before then&lt;br /&gt;
&lt;br /&gt;
= board meeting =&lt;br /&gt;
* andy: discuss further the structure of the group and how we can organize it to be more productive&lt;br /&gt;
** have been working with the DSA, very productive &amp;amp; organized, get a lot of things done&lt;br /&gt;
** some broad areas, communication/outreach, software/monitoring, node mounting - propose some committees/working groups and have meetings focused on specific areas. more focus sense of ownership etc etc&lt;br /&gt;
** &lt;br /&gt;
* daniel: this group seems much more self-motivated, dynamic - we have these groups already, so let's formalize that and let those in the groups decide how they meet / what they work on / etc&lt;br /&gt;
** jorrit: something concrete / formalized to point people to based on how they'd like to participate&lt;br /&gt;
&lt;br /&gt;
* communications - blog, workshops, social media, press&lt;br /&gt;
* outreach - node mounting, neighborhood engagement&lt;br /&gt;
* software - firmware dev, network monitoring&lt;br /&gt;
&lt;br /&gt;
* jorrit: or we could just keep the general part shorter and then break out into different groups?&lt;br /&gt;
** andy: people might want to be part of multiple groups&lt;br /&gt;
&lt;br /&gt;
= next meeting facilitator =&lt;br /&gt;
* if someone volunteers each week to facilitate the next meeting, can help keep us structured&lt;br /&gt;
* facilitator responsibilities -&lt;br /&gt;
* andy!&lt;/div&gt;</summary>
		<author><name>Tunabananas</name></author>
	</entry>
</feed>