Sudo Room - User contributions [en]

Mesh/Reminderbot

2019-10-30T03:30:49Z

Eenblam: List reminderbot as offline

'''Reminderbot is currently offline, since we transitioned to holding business meetings once a month instead of once a week in 2019.'''

Reminderbot pops into peoplesopen.net/chat to remind us of the action items we decided on at the previous meeting!

Reminderbot is [https://github.com/sudomesh/reminderbot on GitHub].

==Troubleshooting==

# Did you move the minutes from [https://peoplesopen.net/notes the pad] to their own page? The minutes actually contain instructions for how to do this.
# Did you create a link to the new page on [[Mesh/Minutes]]?
# Did you put the link at the top and use the same format as the rest of the table?
# Did Reminderbot pop in and report an error? If so, ping eenblam on Signal.

Mesh/Minutes

2019-07-31T02:56:40Z

Eenblam:

<center>'''Sudo Mesh Meeting Minutes'''</center>

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/02_07_2019|2019-07-02]]
| Monthly organizing meeting
|-
| [[Mesh/25_06_2019|2019-06-25]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2019|2019-06-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_June_2019|2019-06-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_May_2019|2019-05-28]]
| Weekly organizing meeting
|-
| 2019-05-21
| Hack night; no notes
|-
| [[Mesh/14_May_2019|2019-05-14]]
| Weekly organizing meeting
|-
| [[Mesh/30_April_2019|2019-04-30]]
| Weekly organizing meeting
|-
| [[Mesh/23_April_2019|2019-04-23]]
| Annual board meeting
|-
| [[Mesh/16_April_2019|2019-04-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_April_2019|2019-04-09]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2019|2019-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/19_March_2019|2019-03-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_March_2019|2019-03-12]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2019|2019-02-26]]
| Weekly organizing meeting
|-
| [[Mesh/19_February_2019|2019-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_February_2019|2019-02-12]]
| Weekly organizing meeting
|-
| [[Mesh/29_January_2019|2019-01-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_January_2019|2019-01-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_January_2019|2019-01-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_January_2019|2019-01-08]]
| Weekly organizing meeting
|-
| [[Mesh/18_December_2018|2018-12-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_December_2018|2018-12-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_December_2018|2018-12-04]]
| Weekly organizing meeting
|-
| [[Mesh/27_November_2018|2018-11-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_November_2018|2018-11-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_November_2018|2018-11-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_November_2018|2018-11-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_October_2018|2018-10-30]]
| Weekly organizing meeting
|-
| [[Mesh/23_October_2018|2018-10-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_October_2018|2018-10-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_October_2018|2018-10-09]]
| Weekly organizing meeting
|-
| [[Mesh/2_October_2018|2018-10-2]]
| Weekly organizing meeting
|-
| [[Mesh/25_September_2018|2018-09-25]]
| Weekly organizing meeting
|-
| [[Mesh/18_September_2018|2018-09-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_September_2018|2018-09-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_September_2018|2018-09-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_August_2018|2018-08-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_August_2018|2018-08-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_August_2018|2018-08-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_August_2018|2018-08-07]]
| Weekly organizing meeting
|-
| [[Mesh/24_July_2018|2018-07-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_July_2018|2018-07-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_July_2018|2018-07-10]]
| Weekly organizing meeting
|-
| [[Mesh/3_July_2018|2018-07-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_June_2018|2018-06-26]]
| Weekly organizing meeting
|-
| [[Mesh/12_June_2018|2018-06-12]]
| Weekly organizing meeting
|-
| [[Mesh/5_June_2018|2018-06-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_May_2018|2018-05-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_May_2018|2018-05-22]]
| Annual Board Meeting
|-
| [[Mesh/15_May_2018|2018-05-15]]
| Weekly organizing meeting & Firmware meeting
|-
| [[Mesh/8_May_2018|2018-05-08]]
| Weekly organizing meeting
|-
| [[Mesh/1_May_2018|2018-05-01]]
| Weekly organizing meeting
|-
| [[Mesh/24_Apr_2018|2018-04-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_Apr_2018|2018-04-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Apr_2018|2018-04-10]]
| Strategic plan meeting
|-
| [[Mesh/03_Apr_2018|2018-04-03]]
| Weekly organizing meeting
|-
| [[Mesh/27_Mar_2018|2018-03-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Mar_2018|2018-03-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_Mar_2018|2018-03-13]]
| Weekly organizing meeting
|-
| [[Mesh/6_Mar_2018|2018-03-06]]
| Weekly organizing meeting
|-
| [[Mesh/27_Feb_2018|2018-02-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Feb_2018|2018-02-20]]
| Weekly organizing meeting
|-
| [[Mesh/17_Feb_2018|2018-02-17]]
| Strategic plan meeting
|-
| [[Mesh/13_Feb_2018|2018-02-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_Feb_2018|2018-02-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_Jan_2018|2018-01-30]]
| Monthly general meeting
|-
| [[Mesh/23_Jan_2018|2018-01-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_Jan_2018|2018-01-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_Jan_2018|2018-01-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_Jan_2018|2018-01-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_Dec_2017|2017-12-26]]
| Monthly general meeting
|-
| [[Mesh/19_Dec_2017|2017-12-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Dec_2017|2017-12-12]]
| Weekly organizing meeting
|-
| [[Mesh/05_Dec_2017|2017-12-05]]
| Weekly organizing meeting
|-
| [[Mesh/28_Nov_2017|2017-11-28]]
| Monthly general meeting
|-
| [[Mesh/21_Nov_2017|2017-11-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_Nov_2017|2017-11-14]]
| Weekly organizing meeting
|-
| [[Mesh/24_Oct_2017|2017-10-24]]
| Monthly general meeting
|-
| [[Mesh/17_Oct_2017|2017-10-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Oct_2017|2017-10-10]]
| Weekly organizing meeting
|-
| [[Mesh/03_Oct_2017|2017-10-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_Sep_2017|2017-09-26]]
| Monthly general meeting
|-
| [[Mesh/19_Sep_2017|2017-09-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Sep_2017|2017-09-12]]
| Weekly organizing meeting
|-
| [[Mesh/11_Sep_2017|2017-09-11]]
| Website redesign session
|-
| [[Mesh/05_Sep_2017|2017-09-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_Aug_2017|2017-08-29]]
| Monthly general meeting
|-
| [[Mesh/22_Aug_2017|2017-08-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_Aug_2017|2017-08-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_Aug_2017|2017-08-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_Aug_2017|2017-08-01]]
| Weekly organizing meeting
|-
| [[Mesh/18_July_2017|2017-07-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_July_2017|2017-07-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_July_2017|2017-07-4]]
| Weekly organizing meeting
|-
| [[Mesh/20_June_2017|2017-06-20]]
| Monthly general meeting
|-
| [[Mesh/13_June_2017|2017-06-13]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2017|2017-06-11]]
| Temescal street fair report-back
|-
| [[Mesh/6_June_2017|2017-06-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_May_2017|2017-05-30]]
| Monthly general meeting
|-
| [[Mesh/16_May_2017|2017-05-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_May_2017|2017-05-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_May_2017|2017-05-02]]
| Weekly organizing meeting
|-
| [[Mesh/25_April_2017|2017-04-25]]
| Monthly general meeting
|-
| [[Mesh/18_April_2017|2017-04-18]]
| Weekly organizing meeting
|-
| [[Mesh/17_April_2017|2017-04-17]]
| Annual sudo mesh board meeting
|-
| [[Mesh/11_April_2017|2017-04-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_April_2017|2017-04-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_March_2017|2017-03-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_March_2017|2017-03-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_March_2017|2017-03-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_March_2017|2017-03-07]]
| Weekly organizing meeting
|-
| [[Mesh/28_February_2017|2017-02-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_February_2017|2017-02-21]]
| Weekly organizing meeting
|-
| [[Mesh/10_February_2017|2017-02-10]]
| Weekly organizing meeting
|-
| [[Mesh/07_February_2017|2017-02-07]]
| Organizing "Build Your Own Internet" Workshop
|-
| [[Mesh/05_July_2016|2016-07-05]]
| Videochat meeting with nycmesh
|-
| [[Mesh/22_June_2016|2016-06-22]]
| Weekly organizing meeting
|-
| [[Mesh/07_June_2016|2016-06-07]]
| Weekly organizing meeting
|-
| [[Mesh/23_February_2016|2016-02-23]]
| Monthly general meeting
|-
| [[Mesh/09_February_2016|2016-02-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_February_2016|2016-02-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_January_2016|2016-01-26]]
| Monthly general meeting
|-
| [[Mesh/27_October_2015|2015-10-27]]
| Monthly general meeting
|-
| [[Mesh/06_October_2015|2015-10-06]]
| Weekly organizing meeting
|-
| [[Mesh/29_September_2015|2015-09-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_September_2015|2015-09-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_September_2015|2015-09-15]]
| Second annual board meeting
|-
| [[Mesh/08_September_2015|2015-09-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_September_2015|2015-09-01]]
| Monthly general meeting
|-
| [[Mesh/07_April_2015|2015-04-07]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2015|2015-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/17_March_2015|2015-03-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_March_2015|2015-03-10]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2015|2015-02-26]]
| Big general meeting
|-
| [[Mesh/24_February_2015|2015-02-24]]
| Hacknight
|-
| [[Mesh/19_February_2015|2015-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/05_February_2015|2015-02-05]]
| Weekly organizing meeting
|-
| [[Mesh/03_February_2015|2015-02-04]]
| Hacknight
|-
| [[Mesh/29_January_2015|2015-01-29]]
| Big general meeting
|-
| [[Mesh/24_January_2015|2015-01-24]]
| Mesh mini-retreat
|-
| [[Mesh/22_January_2015|2015-01-22]]
| Weekly general meeting
|-
| [[Mesh/15_January_2015|2015-01-15]]
| Weekly general meeting
|-
| [[Mesh/30_December_2014|2014-12-30]]
| Big general meeting
|-
| [[Mesh/18_December_2014|2014-12-18]]
| Weekly general meeting
|-
| [[Mesh/13_November_2014|2014-11-13]]
| Weekly general meeting
|-
| [[Mesh/21_October_2014|2014-10-21]]
| Hacknight
|-
| [[Mesh/16_October_2014|2014-10-16]]
| Weekly general meeting
|-
| [[Mesh/09_October_2014|2014-10-09]]
| Weekly general meeting
|-
| [[Mesh/02_October_2014|2014-10-02]]
| Weekly general meeting
|-
| [[Mesh/25_September_2014|2014-09-25]]
| Big general meeting
|-
| [[Mesh/28_August_2014|2014-08-28]]
| Big general meeting
|-
| [[Mesh/21_August_2014|2014-08-21]]
|
|-
| [[Mesh/07_August_2014|2014-08-07]]
|
|-
| [[Mesh/31_July_2014|2014-07-31]]
| Big general meeting
|-
| [[Mesh/17_July_2014|2014-07-17]]
|
|-
| [[Mesh/15_July_2014|2014-07-15]]
|
|-
| [[Mesh/10_July_2014|2014-07-10]]
|
|-
| [[Mesh/06_July_2014|2014-07-06]]
| Hackathon Day 2!
|-
| [[Mesh/05_July_2014|2014-07-05]]
| Hackathon Day 1!
|-
| [[Mesh/03_July_2014|2014-07-03]]
|
|-
| [[Mesh/12_June_2014|2014-06-12]]
|
|-
| [[Mesh/05_June_2014|2014-06-05]]
|
|-
|-
| [[Mesh/29_May_2014|2014-05-29]]
| General meeting
|-
| [[Mesh/27_May_2014|2014-05-27]]
|
|-
| [[Mesh/20_May_2014|2014-05-20]]
|
|-
| [[Mesh/13_May_2014|2014-05-13]]
| First Tuesday meeting ^.^
|-
| [[Mesh/08_May_2014|2014-05-08]]
|
|-
| [[Mesh/01_May_2014|2014-05-01]]
|
|-
| [[Mesh/24_April_2014|2014-04-24]]
| General meeting!
|-
| [[Mesh/17_April_2014|2014-04-17]]
|
|-
| [[Mesh/03_April_2014|2014-04-03]]
|
|-
| [[Mesh/27_March_2014|2014-03-27]]
|
|-
| [[Mesh/20_March_2014|2014-03-20]]
|
|-
| [[Mesh/13_March_2014|2014-03-13]]
|
|-
| [[Mesh/27_February_2014|2014-02-27]]
|
|-
| [[Mesh/20_February_2014|2014-02-20]]
|
|-
| [[Mesh/13_February_2014|2014-02-13]]
|
|-
| [[Mesh/6_February_2014|2014-02-06]]
|
|-
| [[Mesh/30_January_2014|2014-01-30]]
|
|-
| [[Mesh/23_January_2014|2014-01-23]]
|
|-
| [[Mesh/16_January_2014|2014-01-16]]
|
|-
| 31 December - 09 January
| Holidaze Break
|-
| [[Mesh/26_December_2013|2013-12-26]]
|
|-
| [[Mesh/19_December_2013|2013-12-19]]
|
|-
| [[Mesh/12_December_2013|2013-12-12]]
|
|-
| [[Mesh/5_December_2013|2013-12-05]]
|
|-
| [[Mesh/21_November_2013|2013-11-21]]
|
|-
| [[Mesh/14_November_2013|2013-11-14]]
|
|-
| [[Mesh/07_November_2013|2013-11-07]]
|
|-
| [[Mesh/31_October_2013|2013-10-31]]
|
|-
| [[Mesh/24_October_2013|2013-10-24]]
|
|-
| [[Mesh/17_October_2013|2013-10-17]]
|
|-
| [[Mesh/10_October_2013|2013-10-10]]
|
|-
| [[Mesh/26_September_2013|2013-09-26]]
|
|-
| [[Mesh/18_September_2013|2013-09-18]]
|
|-
| [[Mesh/11_September_2013|2013-09-11]]
|
|-
| [[Mesh/4_September_2013|2013-09-04]]
|
|-
| [[Mesh/28_August_2013|2013-08-28]]
|
|-
| 07 August - 21 August
| Hack nights!
|-
| [[Mesh/31_July_2013|2013-07-31]]
|
|-
| [[Mesh/25_July_2013|2013-07-25]]
|
|-
| 18 July 2013
| Hack night: Flashing, firmware
|-
| [[Mesh/11_July_2013|2013-07-11]]
|
|-
| [[Mesh/04_July_2013|2013-07-04]]
|
|-
| [[Mesh/27_June_2013|2013-06-27]]
|
|-
| [[Mesh/20_June_2013|2013-06-20]]
|
|-
| [[Mesh/13_June_2013|2013-06-13]]
|
|-
| 30 May - 05 June
| Hack nights! Trying out some of the nicer Ubiquiti equipment we procured
|-
| [[Mesh/23_May_2013|2013-05-23]]
|
|-
| [[Mesh/09_May_2013|2013-05-09]]
|
|-
| 25 April - 02 May
| Hack nights! See wiki for documentation - principally going through donated routers, flashing them with OpenWRT and installing batman-adv.
|-
| [[Mesh/18_April_2013|2013-04-18]]
|
|-
| [[Mesh/11_April_2013|2013-04-11]]
|
|-
| 28 March - 04 April
| SPRING SHIFT HIATUS
|-
| [[Mesh/21_March_2013|2013-03-21]]
|
|-
| [[Mesh/07_March_2013|2013-03-07]]
|
|-
| [[Mesh/28_February_2013|2013-02-28]]
|
|-
| [[Mesh/21_February_2013|2013-02-21]]
|
|-
| [[Mesh/14_February_2013|2013-02-14]]
|
|-
| [[Mesh/7_February_2013|2013-02-07]]
|
|-
| [http://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html 2013-01-31]
|
|}

Mesh/02 07 2019

2019-07-31T02:55:46Z

Eenblam: Created page with "Notes from 2 July 2019: Email from Jesse re: paying directors: "Anytime a public benefit corporation has a transaction with a director -- which would include a grant, co..."

Notes from 2 July 2019:

Email from Jesse re: paying directors:

"Anytime a public benefit corporation has a transaction with a director -- which would include a grant, compensation, financial transfer, loan, etc -- there should be a self-dealing resolution unless particular circumstance that do not sound relevant in your example are present.
The board resolution should be passed by the non-interested directors and the interested director (the person involved in the transaction) should recuse themselves.
This is under Corporations Code 5233 (d), pasted below. I have previously sent you sample language that covers all the requirements of 5233.
While it is a small hassle, you should do it. Note that the resolution has to be passed before payment is made.
The resolution does not have to be passed unanimously under the Corp. Code.
Let me know if you want to discuss.
take care, jesse"

Corporations Code 5233
(a) Except as provided in subdivision (b), for the purpose of this section, a self-dealing transaction means a transaction to which the corporation is a party and in which one or more of its directors has a material financial interest and which does not meet the requirements of paragraph (1), (2), or (3) of subdivision (d). Such a director is an "interested director" for the purpose of this section.
(b) The provisions of this section do not apply to any of the following:
(1) An action of the board fixing the compensation of a director as a director or officer of the corporation.
(2) A transaction which is part of a public or charitable program of the corporation if it: (i) is approved or authorized by the corporation in good faith and without unjustified favoritism; and (ii) results in a benefit to one or more directors or their families because they are in the class of persons intended to be benefited by the public or charitable program.
(3) A transaction, of which the interested director or directors have no actual knowledge, and which does not exceed the lesser of 1 percent of the gross receipts of the corporation for the preceding fiscal year or one hundred thousand dollars ($100,000).
(c) The Attorney General or, if the Attorney General is joined as an indispensable party, any of the following may bring an action in the superior court of the proper county for the remedies specified in subdivision (h):
(1) The corporation, or a member asserting the right in the name of the corporation pursuant to Section 5710.
(2) A director of the corporation.
(3) An officer of the corporation.
(4) Any person granted relator status by the Attorney General.
(d) In any action brought under subdivision (c) the remedies specified in subdivision (h) shall not be granted if:
(1) The Attorney General, or the court in an action in which the Attorney General is an indispensable party, has approved the transaction before or after it was consummated; or
(2) The following facts are established:
(A) The corporation entered into the transaction for its own benefit;
(B) The transaction was fair and reasonable as to the corporation at the time the corporation entered into the transaction;
(C) Prior to consummating the transaction or any part thereof the board authorized or approved the transaction in good faith by a vote of a majority of the directors then in office without counting the vote of the interested director or directors, and with knowledge of the material facts concerning the transaction and the directorâ€™s interest in the transaction. Except as provided in paragraph (3) of this subdivision, action by a committee of the board shall not satisfy this paragraph; and
(D) (i) Prior to authorizing or approving the transaction the board considered and in good faith determined after reasonable investigation under the circumstances that the corporation could not have obtained a more advantageous arrangement with reasonable effort under the circumstances or (ii) the corporation in fact could not have obtained a more advantageous arrangement with reasonable effort under the circumstances; or
(3) The following facts are established:
(A) A committee or person authorized by the board approved the transaction in a manner consistent with the standards set forth in paragraph (2) of this subdivision;
(B) It was not reasonably practicable to obtain approval of the board prior to entering into the transaction; and
(C) The board, after determining in good faith that the conditions of subparagraphs (A) and (B) of this paragraph were satisfied, ratified the transaction at its next meeting by a vote of the majority of the directors then in office without counting the vote of the interested director or directors.
(e) Except as provided in subdivision (f), an action under subdivision (c) must be filed within two years after written notice setting forth the material facts of the transaction and the directorâ€™s interest in the transaction is filed with the Attorney General in accordance with such regulations, if any, as the Attorney General may adopt or, if no such notice is filed, within three years after the transaction occurred, except for the Attorney General, who shall have 10 years after the transaction occurred within which to file an action.
(f) In any action for breach of an obligation of the corporation owed to an interested director, where the obligation arises from a self-dealing transaction which has not been approved as provided in subdivision (d), the court may, by way of offset only, make any order authorized by subdivision (h), notwithstanding the expiration of the applicable period specified in subdivision (e).
(g) Interested directors may be counted in determining the presence of a quorum at a meeting of the board which authorizes, approves or ratifies a contract or transaction.
(h) If a self-dealing transaction has taken place, the interested director or directors shall do such things and pay such damages as in the discretion of the court will provide an equitable and fair remedy to the corporation, taking into account any benefit received by the corporation and whether the interested director or directors acted in good faith and with intent to further the best interest of the corporation. Without limiting the generality of the foregoing, the court may order the director to do any or all of the following:
(1) Account for any profits made from such transaction, and pay them to the corporation;
(2) Pay the corporation the value of the use of any of its property used in such transaction; and
(3) Return or replace any property lost to the corporation as a result of such transaction, together with any income or appreciation lost to the corporation by reason of such transaction, or account for any proceeds of sale of such property, and pay the proceeds to the corporation together with interest at the legal rate. The court may award prejudgment interest to the extent allowed in Section 3287 or 3288 of the Civil Code. In addition, the court may, in its discretion, grant exemplary damages for a fraudulent or malicious violation of this section.
(Amended by Stats. 1981, Ch. 587, Sec. 7.)

= Action Items =
* Self-dealing resolution on Loomio - Jenny - done

* Flashing N600s with LibreMesh - Marc / seth / lesley / tyler - done

* Email to Temescal Street Fair and BYOI signups - Mai - done
* Ping Commons about double-booking our meeting space - Jenny - done
* Update Github with Q2 financial reports - Jenny - done

Mesh/Mesh Meeting Notes Template

2019-06-02T23:07:45Z

Eenblam: /* Check in on previous action items */

'''People's Open Network Weekly Meeting - Day Month 2019 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Check in on ongoing projects (10 mins)
* Proposal X: (15 mins)
* Discussion Y: (15 mins)
* Weekly updates/check-ins (10 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question:
*

=== Meeting Roles ===
* Facilitator/s:
* Stacktaker:
* Notetaker/s:
** URL of this pad: https://peoplesopen.net/notes

== Check Ins: Action Items & Active Projects ==
Check https://trello.com/b/wBKTQKDs/active-projects for Blocked items.

Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste action items below.

== Other Updates & Reportbacks ==
=== Bugs/Technical ===
Recent issues: https://peoplesopen.net/issues. For a list of recent Github activity, see the widget at the bottom of https://peoplesopen.net/learn/development/.
*

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
*

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
*

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
*

== Next Sunday ==
We host office hours every Sunday from 1-3pm in Sudo Room to talk to people, work on sudomesh projects, and schedule node mounts.
* To sign up to bottomline, fill in your name here: https://ethercalc.org/byoi_office_hours
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays
* Notes from this past Sunday's session:
**

== Example Proposal ==
* Lumbragolonga: I propose that for one week we communicate exclusively via paper airplane. Here's why...
* '''Consenso?'''

== Example Discussion Item ==
* Gormavax: I wanna chat about the recent influx of spotted pigeon-dactyls in the Martian exosphere...

== Action Items ==
Copy and paste from previous action items above, delete completed ones, and add new ones:
*

== Breakout Groups ==
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
*

== Last Meeting Notes ==
* link to previous meeting minutes
* CHANGE ME AFTER PASTING: https://sudoroom.org/wiki/Mesh/10_December_1815

== End of Meeting ==
* please archive these meeting notes by copying the entire pad contents onto the sudomesh wiki with the correct date format: https://sudoroom.org/wiki/Mesh/DD_MONTH_YYYY
* 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_Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wiki/Mesh/Minutes

[[Category:Mesh/Minutes]]

Mesh/Mesh Meeting Notes Template

2019-06-02T23:04:57Z

Eenblam: Update action items + weekly updates/check-ins

'''People's Open Network Weekly Meeting - Day Month 2019 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Check in on ongoing projects (10 mins)
* Proposal X: (15 mins)
* Discussion Y: (15 mins)
* Weekly updates/check-ins (10 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question:
*

=== Meeting Roles ===
* Facilitator/s:
* Stacktaker:
* Notetaker/s:
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check https://trello.com/b/wBKTQKDs/active-projects for Blocked items.
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste action items below.

== Other Updates & Reportbacks ==
=== Bugs/Technical ===
Recent issues: https://peoplesopen.net/issues. For a list of recent Github activity, see the widget at the bottom of https://peoplesopen.net/learn/development/.
*

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
*

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
*

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
*

== Next Sunday ==
We host office hours every Sunday from 1-3pm in Sudo Room to talk to people, work on sudomesh projects, and schedule node mounts.
* To sign up to bottomline, fill in your name here: https://ethercalc.org/byoi_office_hours
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays
* Notes from this past Sunday's session:
**

== Example Proposal ==
* Lumbragolonga: I propose that for one week we communicate exclusively via paper airplane. Here's why...
* '''Consenso?'''

== Example Discussion Item ==
* Gormavax: I wanna chat about the recent influx of spotted pigeon-dactyls in the Martian exosphere...

== Action Items ==
Copy and paste from previous action items above, delete completed ones, and add new ones:
*

== Breakout Groups ==
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
*

== Last Meeting Notes ==
* link to previous meeting minutes
* CHANGE ME AFTER PASTING: https://sudoroom.org/wiki/Mesh/10_December_1815

== End of Meeting ==
* please archive these meeting notes by copying the entire pad contents onto the sudomesh wiki with the correct date format: https://sudoroom.org/wiki/Mesh/DD_MONTH_YYYY
* 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_Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wiki/Mesh/Minutes

[[Category:Mesh/Minutes]]

Mesh/28 May 2019

2019-06-02T21:57:22Z

Eenblam: /* = Breakout Groups */

'''People's Open Network Weekly Meeting - 28 May 2019 7:30pm-9pm'''
"Today is Pungenday, the 2nd day of Confusion in the YOLD 3185"
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Check in on ongoing projects (10 mins)
* Proposal X: (15 mins)
* Discussion Y: (15 mins)
* Weekly updates/check-ins (10 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: how do you like to measure time?
* benny - he/him - in minutes. normally. in measurements of self-exhaustion. in nanoseconds if i have my bracelet with me.
* deniz - he/him met benny through a friend ari--work in arts/film, been here ~6/7 months! mostly here to listen. How I measure time is with my heartbeathe
* juul - he/him - how quickly or slowly other people appear to be speaking
* jenny - she/her - in decisions and revisions, which a minute will unwind (who knows their T. S. Elliott)
** We got accepted by Mobile Citizen!
* eenblam - he/they - reminderbot lets me know when it's thursday
* eve- she - time between ice ages
* robb - he/him - eons
* john-mark - he/they - seconds, because if your meeting is at eight, and your clock says 8:00, you're probably late (better late than never - null)ðŸ‘�)
* Null (remote)- he/him - in pico-sec you have one life to live so live it fully.
* alex - i used to be involved in sudomesh quite a bit--was responsible for some crappy code here and there and stuff like that. a lot of debugging. i measure time in seconds.

=== Meeting Roles ===
* Facilitator/s: benny
* Stacktaker:
* Notetaker/s: jnny, juul,
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste action items below:
CAVEAT: Some of these are SUPER OLD
* ping paxio again, forever @bennlich
* make an 0.3.1 firmware release and add link to walkthrough @bennlich
* create wiki page about EMF Radiation @sierk @tunabananas
** put things here: https://sudoroom.org/wiki/Mesh/EMFradiation
* any reply from LOLSpace? @tunabananas
** last april: wifi has no wifi
* poke ryan about marina @tunabananas
* should we plan to go to cal sailing open house june 16th, sunday, 1--4pm -https://www.cal-sailing.org/activities/csc-open-house
** reply via Ryan from Toeknee: " I spoke to Ryan Alder yesterday. Sounds like they are waiting on the manager approval for Monkey Brain's Proposal. If you want put your pole next to their Flagpole, you'll likely need to peak to the Marina. BTW, Cal Sailing just put up a 30ft pole for our radio antenna which is next to our clubhouse. If you guys want to piggy back on the same pole it should be fine. No need for climbing. Easy access."
** jenny, benny are available june 16th
* e-mail jonah and ask about richmond street light internet @bennlich
** didn't do this
* berkeley light pole mounting research @robb
** didn't do this
* rochdale mount this sunday w/ movie night after?
** didn't do this
* maybe research antenna range calculator--people are always asking about that @bennlich
* schedule HE server install / hike @bennlichm
** w00t @bennlich @null and @mux

=== Node Mounts & Outreach ===

"Tis an ill wind that blows no minds"
â€• Malaclypse the Younger, Principia Discordia

== Weekly updates/check-ins ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste weekly update items below:

== Other Updates & Reportbacks ==
=== Bugs/Technical ===
Recent issues: https://peoplesopen.net/issues. For a list of recent Github activity, see the widget at the bottom of https://peoplesopen.net/learn/development/.
*
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
*

=== Communications & Events ===

Hell is reserved exclusively for them that believe in it.
Further, the lowest Rung in Hell is reserved for them that believe in it on the supposition that they'll go there if they don't. .
-- Principia Discordia

* Jenny: Approved by mobile citizen!!! Woo!!

Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
*

=== Internal Logistics / Finance ===

If you can master nonsense as well as you have already learned to master sense, then each will expose the other for what it is: absurdity.
-- Principia Discordia

Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* Jenny: Sent in our 990EZ (federal) and 199N (State) tax forms last week (nonprofit deadline is May 15). I'd imagined we'd have had to file the full forms, but even with the grants and donations from last year (totaling ~$122K), our average over 3 years was still only $42K since we made virtually no income in 2017 and 2016. Forms were digitally filed here: https://drive.google.com/open?id=1Dx8p0GPu1aq0FExz7kf90AX6xzec0M0o
* Need to coordinate a bank party to a) remove Matt Senate from the account and b) add designated Finance WG people (Mai, Benny, Ben, Null? there may be a limit, will ask) - all signers AND Matt have to be physically present at the bank to do so (or we attempt once more to get our account with Beneficial functional).
** I'll be wherever I need to be to help with this. Thanks -Null
* Moving forward, Reimbursements and payments on invoices will be issued on the Third Friday of the month
* The board also needs to sign a 'Self-Dealing Resolution' whenever we decide to pay an officer or director

=Sundays=
* BYOI Office Hours: Please put your name here: https://ethercalc.org/byoi_office_hours
** eenblam will be here this sunday -- interested in doing work on documentation + educational materials following up discussions at last BYOI
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays

=Discussions & Proposals=
== Proposal ==
* eenblam and others: let's start doing every other Tuesday as hack nights. Want a temperature check here, then Loomio if well-received.
** robb: tyler suggested having increasing seriousness/structure of meetings over the course of the month, then reset.
** jmg - if it doesn't work, nothing prevents us from going back.
* '''Consenso?'''
** yes - proceed to Loomio to gather additional consensus.

== Discussion: Disaster Radio ==
* juul: if anyone is interested in helping out w/ disaster radio, we're going to start working with the Indian team every wednesday at 10:30pm

== Discussion: Visit the mushroom farm ==
* mai: Anyone who's interested in DWeb Camp â€” there'll be a visit to the mushroom farm (where camp will be) on Sat June 8 with Ben of ToMesh to help with some preliminary calculations for the mesh, like radio range tests. Anyone planning on going to Camp wanna go visit to help out and check out the space?
** benny: im interested
*** jnny me three!
** Also eenblam
** I'd like to go null

== Discussion: Quarterly Mesh Report ==
* eenblam: We decided to do this at the last board meeting. Need to determine how we want to go about it.
** Decide on requirements for report
*** Example from Max: https://docs.google.com/document/d/1Hy_bQA7CHTUw_6yKF3VTUv0mHtRMTgJsJkgbK69Br4Y/edit?pli=1
*** These are things that Max would like to see in the report that *are not * easy to find right now. *Not* comprehensive of what would go in report.
*** jmg - have both change/quarter and change/year for node updates so we can see performance relative to time
** Decide on compensation for each report
*** jenny - we should allocate $500/report for someone to dig up all this stuff to ensure responsible reporting.
**** eenblam - or say, $400 for report and $100 to validate and copyedit
** Null 366.30 for report + 133.70 for validate and copy edit - just a suggestion.
* Interested parties: breakout after.

== Discussion: CC Camp ==
* juul - we gotta request those precious, precious tokens
** https://en.m.wikipedia.org/wiki/Chaos_Communication_Camp
** lol -Null

== Discussion: Labs ==
* eenblam - small announcement: I've started working on (currently easy) networking labs you can run on your desktop. Contributions would be awesome!
** https://github.com/eenblam/labs
*** awesome!!

== Action Items ==
Copy and paste from previous action items above, delete completed ones, and add new ones:
* recruit a team to go to cal sailing open house june 16th, sunday, 1--4pm -https://www.cal-sailing.org/activities/csc-open-house
* talk to native health center folks @tunabananas
* e-mail jonah and ask about richmond street light internet @bennlich
* berkeley light pole mounting research @mux
* mobile citizen update @tunabananas
* send out self-dealing resolution loomio thread @tunabananas
* fiber internet via sonic or at&t at omni? @jmg @null
* Quarterly reports @eenblam
* Hack nights proposal @eenblam

= Breakout Groups =
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
* Check in about bank party
* Quarterly mesh reports
** https://peoplesopen.net/pad/p/quarterly

== Last Meeting Notes ==
* https://sudoroom.org/wiki/Mesh/14_May_2019

[[Category:Mesh/Minutes]]

Mesh/28 May 2019

2019-06-02T21:40:46Z

Eenblam: /* Discussion: Labs */

'''People's Open Network Weekly Meeting - 28 May 2019 7:30pm-9pm'''
"Today is Pungenday, the 2nd day of Confusion in the YOLD 3185"
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Check in on ongoing projects (10 mins)
* Proposal X: (15 mins)
* Discussion Y: (15 mins)
* Weekly updates/check-ins (10 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: how do you like to measure time?
* benny - he/him - in minutes. normally. in measurements of self-exhaustion. in nanoseconds if i have my bracelet with me.
* deniz - he/him met benny through a friend ari--work in arts/film, been here ~6/7 months! mostly here to listen. How I measure time is with my heartbeathe
* juul - he/him - how quickly or slowly other people appear to be speaking
* jenny - she/her - in decisions and revisions, which a minute will unwind (who knows their T. S. Elliott)
** We got accepted by Mobile Citizen!
* eenblam - he/they - reminderbot lets me know when it's thursday
* eve- she - time between ice ages
* robb - he/him - eons
* john-mark - he/they - seconds, because if your meeting is at eight, and your clock says 8:00, you're probably late (better late than never - null)ðŸ‘�)
* Null (remote)- he/him - in pico-sec you have one life to live so live it fully.
* alex - i used to be involved in sudomesh quite a bit--was responsible for some crappy code here and there and stuff like that. a lot of debugging. i measure time in seconds.

=== Meeting Roles ===
* Facilitator/s: benny
* Stacktaker:
* Notetaker/s: jnny, juul,
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste action items below:
CAVEAT: Some of these are SUPER OLD
* ping paxio again, forever @bennlich
* make an 0.3.1 firmware release and add link to walkthrough @bennlich
* create wiki page about EMF Radiation @sierk @tunabananas
** put things here: https://sudoroom.org/wiki/Mesh/EMFradiation
* any reply from LOLSpace? @tunabananas
** last april: wifi has no wifi
* poke ryan about marina @tunabananas
* should we plan to go to cal sailing open house june 16th, sunday, 1--4pm -https://www.cal-sailing.org/activities/csc-open-house
** reply via Ryan from Toeknee: " I spoke to Ryan Alder yesterday. Sounds like they are waiting on the manager approval for Monkey Brain's Proposal. If you want put your pole next to their Flagpole, you'll likely need to peak to the Marina. BTW, Cal Sailing just put up a 30ft pole for our radio antenna which is next to our clubhouse. If you guys want to piggy back on the same pole it should be fine. No need for climbing. Easy access."
** jenny, benny are available june 16th
* e-mail jonah and ask about richmond street light internet @bennlich
** didn't do this
* berkeley light pole mounting research @robb
** didn't do this
* rochdale mount this sunday w/ movie night after?
** didn't do this
* maybe research antenna range calculator--people are always asking about that @bennlich
* schedule HE server install / hike @bennlichm
** w00t @bennlich @null and @mux

=== Node Mounts & Outreach ===

"Tis an ill wind that blows no minds"
â€• Malaclypse the Younger, Principia Discordia

== Weekly updates/check-ins ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste weekly update items below:

== Other Updates & Reportbacks ==
=== Bugs/Technical ===
Recent issues: https://peoplesopen.net/issues. For a list of recent Github activity, see the widget at the bottom of https://peoplesopen.net/learn/development/.
*
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
*

=== Communications & Events ===

Hell is reserved exclusively for them that believe in it.
Further, the lowest Rung in Hell is reserved for them that believe in it on the supposition that they'll go there if they don't. .
-- Principia Discordia

* Jenny: Approved by mobile citizen!!! Woo!!

Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
*

=== Internal Logistics / Finance ===

If you can master nonsense as well as you have already learned to master sense, then each will expose the other for what it is: absurdity.
-- Principia Discordia

Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* Jenny: Sent in our 990EZ (federal) and 199N (State) tax forms last week (nonprofit deadline is May 15). I'd imagined we'd have had to file the full forms, but even with the grants and donations from last year (totaling ~$122K), our average over 3 years was still only $42K since we made virtually no income in 2017 and 2016. Forms were digitally filed here: https://drive.google.com/open?id=1Dx8p0GPu1aq0FExz7kf90AX6xzec0M0o
* Need to coordinate a bank party to a) remove Matt Senate from the account and b) add designated Finance WG people (Mai, Benny, Ben, Null? there may be a limit, will ask) - all signers AND Matt have to be physically present at the bank to do so (or we attempt once more to get our account with Beneficial functional).
** I'll be wherever I need to be to help with this. Thanks -Null
* Moving forward, Reimbursements and payments on invoices will be issued on the Third Friday of the month
* The board also needs to sign a 'Self-Dealing Resolution' whenever we decide to pay an officer or director

=Sundays=
* BYOI Office Hours: Please put your name here: https://ethercalc.org/byoi_office_hours
** eenblam will be here this sunday -- interested in doing work on documentation + educational materials following up discussions at last BYOI
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays

=Discussions & Proposals=
== Proposal ==
* eenblam and others: let's start doing every other Tuesday as hack nights. Want a temperature check here, then Loomio if well-received.
** robb: tyler suggested having increasing seriousness/structure of meetings over the course of the month, then reset.
** jmg - if it doesn't work, nothing prevents us from going back.
* '''Consenso?'''
** yes - proceed to Loomio to gather additional consensus.

== Discussion: Disaster Radio ==
* juul: if anyone is interested in helping out w/ disaster radio, we're going to start working with the Indian team every wednesday at 10:30pm

== Discussion: Visit the mushroom farm ==
* mai: Anyone who's interested in DWeb Camp â€” there'll be a visit to the mushroom farm (where camp will be) on Sat June 8 with Ben of ToMesh to help with some preliminary calculations for the mesh, like radio range tests. Anyone planning on going to Camp wanna go visit to help out and check out the space?
** benny: im interested
*** jnny me three!
** Also eenblam
** I'd like to go null

== Discussion: Quarterly Mesh Report ==
* eenblam: We decided to do this at the last board meeting. Need to determine how we want to go about it.
** Decide on requirements for report
*** Example from Max: https://docs.google.com/document/d/1Hy_bQA7CHTUw_6yKF3VTUv0mHtRMTgJsJkgbK69Br4Y/edit?pli=1
*** These are things that Max would like to see in the report that *are not * easy to find right now. *Not* comprehensive of what would go in report.
*** jmg - have both change/quarter and change/year for node updates so we can see performance relative to time
** Decide on compensation for each report
*** jenny - we should allocate $500/report for someone to dig up all this stuff to ensure responsible reporting.
**** eenblam - or say, $400 for report and $100 to validate and copyedit
** Null 366.30 for report + 133.70 for validate and copy edit - just a suggestion.
* Interested parties: breakout after.

== Discussion: CC Camp ==
* juul - we gotta request those precious, precious tokens
** https://en.m.wikipedia.org/wiki/Chaos_Communication_Camp
** lol -Null

== Discussion: Labs ==
* eenblam - small announcement: I've started working on (currently easy) networking labs you can run on your desktop. Contributions would be awesome!
** https://github.com/eenblam/labs
*** awesome!!

== Action Items ==
Copy and paste from previous action items above, delete completed ones, and add new ones:
* recruit a team to go to cal sailing open house june 16th, sunday, 1--4pm -https://www.cal-sailing.org/activities/csc-open-house
* talk to native health center folks @tunabananas
* e-mail jonah and ask about richmond street light internet @bennlich
* berkeley light pole mounting research @mux
* mobile citizen update @tunabananas
* send out self-dealing resolution loomio thread @tunabananas
* fiber internet via sonic or at&t at omni? @jmg @null
* Quarterly reports @eenblam
* Hack nights proposal @eenblam

== Breakout Groups =
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
* Check in about bank party
* Quarterly mesh reports
** https://peoplesopen.net/pad/p/quarterly

== Last Meeting Notes ==
* https://sudoroom.org/wiki/Mesh/14_May_2019

[[Category:Mesh/Minutes]]

Mesh/28 May 2019

2019-06-02T21:40:28Z

Eenblam: /* Sundays */

'''People's Open Network Weekly Meeting - 28 May 2019 7:30pm-9pm'''
"Today is Pungenday, the 2nd day of Confusion in the YOLD 3185"
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Check in on ongoing projects (10 mins)
* Proposal X: (15 mins)
* Discussion Y: (15 mins)
* Weekly updates/check-ins (10 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: how do you like to measure time?
* benny - he/him - in minutes. normally. in measurements of self-exhaustion. in nanoseconds if i have my bracelet with me.
* deniz - he/him met benny through a friend ari--work in arts/film, been here ~6/7 months! mostly here to listen. How I measure time is with my heartbeathe
* juul - he/him - how quickly or slowly other people appear to be speaking
* jenny - she/her - in decisions and revisions, which a minute will unwind (who knows their T. S. Elliott)
** We got accepted by Mobile Citizen!
* eenblam - he/they - reminderbot lets me know when it's thursday
* eve- she - time between ice ages
* robb - he/him - eons
* john-mark - he/they - seconds, because if your meeting is at eight, and your clock says 8:00, you're probably late (better late than never - null)ðŸ‘�)
* Null (remote)- he/him - in pico-sec you have one life to live so live it fully.
* alex - i used to be involved in sudomesh quite a bit--was responsible for some crappy code here and there and stuff like that. a lot of debugging. i measure time in seconds.

=== Meeting Roles ===
* Facilitator/s: benny
* Stacktaker:
* Notetaker/s: jnny, juul,
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste action items below:
CAVEAT: Some of these are SUPER OLD
* ping paxio again, forever @bennlich
* make an 0.3.1 firmware release and add link to walkthrough @bennlich
* create wiki page about EMF Radiation @sierk @tunabananas
** put things here: https://sudoroom.org/wiki/Mesh/EMFradiation
* any reply from LOLSpace? @tunabananas
** last april: wifi has no wifi
* poke ryan about marina @tunabananas
* should we plan to go to cal sailing open house june 16th, sunday, 1--4pm -https://www.cal-sailing.org/activities/csc-open-house
** reply via Ryan from Toeknee: " I spoke to Ryan Alder yesterday. Sounds like they are waiting on the manager approval for Monkey Brain's Proposal. If you want put your pole next to their Flagpole, you'll likely need to peak to the Marina. BTW, Cal Sailing just put up a 30ft pole for our radio antenna which is next to our clubhouse. If you guys want to piggy back on the same pole it should be fine. No need for climbing. Easy access."
** jenny, benny are available june 16th
* e-mail jonah and ask about richmond street light internet @bennlich
** didn't do this
* berkeley light pole mounting research @robb
** didn't do this
* rochdale mount this sunday w/ movie night after?
** didn't do this
* maybe research antenna range calculator--people are always asking about that @bennlich
* schedule HE server install / hike @bennlichm
** w00t @bennlich @null and @mux

=== Node Mounts & Outreach ===

"Tis an ill wind that blows no minds"
â€• Malaclypse the Younger, Principia Discordia

== Weekly updates/check-ins ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste weekly update items below:

== Other Updates & Reportbacks ==
=== Bugs/Technical ===
Recent issues: https://peoplesopen.net/issues. For a list of recent Github activity, see the widget at the bottom of https://peoplesopen.net/learn/development/.
*
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
*

=== Communications & Events ===

Hell is reserved exclusively for them that believe in it.
Further, the lowest Rung in Hell is reserved for them that believe in it on the supposition that they'll go there if they don't. .
-- Principia Discordia

* Jenny: Approved by mobile citizen!!! Woo!!

Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
*

=== Internal Logistics / Finance ===

If you can master nonsense as well as you have already learned to master sense, then each will expose the other for what it is: absurdity.
-- Principia Discordia

Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* Jenny: Sent in our 990EZ (federal) and 199N (State) tax forms last week (nonprofit deadline is May 15). I'd imagined we'd have had to file the full forms, but even with the grants and donations from last year (totaling ~$122K), our average over 3 years was still only $42K since we made virtually no income in 2017 and 2016. Forms were digitally filed here: https://drive.google.com/open?id=1Dx8p0GPu1aq0FExz7kf90AX6xzec0M0o
* Need to coordinate a bank party to a) remove Matt Senate from the account and b) add designated Finance WG people (Mai, Benny, Ben, Null? there may be a limit, will ask) - all signers AND Matt have to be physically present at the bank to do so (or we attempt once more to get our account with Beneficial functional).
** I'll be wherever I need to be to help with this. Thanks -Null
* Moving forward, Reimbursements and payments on invoices will be issued on the Third Friday of the month
* The board also needs to sign a 'Self-Dealing Resolution' whenever we decide to pay an officer or director

=Sundays=
* BYOI Office Hours: Please put your name here: https://ethercalc.org/byoi_office_hours
** eenblam will be here this sunday -- interested in doing work on documentation + educational materials following up discussions at last BYOI
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays

=Discussions & Proposals=
== Proposal ==
* eenblam and others: let's start doing every other Tuesday as hack nights. Want a temperature check here, then Loomio if well-received.
** robb: tyler suggested having increasing seriousness/structure of meetings over the course of the month, then reset.
** jmg - if it doesn't work, nothing prevents us from going back.
* '''Consenso?'''
** yes - proceed to Loomio to gather additional consensus.

== Discussion: Disaster Radio ==
* juul: if anyone is interested in helping out w/ disaster radio, we're going to start working with the Indian team every wednesday at 10:30pm

== Discussion: Visit the mushroom farm ==
* mai: Anyone who's interested in DWeb Camp â€” there'll be a visit to the mushroom farm (where camp will be) on Sat June 8 with Ben of ToMesh to help with some preliminary calculations for the mesh, like radio range tests. Anyone planning on going to Camp wanna go visit to help out and check out the space?
** benny: im interested
*** jnny me three!
** Also eenblam
** I'd like to go null

== Discussion: Quarterly Mesh Report ==
* eenblam: We decided to do this at the last board meeting. Need to determine how we want to go about it.
** Decide on requirements for report
*** Example from Max: https://docs.google.com/document/d/1Hy_bQA7CHTUw_6yKF3VTUv0mHtRMTgJsJkgbK69Br4Y/edit?pli=1
*** These are things that Max would like to see in the report that *are not * easy to find right now. *Not* comprehensive of what would go in report.
*** jmg - have both change/quarter and change/year for node updates so we can see performance relative to time
** Decide on compensation for each report
*** jenny - we should allocate $500/report for someone to dig up all this stuff to ensure responsible reporting.
**** eenblam - or say, $400 for report and $100 to validate and copyedit
** Null 366.30 for report + 133.70 for validate and copy edit - just a suggestion.
* Interested parties: breakout after.

== Discussion: CC Camp ==
* juul - we gotta request those precious, precious tokens
** https://en.m.wikipedia.org/wiki/Chaos_Communication_Camp
** lol -Null

== Discussion: Labs ==
* eenblam - small announcement: I've started working on (currently easy) networking labs you can run on your desktop. Contributions would be awesome!
** https://github.com/eenblam/labs/pull/1
*** awesome!!

== Action Items ==
Copy and paste from previous action items above, delete completed ones, and add new ones:
* recruit a team to go to cal sailing open house june 16th, sunday, 1--4pm -https://www.cal-sailing.org/activities/csc-open-house
* talk to native health center folks @tunabananas
* e-mail jonah and ask about richmond street light internet @bennlich
* berkeley light pole mounting research @mux
* mobile citizen update @tunabananas
* send out self-dealing resolution loomio thread @tunabananas
* fiber internet via sonic or at&t at omni? @jmg @null
* Quarterly reports @eenblam
* Hack nights proposal @eenblam

== Breakout Groups =
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
* Check in about bank party
* Quarterly mesh reports
** https://peoplesopen.net/pad/p/quarterly

== Last Meeting Notes ==
* https://sudoroom.org/wiki/Mesh/14_May_2019

[[Category:Mesh/Minutes]]

Mesh/28 May 2019

2019-05-29T16:33:04Z

Eenblam: Created page with "'''People's Open Network Weekly Meeting - 28 May 2019 7:30pm-9pm''' "Today is Pungenday, the 2nd day of Confusion in the YOLD 3185" * https://omnicommons.org/wiki/Safer_Space_..."

'''People's Open Network Weekly Meeting - 28 May 2019 7:30pm-9pm'''
"Today is Pungenday, the 2nd day of Confusion in the YOLD 3185"
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Check in on ongoing projects (10 mins)
* Proposal X: (15 mins)
* Discussion Y: (15 mins)
* Weekly updates/check-ins (10 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: how do you like to measure time?
* benny - he/him - in minutes. normally. in measurements of self-exhaustion. in nanoseconds if i have my bracelet with me.
* deniz - he/him met benny through a friend ari--work in arts/film, been here ~6/7 months! mostly here to listen. How I measure time is with my heartbeathe
* juul - he/him - how quickly or slowly other people appear to be speaking
* jenny - she/her - in decisions and revisions, which a minute will unwind (who knows their T. S. Elliott)
** We got accepted by Mobile Citizen!
* eenblam - he/they - reminderbot lets me know when it's thursday
* eve- she - time between ice ages
* robb - he/him - eons
* john-mark - he/they - seconds, because if your meeting is at eight, and your clock says 8:00, you're probably late (better late than never - null)ðŸ‘�)
* Null (remote)- he/him - in pico-sec you have one life to live so live it fully.
* alex - i used to be involved in sudomesh quite a bit--was responsible for some crappy code here and there and stuff like that. a lot of debugging. i measure time in seconds.

=== Meeting Roles ===
* Facilitator/s: benny
* Stacktaker:
* Notetaker/s: jnny, juul,
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste action items below:
CAVEAT: Some of these are SUPER OLD
* ping paxio again, forever @bennlich
* make an 0.3.1 firmware release and add link to walkthrough @bennlich
* create wiki page about EMF Radiation @sierk @tunabananas
** put things here: https://sudoroom.org/wiki/Mesh/EMFradiation
* any reply from LOLSpace? @tunabananas
** last april: wifi has no wifi
* poke ryan about marina @tunabananas
* should we plan to go to cal sailing open house june 16th, sunday, 1--4pm -https://www.cal-sailing.org/activities/csc-open-house
** reply via Ryan from Toeknee: " I spoke to Ryan Alder yesterday. Sounds like they are waiting on the manager approval for Monkey Brain's Proposal. If you want put your pole next to their Flagpole, you'll likely need to peak to the Marina. BTW, Cal Sailing just put up a 30ft pole for our radio antenna which is next to our clubhouse. If you guys want to piggy back on the same pole it should be fine. No need for climbing. Easy access."
** jenny, benny are available june 16th
* e-mail jonah and ask about richmond street light internet @bennlich
** didn't do this
* berkeley light pole mounting research @robb
** didn't do this
* rochdale mount this sunday w/ movie night after?
** didn't do this
* maybe research antenna range calculator--people are always asking about that @bennlich
* schedule HE server install / hike @bennlichm
** w00t @bennlich @null and @mux

=== Node Mounts & Outreach ===

"Tis an ill wind that blows no minds"
â€• Malaclypse the Younger, Principia Discordia

== Weekly updates/check-ins ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste weekly update items below:

== Other Updates & Reportbacks ==
=== Bugs/Technical ===
Recent issues: https://peoplesopen.net/issues. For a list of recent Github activity, see the widget at the bottom of https://peoplesopen.net/learn/development/.
*
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
*

=== Communications & Events ===

Hell is reserved exclusively for them that believe in it.
Further, the lowest Rung in Hell is reserved for them that believe in it on the supposition that they'll go there if they don't. .
-- Principia Discordia

* Jenny: Approved by mobile citizen!!! Woo!!

Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
*

=== Internal Logistics / Finance ===

If you can master nonsense as well as you have already learned to master sense, then each will expose the other for what it is: absurdity.
-- Principia Discordia

Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* Jenny: Sent in our 990EZ (federal) and 199N (State) tax forms last week (nonprofit deadline is May 15). I'd imagined we'd have had to file the full forms, but even with the grants and donations from last year (totaling ~$122K), our average over 3 years was still only $42K since we made virtually no income in 2017 and 2016. Forms were digitally filed here: https://drive.google.com/open?id=1Dx8p0GPu1aq0FExz7kf90AX6xzec0M0o
* Need to coordinate a bank party to a) remove Matt Senate from the account and b) add designated Finance WG people (Mai, Benny, Ben, Null? there may be a limit, will ask) - all signers AND Matt have to be physically present at the bank to do so (or we attempt once more to get our account with Beneficial functional).
** I'll be wherever I need to be to help with this. Thanks -Null
* Moving forward, Reimbursements and payments on invoices will be issued on the Third Friday of the month
* The board also needs to sign a 'Self-Dealing Resolution' whenever we decide to pay an officer or director

=Sundays=
* BYOI Office Hours: Please put your name here: https://ethercalc.org/byoi_office_hours
** eenblam will be here this sunday -- interested in doing work on documentation + educational materials following up discussions at last BYOI
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays
* Notes from this past Sunday's session:
**

== Proposal ==
* eenblam and others: let's start doing every other Tuesday as hack nights. Want a temperature check here, then Loomio if well-received.
** robb: tyler suggested having increasing seriousness/structure of meetings over the course of the month, then reset.
** jmg - if it doesn't work, nothing prevents us from going back.
* '''Consenso?'''
** yes - proceed to Loomio to gather additional consensus.

== Discussion: Disaster Radio ==
* juul: if anyone is interested in helping out w/ disaster radio, we're going to start working with the Indian team every wednesday at 10:30pm

== Discussion: Visit the mushroom farm ==
* mai: Anyone who's interested in DWeb Camp â€” there'll be a visit to the mushroom farm (where camp will be) on Sat June 8 with Ben of ToMesh to help with some preliminary calculations for the mesh, like radio range tests. Anyone planning on going to Camp wanna go visit to help out and check out the space?
** benny: im interested
*** jnny me three!
** Also eenblam
** I'd like to go null

== Discussion: Quarterly Mesh Report ==
* eenblam: We decided to do this at the last board meeting. Need to determine how we want to go about it.
** Decide on requirements for report
*** Example from Max: https://docs.google.com/document/d/1Hy_bQA7CHTUw_6yKF3VTUv0mHtRMTgJsJkgbK69Br4Y/edit?pli=1
*** These are things that Max would like to see in the report that *are not * easy to find right now. *Not* comprehensive of what would go in report.
*** jmg - have both change/quarter and change/year for node updates so we can see performance relative to time
** Decide on compensation for each report
*** jenny - we should allocate $500/report for someone to dig up all this stuff to ensure responsible reporting.
**** eenblam - or say, $400 for report and $100 to validate and copyedit
** Null 366.30 for report + 133.70 for validate and copy edit - just a suggestion.
* Interested parties: breakout after.

== Discussion: CC Camp ==
* juul - we gotta request those precious, precious tokens
** https://en.m.wikipedia.org/wiki/Chaos_Communication_Camp
** lol -Null

== Discussion: Labs ==
* eenblam - small announcement: I've started working on (currently easy) networking labs you can run on your desktop. Contributions would be awesome!
** https://github.com/eenblam/labs/pull/1
*** awesome!!

== Action Items ==
Copy and paste from previous action items above, delete completed ones, and add new ones:
* recruit a team to go to cal sailing open house june 16th, sunday, 1--4pm -https://www.cal-sailing.org/activities/csc-open-house
* talk to native health center folks @tunabananas
* e-mail jonah and ask about richmond street light internet @bennlich
* berkeley light pole mounting research @mux
* mobile citizen update @tunabananas
* send out self-dealing resolution loomio thread @tunabananas
* fiber internet via sonic or at&t at omni? @jmg @null
* Quarterly reports @eenblam
* Hack nights proposal @eenblam

== Breakout Groups =
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
* Check in about bank party
* Quarterly mesh reports
** https://peoplesopen.net/pad/p/quarterly

== Last Meeting Notes ==
* https://sudoroom.org/wiki/Mesh/14_May_2019

[[Category:Mesh/Minutes]]

Mesh/Minutes

2019-05-29T16:30:40Z

Eenblam: Add 5/21 and 5/28

<center>'''Sudo Mesh Meeting Minutes'''</center>

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes

|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/28_May_2019|2019-05-28]]
| Weekly organizing meeting
|-
| 2019-05-21
| Hack night; no notes
|-
| [[Mesh/14_May_2019|2019-05-14]]
| Weekly organizing meeting
|-
| [[Mesh/30_April_2019|2019-04-30]]
| Weekly organizing meeting
|-
| [[Mesh/23_April_2019|2019-04-23]]
| Annual board meeting
|-
| [[Mesh/16_April_2019|2019-04-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_April_2019|2019-04-09]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2019|2019-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/19_March_2019|2019-03-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_March_2019|2019-03-12]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2019|2019-02-26]]
| Weekly organizing meeting
|-
| [[Mesh/19_February_2019|2019-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_February_2019|2019-02-12]]
| Weekly organizing meeting
|-
| [[Mesh/29_January_2019|2019-01-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_January_2019|2019-01-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_January_2019|2019-01-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_January_2019|2019-01-08]]
| Weekly organizing meeting
|-
| [[Mesh/18_December_2018|2018-12-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_December_2018|2018-12-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_December_2018|2018-12-04]]
| Weekly organizing meeting
|-
| [[Mesh/27_November_2018|2018-11-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_November_2018|2018-11-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_November_2018|2018-11-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_November_2018|2018-11-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_October_2018|2018-10-30]]
| Weekly organizing meeting
|-
| [[Mesh/23_October_2018|2018-10-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_October_2018|2018-10-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_October_2018|2018-10-09]]
| Weekly organizing meeting
|-
| [[Mesh/2_October_2018|2018-10-2]]
| Weekly organizing meeting
|-
| [[Mesh/25_September_2018|2018-09-25]]
| Weekly organizing meeting
|-
| [[Mesh/18_September_2018|2018-09-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_September_2018|2018-09-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_September_2018|2018-09-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_August_2018|2018-08-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_August_2018|2018-08-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_August_2018|2018-08-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_August_2018|2018-08-07]]
| Weekly organizing meeting
|-
| [[Mesh/24_July_2018|2018-07-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_July_2018|2018-07-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_July_2018|2018-07-10]]
| Weekly organizing meeting
|-
| [[Mesh/3_July_2018|2018-07-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_June_2018|2018-06-26]]
| Weekly organizing meeting
|-
| [[Mesh/12_June_2018|2018-06-12]]
| Weekly organizing meeting
|-
| [[Mesh/5_June_2018|2018-06-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_May_2018|2018-05-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_May_2018|2018-05-22]]
| Annual Board Meeting
|-
| [[Mesh/15_May_2018|2018-05-15]]
| Weekly organizing meeting & Firmware meeting
|-
| [[Mesh/8_May_2018|2018-05-08]]
| Weekly organizing meeting
|-
| [[Mesh/1_May_2018|2018-05-01]]
| Weekly organizing meeting
|-
| [[Mesh/24_Apr_2018|2018-04-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_Apr_2018|2018-04-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Apr_2018|2018-04-10]]
| Strategic plan meeting
|-
| [[Mesh/03_Apr_2018|2018-04-03]]
| Weekly organizing meeting
|-
| [[Mesh/27_Mar_2018|2018-03-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Mar_2018|2018-03-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_Mar_2018|2018-03-13]]
| Weekly organizing meeting
|-
| [[Mesh/6_Mar_2018|2018-03-06]]
| Weekly organizing meeting
|-
| [[Mesh/27_Feb_2018|2018-02-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Feb_2018|2018-02-20]]
| Weekly organizing meeting
|-
| [[Mesh/17_Feb_2018|2018-02-17]]
| Strategic plan meeting
|-
| [[Mesh/13_Feb_2018|2018-02-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_Feb_2018|2018-02-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_Jan_2018|2018-01-30]]
| Monthly general meeting
|-
| [[Mesh/23_Jan_2018|2018-01-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_Jan_2018|2018-01-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_Jan_2018|2018-01-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_Jan_2018|2018-01-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_Dec_2017|2017-12-26]]
| Monthly general meeting
|-
| [[Mesh/19_Dec_2017|2017-12-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Dec_2017|2017-12-12]]
| Weekly organizing meeting
|-
| [[Mesh/05_Dec_2017|2017-12-05]]
| Weekly organizing meeting
|-
| [[Mesh/28_Nov_2017|2017-11-28]]
| Monthly general meeting
|-
| [[Mesh/21_Nov_2017|2017-11-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_Nov_2017|2017-11-14]]
| Weekly organizing meeting
|-
| [[Mesh/24_Oct_2017|2017-10-24]]
| Monthly general meeting
|-
| [[Mesh/17_Oct_2017|2017-10-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Oct_2017|2017-10-10]]
| Weekly organizing meeting
|-
| [[Mesh/03_Oct_2017|2017-10-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_Sep_2017|2017-09-26]]
| Monthly general meeting
|-
| [[Mesh/19_Sep_2017|2017-09-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Sep_2017|2017-09-12]]
| Weekly organizing meeting
|-
| [[Mesh/11_Sep_2017|2017-09-11]]
| Website redesign session
|-
| [[Mesh/05_Sep_2017|2017-09-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_Aug_2017|2017-08-29]]
| Monthly general meeting
|-
| [[Mesh/22_Aug_2017|2017-08-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_Aug_2017|2017-08-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_Aug_2017|2017-08-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_Aug_2017|2017-08-01]]
| Weekly organizing meeting
|-
| [[Mesh/18_July_2017|2017-07-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_July_2017|2017-07-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_July_2017|2017-07-4]]
| Weekly organizing meeting
|-
| [[Mesh/20_June_2017|2017-06-20]]
| Monthly general meeting
|-
| [[Mesh/13_June_2017|2017-06-13]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2017|2017-06-11]]
| Temescal street fair report-back
|-
| [[Mesh/6_June_2017|2017-06-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_May_2017|2017-05-30]]
| Monthly general meeting
|-
| [[Mesh/16_May_2017|2017-05-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_May_2017|2017-05-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_May_2017|2017-05-02]]
| Weekly organizing meeting
|-
| [[Mesh/25_April_2017|2017-04-25]]
| Monthly general meeting
|-
| [[Mesh/18_April_2017|2017-04-18]]
| Weekly organizing meeting
|-
| [[Mesh/17_April_2017|2017-04-17]]
| Annual sudo mesh board meeting
|-
| [[Mesh/11_April_2017|2017-04-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_April_2017|2017-04-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_March_2017|2017-03-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_March_2017|2017-03-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_March_2017|2017-03-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_March_2017|2017-03-07]]
| Weekly organizing meeting
|-
| [[Mesh/28_February_2017|2017-02-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_February_2017|2017-02-21]]
| Weekly organizing meeting
|-
| [[Mesh/10_February_2017|2017-02-10]]
| Weekly organizing meeting
|-
| [[Mesh/07_February_2017|2017-02-07]]
| Organizing "Build Your Own Internet" Workshop
|-
| [[Mesh/05_July_2016|2016-07-05]]
| Videochat meeting with nycmesh
|-
| [[Mesh/22_June_2016|2016-06-22]]
| Weekly organizing meeting
|-
| [[Mesh/07_June_2016|2016-06-07]]
| Weekly organizing meeting
|-
| [[Mesh/23_February_2016|2016-02-23]]
| Monthly general meeting
|-
| [[Mesh/09_February_2016|2016-02-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_February_2016|2016-02-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_January_2016|2016-01-26]]
| Monthly general meeting
|-
| [[Mesh/27_October_2015|2015-10-27]]
| Monthly general meeting
|-
| [[Mesh/06_October_2015|2015-10-06]]
| Weekly organizing meeting
|-
| [[Mesh/29_September_2015|2015-09-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_September_2015|2015-09-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_September_2015|2015-09-15]]
| Second annual board meeting
|-
| [[Mesh/08_September_2015|2015-09-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_September_2015|2015-09-01]]
| Monthly general meeting
|-
| [[Mesh/07_April_2015|2015-04-07]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2015|2015-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/17_March_2015|2015-03-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_March_2015|2015-03-10]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2015|2015-02-26]]
| Big general meeting
|-
| [[Mesh/24_February_2015|2015-02-24]]
| Hacknight
|-
| [[Mesh/19_February_2015|2015-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/05_February_2015|2015-02-05]]
| Weekly organizing meeting
|-
| [[Mesh/03_February_2015|2015-02-04]]
| Hacknight
|-
| [[Mesh/29_January_2015|2015-01-29]]
| Big general meeting
|-
| [[Mesh/24_January_2015|2015-01-24]]
| Mesh mini-retreat
|-
| [[Mesh/22_January_2015|2015-01-22]]
| Weekly general meeting
|-
| [[Mesh/15_January_2015|2015-01-15]]
| Weekly general meeting
|-
| [[Mesh/30_December_2014|2014-12-30]]
| Big general meeting
|-
| [[Mesh/18_December_2014|2014-12-18]]
| Weekly general meeting
|-
| [[Mesh/13_November_2014|2014-11-13]]
| Weekly general meeting
|-
| [[Mesh/21_October_2014|2014-10-21]]
| Hacknight
|-
| [[Mesh/16_October_2014|2014-10-16]]
| Weekly general meeting
|-
| [[Mesh/09_October_2014|2014-10-09]]
| Weekly general meeting
|-
| [[Mesh/02_October_2014|2014-10-02]]
| Weekly general meeting
|-
| [[Mesh/25_September_2014|2014-09-25]]
| Big general meeting
|-
| [[Mesh/28_August_2014|2014-08-28]]
| Big general meeting
|-
| [[Mesh/21_August_2014|2014-08-21]]
|
|-
| [[Mesh/07_August_2014|2014-08-07]]
|
|-
| [[Mesh/31_July_2014|2014-07-31]]
| Big general meeting
|-
| [[Mesh/17_July_2014|2014-07-17]]
|
|-
| [[Mesh/15_July_2014|2014-07-15]]
|
|-
| [[Mesh/10_July_2014|2014-07-10]]
|
|-
| [[Mesh/06_July_2014|2014-07-06]]
| Hackathon Day 2!
|-
| [[Mesh/05_July_2014|2014-07-05]]
| Hackathon Day 1!
|-
| [[Mesh/03_July_2014|2014-07-03]]
|
|-
| [[Mesh/12_June_2014|2014-06-12]]
|
|-
| [[Mesh/05_June_2014|2014-06-05]]
|
|-
|-
| [[Mesh/29_May_2014|2014-05-29]]
| General meeting
|-
| [[Mesh/27_May_2014|2014-05-27]]
|
|-
| [[Mesh/20_May_2014|2014-05-20]]
|
|-
| [[Mesh/13_May_2014|2014-05-13]]
| First Tuesday meeting ^.^
|-
| [[Mesh/08_May_2014|2014-05-08]]
|
|-
| [[Mesh/01_May_2014|2014-05-01]]
|
|-
| [[Mesh/24_April_2014|2014-04-24]]
| General meeting!
|-
| [[Mesh/17_April_2014|2014-04-17]]
|
|-
| [[Mesh/03_April_2014|2014-04-03]]
|
|-
| [[Mesh/27_March_2014|2014-03-27]]
|
|-
| [[Mesh/20_March_2014|2014-03-20]]
|
|-
| [[Mesh/13_March_2014|2014-03-13]]
|
|-
| [[Mesh/27_February_2014|2014-02-27]]
|
|-
| [[Mesh/20_February_2014|2014-02-20]]
|
|-
| [[Mesh/13_February_2014|2014-02-13]]
|
|-
| [[Mesh/6_February_2014|2014-02-06]]
|
|-
| [[Mesh/30_January_2014|2014-01-30]]
|
|-
| [[Mesh/23_January_2014|2014-01-23]]
|
|-
| [[Mesh/16_January_2014|2014-01-16]]
|
|-
| 31 December - 09 January
| Holidaze Break
|-
| [[Mesh/26_December_2013|2013-12-26]]
|
|-
| [[Mesh/19_December_2013|2013-12-19]]
|
|-
| [[Mesh/12_December_2013|2013-12-12]]
|
|-
| [[Mesh/5_December_2013|2013-12-05]]
|
|-
| [[Mesh/21_November_2013|2013-11-21]]
|
|-
| [[Mesh/14_November_2013|2013-11-14]]
|
|-
| [[Mesh/07_November_2013|2013-11-07]]
|
|-
| [[Mesh/31_October_2013|2013-10-31]]
|
|-
| [[Mesh/24_October_2013|2013-10-24]]
|
|-
| [[Mesh/17_October_2013|2013-10-17]]
|
|-
| [[Mesh/10_October_2013|2013-10-10]]
|
|-
| [[Mesh/26_September_2013|2013-09-26]]
|
|-
| [[Mesh/18_September_2013|2013-09-18]]
|
|-
| [[Mesh/11_September_2013|2013-09-11]]
|
|-
| [[Mesh/4_September_2013|2013-09-04]]
|
|-
| [[Mesh/28_August_2013|2013-08-28]]
|
|-
| 07 August - 21 August
| Hack nights!
|-
| [[Mesh/31_July_2013|2013-07-31]]
|
|-
| [[Mesh/25_July_2013|2013-07-25]]
|
|-
| 18 July 2013
| Hack night: Flashing, firmware
|-
| [[Mesh/11_July_2013|2013-07-11]]
|
|-
| [[Mesh/04_July_2013|2013-07-04]]
|
|-
| [[Mesh/27_June_2013|2013-06-27]]
|
|-
| [[Mesh/20_June_2013|2013-06-20]]
|
|-
| [[Mesh/13_June_2013|2013-06-13]]
|
|-
| 30 May - 05 June
| Hack nights! Trying out some of the nicer Ubiquiti equipment we procured
|-
| [[Mesh/23_May_2013|2013-05-23]]
|
|-
| [[Mesh/09_May_2013|2013-05-09]]
|
|-
| 25 April - 02 May
| Hack nights! See wiki for documentation - principally going through donated routers, flashing them with OpenWRT and installing batman-adv.
|-
| [[Mesh/18_April_2013|2013-04-18]]
|
|-
| [[Mesh/11_April_2013|2013-04-11]]
|
|-
| 28 March - 04 April
| SPRING SHIFT HIATUS
|-
| [[Mesh/21_March_2013|2013-03-21]]
|
|-
| [[Mesh/07_March_2013|2013-03-07]]
|
|-
| [[Mesh/28_February_2013|2013-02-28]]
|
|-
| [[Mesh/21_February_2013|2013-02-21]]
|
|-
| [[Mesh/14_February_2013|2013-02-14]]
|
|-
| [[Mesh/7_February_2013|2013-02-07]]
|
|-
| [http://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html 2013-01-31]
|
|}

Mesh/Reminderbot

2019-05-29T02:56:42Z

Eenblam: Link to github

Reminderbot pops into peoplesopen.net/chat to remind us of the action items we decided on at the previous meeting!

Reminderbot is [https://github.com/sudomesh/reminderbot on GitHub].

==Troubleshooting==

# Did you move the minutes from [https://peoplesopen.net/notes the pad] to their own page? The minutes actually contain instructions for how to do this.
# Did you create a link to the new page on [[Mesh/Minutes]]?
# Did you put the link at the top and use the same format as the rest of the table?
# Did Reminderbot pop in and report an error? If so, ping eenblam on Signal.

Mesh/Mesh Meeting Notes Template

2019-03-27T04:17:26Z

Eenblam: Fix Action Item section label; breaks reminderbot

'''People's Open Network Weekly Meeting - Day Month 2019 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Check in on ongoing projects (10 mins)
* Proposal X: (15 mins)
* Discussion Y: (15 mins)
* Weekly updates/check-ins (10 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question:
*

=== Meeting Roles ===
* Facilitator/s:
* Stacktaker:
* Notetaker/s:
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste action items below:

== Weekly updates/check-ins ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and paste weekly update items below:

== Other Updates & Reportbacks ==
=== Bugs/Technical ===
Recent issues: https://peoplesopen.net/issues. For a list of recent Github activity, see the widget at the bottom of https://peoplesopen.net/learn/development/.
*

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
*

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
*

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
*

== Next Sunday ==
We host office hours every Sunday from 1-3pm in Sudo Room to talk to people, work on sudomesh projects, and schedule node mounts.
* To sign up to bottomline, fill in your name here: https://ethercalc.org/byoi_office_hours
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays
* Notes from this past Sunday's session:
**

== Example Proposal ==
* Lumbragolonga: I propose that for one week we communicate exclusively via paper airplane. Here's why...
* '''Consenso?'''

== Example Discussion Item ==
* Gormavax: I wanna chat about the recent influx of spotted pigeon-dactyls in the Martian exosphere...

== Action Items ==
Copy and paste from previous action items above, delete completed ones, and add new ones:
*

== Breakout Groups ==
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
*

== Last Meeting Notes ==
* link to previous meeting minutes
* CHANGE ME AFTER PASTING: https://sudoroom.org/wiki/Mesh/10_December_1815

== End of Meeting ==
* please archive these meeting notes by copying the entire pad contents onto the sudomesh wiki with the correct date format: https://sudoroom.org/wiki/Mesh/DD_MONTH_YYYY
* 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_Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wiki/Mesh/Minutes

[[Category:Mesh/Minutes]]

Mesh/Minutes

2019-03-20T04:14:08Z

Eenblam: Add March 19, 2019

<center>'''Sudo Mesh Meeting Minutes'''</center>

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes

|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/19_March_2019|2019-03-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_March_2019|2019-03-12]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2019|2019-02-26]]
| Weekly organizing meeting
|-
| [[Mesh/19_February_2019|2019-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_February_2019|2019-02-12]]
| Weekly organizing meeting
|-
| [[Mesh/29_January_2019|2019-01-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_January_2019|2019-01-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_January_2019|2019-01-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_January_2019|2019-01-08]]
| Weekly organizing meeting
|-
| [[Mesh/18_December_2018|2018-12-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_December_2018|2018-12-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_December_2018|2018-12-04]]
| Weekly organizing meeting
|-
| [[Mesh/27_November_2018|2018-11-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_November_2018|2018-11-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_November_2018|2018-11-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_November_2018|2018-11-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_October_2018|2018-10-30]]
| Weekly organizing meeting
|-
| [[Mesh/23_October_2018|2018-10-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_October_2018|2018-10-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_October_2018|2018-10-09]]
| Weekly organizing meeting
|-
| [[Mesh/2_October_2018|2018-10-2]]
| Weekly organizing meeting
|-
| [[Mesh/25_September_2018|2018-09-25]]
| Weekly organizing meeting
|-
| [[Mesh/18_September_2018|2018-09-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_September_2018|2018-09-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_September_2018|2018-09-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_August_2018|2018-08-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_August_2018|2018-08-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_August_2018|2018-08-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_August_2018|2018-08-07]]
| Weekly organizing meeting
|-
| [[Mesh/24_July_2018|2018-07-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_July_2018|2018-07-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_July_2018|2018-07-10]]
| Weekly organizing meeting
|-
| [[Mesh/3_July_2018|2018-07-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_June_2018|2018-06-26]]
| Weekly organizing meeting
|-
| [[Mesh/12_June_2018|2018-06-12]]
| Weekly organizing meeting
|-
| [[Mesh/5_June_2018|2018-06-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_May_2018|2018-05-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_May_2018|2018-05-22]]
| Annual Board Meeting
|-
| [[Mesh/15_May_2018|2018-05-15]]
| Weekly organizing meeting & Firmware meeting
|-
| [[Mesh/8_May_2018|2018-05-08]]
| Weekly organizing meeting
|-
| [[Mesh/1_May_2018|2018-05-01]]
| Weekly organizing meeting
|-
| [[Mesh/24_Apr_2018|2018-04-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_Apr_2018|2018-04-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Apr_2018|2018-04-10]]
| Strategic plan meeting
|-
| [[Mesh/03_Apr_2018|2018-04-03]]
| Weekly organizing meeting
|-
| [[Mesh/27_Mar_2018|2018-03-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Mar_2018|2018-03-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_Mar_2018|2018-03-13]]
| Weekly organizing meeting
|-
| [[Mesh/6_Mar_2018|2018-03-06]]
| Weekly organizing meeting
|-
| [[Mesh/27_Feb_2018|2018-02-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Feb_2018|2018-02-20]]
| Weekly organizing meeting
|-
| [[Mesh/17_Feb_2018|2018-02-17]]
| Strategic plan meeting
|-
| [[Mesh/13_Feb_2018|2018-02-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_Feb_2018|2018-02-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_Jan_2018|2018-01-30]]
| Monthly general meeting
|-
| [[Mesh/23_Jan_2018|2018-01-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_Jan_2018|2018-01-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_Jan_2018|2018-01-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_Jan_2018|2018-01-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_Dec_2017|2017-12-26]]
| Monthly general meeting
|-
| [[Mesh/19_Dec_2017|2017-12-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Dec_2017|2017-12-12]]
| Weekly organizing meeting
|-
| [[Mesh/05_Dec_2017|2017-12-05]]
| Weekly organizing meeting
|-
| [[Mesh/28_Nov_2017|2017-11-28]]
| Monthly general meeting
|-
| [[Mesh/21_Nov_2017|2017-11-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_Nov_2017|2017-11-14]]
| Weekly organizing meeting
|-
| [[Mesh/24_Oct_2017|2017-10-24]]
| Monthly general meeting
|-
| [[Mesh/17_Oct_2017|2017-10-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Oct_2017|2017-10-10]]
| Weekly organizing meeting
|-
| [[Mesh/03_Oct_2017|2017-10-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_Sep_2017|2017-09-26]]
| Monthly general meeting
|-
| [[Mesh/19_Sep_2017|2017-09-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Sep_2017|2017-09-12]]
| Weekly organizing meeting
|-
| [[Mesh/11_Sep_2017|2017-09-11]]
| Website redesign session
|-
| [[Mesh/05_Sep_2017|2017-09-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_Aug_2017|2017-08-29]]
| Monthly general meeting
|-
| [[Mesh/22_Aug_2017|2017-08-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_Aug_2017|2017-08-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_Aug_2017|2017-08-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_Aug_2017|2017-08-01]]
| Weekly organizing meeting
|-
| [[Mesh/18_July_2017|2017-07-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_July_2017|2017-07-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_July_2017|2017-07-4]]
| Weekly organizing meeting
|-
| [[Mesh/20_June_2017|2017-06-20]]
| Monthly general meeting
|-
| [[Mesh/13_June_2017|2017-06-13]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2017|2017-06-11]]
| Temescal street fair report-back
|-
| [[Mesh/6_June_2017|2017-06-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_May_2017|2017-05-30]]
| Monthly general meeting
|-
| [[Mesh/16_May_2017|2017-05-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_May_2017|2017-05-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_May_2017|2017-05-02]]
| Weekly organizing meeting
|-
| [[Mesh/25_April_2017|2017-04-25]]
| Monthly general meeting
|-
| [[Mesh/18_April_2017|2017-04-18]]
| Weekly organizing meeting
|-
| [[Mesh/17_April_2017|2017-04-17]]
| Annual sudo mesh board meeting
|-
| [[Mesh/11_April_2017|2017-04-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_April_2017|2017-04-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_March_2017|2017-03-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_March_2017|2017-03-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_March_2017|2017-03-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_March_2017|2017-03-07]]
| Weekly organizing meeting
|-
| [[Mesh/28_February_2017|2017-02-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_February_2017|2017-02-21]]
| Weekly organizing meeting
|-
| [[Mesh/10_February_2017|2017-02-10]]
| Weekly organizing meeting
|-
| [[Mesh/07_February_2017|2017-02-07]]
| Organizing "Build Your Own Internet" Workshop
|-
| [[Mesh/05_July_2016|2016-07-05]]
| Videochat meeting with nycmesh
|-
| [[Mesh/22_June_2016|2016-06-22]]
| Weekly organizing meeting
|-
| [[Mesh/07_June_2016|2016-06-07]]
| Weekly organizing meeting
|-
| [[Mesh/23_February_2016|2016-02-23]]
| Monthly general meeting
|-
| [[Mesh/09_February_2016|2016-02-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_February_2016|2016-02-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_January_2016|2016-01-26]]
| Monthly general meeting
|-
| [[Mesh/27_October_2015|2015-10-27]]
| Monthly general meeting
|-
| [[Mesh/06_October_2015|2015-10-06]]
| Weekly organizing meeting
|-
| [[Mesh/29_September_2015|2015-09-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_September_2015|2015-09-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_September_2015|2015-09-15]]
| Second annual board meeting
|-
| [[Mesh/08_September_2015|2015-09-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_September_2015|2015-09-01]]
| Monthly general meeting
|-
| [[Mesh/07_April_2015|2015-04-07]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2015|2015-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/17_March_2015|2015-03-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_March_2015|2015-03-10]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2015|2015-02-26]]
| Big general meeting
|-
| [[Mesh/24_February_2015|2015-02-24]]
| Hacknight
|-
| [[Mesh/19_February_2015|2015-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/05_February_2015|2015-02-05]]
| Weekly organizing meeting
|-
| [[Mesh/03_February_2015|2015-02-04]]
| Hacknight
|-
| [[Mesh/29_January_2015|2015-01-29]]
| Big general meeting
|-
| [[Mesh/24_January_2015|2015-01-24]]
| Mesh mini-retreat
|-
| [[Mesh/22_January_2015|2015-01-22]]
| Weekly general meeting
|-
| [[Mesh/15_January_2015|2015-01-15]]
| Weekly general meeting
|-
| [[Mesh/30_December_2014|2014-12-30]]
| Big general meeting
|-
| [[Mesh/18_December_2014|2014-12-18]]
| Weekly general meeting
|-
| [[Mesh/13_November_2014|2014-11-13]]
| Weekly general meeting
|-
| [[Mesh/21_October_2014|2014-10-21]]
| Hacknight
|-
| [[Mesh/16_October_2014|2014-10-16]]
| Weekly general meeting
|-
| [[Mesh/09_October_2014|2014-10-09]]
| Weekly general meeting
|-
| [[Mesh/02_October_2014|2014-10-02]]
| Weekly general meeting
|-
| [[Mesh/25_September_2014|2014-09-25]]
| Big general meeting
|-
| [[Mesh/28_August_2014|2014-08-28]]
| Big general meeting
|-
| [[Mesh/21_August_2014|2014-08-21]]
|
|-
| [[Mesh/07_August_2014|2014-08-07]]
|
|-
| [[Mesh/31_July_2014|2014-07-31]]
| Big general meeting
|-
| [[Mesh/17_July_2014|2014-07-17]]
|
|-
| [[Mesh/15_July_2014|2014-07-15]]
|
|-
| [[Mesh/10_July_2014|2014-07-10]]
|
|-
| [[Mesh/06_July_2014|2014-07-06]]
| Hackathon Day 2!
|-
| [[Mesh/05_July_2014|2014-07-05]]
| Hackathon Day 1!
|-
| [[Mesh/03_July_2014|2014-07-03]]
|
|-
| [[Mesh/12_June_2014|2014-06-12]]
|
|-
| [[Mesh/05_June_2014|2014-06-05]]
|
|-
|-
| [[Mesh/29_May_2014|2014-05-29]]
| General meeting
|-
| [[Mesh/27_May_2014|2014-05-27]]
|
|-
| [[Mesh/20_May_2014|2014-05-20]]
|
|-
| [[Mesh/13_May_2014|2014-05-13]]
| First Tuesday meeting ^.^
|-
| [[Mesh/08_May_2014|2014-05-08]]
|
|-
| [[Mesh/01_May_2014|2014-05-01]]
|
|-
| [[Mesh/24_April_2014|2014-04-24]]
| General meeting!
|-
| [[Mesh/17_April_2014|2014-04-17]]
|
|-
| [[Mesh/03_April_2014|2014-04-03]]
|
|-
| [[Mesh/27_March_2014|2014-03-27]]
|
|-
| [[Mesh/20_March_2014|2014-03-20]]
|
|-
| [[Mesh/13_March_2014|2014-03-13]]
|
|-
| [[Mesh/27_February_2014|2014-02-27]]
|
|-
| [[Mesh/20_February_2014|2014-02-20]]
|
|-
| [[Mesh/13_February_2014|2014-02-13]]
|
|-
| [[Mesh/6_February_2014|2014-02-06]]
|
|-
| [[Mesh/30_January_2014|2014-01-30]]
|
|-
| [[Mesh/23_January_2014|2014-01-23]]
|
|-
| [[Mesh/16_January_2014|2014-01-16]]
|
|-
| 31 December - 09 January
| Holidaze Break
|-
| [[Mesh/26_December_2013|2013-12-26]]
|
|-
| [[Mesh/19_December_2013|2013-12-19]]
|
|-
| [[Mesh/12_December_2013|2013-12-12]]
|
|-
| [[Mesh/5_December_2013|2013-12-05]]
|
|-
| [[Mesh/21_November_2013|2013-11-21]]
|
|-
| [[Mesh/14_November_2013|2013-11-14]]
|
|-
| [[Mesh/07_November_2013|2013-11-07]]
|
|-
| [[Mesh/31_October_2013|2013-10-31]]
|
|-
| [[Mesh/24_October_2013|2013-10-24]]
|
|-
| [[Mesh/17_October_2013|2013-10-17]]
|
|-
| [[Mesh/10_October_2013|2013-10-10]]
|
|-
| [[Mesh/26_September_2013|2013-09-26]]
|
|-
| [[Mesh/18_September_2013|2013-09-18]]
|
|-
| [[Mesh/11_September_2013|2013-09-11]]
|
|-
| [[Mesh/4_September_2013|2013-09-04]]
|
|-
| [[Mesh/28_August_2013|2013-08-28]]
|
|-
| 07 August - 21 August
| Hack nights!
|-
| [[Mesh/31_July_2013|2013-07-31]]
|
|-
| [[Mesh/25_July_2013|2013-07-25]]
|
|-
| 18 July 2013
| Hack night: Flashing, firmware
|-
| [[Mesh/11_July_2013|2013-07-11]]
|
|-
| [[Mesh/04_July_2013|2013-07-04]]
|
|-
| [[Mesh/27_June_2013|2013-06-27]]
|
|-
| [[Mesh/20_June_2013|2013-06-20]]
|
|-
| [[Mesh/13_June_2013|2013-06-13]]
|
|-
| 30 May - 05 June
| Hack nights! Trying out some of the nicer Ubiquiti equipment we procured
|-
| [[Mesh/23_May_2013|2013-05-23]]
|
|-
| [[Mesh/09_May_2013|2013-05-09]]
|
|-
| 25 April - 02 May
| Hack nights! See wiki for documentation - principally going through donated routers, flashing them with OpenWRT and installing batman-adv.
|-
| [[Mesh/18_April_2013|2013-04-18]]
|
|-
| [[Mesh/11_April_2013|2013-04-11]]
|
|-
| 28 March - 04 April
| SPRING SHIFT HIATUS
|-
| [[Mesh/21_March_2013|2013-03-21]]
|
|-
| [[Mesh/07_March_2013|2013-03-07]]
|
|-
| [[Mesh/28_February_2013|2013-02-28]]
|
|-
| [[Mesh/21_February_2013|2013-02-21]]
|
|-
| [[Mesh/14_February_2013|2013-02-14]]
|
|-
| [[Mesh/7_February_2013|2013-02-07]]
|
|-
| [http://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html 2013-01-31]
|
|}

Mesh/19 March 2019

2019-03-20T04:12:57Z

Eenblam: copypasta

'''People's Open Network Weekly Meeting - 19 March 2019 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)

* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Proposal: Neighbor Outreach Pamphlet (15 mins)
* Discussion Y: (15 mins)
* Discussion Z (15 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question:
* Eve - she
* juul he/him
* doyouhaveamirror - them
* seth - he/they
* mai - she/they
* remote-and-late-benny - he/him

=== Meeting Roles ===
* Facilitator/s: Ben
* Stacktaker:
* Notetaker/s: Juul
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and past action items below:
* poke ryan about marina @tunabananas
* handshake tokens @juul
** Tried claiming them today, ran up against issues with our network
** Can try an easier way (email) that seems less secure for them but fine for us...
* ping david and niki re: sunday @tunabananas
* ping golden gate paxio link @bennlich
** didn't do it
* create wiki page about EMF radiation @sierk @tunabananas
** juul - this would've been handy to have at the people's park meeting. Someone brought it up, another person backed them up and they have a committee to explore it now
* any reply from LOLSpace? @tunabananas
* document battery-powered node in a waterproof bag @juul
** Mostly complete; didn't document the bag. Hoping they come by with the gear, since they don't have a charger yet.
* e-mail other community wifi groups about rooftop insurance
** What this a @bennlich thing?
** yes

== 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-mesh-github-repos
* eenblam: working with benny remotely on friday we ran into an issue where the server will boot a connection off (l2tp) every so often. I was receiving routes with babel but I couldn't send anything over the tunnel interface (and that's why the tunnel would fail). benny has seen this in a few other places. there's a client issue to investigate.
** juul: sounds like a routing issue.
** benny: the client successfully establishes a tunnel, and the broker publishes routes to the client, but the broker doesn't hear anything from the client for two minutes, so it sends a teardown message. this repeats forever. restarting the node a couple of times fixed it, which seems to be a fix that has worked in the past. so it seems like somehow the client node is able to get to a bad state where it can't route packets to the exitnode. There is some relevant conversation here: https://github.com/sudomesh/sudowrt-firmware/issues/148#issuecomment-424934986

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* seth: I created another(3.0) generic outreach email template that I would like to send to folx that contacted us about hosting a node. Let me know if you have any concerns about it. Also I'm want to email a dozen folx, move their trello card from 'To schedule' to 'In Contact With', and add a contact label. Lastly, What email can i use to receive replies??
* seth: I'd be down to fix the node at Hearth (Jake)
** eenblam: We might need to replace both nodes (antenna and router)
*** seth: cool I think I'll do it this weekend.

People's park proposed node

Side view of metal structure:

|> <-- node
|
| < -- mast
|
|
------- <-- base

Top view of metal structure:

|
---|--- <-- base
|

Side view with box:

|>
|
|
|
|-------|
|-------|

Box enlarged view:

|| <- pole
||
|------------------------------|
|_________________| <- soil
| | <- cement
|------------------------------|

* juul: Above is the proposal to mount the Calyx node at People's Park in a way that ensures that it won't get stolen
** What are the legal repercussions of installing a pole w/ gear on it at the park?

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
*

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms

== Next Sunday ==
We host office hours every Sunday from 1-3pm in Sudo Room, and often arrange a rooftop node mount.
* To sign up to bottomline, fill in your name here: https://ethercalc.org/byoi_office_hours
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays
* Notes from this past Sunday's session:

== Proposal: Neighbor Outreach Pamphlet ==
* Title - Neighbor Outreach Pamphlet
* Collaborators - Who is responsible for completing the work?
** Mai
* Scope - What problem is this solving? What is the tangible solution being implemented?
** The best way for the mesh to grow is to decentralize the outreach of the mesh, and empower people with nodes to grow the network in their own neighborhoods. To encourage people to do this, we need a pamphlet/flier that we can distribute to new node owners to give to their neighbors. We would have this available online but also format it for print so that we can have physical copies to leave with people when we do a node mount.
** The pamphlet would include
*** Introduction: What is SudoMesh/People's Open Net
*** What is a mesh network?
*** A brief FAQ to address concerns re: RF and security of the networks
**** Benny: I think a picture would be good for explaining RF. I poked around a bit and the simplest thing I found was the chart on the bottom of this page: https://www.hawaiianelectric.com/clean-energy-hawaii/grid-modernization-technologies/safety-of-advanced-meters
*** Contact information
*** Anything else?
* Timeline - How long will it take? (Start date, end date, and any other milestones.)
** It should take about 6 hours altogether, including drafting the text, gathering edits/comments, then designing it.
* Budget - What are the material and labor costs? Line item budget should include material and labor costs as well as any additional sources of income/funding. Require invoicing and timekeeping for hours worked. Use a template.
** Material costs would only be for printing. If we have access to a printer at Omni then this would not be a cost (?)
** Labor costs would be 5 hours x $30 = $150
* Risks - Are there any potential blockers on progress? (E.g. is research required?)
** Disagreement among people about what is critical information to include in the pamphlet.
** Benny: I think whoever is doing the work is responsible for what ends up on the pamphlet and can gather input as much as they see fit. If people have unresolveable disagreements, they can make a proposal to design a different pamphlet :)
* Outcomes / reporting requirements - What are the deliverables due at project end date?
** Pamphlet as a PDF and other editable file formats
** Uploaded to peoplesopen.net and our Github page
* Accountability buddy / peer advisor - Who will check in with the collaborators and help them stay on track?\
** Benny??
** Benny: Sure. I just got my first accountability... client? last week! Tyler's writing an e-mail to his peeps.
* Discussion
** eenblam: You can link to things for people to learn more, for example the issue re: RF safety
* '''Consenso?''' (to move to Loomio)
** Yes: juul, eenblam, seth, eve

== Weekly updates/check-ins ==
* Internet Archive link
** No one available to speak; JMG said he'd be investigating LoS from his place.
** Benny: I think Marina falls into this category, if anyone knows that status
** (No one present knows)
* Paxio link
** Juul?
** mai: Should we just kick that off the list? They've seemed uninterested since StorQuest fell through.
** benny: hell naw. :-P I would like to see the last correspondence Juul had with them. I'm not convinced it not just one of those, need to keep reminding em cause its not their main gig things.
* Golden gate link
** Benny hasn't emailed yet.
* Chuck/MJT link
** eenblam: Any word from Chuck since last week?
** mai: No
** eenblam+mai: we can swing by this weekend if MJ+T are in town and Chuck is available
** benny: Gonna send him another rocket chat message right after this. (eenblam: thanks benny!)
* Hurricane Electric
** juul: Null had to take off earlier, but I have root access now. Can work on it over the next couple of days.
* People's Park
** Already heard from Juul
* ToMesh Workshop
** Benny: ToBen would like to do workshop Sat, April 6, anytime (some 3 hour block). Does that sound good to those who were interested?
** I was going to make a proposal to buy some of the materials. I think it comes out to <$100 (mostly a bunch of pis)
**seth-yeah! benny: woot!
** mai: +1 benny: yay
** eenblam: just put in a purchase request. I think it makes sense to fund it. benny: woo yay.

** does the time of day matter to anyone? maybe ill send an e-mail/doodle to the people that expressed interest this meeting and last meeting.

* benny: the color scheme of chats tonight has been great. digging the palette.

== Action Items ==
* e-mail other community wifi groups about rooftop insurance @bennlich
* adding neighbor outreach pamphlet to Loomio @iamai
* get in touch with chuck / mary jo and terry @iamai @eenblam
* script for updating nodes re: new tunneldigger config @bennlich
* revisit priorities brainstorm pad and report back @bennlich
* ping golden gate paxio link @bennlich
* poke ryan about marina @tunabananas
* handshake tokens @juul
* ping david and niki re: sunday @tunabananas
* create wiki page about EMF radiation @sierk @tunabananas
* any reply from LOLSpace? @tunabananas
* document battery-powered node in a waterproof bag @juul

== Breakout Groups ==
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
*

== Last Meeting Notes ==
* link to previous meeting minutes
* CHANGE ME AFTER PASTING: https://sudoroom.org/wiki/Mesh/10_December_1815

== End of Meeting ==
* please archive these meeting notes by copying the entire pad contents onto the sudomesh wiki with the correct date format: https://sudoroom.org/wiki/Mesh/DD_MONTH_YYYY
* 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_Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wki/Mesh/Minutes

[[Category:Mesh/Minutes]]

Mesh/29 January 2019

2019-02-10T22:33:37Z

Eenblam: /* Action Items */ make names taggable in rocketchat

'''People's Open Network Weekly Meeting - Tues 29 January 2019 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Proposal: Contract Jenny for Bookkeeping/Admin Labor (15 mins)
* Action Items (5 mins)

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: Who do you want for the next president of the US?
* Benny (afk getting pizza)
* seth-he/they - mumia.
** announcement - knows a guy who would give away a 80ft tower a block away from Broadway on 40th St.
* Eve- she/her - Jenny - for mayor. President - I don't know, but I have a little counter on my phone, and counting down the days. 643 days to the next election.
* Rob- he/him Sanders
* Mai - she/her/they - Warren
* Lesley - they/xyr/she/he - Barbara Lee
* Ned - he/him - probably Sanders
* Null - he/him - Bernie Sanders, doesn't really know competition
* Jenny - she/her - herself for president! Not Kamala Harris. yes mumia!

=== Announcements ===
Jenny - Berkeley Marina would be willing to have a tower

=== Meeting Roles ===
* Facilitator/s: Jenny
* Stacktaker: Mai
* Notetaker/s: lesley
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and past action items below:
* Look for list of stewards @iamai
** Mai: I just found it! Seems like we emailed the whole list and not many people responded
** Jenny: Five for consensus is what it is
*** Maybe tell them they're deleted if they don't respond? @iamai
* Ping Chuck re: connection @iamai @eenblam
** benny did, he responded. said he would check tonight. follow-up action item
** HE exit node issue
*** robb: juul tunneled in; it won't boot. probably need to reformat and reassemble the mirror from the other drive. doesn't have grub which is the primary issue.
*** null: "failed array"
*** Rob - only thing I can think of is go in with usb, reformat first partition and install grub on it. One is borked, one doesn't have grub. I don't know if you can install grub after its already been mirrored. Reseeded SATA cable, but this is a RAID error not a drive error. Reseeding might have repaired it? Running smartl didn't reveal any errors other than a fan error
*** null: how long would it take to just recreate the image? maybe a hour or two

* Create proposal for changing meeting language @iamai
** Proposal now live at https://www.loomio.org/d/GN2sK3Jt/first-tuesday-hangout-nights
** mai: You can still vote but we have reached quorum on this. :)

* Finalize details of node mount specs with Jonah @bennlich
** got some safety gear - heavy duty clips mainly - borrowing a lot of gear from @eenblam (thank you @eenblam!)
** Heading over sometime in the afternoon this Thurs with Grant, Robb, Lesley and whoever else is interested. I think Pam also wants to come and help document. Jenny, can we use your car and do you want to come?
** Went to Grainger in San Leandro to get safety lanyards on Monday
** Still have some preparation work Todo. See https://trello.com/b/wBKTQKDs/active-projects if you want to help.
** Priority is airfiber mount but would be cool if we can do both at once.(~48V)
*** need to find the PoE injectors for the AirFibers -
****Maybe use the poe on the roof and buy another later
** mai: probably want to do it earlier than 3 - closer to 2. (because of sunlight)

* WD mynet N600 router order (post-checkin to oakstop) - @tunabananas
** Jenny - Marc is in NYC, hasn't been immediately available for questions for a bit.

* finish APC app - @tunabananas
** app begun, could use support to finish. copying to doc: https://docs.google.com/document/d/1jcwDAPEG2CrvEXSwKF1lbornCQHdv_-ORUjQr1ZkCsk

* Tablet for AssetTiger @null
** robb: we have some android tablets in the harry potter room. Will look after this meeting.

* Upload photos from scouting Berkeley Marina - @tunabananas
** uploaded to https://drive.google.com/drive/folders/1HPZRfG5LHVO1ELvjT8SjtYblwRS7jp0J and created trello card @ https://trello.com/c/OzdYIT0P
** sync with dmytri, marina contact, and and

== 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-mesh-github-repos
* HE exit node being down affecting all the nodes that used it as an exit node
** Does it make sense to use a server at HE to be an exit node?
*** Benny: I think it probably does make sense to have it there. Useful to be close to backbone for speed, tho others may know more.
*** null: they're a real data center, that's especially good for streaming services
** Jenny: they don't issue take down notices, or haven't yet
** Lesley: they're a reseller to other ISPs, right? so the same consumer dmca laws don't apply, or something like that
** Benny: we could use domain names instead of IP addresses to direct exit nodes to other ips if that happens
** Mai: Just raising the question because we took so long to fix it and we were not ready to deal with the outage. We need other solutions to make sure we can handle outages like this in the future.
** Lesley: we need as robust and distributed a network as possible - we should have many exit nodes as possible. No need to arbitrarily give up individual ones - if the problem is that it's going down, we just need more.
** What other ways can we make our exit node infrastructure less prone to outages and more easily fixable?
*** Benny: use domain names e.g. exit.sudomesh.org in home node config instead of hardcoded ip addresses.
*** Null: you can use domain redirection, we could use something like that? If one domain fails, it goes on to the next one. It can give you a list of the servers it would try just by searching one domain. E.g. google does it.

* Benny: Discovered with Seth that the walkthrough page linked to a broken version of the firmware. I fixed the link, but the firmware build process could use some tidying up and documenting. Would be nice if someone wanted to take this on. I can share what notes I have.
** jenny: Do you mean the walkthrough page? or technical overview?
** benny: walkthrough page.
** lesley: i need editing permissions for the wiki walkthrough page

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* Dmitri sez there's someone at Berkeley Marina interested and experienced in setting up a tower for a mount! and evidently whatever Powers That Be are fully on board. Jenny will followup on the contact @ the Marina and work on a funding proposal
** Benny: incredible

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
* Update on Paxio?
** Benny: I think Marc was the contact here.
*** marc: "no, we should ping them again" PP is @juul - @iamai accountabilibuddy

* Anyone want to call in to talk with a group in Minneapolis next month? Re: https://twitter.com/iotmpls/status/1087748684476006400

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* Jenny is moving us to a new quickbooks account so as to secure a $30/mo lifetime discount for QBO
* Insurance broker sent us the following questions on Jan 25th:
** Can you confirm whether the members/employees of Sudo Mesh have experience with the antenna installations? What is the total annual payroll/revenue of the installations?
*** Jehan: "Most of us have experience, but there is always the possibility that we're taking someone new up as well so they can get experience. "
** Regarding the classes to educate the public about wireless networking technologies. What is average attendance?
*** Jehan: "On the classes, it varies, but usually around 20-50 attendees"

* Accounting group met up today at sudo room
** We revisited/cleared to do items that were no longer relevant, cleaned up the Accounting trello board, fixed the purchases request form to include the description
** Benny, Jenny, and Mai will go to Unify credit union (where our account is) to order more checks and debit cards next week

== Proposal: Contract Jenny for Bookkeeping/Admin Labor ==
via Jenny 1/27:

* Benny: yessssssss
* jenny: The premise is to start the ball rolling on people being responsible for specific roles and getting compensated for it.

I propose to do Sudo Meshâ€™s bookkeeping, legal due diligence and state filing work for hire (while still participating in additional volunteer capacity as I always have) on a 3-month trial basis at $30/hr - capped at 40hrs/month (but more likely to average 20hrs/month) unless an additional contract is agreed upon - with a reexamination of the agreement and contractual follow-up due diligence by a "proposal buddy" (Benny? Mai?) upon the start of the next fiscal quarter.
* mai: I would be happy to be an accountability buddy :)
* lesley: i volunteer to listen to stress venting

Summary of deliverables:
* Monthly bank account reconciliations and bookkeeping;

* Prepare and submit regular state filings (eg 990s, RRF-1s, SI-100s);

* Monthly and annual reporting and documentation;
* Update and maintain budget & business plan;
* Maintain digital and analog filing system and legal contractual due diligence (eg; donor acknowledgement letters, fiscal sponsorship agreements, annual board meeting minutes)

Full proposal at https://docs.google.com/document/d/1Y-tXdXqPgFIgOb6XJlHb-ljUzScVK6EX2FUIKlwEwF4

* '''Consenso?'''

* Lesley: This is awesome! I'm so happy about this. You've done all this work on a volunteer basis for years. I'm totally on board with this.
* Lesley: I also think we should prioritize having income beyond grants--I think we can and should start getting donations in exchange for internet access. I also think we should prioritize (what was the second thing?)

* Robb: I like the idea of having bounties for grant-writing (5, 7, 10% or something)
* Mai: I want to do a bigger push on our patreon. I agree that not relying on grants is a good idea. There're plenty of people in the bay area who are able and willing to give $20/mo for something they believe in.

== Next Sunday ==
We host office hours every Sunday from 1-3pm in Sudo Room, and often arrange a rooftop node mount.
* To sign up to bottomline, fill in your name here: https://ethercalc.org/byoi_office_hours
** tentatively null, mai, benny, ned.
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays
* Notes from this past Sunday's session:
** null was there but he was very sick. No one came by and he just hung out. There's a lot to do!

== Action Items ==
* email stewards list to stay on/be a steward @iamai
* follow up with chuck if he doesn't respond regarding checking config on his node @iamai
* write language for new hang out + newcomer night. Put it on calendars: Omni, wiki, peoplesopen.net @iamai, @tunabananas
* schedule hack session for APC application @tunabananas
* ask eenblam about people who can dismantle towers re: seth's contact @mux
* follow up w/ marc about using domain names for tunneldigger config @bennlich

== Last Meeting Notes ==
* link to previous meeting minutes
* https://sudoroom.org/wiki/Mesh/22_January_2019

== End of Meeting ==
* please archive these meeting notes by copying the entire pad contents onto the sudomesh wiki with the correct date format: https://sudoroom.org/wiki/Mesh/DD_MONTH_YYYY
* 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_Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wiki/Mesh/Minutes

[[Category:Mesh/Minutes]]

Mesh/Reminderbot

2019-01-18T06:42:55Z

Eenblam: /* Troubleshooting */

Reminderbot pops into peoplesopen.net/chat to remind us of the action items we decided on at the previous meeting!

==Troubleshooting==

# Did you move the minutes from [https://peoplesopen.net/notes the pad] to their own page? The minutes actually contain instructions for how to do this.
# Did you create a link to the new page on [[Mesh/Minutes]]?
# Did you put the link at the top and use the same format as the rest of the table?
# Did Reminderbot pop in and report an error? If so, ping eenblam on Signal.

Mesh/Reminderbot

2019-01-18T06:41:59Z

Eenblam: /* Troubleshooting */

Reminderbot pops into peoplesopen.net/chat to remind us of the action items we decided on at the previous meeting!

==Troubleshooting==

# Did you move the minutes from [https://peoplesopen.net/notes the pad] to their own page? The minutes actually contain instructions for how to do this.
# Did you create a link to the page on the [[Mesh/Minutes]]?
# Did you put the link at the top and use the same format as the rest of the table?
# Did Reminderbot pop in and report an error? If so, ping eenblam on Signal.

Mesh/Reminderbot

2019-01-18T06:38:58Z

Eenblam: Created page with "Reminderbot pops into peoplesopen.net/chat to remind us of the action items we decided on at the previous meeting! ==Troubleshooting== 1. Did you move the minutes from [https..."

Reminderbot pops into peoplesopen.net/chat to remind us of the action items we decided on at the previous meeting!

==Troubleshooting==
1. Did you move the minutes from [https://peoplesopen.net/notes the pad] to their own page? The minutes actually contain instructions for how to do this.
2. Did you create a link to the page on the [[Mesh/Minutes]]?
3. Did you put the link at the top and use the same format as the rest of the table?
4. Did Reminderbot pop in and report an error? If so, ping eenblam on Signal.

Mesh/WalkThrough

2019-01-13T22:42:36Z

Eenblam: /* Makenode (v.0.2.3 and earlier) */ Move Makenode instructions to Mesh/Makenode

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with Sudo Mesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by Sudo Mesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to ensure your router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || '''[https://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest]''' [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0]
|-
|}

Builds for other routers can be found on our [http://builds.sudomesh.org/builds/sudowrt/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use Sudo Mesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
[[File:Router_reset_mynet.png|200px|thumb|right|Reset hole location!]]
Instructions to reset / default a WD MyNet N600 or N750 router:
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin / paperclip / tiny screwdriver into the reset hole and hold it for at least 15 seconds.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Configure =
A freshly flashed node automatically sets its IP address to 172.30.0.xx. You will need to configure your laptop to use the following network settings to communicate with the node:

* IP address: 172.30.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.30.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

== Autoconf (v.0.3.0) ==
'''''Note: If you installed autoconfiguring [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers, you will not need to use makenode ([[#Makenode_.28v.0.2.3_and_earlier.29|instructions further down]]) after flashing the sudowrt-firmware to your router to configure it to work on People's Open Network.'''''

[[File:Nodeports titles.png|400px|thumb|right|Plug into port 3 to access the private network from your laptop. Port 2 connects to the public 'peoplesopen.net' network]] Connect your newly-flashed MyNet N600 to your existing Internet router via ethernet from your existing router's LAN port to your new node's Internet port. Wait a few minutes for your new node to connect to the Internet and obtain its private IP address. Once this happens, the node will broadcast a new WiFi network starting with 'peoplesopen.net' (and ending with a unique IP address). This is the public network, has no password, and is suitable for day-to-day internet access.

There is also a wireless network called 'pplsopen-admin'. This is the private network, and you can use it to access a web dashboard to configure some settings. The default WiFi password is 'meshtheworld'. Try connecting to it (you can also connect to the private network using an ethernet cable connected to port 3 on an N600).

While connected to the ''private'' network, try connecting to the home node's web dashboard by opening a web browser and navigating to http://172.30.0.1

If the flash was successful you should be brought to the following screen:

[[File:Peoplesopen-dash.jpg|frame|center|upright=2]]

The default password is 'meshtheplanet'.

Here you can set the amount of downstream and upstream bandwidth you're willing to share (default is set to 4096kb, or roughly 4 megabits/second):
[[File:homeScreen.jpg|frame|center|upright=2]]

[[File:WifiSettings.jpg|frame|left|upright=2|Set your private SSID and password via the 'WIFi Settings' tab. NOTE: When you first set your private SSID name and hit 'Save', you will have to reconnect to the newly-named SSID using the original default password ('meshtheworld') and then reconnect again with the new password after setting it in the dashboard]] [[File:newrouter.png|frame|right|upright=2|See all devices connected to your node via the 'Connections' tab]]
 

'''''Note: If you would like to be able to change these settings in the future, or ssh into your router, you will need to change the admin and root passwords within 12 hours.'''''

To do so, open a terminal while connected to the 'pplsopen-admin' SSID:
ssh root@172.30.0.1
Enter the following password: meshtheplanet

Set the root password.
passwd
Now set the admin password for logging into the web dashboard:
passwd admin

== Makenode (v.0.2.3 and earlier) ==
'''''Note: If you installed autoconfiguring [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers, you do not need to use makenode. See the autoconf instructions above.'''''

Makenode's documentation has been consolidated to [[Mesh/Makenode|its page.]]

= Testing =

After you're finished with the flashing and configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available. It should also be populated on the [https://peoplesopen.herokuapp.com monitor]!

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, upload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

[[Category:Mesh]]

Mesh/Makenode

2019-01-13T22:42:09Z

Eenblam: Add original makenode instructions from Mesh/WalkThrough

makenode is a script that finishes the configuration for People's Open nodes flashed with the sudowrt firmware, see https://github.com/sudomesh/makenode.

This script is in the process of being deprecated, below is ongoing documentation this deprecation.

"Early alpha status. Things may break."

= makenode theory =
There are two interconnected theories that govern the implementation, usage, and deprecation of the makenode script

== theory for implementation ==
The story goes that makenode was created to solve a few problems with the sudowrt firmware. Mainly, it was much quicker to implement changes in makenode rather than rebuilding the firmware. This way patches could be rapidly deployed with out a full rebuild and reflash of the firmware (however this is ignoring the existence of a lot of already "made nodes"). This use case of triaging patches before integrating them into a new build of the firmware devolved into using makenode to do perform almost all node configurations. While these configurations are mostly "per-node"

1. To retrieve an IP from secrets.peoplesopen.net (our meshnode-database) and then copy it into a lot of config files

2. To set a root password other per-node configs, such as hostname, private SSID, etc.

3. To perform hardware detection to select which config files to copy onto node

== theory for deprecation ==
While makenode does work, it presents a large barrier to inclusion (e.g. doesn't work on Windows, have to be relatively comfortable with terminal) as well as limiting our ability to quickly configure "blank" routers that can be handed out to anyone. Instead, it would be preferable to have a version of the firmware that requires "zero configurations", aka zeroconf. To do this, we first need to address the three main reasons for implementation.

1. retrieving a mesh IP:
* this can be done shortly after boot by making a POST request to secrets.peoplesopen.net using curl, the IP can then be then be parse from the json response and inserted into the correct config files using OpenWRT's build UCI configuration tool.

2. setting a root password:
* the quick (but insecure) solution is to set a default root password. The better solution is to limit the access of the root user to only the hardwired interface and/or disable the password after a certain period of time and/or on second boot
* any other non-security-related, per-node configurations could and should be set through the admin dashboard

3. hardware detection:
* an example of this can already be seen for extender nodes in the [https://github.com/paidforby/sudowrt-firmware/blob/master/files_extender-node/etc/uci-defaults/99_wireless 99_wireless script]
* at boot OpenWrt needs to detect number of antennas and ports,
* currently we find ourselves flashing almost exclusively one model of router

However, before tackling these concerns, all the configurations made by makenode must be moved back to the firmware and adapted to be somewhat configurable. To do this, we will create a uci-defaults script that does exactly what make makenode previously did...copy a lot of IP addresses into different config files.

== What does makenode change? ==

=== configs/templates/files/opt/mesh/ ===
* tunnelhook -> callback called by config_load tunneldigger

=== configs/templates/files/etc/ ===

dropbear/
* authorized keys, i.e. adds developer keys -> remove? or add more people? opt-in option in dashboard

config/
* dhcp -> dnsmasq, mesh pool, private pool
* network -> loopback, lan, adhoc, open, priv
* notdhcpserver -> extender node static ips
* polipo -> daemonised caching web proxy
* rpcd, -> sets ubus username and pass (from where?)
* snmpd -> managment/monitoring, pulls in operator email/name, presumably from makenode.js
* system -> sets hostname and log ip? from makenode.js?
* tunneldigger- > sets tunnel broker ip, l2tp interface, upstream, downstream bandwidth (related to bug #2), and tunnel hook callback script
* uhttpd -> http server, sets index directory, ubus, cgi-bin, locale

init.d/
* log -> copied from openwrt? purpose?

iproute2/
* rt_tables -> moved to makenode by MaxB, unclear purpose? reverses values for ...?

babeld.conf -> allows babel to run on l2tp, adhoc, and open interface, (could address bug #13 here)

banner -> presents version info, move back to firmware

dnsmasq.conf -> excepts interfaces l2tp0, adhoc0, eth0, why?

= Original Makenode Instructions =
This section was migrated from [Mesh/WalkThrough].

=== Install Dependencies ===
You first will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

==== Linux ====

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # or you can close and reopen your terminal before using nvm
nvm install 7.10

===== OS Compatibility checklist =====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

==== Mac ====

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

==== Windows 10 (Experimental)====

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

=== Install and run makenode ===
From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

Mesh/WalkThrough

2018-12-09T21:48:36Z

Eenblam: Add flag to Makenode section warning away Autoconf users.

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with Sudo Mesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by Sudo Mesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to ensure your router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || '''[https://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest]''' [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0]
|-
|}

Builds for other routers can be found on our [http://builds.sudomesh.org/builds/sudowrt/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use Sudo Mesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
[[File:Router_reset_mynet.png|200px|thumb|right|Reset hole location!]]
Instructions to reset / default a WD MyNet N600 or N750 router:
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin / paperclip / tiny screwdriver into the reset hole and hold it for at least 15 seconds.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Configure =
A freshly flashed node automatically sets its IP address to 172.30.0.xx. You will need to configure your laptop to use the following network settings to communicate with the node:

* IP address: 172.30.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.30.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

== Autoconf (v.0.3.0) ==
'''''Note: If you installed autoconfiguring [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers, you will not need to use makenode ([[#Makenode_.28v.0.2.3_and_earlier.29|instructions further down]]) after flashing the sudowrt-firmware to your router to configure it to work on People's Open Network.'''''

[[File:Nodeports titles.png|400px|thumb|right|Plug into port 3 to access the private network from your laptop. Port 2 connects to the public 'peoplesopen.net' network]] Connect your newly-flashed MyNet N600 to your existing Internet router via ethernet from your existing router's LAN port to your new node's Internet port. Wait a few minutes for your new node to connect to the Internet and obtain its private IP address. Once this happens, the node will broadcast a new WiFi network starting with 'peoplesopen.net' (and ending with a unique IP address). This is the public network, has no password, and is suitable for day-to-day internet access.

There is also a wireless network called 'pplsopen-admin'. This is the private network, and you can use it to access a web dashboard to configure some settings. The default WiFi password is 'meshtheworld'. Try connecting to it (you can also connect to the private network using an ethernet cable connected to port 3 on an N600).

While connected to the ''private'' network, try connecting to the home node's web dashboard by opening a web browser and navigating to http://172.30.0.1

If the flash was successful you should be brought to the following screen:

[[File:Peoplesopen-dash.jpg|frame|center|upright=2]]

The default password is 'meshtheplanet'.

Here you can set the amount of downstream and upstream bandwidth you're willing to share (default is set to 4096kb, or roughly 4 megabits/second):
[[File:homeScreen.jpg|frame|center|upright=2]]

[[File:WifiSettings.jpg|frame|left|upright=2|Set your private SSID and password via the 'WIFi Settings' tab. NOTE: When you first set your private SSID name and hit 'Save', you will have to reconnect to the newly-named SSID using the original default password ('meshtheworld') and then reconnect again with the new password after setting it in the dashboard]] [[File:newrouter.png|frame|right|upright=2|See all devices connected to your node via the 'Connections' tab]]
 

'''''Note: If you would like to be able to change these settings in the future, or ssh into your router, you will need to change the admin and root passwords within 12 hours.'''''

To do so, open a terminal while connected to the 'pplsopen-admin' SSID:
ssh root@172.30.0.1
Enter the following password: meshtheplanet

Set the root password.
passwd
Now set the admin password for logging into the web dashboard:
passwd admin

== Makenode (v.0.2.3 and earlier) ==
'''''Note: If you installed autoconfiguring [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers, you do not need to use makenode. See the autoconf instructions above.'''''

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

=== Install Dependencies ===
You first will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

==== Linux ====

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # or you can close and reopen your terminal before using nvm
nvm install 7.10

===== OS Compatibility checklist =====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

==== Mac ====

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

==== Windows 10 (Experimental)====

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

=== Install and run makenode ===
From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the flashing and configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available. It should also be populated on the [https://peoplesopen.herokuapp.com monitor]!

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, upload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

[[Category:Mesh]]

Mesh/06 November 2018

2018-11-07T16:27:31Z

Eenblam: meeting met

'''People's Open Network Weekly Meeting - 6 November 2018 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Proposal: Mobile Calyx Node for The Village (15 mins)
* Discussion: BYOI / Office Hours (15 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: Favorite artist? Visual, musical, otherwise
* null - him/her - I like Infected Mushroom
** have u heard of Unwashed Tomato? ;D https://www.discogs.com/artist/1329175-Unwashed-Tomato
* marc - he/him - the author of The Gods Are Bastards
* lesley - pretty much anything or she/they - I really like artists whose work you can identify from across the room. Odilon Redon, Egon Schiele, Davinci
* ben - he/they - Restricting scope to favorite webcomic. Zach Morrison - paranatural.net Middle-school kids go on adventures with goofy spirits and stuff
* felix - he/him - Thomas Kling; German poet who does language installations
* scott - any are fine - Minna Sundberg http://www.minnasundberg.fi/
* seth - he/they - julian oliver
* Mai- she/they - Doesn't like rockstar artists and having to know the personality behind art but like internet mash-ups and general memery art that emerges on the internet. Also would say Aphex Twin.
* jehan - he/him - Niac (niac.org), which I'll be going over with you today!
** ballot Benny - greetings from the polls! 4 minutes left to vote go go go go go go

=== Meeting Roles ===
* Facilitator/s: ben
* Stacktaker:
* Notetaker/s: lesley, ben
** URL of this pad: https://peoplesopen.net/notes

=== Proposals ===

== Proposal: Mobile Calyx Node for The Village ==
Proposal to spend ~$900~1000 on a mobile Calyx node to be first deployed at the new Village site near Coliseum for one year. Will be returned once we establish line of sight to a neighbor open to sharing their bandwidth (or reach it via Paxio link to the hills) and thus reusable for future actions / temp locations.
* https://github.com/sudomesh/projects/blob/master/proposals/mobilenode.md
* https://peoplesopen.net/pad/p/villagewifi

Idea: get a box, put a thing in it with WiFi, 4G, a battery, and a solar panel.
* 4G via Calyx membership - 400/year + 100 initial equipment fee
** scott - will they waive equipment fee if we're providing our own?
* Put it up at the village. If it works well, then we start raising funds. Every time we get enough, we throw together another one and deploy it where there's high need.
** Spread with mesh routers once one is up.
** marc - during december, not that much sun - so running solar power might not work during this time - peak power usage is above 12 watts, average might be less than 8 watts. Would need 100 watt solar power to run it 24/7. Hard to mount on tall pole with 100 watt panel. Maybe have smaller panel lower. Issue is that it might get stolen.
* Total cost would be around - 400
**modem - 125
** altogether - 1000 for up front equipment and first year
** Jehan - Mesh ++ makes something like this, but for 3000 - maybe they would sponsor us with one of their units.
** Ben - 4G?
** Jehan - not sure.
** Mai - we should work out the logistics before we pay the 400 and start the membership. Concerns with how to secure it
** Jehan - we could put up decoys
** Marc - how long before we can move forward?
** Lesley - if it's not past the 2000 limit, then we don't have to do that
** Jehan - we have consensus, don't we
** null - can we use a streetlight?
** juul - no that won't work.
** Ben - pole mounted to fence?
** Jehan - drill, put in pilings, 30 ft
** Marc - if someone can find a way to mount it so it won't get stolen, let's just go ahead and do it. And even if it doesn't work, we'll have a 4g access point we can use for something else
*** jenny: harbor freight flagpole w/ guy wires? there are also several structures we could mount to
**** also, village folks lock the gate when not open (currently open mon/wed/fri 10-5) and have 24/7 security

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and past action items below:
* Get in touch with MonkeyBrains about donated bandwidth (ben)
** ben - I messaged them back again during last meeting; no response
* Working group to meet and plan out routing config for Archive mount on thursday 5-7
** juul, benny, null, mai, jenny, eenblam, lesley
** Archive Tower Meeting Notes - https://peoplesopen.net/pad/p/richmond-tower-hardware
** ben: We talked about what we wanted and also what a minimum viable product would be for what we want to install and they're willing to just give us rackspace. We talked about bringing in a router and a switch for multiple radios on the roof. We have a 12-harddrive storage server. We just need to buy hard drives for it.
*** Mai: somebody was gonna follow up, who? (benny) the last thing Jonah asked us is what routing configuration we would use that is connected to our equipment on the tower
*** null: I think benny?
** send e-mail about richmond tower working group meeting (mai) - done
** marc - we agreed to meet this past Sunday. I set up the rackmount server with latest debian. Need to add babel and tunneldigger, set up cron backup, etc.
*** we're meeting again tomorrow at 3pm to finalize that.
*** When done we should be ready to just go shove it into the rack.
*** Meeting tomorrow at 3 PM to finalize.
* create text for byoi eventbrite (benny)
** not done yet. Will do tomorrow. take a look at https://www.loomio.org/d/0h914dO3/byoi-fall-2018/5 would be awesome to decide on a simple event timeline tonite! 12-5? 3-8?
** what do we want to do besides hang out at activity booths?
* create poster for byoi event (benny)
** Not yet. Planning to do this week / weekend
* combine "node mount" and "office hours" sections in notes template (benny)
** Didn't do it yet.
** jenny did this today
*** Sick!

== 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-mesh-github-repos
*

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* grant - Matt from Paxio got back to us, said there is no LOS between Omni Commons and downtown Oakland? Suggested looking for places in Emeryville or Golden Gate neighborhood.
** Ben, Marc, Jehan - ... But we do have line of sight
*** Is it possible we have wrong building?
****-Seth i'm gonna make a googleearth map tomorrow night.
** I'm not sure how to respond to Matt's last email, Marc or Mai wanna pick up on this thread?
** Also benny was looking at places for Internet Archive mount in West Berkeley, maybe one those that could also see Paxio?
** Paxio's presumed location in 436 14th St, Oakland.

* Jason's install - decide equipment - he will get sonic gigabit fiber soon. Lesley dropped off rocket + N600 with him and can see the signal from her place, but it only has a ~300 mbps throughput maximum.
* Ben - power constraints at Jeff's place. Ideally would have omnidirectional. But for his proposed setup, we might need to store equipment at Jeff's/John's and run another wire.
** i.e. if we're going to have a rocket at each site, we'll want a directional point-to-point link as well. This means we need a switch, etc.
** bonus issue - we're under the radar at Jeff's place
* Ben - rigth now we just have a nanobridge at Jeff's place, running sudowrt, so we would need to swap it out with one running airos. We should have either omni or sector attached to a rocket. If we're also going to put a rocket at Jeff's and a rocket at Jasons, we could just put rockets on both, or we could get a couple of Microtic wireless routers, but that would require plugging into both extender node ports on n600, which would be slow, or throwing in a switch. If we did microtics we'd need switches on both ends, which might be difficult due to landlord/power constraints at Jeff's place. I'd like to keep that simple on that side.

* scott - Should I reach out to All Power labs about getting a tower on their place as an Internet Archive connection?
** They're like two buildings down from Pief's.
** What can we offer them?
*** marc - expect half a gigabit.

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications
Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
* See BYOI discussion item

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* jehan - I need answers for insurance stuff
** said 20 volunteers
** put sources of funding as private foundations - what would you say are other sources of funding?
*** plz share questions and i can answer them --jenny (no, not private foundations. big diff btw private foundations & public charities...) - jenny
**** small recurring and one-time charitable contributions and grants; in-kind donations
** also officer's insurance is supplementary doc
*** we want general liability as well as D&O
** Marc - suggests putting questions in google docs

== Next Sunday ==
We host office hours every Sunday from 1-3pm in Sudo Room, and often arrange a rooftop node mount.
* To sign up to bottomline, fill in your name here: https://ethercalc.org/byoi_office_hours
* Ongoing node mounting spreadsheet is located at: https://peoplesopen.net/sundays
* Notes from this past Sunday's session:
* seth - me and null inventoried cage last sunday. Antoinette and Cassidy box inventoried in cage - anybody know if these projects are ongoing or defunct?
** jenny - antoinette bin is my bad. will recoup

== Discussion: November BYOI Event ==
* Let's look at Benny's Loomio! https://www.loomio.org/d/0h914dO3/byoi-fall-2018/5
** food
*** scott - I'm willing to do food again. Anyone have requests for types of food?
**** Thinking southeast asian - spring rolls with peanut sauce, pad thai, etc.
**** ben - we should have non-peanut options
** swag
*** Seth-im bringing t-shirts.
*** jenny can make buttons & stickers - mebbe an upcoming sunday aft activity?
** activities
*** juul - thinking about playing around with pogo plugs, which I've got a bunch of. You can pull them apart without tools, have root access, and bootload them easily. They're $15 each. We can play with these, and use some hard drives, and play around with them at the event.
*** marc - not much has been happening with disaster radio but maybe Grant would be interested in showing off the simulator
**** ben - could be cool to set up a monitor up for the simulator's visualization
*** TCP Roller disco
** outreach
*** print flyers for null, nanomonkey, jnny, anyone else attending nonprofit dev summit
*** marc - we were talking about having more of a party atmosphere. Maybe start roller disco earlyish?
**** mai - maybe have a movie showing?
**** ben - maybe the suggested 3-8 timeslot instead of 12-5? Closer to party time.
***** several people thought this was a good idea

== Action Items ==
* Email Jonah re: what kind of routing configuration we plan to have for our Archive mount (benny?)
* Meeting to configure servers for Archive mount 3pm Wed Nov 7 (juul, et al)
* Add BYOI to Omni Calendar (jenny?)
** jenny: submitted some weeks ago & contract signed - event will be published following payment of invoice (offered $300 which is nonprofit rate)
*** should also make event posts on indybay, fb, SSB... did i just volunteer? :D
* Insurance details - jehan, ben, jenny
* Purchase gear for Jason's install - lesley, ben

[[Category:Mesh/Minutes]]

Mesh/Minutes

2018-11-07T16:26:19Z

Eenblam: 2018-11-06

<center>'''Sudo Mesh Meeting Minutes'''</center>

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/06_November_2018|2018-11-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_October_2018|2018-10-30]]
| Weekly organizing meeting
|-
| [[Mesh/23_October_2018|2018-10-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_October_2018|2018-10-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_October_2018|2018-10-09]]
| Weekly organizing meeting
|-
| [[Mesh/2_October_2018|2018-10-2]]
| Weekly organizing meeting
|-
| [[Mesh/25_September_2018|2018-09-25]]
| Weekly organizing meeting
|-
| [[Mesh/18_September_2018|2018-09-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_September_2018|2018-09-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_September_2018|2018-09-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_August_2018|2018-08-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_August_2018|2018-08-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_August_2018|2018-08-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_August_2018|2018-08-07]]
| Weekly organizing meeting
|-
| [[Mesh/24_July_2018|2018-07-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_July_2018|2018-07-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_July_2018|2018-07-10]]
| Weekly organizing meeting
|-
| [[Mesh/3_July_2018|2018-07-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_June_2018|2018-06-26]]
| Weekly organizing meeting
|-
| [[Mesh/12_June_2018|2018-06-12]]
| Weekly organizing meeting
|-
| [[Mesh/5_June_2018|2018-06-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_May_2018|2018-05-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_May_2018|2018-05-22]]
| Annual Board Meeting
|-
| [[Mesh/15_May_2018|2018-05-15]]
| Weekly organizing meeting & Firmware meeting
|-
| [[Mesh/8_May_2018|2018-05-08]]
| Weekly organizing meeting
|-
| [[Mesh/1_May_2018|2018-05-01]]
| Weekly organizing meeting
|-
| [[Mesh/24_Apr_2018|2018-04-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_Apr_2018|2018-04-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Apr_2018|2018-04-10]]
| Strategic plan meeting
|-
| [[Mesh/03_Apr_2018|2018-04-03]]
| Weekly organizing meeting
|-
| [[Mesh/27_Mar_2018|2018-03-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Mar_2018|2018-03-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_Mar_2018|2018-03-13]]
| Weekly organizing meeting
|-
| [[Mesh/6_Mar_2018|2018-03-06]]
| Weekly organizing meeting
|-
| [[Mesh/27_Feb_2018|2018-02-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Feb_2018|2018-02-20]]
| Weekly organizing meeting
|-
| [[Mesh/17_Feb_2018|2018-02-17]]
| Strategic plan meeting
|-
| [[Mesh/13_Feb_2018|2018-02-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_Feb_2018|2018-02-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_Jan_2018|2018-01-30]]
| Monthly general meeting
|-
| [[Mesh/23_Jan_2018|2018-01-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_Jan_2018|2018-01-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_Jan_2018|2018-01-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_Jan_2018|2018-01-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_Dec_2017|2017-12-26]]
| Monthly general meeting
|-
| [[Mesh/19_Dec_2017|2017-12-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Dec_2017|2017-12-12]]
| Weekly organizing meeting
|-
| [[Mesh/05_Dec_2017|2017-12-05]]
| Weekly organizing meeting
|-
| [[Mesh/28_Nov_2017|2017-11-28]]
| Monthly general meeting
|-
| [[Mesh/21_Nov_2017|2017-11-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_Nov_2017|2017-11-14]]
| Weekly organizing meeting
|-
| [[Mesh/24_Oct_2017|2017-10-24]]
| Monthly general meeting
|-
| [[Mesh/17_Oct_2017|2017-10-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Oct_2017|2017-10-10]]
| Weekly organizing meeting
|-
| [[Mesh/03_Oct_2017|2017-10-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_Sep_2017|2017-09-26]]
| Monthly general meeting
|-
| [[Mesh/19_Sep_2017|2017-09-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Sep_2017|2017-09-12]]
| Weekly organizing meeting
|-
| [[Mesh/11_Sep_2017|2017-09-11]]
| Website redesign session
|-
| [[Mesh/05_Sep_2017|2017-09-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_Aug_2017|2017-08-29]]
| Monthly general meeting
|-
| [[Mesh/22_Aug_2017|2017-08-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_Aug_2017|2017-08-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_Aug_2017|2017-08-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_Aug_2017|2017-08-01]]
| Weekly organizing meeting
|-
| [[Mesh/18_July_2017|2017-07-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_July_2017|2017-07-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_July_2017|2017-07-4]]
| Weekly organizing meeting
|-
| [[Mesh/20_June_2017|2017-06-20]]
| Monthly general meeting
|-
| [[Mesh/13_June_2017|2017-06-13]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2017|2017-06-11]]
| Temescal street fair report-back
|-
| [[Mesh/6_June_2017|2017-06-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_May_2017|2017-05-30]]
| Monthly general meeting
|-
| [[Mesh/16_May_2017|2017-05-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_May_2017|2017-05-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_May_2017|2017-05-02]]
| Weekly organizing meeting
|-
| [[Mesh/25_April_2017|2017-04-25]]
| Monthly general meeting
|-
| [[Mesh/18_April_2017|2017-04-18]]
| Weekly organizing meeting
|-
| [[Mesh/17_April_2017|2017-04-17]]
| Annual sudo mesh board meeting
|-
| [[Mesh/11_April_2017|2017-04-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_April_2017|2017-04-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_March_2017|2017-03-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_March_2017|2017-03-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_March_2017|2017-03-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_March_2017|2017-03-07]]
| Weekly organizing meeting
|-
| [[Mesh/28_February_2017|2017-02-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_February_2017|2017-02-21]]
| Weekly organizing meeting
|-
| [[Mesh/10_February_2017|2017-02-10]]
| Weekly organizing meeting
|-
| [[Mesh/07_February_2017|2017-02-07]]
| Organizing "Build Your Own Internet" Workshop
|-
| [[Mesh/05_July_2016|2016-07-05]]
| Videochat meeting with nycmesh
|-
| [[Mesh/22_June_2016|2016-06-22]]
| Weekly organizing meeting
|-
| [[Mesh/07_June_2016|2016-06-07]]
| Weekly organizing meeting
|-
| [[Mesh/23_February_2016|2016-02-23]]
| Monthly general meeting
|-
| [[Mesh/09_February_2016|2016-02-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_February_2016|2016-02-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_January_2016|2016-01-26]]
| Monthly general meeting
|-
| [[Mesh/27_October_2015|2015-10-27]]
| Monthly general meeting
|-
| [[Mesh/06_October_2015|2015-10-06]]
| Weekly organizing meeting
|-
| [[Mesh/29_September_2015|2015-09-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_September_2015|2015-09-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_September_2015|2015-09-15]]
| Second annual board meeting
|-
| [[Mesh/08_September_2015|2015-09-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_September_2015|2015-09-01]]
| Monthly general meeting
|-
| [[Mesh/07_April_2015|2015-04-07]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2015|2015-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/17_March_2015|2015-03-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_March_2015|2015-03-10]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2015|2015-02-26]]
| Big general meeting
|-
| [[Mesh/24_February_2015|2015-02-24]]
| Hacknight
|-
| [[Mesh/19_February_2015|2015-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/05_February_2015|2015-02-05]]
| Weekly organizing meeting
|-
| [[Mesh/03_February_2015|2015-02-04]]
| Hacknight
|-
| [[Mesh/29_January_2015|2015-01-29]]
| Big general meeting
|-
| [[Mesh/24_January_2015|2015-01-24]]
| Mesh mini-retreat
|-
| [[Mesh/22_January_2015|2015-01-22]]
| Weekly general meeting
|-
| [[Mesh/15_January_2015|2015-01-15]]
| Weekly general meeting
|-
| [[Mesh/30_December_2014|2014-12-30]]
| Big general meeting
|-
| [[Mesh/18_December_2014|2014-12-18]]
| Weekly general meeting
|-
| [[Mesh/13_November_2014|2014-11-13]]
| Weekly general meeting
|-
| [[Mesh/21_October_2014|2014-10-21]]
| Hacknight
|-
| [[Mesh/16_October_2014|2014-10-16]]
| Weekly general meeting
|-
| [[Mesh/09_October_2014|2014-10-09]]
| Weekly general meeting
|-
| [[Mesh/02_October_2014|2014-10-02]]
| Weekly general meeting
|-
| [[Mesh/25_September_2014|2014-09-25]]
| Big general meeting
|-
| [[Mesh/28_August_2014|2014-08-28]]
| Big general meeting
|-
| [[Mesh/21_August_2014|2014-08-21]]
|
|-
| [[Mesh/07_August_2014|2014-08-07]]
|
|-
| [[Mesh/31_July_2014|2014-07-31]]
| Big general meeting
|-
| [[Mesh/17_July_2014|2014-07-17]]
|
|-
| [[Mesh/15_July_2014|2014-07-15]]
|
|-
| [[Mesh/10_July_2014|2014-07-10]]
|
|-
| [[Mesh/06_July_2014|2014-07-06]]
| Hackathon Day 2!
|-
| [[Mesh/05_July_2014|2014-07-05]]
| Hackathon Day 1!
|-
| [[Mesh/03_July_2014|2014-07-03]]
|
|-
| [[Mesh/12_June_2014|2014-06-12]]
|
|-
| [[Mesh/05_June_2014|2014-06-05]]
|
|-
|-
| [[Mesh/29_May_2014|2014-05-29]]
| General meeting
|-
| [[Mesh/27_May_2014|2014-05-27]]
|
|-
| [[Mesh/20_May_2014|2014-05-20]]
|
|-
| [[Mesh/13_May_2014|2014-05-13]]
| First Tuesday meeting ^.^
|-
| [[Mesh/08_May_2014|2014-05-08]]
|
|-
| [[Mesh/01_May_2014|2014-05-01]]
|
|-
| [[Mesh/24_April_2014|2014-04-24]]
| General meeting!
|-
| [[Mesh/17_April_2014|2014-04-17]]
|
|-
| [[Mesh/03_April_2014|2014-04-03]]
|
|-
| [[Mesh/27_March_2014|2014-03-27]]
|
|-
| [[Mesh/20_March_2014|2014-03-20]]
|
|-
| [[Mesh/13_March_2014|2014-03-13]]
|
|-
| [[Mesh/27_February_2014|2014-02-27]]
|
|-
| [[Mesh/20_February_2014|2014-02-20]]
|
|-
| [[Mesh/13_February_2014|2014-02-13]]
|
|-
| [[Mesh/6_February_2014|2014-02-06]]
|
|-
| [[Mesh/30_January_2014|2014-01-30]]
|
|-
| [[Mesh/23_January_2014|2014-01-23]]
|
|-
| [[Mesh/16_January_2014|2014-01-16]]
|
|-
| 31 December - 09 January
| Holidaze Break
|-
| [[Mesh/26_December_2013|2013-12-26]]
|
|-
| [[Mesh/19_December_2013|2013-12-19]]
|
|-
| [[Mesh/12_December_2013|2013-12-12]]
|
|-
| [[Mesh/5_December_2013|2013-12-05]]
|
|-
| [[Mesh/21_November_2013|2013-11-21]]
|
|-
| [[Mesh/14_November_2013|2013-11-14]]
|
|-
| [[Mesh/07_November_2013|2013-11-07]]
|
|-
| [[Mesh/31_October_2013|2013-10-31]]
|
|-
| [[Mesh/24_October_2013|2013-10-24]]
|
|-
| [[Mesh/17_October_2013|2013-10-17]]
|
|-
| [[Mesh/10_October_2013|2013-10-10]]
|
|-
| [[Mesh/26_September_2013|2013-09-26]]
|
|-
| [[Mesh/18_September_2013|2013-09-18]]
|
|-
| [[Mesh/11_September_2013|2013-09-11]]
|
|-
| [[Mesh/4_September_2013|2013-09-04]]
|
|-
| [[Mesh/28_August_2013|2013-08-28]]
|
|-
| 07 August - 21 August
| Hack nights!
|-
| [[Mesh/31_July_2013|2013-07-31]]
|
|-
| [[Mesh/25_July_2013|2013-07-25]]
|
|-
| 18 July 2013
| Hack night: Flashing, firmware
|-
| [[Mesh/11_July_2013|2013-07-11]]
|
|-
| [[Mesh/04_July_2013|2013-07-04]]
|
|-
| [[Mesh/27_June_2013|2013-06-27]]
|
|-
| [[Mesh/20_June_2013|2013-06-20]]
|
|-
| [[Mesh/13_June_2013|2013-06-13]]
|
|-
| 30 May - 05 June
| Hack nights! Trying out some of the nicer Ubiquiti equipment we procured
|-
| [[Mesh/23_May_2013|2013-05-23]]
|
|-
| [[Mesh/09_May_2013|2013-05-09]]
|
|-
| 25 April - 02 May
| Hack nights! See wiki for documentation - principally going through donated routers, flashing them with OpenWRT and installing batman-adv.
|-
| [[Mesh/18_April_2013|2013-04-18]]
|
|-
| [[Mesh/11_April_2013|2013-04-11]]
|
|-
| 28 March - 04 April
| SPRING SHIFT HIATUS
|-
| [[Mesh/21_March_2013|2013-03-21]]
|
|-
| [[Mesh/07_March_2013|2013-03-07]]
|
|-
| [[Mesh/28_February_2013|2013-02-28]]
|
|-
| [[Mesh/21_February_2013|2013-02-21]]
|
|-
| [[Mesh/14_February_2013|2013-02-14]]
|
|-
| [[Mesh/7_February_2013|2013-02-07]]
|
|-
| [http://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html 2013-01-31]
|
|}

Mesh/30 October 2018

2018-10-31T04:10:10Z

Eenblam: We talked about these things

'''People's Open Network Weekly Meeting - 30 October 2018 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Proposal X: (15 mins)
* Discussion Y: (15 mins)
* Discussion Z (15 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: favorite icebreaker question/activity
* null - him/her - favorite icebreaker question is my favorite flavor of ice cream
* mai - she/they - i like ones involving favorite memories: favorite summer, or comfort item
* jenny - she/her - involved talking to the person next to you for 2 minutes and then you have to introduce them
* seth-he/they- does drinking alcohol count?
* ben (eenblam) - he/they - dunno if it'd be right for PON since we see each other every week, but 2 truths and a lie
* juul - he/him - why am i all alone in here?
* scott - he/him - describe a time when you were most happy
* benny - he/him - something you wish all your friends knew about you
* lesley - she/they/he - it's a hard question. I like, 'what is your final form?' although that's an extra hard question :p

== announcements ==
* mai: have an extra ticket for devsummit if someone wants to go - If so let me know via RC
* ben: in touch with Rudy from Monkeybrains about getting donated bandwidth, will text him tomorrow.

=== Meeting Roles ===
* Facilitator/s: ben eenblam
* Stacktaker: benny
* Notetaker/s: jenny, mai, swth
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and past action items below:
* e-mail yar about tcp activities (benny)
** done!
* Reach out to insurance broker recommended by Jesse - Jehan
** jenny - I'll pick it back up and rope in Jehan, too
* e-mail some spaces about richmond tower link (benny)
** didn't get to it
** seth is getting good at Google Earth; might be cool if we could *show* places that can see it
* talk to marc about richmond tower server hardware (benny)
** juul says we don't have anything fancy to put there, but we do have some old servers we could use
** question for juul: what would be the ideal hardware we would want to put there? then: let's propose that to jonah and ask if he has anything similar--last time he came here, he said he probably had some hardware he would like to donate to us. in general jonah sounds super willing to help and collaborate--I think we should take him up on his energy in that regard. e.g. if we tell him at a high level what we want to happen there (e.g. run an exitnode) he might have good ideas. could have a breakout group to discuss our vision?
** benny: what would do with a server there?
*** scott: should we be able to have users share space on it?
*** benny: maybe we should just use this hardware for things in which the location is more important
*** eenblam: we should at least get an exitnode on there and random project hosting
*** juul: what if we had scuttlebutt & DAT on ithttps://www.reddit.com/r/all/

* create text for byoi eventbrite (mai)
** haven't done it yet (~_~) going to be gone for a lot of November, would like to hand it off
** benny - I can pick it up

== 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-mesh-github-repos
* benny: grant made lots of progress replacing psychz exitnode with less expensive digital ocean droplet. currently blocked by:
** blocker: need to repoint disaster.radio to a new DO ip address. Who owns the DNS entry? Juul?

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* benny: seth researched LOS to richmond from urban ore
* Follow up with Paxio?
* Archive mount
** ben: let's ask for rackspace
** juul: Would be really cool to peer with the archive, especially as a backup repo of content in the event of Internet going down
*** robb: hell ya!
** dedicating software working group this Thursday to further discussion - 5pm Thursday
** clear LOS from tower to urban ore based on google earth estimates
** discussed reconnecting w/ peef
* request for internets at Village's new site - Edes & Elmhurst
** juul: was going to write a proposal for Calyx subscription - $500/year, put it all in a box and secure it really well and have a mobile source of bandwidth w/ solar panel & battery!
*** widespread support for this idea
* Lesley - will test hardware for Jason. Maybe schedule weekend after next? Also, maybe we should upgrade currently scheduled hardware - he will soon have a fiber gigabit connection, so maybe get new equipment with higher throughput? In whihc case, installation would be delayed
** ben - e.g. a rocket for Benvenue. @lesley feel free to hit me up if you want to coordinate
*** lesley - sure! I was thinking this weekend or next. I need to confirm with Jason though.
*** ben - I'm out of town this weekend, but could work on gear next week and start hitting Benvenue folks up this week.

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
* seth-tshirts
** woo!
* jenny - aaron swartz hackathon - https://www.eventbrite.com/e/aaron-swartz-day-international-hackathon-evening-event-2018-tickets-49082111918
* trip to visit grant's puppet show on wednesday eve! https://www.drivewayfollies.com/ 3854 greenwood ave

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* jenny - deadline for disaster.radio grant work is coming up on Friday - probably going to be hackin on it thurs night

== Next Sunday ==
=== 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: to be determined?

=== 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: Seth
* Notes from this past Sunday's session: x

== Action Items ==
* Get in touch with MonkeyBrains about donated bandwidth (ben)
* Working group to meet and plan out routing config for Archive mount on thursday 5-7
** juul, benny, null, mai, jenny, eenblam, grant, lesley
** send e-mail about richmond tower working group meeting (mai)
* create text for byoi eventbrite (benny)
* create poster for byoi event (benny)
* combine "node mount" and "office hours" sections in notes template (benny)

== Breakout Groups ==
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
*

== Last Meeting Notes ==
* link to previous meeting minutes
https://sudoroom.org/wiki/Mesh/23_October_2018

== End of Meeting ==
* please archive these meeting notes by copying the entire pad contents onto the sudomesh wiki with the correct date format: https://sudoroom.org/wiki/Mesh/30_October_2018
* 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_Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wiki/Mesh/Minutes

[[Category:Mesh/Minutes]]

Mesh/Minutes

2018-10-31T04:08:40Z

Eenblam: 2018-10-30

<center>'''Sudo Mesh Meeting Minutes'''</center>

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/30_October_2018|2018-10-30]]
| Weekly organizing meeting
|-
| [[Mesh/23_October_2018|2018-10-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_October_2018|2018-10-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_October_2018|2018-10-09]]
| Weekly organizing meeting
|-
| [[Mesh/2_October_2018|2018-10-2]]
| Weekly organizing meeting
|-
| [[Mesh/25_September_2018|2018-09-25]]
| Weekly organizing meeting
|-
| [[Mesh/18_September_2018|2018-09-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_September_2018|2018-09-11]]
| Weekly organizing meeting
|-
| [[Mesh/04_September_2018|2018-09-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_August_2018|2018-08-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_August_2018|2018-08-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_August_2018|2018-08-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_August_2018|2018-08-07]]
| Weekly organizing meeting
|-
| [[Mesh/24_July_2018|2018-07-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_July_2018|2018-07-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_July_2018|2018-07-10]]
| Weekly organizing meeting
|-
| [[Mesh/3_July_2018|2018-07-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_June_2018|2018-06-26]]
| Weekly organizing meeting
|-
| [[Mesh/12_June_2018|2018-06-12]]
| Weekly organizing meeting
|-
| [[Mesh/5_June_2018|2018-06-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_May_2018|2018-05-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_May_2018|2018-05-22]]
| Annual Board Meeting
|-
| [[Mesh/15_May_2018|2018-05-15]]
| Weekly organizing meeting & Firmware meeting
|-
| [[Mesh/8_May_2018|2018-05-08]]
| Weekly organizing meeting
|-
| [[Mesh/1_May_2018|2018-05-01]]
| Weekly organizing meeting
|-
| [[Mesh/24_Apr_2018|2018-04-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_Apr_2018|2018-04-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Apr_2018|2018-04-10]]
| Strategic plan meeting
|-
| [[Mesh/03_Apr_2018|2018-04-03]]
| Weekly organizing meeting
|-
| [[Mesh/27_Mar_2018|2018-03-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Mar_2018|2018-03-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_Mar_2018|2018-03-13]]
| Weekly organizing meeting
|-
| [[Mesh/6_Mar_2018|2018-03-06]]
| Weekly organizing meeting
|-
| [[Mesh/27_Feb_2018|2018-02-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Feb_2018|2018-02-20]]
| Weekly organizing meeting
|-
| [[Mesh/17_Feb_2018|2018-02-17]]
| Strategic plan meeting
|-
| [[Mesh/13_Feb_2018|2018-02-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_Feb_2018|2018-02-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_Jan_2018|2018-01-30]]
| Monthly general meeting
|-
| [[Mesh/23_Jan_2018|2018-01-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_Jan_2018|2018-01-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_Jan_2018|2018-01-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_Jan_2018|2018-01-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_Dec_2017|2017-12-26]]
| Monthly general meeting
|-
| [[Mesh/19_Dec_2017|2017-12-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Dec_2017|2017-12-12]]
| Weekly organizing meeting
|-
| [[Mesh/05_Dec_2017|2017-12-05]]
| Weekly organizing meeting
|-
| [[Mesh/28_Nov_2017|2017-11-28]]
| Monthly general meeting
|-
| [[Mesh/21_Nov_2017|2017-11-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_Nov_2017|2017-11-14]]
| Weekly organizing meeting
|-
| [[Mesh/24_Oct_2017|2017-10-24]]
| Monthly general meeting
|-
| [[Mesh/17_Oct_2017|2017-10-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Oct_2017|2017-10-10]]
| Weekly organizing meeting
|-
| [[Mesh/03_Oct_2017|2017-10-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_Sep_2017|2017-09-26]]
| Monthly general meeting
|-
| [[Mesh/19_Sep_2017|2017-09-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Sep_2017|2017-09-12]]
| Weekly organizing meeting
|-
| [[Mesh/11_Sep_2017|2017-09-11]]
| Website redesign session
|-
| [[Mesh/05_Sep_2017|2017-09-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_Aug_2017|2017-08-29]]
| Monthly general meeting
|-
| [[Mesh/22_Aug_2017|2017-08-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_Aug_2017|2017-08-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_Aug_2017|2017-08-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_Aug_2017|2017-08-01]]
| Weekly organizing meeting
|-
| [[Mesh/18_July_2017|2017-07-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_July_2017|2017-07-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_July_2017|2017-07-4]]
| Weekly organizing meeting
|-
| [[Mesh/20_June_2017|2017-06-20]]
| Monthly general meeting
|-
| [[Mesh/13_June_2017|2017-06-13]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2017|2017-06-11]]
| Temescal street fair report-back
|-
| [[Mesh/6_June_2017|2017-06-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_May_2017|2017-05-30]]
| Monthly general meeting
|-
| [[Mesh/16_May_2017|2017-05-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_May_2017|2017-05-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_May_2017|2017-05-02]]
| Weekly organizing meeting
|-
| [[Mesh/25_April_2017|2017-04-25]]
| Monthly general meeting
|-
| [[Mesh/18_April_2017|2017-04-18]]
| Weekly organizing meeting
|-
| [[Mesh/17_April_2017|2017-04-17]]
| Annual sudo mesh board meeting
|-
| [[Mesh/11_April_2017|2017-04-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_April_2017|2017-04-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_March_2017|2017-03-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_March_2017|2017-03-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_March_2017|2017-03-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_March_2017|2017-03-07]]
| Weekly organizing meeting
|-
| [[Mesh/28_February_2017|2017-02-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_February_2017|2017-02-21]]
| Weekly organizing meeting
|-
| [[Mesh/10_February_2017|2017-02-10]]
| Weekly organizing meeting
|-
| [[Mesh/07_February_2017|2017-02-07]]
| Organizing "Build Your Own Internet" Workshop
|-
| [[Mesh/05_July_2016|2016-07-05]]
| Videochat meeting with nycmesh
|-
| [[Mesh/22_June_2016|2016-06-22]]
| Weekly organizing meeting
|-
| [[Mesh/07_June_2016|2016-06-07]]
| Weekly organizing meeting
|-
| [[Mesh/23_February_2016|2016-02-23]]
| Monthly general meeting
|-
| [[Mesh/09_February_2016|2016-02-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_February_2016|2016-02-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_January_2016|2016-01-26]]
| Monthly general meeting
|-
| [[Mesh/27_October_2015|2015-10-27]]
| Monthly general meeting
|-
| [[Mesh/06_October_2015|2015-10-06]]
| Weekly organizing meeting
|-
| [[Mesh/29_September_2015|2015-09-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_September_2015|2015-09-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_September_2015|2015-09-15]]
| Second annual board meeting
|-
| [[Mesh/08_September_2015|2015-09-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_September_2015|2015-09-01]]
| Monthly general meeting
|-
| [[Mesh/07_April_2015|2015-04-07]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2015|2015-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/17_March_2015|2015-03-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_March_2015|2015-03-10]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2015|2015-02-26]]
| Big general meeting
|-
| [[Mesh/24_February_2015|2015-02-24]]
| Hacknight
|-
| [[Mesh/19_February_2015|2015-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/05_February_2015|2015-02-05]]
| Weekly organizing meeting
|-
| [[Mesh/03_February_2015|2015-02-04]]
| Hacknight
|-
| [[Mesh/29_January_2015|2015-01-29]]
| Big general meeting
|-
| [[Mesh/24_January_2015|2015-01-24]]
| Mesh mini-retreat
|-
| [[Mesh/22_January_2015|2015-01-22]]
| Weekly general meeting
|-
| [[Mesh/15_January_2015|2015-01-15]]
| Weekly general meeting
|-
| [[Mesh/30_December_2014|2014-12-30]]
| Big general meeting
|-
| [[Mesh/18_December_2014|2014-12-18]]
| Weekly general meeting
|-
| [[Mesh/13_November_2014|2014-11-13]]
| Weekly general meeting
|-
| [[Mesh/21_October_2014|2014-10-21]]
| Hacknight
|-
| [[Mesh/16_October_2014|2014-10-16]]
| Weekly general meeting
|-
| [[Mesh/09_October_2014|2014-10-09]]
| Weekly general meeting
|-
| [[Mesh/02_October_2014|2014-10-02]]
| Weekly general meeting
|-
| [[Mesh/25_September_2014|2014-09-25]]
| Big general meeting
|-
| [[Mesh/28_August_2014|2014-08-28]]
| Big general meeting
|-
| [[Mesh/21_August_2014|2014-08-21]]
|
|-
| [[Mesh/07_August_2014|2014-08-07]]
|
|-
| [[Mesh/31_July_2014|2014-07-31]]
| Big general meeting
|-
| [[Mesh/17_July_2014|2014-07-17]]
|
|-
| [[Mesh/15_July_2014|2014-07-15]]
|
|-
| [[Mesh/10_July_2014|2014-07-10]]
|
|-
| [[Mesh/06_July_2014|2014-07-06]]
| Hackathon Day 2!
|-
| [[Mesh/05_July_2014|2014-07-05]]
| Hackathon Day 1!
|-
| [[Mesh/03_July_2014|2014-07-03]]
|
|-
| [[Mesh/12_June_2014|2014-06-12]]
|
|-
| [[Mesh/05_June_2014|2014-06-05]]
|
|-
|-
| [[Mesh/29_May_2014|2014-05-29]]
| General meeting
|-
| [[Mesh/27_May_2014|2014-05-27]]
|
|-
| [[Mesh/20_May_2014|2014-05-20]]
|
|-
| [[Mesh/13_May_2014|2014-05-13]]
| First Tuesday meeting ^.^
|-
| [[Mesh/08_May_2014|2014-05-08]]
|
|-
| [[Mesh/01_May_2014|2014-05-01]]
|
|-
| [[Mesh/24_April_2014|2014-04-24]]
| General meeting!
|-
| [[Mesh/17_April_2014|2014-04-17]]
|
|-
| [[Mesh/03_April_2014|2014-04-03]]
|
|-
| [[Mesh/27_March_2014|2014-03-27]]
|
|-
| [[Mesh/20_March_2014|2014-03-20]]
|
|-
| [[Mesh/13_March_2014|2014-03-13]]
|
|-
| [[Mesh/27_February_2014|2014-02-27]]
|
|-
| [[Mesh/20_February_2014|2014-02-20]]
|
|-
| [[Mesh/13_February_2014|2014-02-13]]
|
|-
| [[Mesh/6_February_2014|2014-02-06]]
|
|-
| [[Mesh/30_January_2014|2014-01-30]]
|
|-
| [[Mesh/23_January_2014|2014-01-23]]
|
|-
| [[Mesh/16_January_2014|2014-01-16]]
|
|-
| 31 December - 09 January
| Holidaze Break
|-
| [[Mesh/26_December_2013|2013-12-26]]
|
|-
| [[Mesh/19_December_2013|2013-12-19]]
|
|-
| [[Mesh/12_December_2013|2013-12-12]]
|
|-
| [[Mesh/5_December_2013|2013-12-05]]
|
|-
| [[Mesh/21_November_2013|2013-11-21]]
|
|-
| [[Mesh/14_November_2013|2013-11-14]]
|
|-
| [[Mesh/07_November_2013|2013-11-07]]
|
|-
| [[Mesh/31_October_2013|2013-10-31]]
|
|-
| [[Mesh/24_October_2013|2013-10-24]]
|
|-
| [[Mesh/17_October_2013|2013-10-17]]
|
|-
| [[Mesh/10_October_2013|2013-10-10]]
|
|-
| [[Mesh/26_September_2013|2013-09-26]]
|
|-
| [[Mesh/18_September_2013|2013-09-18]]
|
|-
| [[Mesh/11_September_2013|2013-09-11]]
|
|-
| [[Mesh/4_September_2013|2013-09-04]]
|
|-
| [[Mesh/28_August_2013|2013-08-28]]
|
|-
| 07 August - 21 August
| Hack nights!
|-
| [[Mesh/31_July_2013|2013-07-31]]
|
|-
| [[Mesh/25_July_2013|2013-07-25]]
|
|-
| 18 July 2013
| Hack night: Flashing, firmware
|-
| [[Mesh/11_July_2013|2013-07-11]]
|
|-
| [[Mesh/04_July_2013|2013-07-04]]
|
|-
| [[Mesh/27_June_2013|2013-06-27]]
|
|-
| [[Mesh/20_June_2013|2013-06-20]]
|
|-
| [[Mesh/13_June_2013|2013-06-13]]
|
|-
| 30 May - 05 June
| Hack nights! Trying out some of the nicer Ubiquiti equipment we procured
|-
| [[Mesh/23_May_2013|2013-05-23]]
|
|-
| [[Mesh/09_May_2013|2013-05-09]]
|
|-
| 25 April - 02 May
| Hack nights! See wiki for documentation - principally going through donated routers, flashing them with OpenWRT and installing batman-adv.
|-
| [[Mesh/18_April_2013|2013-04-18]]
|
|-
| [[Mesh/11_April_2013|2013-04-11]]
|
|-
| 28 March - 04 April
| SPRING SHIFT HIATUS
|-
| [[Mesh/21_March_2013|2013-03-21]]
|
|-
| [[Mesh/07_March_2013|2013-03-07]]
|
|-
| [[Mesh/28_February_2013|2013-02-28]]
|
|-
| [[Mesh/21_February_2013|2013-02-21]]
|
|-
| [[Mesh/14_February_2013|2013-02-14]]
|
|-
| [[Mesh/7_February_2013|2013-02-07]]
|
|-
| [http://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html 2013-01-31]
|
|}

Mesh/Minutes

2018-09-05T04:19:39Z

Eenblam: Remove redundant page list

<center>'''Sudo Mesh Meeting Minutes'''</center>

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/04_September_2018|2018-09-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_August_2018|2018-08-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_August_2018|2018-08-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_August_2018|2018-08-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_August_2018|2018-08-07]]
| Weekly organizing meeting
|-
| [[Mesh/24_July_2018|2018-07-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_July_2018|2018-07-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_July_2018|2018-07-10]]
| Weekly organizing meeting
|-
| [[Mesh/3_July_2018|2018-07-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_June_2018|2018-06-26]]
| Weekly organizing meeting
|-
| [[Mesh/12_June_2018|2018-06-12]]
| Weekly organizing meeting
|-
| [[Mesh/5_June_2018|2018-06-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_May_2018|2018-05-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_May_2018|2018-05-22]]
| Annual Board Meeting
|-
| [[Mesh/15_May_2018|2018-05-15]]
| Weekly organizing meeting & Firmware meeting
|-
| [[Mesh/8_May_2018|2018-05-08]]
| Weekly organizing meeting
|-
| [[Mesh/1_May_2018|2018-05-01]]
| Weekly organizing meeting
|-
| [[Mesh/24_Apr_2018|2018-04-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_Apr_2018|2018-04-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Apr_2018|2018-04-10]]
| Strategic plan meeting
|-
| [[Mesh/03_Apr_2018|2018-04-03]]
| Weekly organizing meeting
|-
| [[Mesh/27_Mar_2018|2018-03-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Mar_2018|2018-03-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_Mar_2018|2018-03-13]]
| Weekly organizing meeting
|-
| [[Mesh/6_Mar_2018|2018-03-06]]
| Weekly organizing meeting
|-
| [[Mesh/27_Feb_2018|2018-02-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Feb_2018|2018-02-20]]
| Weekly organizing meeting
|-
| [[Mesh/17_Feb_2018|2018-02-17]]
| Strategic plan meeting
|-
| [[Mesh/13_Feb_2018|2018-02-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_Feb_2018|2018-02-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_Jan_2018|2018-01-30]]
| Monthly general meeting
|-
| [[Mesh/23_Jan_2018|2018-01-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_Jan_2018|2018-01-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_Jan_2018|2018-01-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_Jan_2018|2018-01-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_Dec_2017|2017-12-26]]
| Monthly general meeting
|-
| [[Mesh/19_Dec_2017|2017-12-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Dec_2017|2017-12-12]]
| Weekly organizing meeting
|-
| [[Mesh/05_Dec_2017|2017-12-05]]
| Weekly organizing meeting
|-
| [[Mesh/28_Nov_2017|2017-11-28]]
| Monthly general meeting
|-
| [[Mesh/21_Nov_2017|2017-11-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_Nov_2017|2017-11-14]]
| Weekly organizing meeting
|-
| [[Mesh/24_Oct_2017|2017-10-24]]
| Monthly general meeting
|-
| [[Mesh/17_Oct_2017|2017-10-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Oct_2017|2017-10-10]]
| Weekly organizing meeting
|-
| [[Mesh/03_Oct_2017|2017-10-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_Sep_2017|2017-09-26]]
| Monthly general meeting
|-
| [[Mesh/19_Sep_2017|2017-09-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Sep_2017|2017-09-12]]
| Weekly organizing meeting
|-
| [[Mesh/11_Sep_2017|2017-09-11]]
| Website redesign session
|-
| [[Mesh/05_Sep_2017|2017-09-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_Aug_2017|2017-08-29]]
| Monthly general meeting
|-
| [[Mesh/22_Aug_2017|2017-08-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_Aug_2017|2017-08-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_Aug_2017|2017-08-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_Aug_2017|2017-08-01]]
| Weekly organizing meeting
|-
| [[Mesh/18_July_2017|2017-07-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_July_2017|2017-07-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_July_2017|2017-07-4]]
| Weekly organizing meeting
|-
| [[Mesh/20_June_2017|2017-06-20]]
| Monthly general meeting
|-
| [[Mesh/13_June_2017|2017-06-13]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2017|2017-06-11]]
| Temescal street fair report-back
|-
| [[Mesh/6_June_2017|2017-06-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_May_2017|2017-05-30]]
| Monthly general meeting
|-
| [[Mesh/16_May_2017|2017-05-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_May_2017|2017-05-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_May_2017|2017-05-02]]
| Weekly organizing meeting
|-
| [[Mesh/25_April_2017|2017-04-25]]
| Monthly general meeting
|-
| [[Mesh/18_April_2017|2017-04-18]]
| Weekly organizing meeting
|-
| [[Mesh/17_April_2017|2017-04-17]]
| Annual sudo mesh board meeting
|-
| [[Mesh/11_April_2017|2017-04-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_April_2017|2017-04-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_March_2017|2017-03-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_March_2017|2017-03-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_March_2017|2017-03-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_March_2017|2017-03-07]]
| Weekly organizing meeting
|-
| [[Mesh/28_February_2017|2017-02-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_February_2017|2017-02-21]]
| Weekly organizing meeting
|-
| [[Mesh/10_February_2017|2017-02-10]]
| Weekly organizing meeting
|-
| [[Mesh/07_February_2017|2017-02-07]]
| Organizing "Build Your Own Internet" Workshop
|-
| [[Mesh/05_July_2016|2016-07-05]]
| Videochat meeting with nycmesh
|-
| [[Mesh/22_June_2016|2016-06-22]]
| Weekly organizing meeting
|-
| [[Mesh/07_June_2016|2016-06-07]]
| Weekly organizing meeting
|-
| [[Mesh/23_February_2016|2016-02-23]]
| Monthly general meeting
|-
| [[Mesh/09_February_2016|2016-02-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_February_2016|2016-02-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_January_2016|2016-01-26]]
| Monthly general meeting
|-
| [[Mesh/27_October_2015|2015-10-27]]
| Monthly general meeting
|-
| [[Mesh/06_October_2015|2015-10-06]]
| Weekly organizing meeting
|-
| [[Mesh/29_September_2015|2015-09-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_September_2015|2015-09-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_September_2015|2015-09-15]]
| Second annual board meeting
|-
| [[Mesh/08_September_2015|2015-09-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_September_2015|2015-09-01]]
| Monthly general meeting
|-
| [[Mesh/07_April_2015|2015-04-07]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2015|2015-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/17_March_2015|2015-03-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_March_2015|2015-03-10]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2015|2015-02-26]]
| Big general meeting
|-
| [[Mesh/24_February_2015|2015-02-24]]
| Hacknight
|-
| [[Mesh/19_February_2015|2015-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/05_February_2015|2015-02-05]]
| Weekly organizing meeting
|-
| [[Mesh/03_February_2015|2015-02-04]]
| Hacknight
|-
| [[Mesh/29_January_2015|2015-01-29]]
| Big general meeting
|-
| [[Mesh/24_January_2015|2015-01-24]]
| Mesh mini-retreat
|-
| [[Mesh/22_January_2015|2015-01-22]]
| Weekly general meeting
|-
| [[Mesh/15_January_2015|2015-01-15]]
| Weekly general meeting
|-
| [[Mesh/30_December_2014|2014-12-30]]
| Big general meeting
|-
| [[Mesh/18_December_2014|2014-12-18]]
| Weekly general meeting
|-
| [[Mesh/13_November_2014|2014-11-13]]
| Weekly general meeting
|-
| [[Mesh/21_October_2014|2014-10-21]]
| Hacknight
|-
| [[Mesh/16_October_2014|2014-10-16]]
| Weekly general meeting
|-
| [[Mesh/09_October_2014|2014-10-09]]
| Weekly general meeting
|-
| [[Mesh/02_October_2014|2014-10-02]]
| Weekly general meeting
|-
| [[Mesh/25_September_2014|2014-09-25]]
| Big general meeting
|-
| [[Mesh/28_August_2014|2014-08-28]]
| Big general meeting
|-
| [[Mesh/21_August_2014|2014-08-21]]
|
|-
| [[Mesh/07_August_2014|2014-08-07]]
|
|-
| [[Mesh/31_July_2014|2014-07-31]]
| Big general meeting
|-
| [[Mesh/17_July_2014|2014-07-17]]
|
|-
| [[Mesh/15_July_2014|2014-07-15]]
|
|-
| [[Mesh/10_July_2014|2014-07-10]]
|
|-
| [[Mesh/06_July_2014|2014-07-06]]
| Hackathon Day 2!
|-
| [[Mesh/05_July_2014|2014-07-05]]
| Hackathon Day 1!
|-
| [[Mesh/03_July_2014|2014-07-03]]
|
|-
| [[Mesh/12_June_2014|2014-06-12]]
|
|-
| [[Mesh/05_June_2014|2014-06-05]]
|
|-
|-
| [[Mesh/29_May_2014|2014-05-29]]
| General meeting
|-
| [[Mesh/27_May_2014|2014-05-27]]
|
|-
| [[Mesh/20_May_2014|2014-05-20]]
|
|-
| [[Mesh/13_May_2014|2014-05-13]]
| First Tuesday meeting ^.^
|-
| [[Mesh/08_May_2014|2014-05-08]]
|
|-
| [[Mesh/01_May_2014|2014-05-01]]
|
|-
| [[Mesh/24_April_2014|2014-04-24]]
| General meeting!
|-
| [[Mesh/17_April_2014|2014-04-17]]
|
|-
| [[Mesh/03_April_2014|2014-04-03]]
|
|-
| [[Mesh/27_March_2014|2014-03-27]]
|
|-
| [[Mesh/20_March_2014|2014-03-20]]
|
|-
| [[Mesh/13_March_2014|2014-03-13]]
|
|-
| [[Mesh/27_February_2014|2014-02-27]]
|
|-
| [[Mesh/20_February_2014|2014-02-20]]
|
|-
| [[Mesh/13_February_2014|2014-02-13]]
|
|-
| [[Mesh/6_February_2014|2014-02-06]]
|
|-
| [[Mesh/30_January_2014|2014-01-30]]
|
|-
| [[Mesh/23_January_2014|2014-01-23]]
|
|-
| [[Mesh/16_January_2014|2014-01-16]]
|
|-
| 31 December - 09 January
| Holidaze Break
|-
| [[Mesh/26_December_2013|2013-12-26]]
|
|-
| [[Mesh/19_December_2013|2013-12-19]]
|
|-
| [[Mesh/12_December_2013|2013-12-12]]
|
|-
| [[Mesh/5_December_2013|2013-12-05]]
|
|-
| [[Mesh/21_November_2013|2013-11-21]]
|
|-
| [[Mesh/14_November_2013|2013-11-14]]
|
|-
| [[Mesh/07_November_2013|2013-11-07]]
|
|-
| [[Mesh/31_October_2013|2013-10-31]]
|
|-
| [[Mesh/24_October_2013|2013-10-24]]
|
|-
| [[Mesh/17_October_2013|2013-10-17]]
|
|-
| [[Mesh/10_October_2013|2013-10-10]]
|
|-
| [[Mesh/26_September_2013|2013-09-26]]
|
|-
| [[Mesh/18_September_2013|2013-09-18]]
|
|-
| [[Mesh/11_September_2013|2013-09-11]]
|
|-
| [[Mesh/4_September_2013|2013-09-04]]
|
|-
| [[Mesh/28_August_2013|2013-08-28]]
|
|-
| 07 August - 21 August
| Hack nights!
|-
| [[Mesh/31_July_2013|2013-07-31]]
|
|-
| [[Mesh/25_July_2013|2013-07-25]]
|
|-
| 18 July 2013
| Hack night: Flashing, firmware
|-
| [[Mesh/11_July_2013|2013-07-11]]
|
|-
| [[Mesh/04_July_2013|2013-07-04]]
|
|-
| [[Mesh/27_June_2013|2013-06-27]]
|
|-
| [[Mesh/20_June_2013|2013-06-20]]
|
|-
| [[Mesh/13_June_2013|2013-06-13]]
|
|-
| 30 May - 05 June
| Hack nights! Trying out some of the nicer Ubiquiti equipment we procured
|-
| [[Mesh/23_May_2013|2013-05-23]]
|
|-
| [[Mesh/09_May_2013|2013-05-09]]
|
|-
| 25 April - 02 May
| Hack nights! See wiki for documentation - principally going through donated routers, flashing them with OpenWRT and installing batman-adv.
|-
| [[Mesh/18_April_2013|2013-04-18]]
|
|-
| [[Mesh/11_April_2013|2013-04-11]]
|
|-
| 28 March - 04 April
| SPRING SHIFT HIATUS
|-
| [[Mesh/21_March_2013|2013-03-21]]
|
|-
| [[Mesh/07_March_2013|2013-03-07]]
|
|-
| [[Mesh/28_February_2013|2013-02-28]]
|
|-
| [[Mesh/21_February_2013|2013-02-21]]
|
|-
| [[Mesh/14_February_2013|2013-02-14]]
|
|-
| [[Mesh/7_February_2013|2013-02-07]]
|
|-
| [http://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html 2013-01-31]
|
|}

Mesh/Minutes

2018-09-05T04:19:21Z

Eenblam: Add 09/04/2018

<center>'''Sudo Mesh Meeting Minutes'''</center>

<DynamicPageList>
category = Mesh/Minutes
order = descending
</DynamicPageList>

{| class="wikitable sortable collapsible"
! colspan="2"| Past Meeting Notes
|-
! data-sort-type="isoDate" | date
! class="unsortable" | comments
|-
| [[Mesh/04_September_2018|2018-09-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_August_2018|2018-08-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_August_2018|2018-08-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_August_2018|2018-08-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_August_2018|2018-08-07]]
| Weekly organizing meeting
|-
| [[Mesh/24_July_2018|2018-07-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_July_2018|2018-07-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_July_2018|2018-07-10]]
| Weekly organizing meeting
|-
| [[Mesh/3_July_2018|2018-07-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_June_2018|2018-06-26]]
| Weekly organizing meeting
|-
| [[Mesh/12_June_2018|2018-06-12]]
| Weekly organizing meeting
|-
| [[Mesh/5_June_2018|2018-06-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_May_2018|2018-05-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_May_2018|2018-05-22]]
| Annual Board Meeting
|-
| [[Mesh/15_May_2018|2018-05-15]]
| Weekly organizing meeting & Firmware meeting
|-
| [[Mesh/8_May_2018|2018-05-08]]
| Weekly organizing meeting
|-
| [[Mesh/1_May_2018|2018-05-01]]
| Weekly organizing meeting
|-
| [[Mesh/24_Apr_2018|2018-04-24]]
| Weekly organizing meeting
|-
| [[Mesh/17_Apr_2018|2018-04-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Apr_2018|2018-04-10]]
| Strategic plan meeting
|-
| [[Mesh/03_Apr_2018|2018-04-03]]
| Weekly organizing meeting
|-
| [[Mesh/27_Mar_2018|2018-03-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Mar_2018|2018-03-20]]
| Weekly organizing meeting
|-
| [[Mesh/13_Mar_2018|2018-03-13]]
| Weekly organizing meeting
|-
| [[Mesh/6_Mar_2018|2018-03-06]]
| Weekly organizing meeting
|-
| [[Mesh/27_Feb_2018|2018-02-27]]
| Weekly organizing meeting
|-
| [[Mesh/20_Feb_2018|2018-02-20]]
| Weekly organizing meeting
|-
| [[Mesh/17_Feb_2018|2018-02-17]]
| Strategic plan meeting
|-
| [[Mesh/13_Feb_2018|2018-02-13]]
| Weekly organizing meeting
|-
| [[Mesh/06_Feb_2018|2018-02-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_Jan_2018|2018-01-30]]
| Monthly general meeting
|-
| [[Mesh/23_Jan_2018|2018-01-23]]
| Weekly organizing meeting
|-
| [[Mesh/16_Jan_2018|2018-01-16]]
| Weekly organizing meeting
|-
| [[Mesh/09_Jan_2018|2018-01-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_Jan_2018|2018-01-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_Dec_2017|2017-12-26]]
| Monthly general meeting
|-
| [[Mesh/19_Dec_2017|2017-12-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Dec_2017|2017-12-12]]
| Weekly organizing meeting
|-
| [[Mesh/05_Dec_2017|2017-12-05]]
| Weekly organizing meeting
|-
| [[Mesh/28_Nov_2017|2017-11-28]]
| Monthly general meeting
|-
| [[Mesh/21_Nov_2017|2017-11-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_Nov_2017|2017-11-14]]
| Weekly organizing meeting
|-
| [[Mesh/24_Oct_2017|2017-10-24]]
| Monthly general meeting
|-
| [[Mesh/17_Oct_2017|2017-10-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_Oct_2017|2017-10-10]]
| Weekly organizing meeting
|-
| [[Mesh/03_Oct_2017|2017-10-03]]
| Weekly organizing meeting
|-
| [[Mesh/26_Sep_2017|2017-09-26]]
| Monthly general meeting
|-
| [[Mesh/19_Sep_2017|2017-09-19]]
| Weekly organizing meeting
|-
| [[Mesh/12_Sep_2017|2017-09-12]]
| Weekly organizing meeting
|-
| [[Mesh/11_Sep_2017|2017-09-11]]
| Website redesign session
|-
| [[Mesh/05_Sep_2017|2017-09-05]]
| Weekly organizing meeting
|-
| [[Mesh/29_Aug_2017|2017-08-29]]
| Monthly general meeting
|-
| [[Mesh/22_Aug_2017|2017-08-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_Aug_2017|2017-08-15]]
| Weekly organizing meeting
|-
| [[Mesh/08_Aug_2017|2017-08-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_Aug_2017|2017-08-01]]
| Weekly organizing meeting
|-
| [[Mesh/18_July_2017|2017-07-18]]
| Weekly organizing meeting
|-
| [[Mesh/11_July_2017|2017-07-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_July_2017|2017-07-4]]
| Weekly organizing meeting
|-
| [[Mesh/20_June_2017|2017-06-20]]
| Monthly general meeting
|-
| [[Mesh/13_June_2017|2017-06-13]]
| Weekly organizing meeting
|-
| [[Mesh/11_June_2017|2017-06-11]]
| Temescal street fair report-back
|-
| [[Mesh/6_June_2017|2017-06-06]]
| Weekly organizing meeting
|-
| [[Mesh/30_May_2017|2017-05-30]]
| Monthly general meeting
|-
| [[Mesh/16_May_2017|2017-05-16]]
| Weekly organizing meeting
|-
| [[Mesh/9_May_2017|2017-05-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_May_2017|2017-05-02]]
| Weekly organizing meeting
|-
| [[Mesh/25_April_2017|2017-04-25]]
| Monthly general meeting
|-
| [[Mesh/18_April_2017|2017-04-18]]
| Weekly organizing meeting
|-
| [[Mesh/17_April_2017|2017-04-17]]
| Annual sudo mesh board meeting
|-
| [[Mesh/11_April_2017|2017-04-11]]
| Weekly organizing meeting
|-
| [[Mesh/4_April_2017|2017-04-04]]
| Weekly organizing meeting
|-
| [[Mesh/28_March_2017|2017-03-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_March_2017|2017-03-21]]
| Weekly organizing meeting
|-
| [[Mesh/14_March_2017|2017-03-14]]
| Weekly organizing meeting
|-
| [[Mesh/07_March_2017|2017-03-07]]
| Weekly organizing meeting
|-
| [[Mesh/28_February_2017|2017-02-28]]
| Weekly organizing meeting
|-
| [[Mesh/21_February_2017|2017-02-21]]
| Weekly organizing meeting
|-
| [[Mesh/10_February_2017|2017-02-10]]
| Weekly organizing meeting
|-
| [[Mesh/07_February_2017|2017-02-07]]
| Organizing "Build Your Own Internet" Workshop
|-
| [[Mesh/05_July_2016|2016-07-05]]
| Videochat meeting with nycmesh
|-
| [[Mesh/22_June_2016|2016-06-22]]
| Weekly organizing meeting
|-
| [[Mesh/07_June_2016|2016-06-07]]
| Weekly organizing meeting
|-
| [[Mesh/23_February_2016|2016-02-23]]
| Monthly general meeting
|-
| [[Mesh/09_February_2016|2016-02-09]]
| Weekly organizing meeting
|-
| [[Mesh/02_February_2016|2016-02-02]]
| Weekly organizing meeting
|-
| [[Mesh/26_January_2016|2016-01-26]]
| Monthly general meeting
|-
| [[Mesh/27_October_2015|2015-10-27]]
| Monthly general meeting
|-
| [[Mesh/06_October_2015|2015-10-06]]
| Weekly organizing meeting
|-
| [[Mesh/29_September_2015|2015-09-29]]
| Weekly organizing meeting
|-
| [[Mesh/22_September_2015|2015-09-22]]
| Weekly organizing meeting
|-
| [[Mesh/15_September_2015|2015-09-15]]
| Second annual board meeting
|-
| [[Mesh/08_September_2015|2015-09-08]]
| Weekly organizing meeting
|-
| [[Mesh/01_September_2015|2015-09-01]]
| Monthly general meeting
|-
| [[Mesh/07_April_2015|2015-04-07]]
| Weekly organizing meeting
|-
| [[Mesh/26_March_2015|2015-03-26]]
| Weekly organizing meeting
|-
| [[Mesh/17_March_2015|2015-03-17]]
| Weekly organizing meeting
|-
| [[Mesh/10_March_2015|2015-03-10]]
| Weekly organizing meeting
|-
| [[Mesh/26_February_2015|2015-02-26]]
| Big general meeting
|-
| [[Mesh/24_February_2015|2015-02-24]]
| Hacknight
|-
| [[Mesh/19_February_2015|2015-02-19]]
| Weekly organizing meeting
|-
| [[Mesh/05_February_2015|2015-02-05]]
| Weekly organizing meeting
|-
| [[Mesh/03_February_2015|2015-02-04]]
| Hacknight
|-
| [[Mesh/29_January_2015|2015-01-29]]
| Big general meeting
|-
| [[Mesh/24_January_2015|2015-01-24]]
| Mesh mini-retreat
|-
| [[Mesh/22_January_2015|2015-01-22]]
| Weekly general meeting
|-
| [[Mesh/15_January_2015|2015-01-15]]
| Weekly general meeting
|-
| [[Mesh/30_December_2014|2014-12-30]]
| Big general meeting
|-
| [[Mesh/18_December_2014|2014-12-18]]
| Weekly general meeting
|-
| [[Mesh/13_November_2014|2014-11-13]]
| Weekly general meeting
|-
| [[Mesh/21_October_2014|2014-10-21]]
| Hacknight
|-
| [[Mesh/16_October_2014|2014-10-16]]
| Weekly general meeting
|-
| [[Mesh/09_October_2014|2014-10-09]]
| Weekly general meeting
|-
| [[Mesh/02_October_2014|2014-10-02]]
| Weekly general meeting
|-
| [[Mesh/25_September_2014|2014-09-25]]
| Big general meeting
|-
| [[Mesh/28_August_2014|2014-08-28]]
| Big general meeting
|-
| [[Mesh/21_August_2014|2014-08-21]]
|
|-
| [[Mesh/07_August_2014|2014-08-07]]
|
|-
| [[Mesh/31_July_2014|2014-07-31]]
| Big general meeting
|-
| [[Mesh/17_July_2014|2014-07-17]]
|
|-
| [[Mesh/15_July_2014|2014-07-15]]
|
|-
| [[Mesh/10_July_2014|2014-07-10]]
|
|-
| [[Mesh/06_July_2014|2014-07-06]]
| Hackathon Day 2!
|-
| [[Mesh/05_July_2014|2014-07-05]]
| Hackathon Day 1!
|-
| [[Mesh/03_July_2014|2014-07-03]]
|
|-
| [[Mesh/12_June_2014|2014-06-12]]
|
|-
| [[Mesh/05_June_2014|2014-06-05]]
|
|-
|-
| [[Mesh/29_May_2014|2014-05-29]]
| General meeting
|-
| [[Mesh/27_May_2014|2014-05-27]]
|
|-
| [[Mesh/20_May_2014|2014-05-20]]
|
|-
| [[Mesh/13_May_2014|2014-05-13]]
| First Tuesday meeting ^.^
|-
| [[Mesh/08_May_2014|2014-05-08]]
|
|-
| [[Mesh/01_May_2014|2014-05-01]]
|
|-
| [[Mesh/24_April_2014|2014-04-24]]
| General meeting!
|-
| [[Mesh/17_April_2014|2014-04-17]]
|
|-
| [[Mesh/03_April_2014|2014-04-03]]
|
|-
| [[Mesh/27_March_2014|2014-03-27]]
|
|-
| [[Mesh/20_March_2014|2014-03-20]]
|
|-
| [[Mesh/13_March_2014|2014-03-13]]
|
|-
| [[Mesh/27_February_2014|2014-02-27]]
|
|-
| [[Mesh/20_February_2014|2014-02-20]]
|
|-
| [[Mesh/13_February_2014|2014-02-13]]
|
|-
| [[Mesh/6_February_2014|2014-02-06]]
|
|-
| [[Mesh/30_January_2014|2014-01-30]]
|
|-
| [[Mesh/23_January_2014|2014-01-23]]
|
|-
| [[Mesh/16_January_2014|2014-01-16]]
|
|-
| 31 December - 09 January
| Holidaze Break
|-
| [[Mesh/26_December_2013|2013-12-26]]
|
|-
| [[Mesh/19_December_2013|2013-12-19]]
|
|-
| [[Mesh/12_December_2013|2013-12-12]]
|
|-
| [[Mesh/5_December_2013|2013-12-05]]
|
|-
| [[Mesh/21_November_2013|2013-11-21]]
|
|-
| [[Mesh/14_November_2013|2013-11-14]]
|
|-
| [[Mesh/07_November_2013|2013-11-07]]
|
|-
| [[Mesh/31_October_2013|2013-10-31]]
|
|-
| [[Mesh/24_October_2013|2013-10-24]]
|
|-
| [[Mesh/17_October_2013|2013-10-17]]
|
|-
| [[Mesh/10_October_2013|2013-10-10]]
|
|-
| [[Mesh/26_September_2013|2013-09-26]]
|
|-
| [[Mesh/18_September_2013|2013-09-18]]
|
|-
| [[Mesh/11_September_2013|2013-09-11]]
|
|-
| [[Mesh/4_September_2013|2013-09-04]]
|
|-
| [[Mesh/28_August_2013|2013-08-28]]
|
|-
| 07 August - 21 August
| Hack nights!
|-
| [[Mesh/31_July_2013|2013-07-31]]
|
|-
| [[Mesh/25_July_2013|2013-07-25]]
|
|-
| 18 July 2013
| Hack night: Flashing, firmware
|-
| [[Mesh/11_July_2013|2013-07-11]]
|
|-
| [[Mesh/04_July_2013|2013-07-04]]
|
|-
| [[Mesh/27_June_2013|2013-06-27]]
|
|-
| [[Mesh/20_June_2013|2013-06-20]]
|
|-
| [[Mesh/13_June_2013|2013-06-13]]
|
|-
| 30 May - 05 June
| Hack nights! Trying out some of the nicer Ubiquiti equipment we procured
|-
| [[Mesh/23_May_2013|2013-05-23]]
|
|-
| [[Mesh/09_May_2013|2013-05-09]]
|
|-
| 25 April - 02 May
| Hack nights! See wiki for documentation - principally going through donated routers, flashing them with OpenWRT and installing batman-adv.
|-
| [[Mesh/18_April_2013|2013-04-18]]
|
|-
| [[Mesh/11_April_2013|2013-04-11]]
|
|-
| 28 March - 04 April
| SPRING SHIFT HIATUS
|-
| [[Mesh/21_March_2013|2013-03-21]]
|
|-
| [[Mesh/07_March_2013|2013-03-07]]
|
|-
| [[Mesh/28_February_2013|2013-02-28]]
|
|-
| [[Mesh/21_February_2013|2013-02-21]]
|
|-
| [[Mesh/14_February_2013|2013-02-14]]
|
|-
| [[Mesh/7_February_2013|2013-02-07]]
|
|-
| [http://lists.sudoroom.org/pipermail/mesh/2013-January/000000.html 2013-01-31]
|
|}

Mesh/04 September 2018

2018-09-05T04:16:13Z

Eenblam: created!

'''People's Open Network Weekly Meeting - 4 Sep 2018 7:30pm-9pm'''
* https://omnicommons.org/wiki/Safer_Space_Policy

=== Agenda ===
* Introductions and Meeting Roles (10 mins)
* Check in on previous action items (5 mins)
* Updates & Reportbacks (20 mins)
* Next Sunday (5 mins)
* Proposal: Handshake Distribution (5 mins)
* Discussion: Brainstorm Places to Email re: Internet Archive LoS (15 mins)
* Discussion: Project Proposal Process (15 mins)
* Action Items (5 mins)
* Breakout Groups

=== Introductions ===
Introduce yourself: Name; Preferred Pronoun; Icebreaker Response; BRIEF Announcements
* Icebreaker question: What was your favorite class in high school? (Recess okay)
* scott - don't care about pronouns - physics or chemistry
* benny - he/him - creative writing
* jenny - she/her - history, read howard zinn, shaped me
* eve - french
* mai - she/they - toss up between spanish and philosophy, which i had to take because it was a catholic school
* null - them/they - not sure... math?
* mickey - he/him - really liked theater
** I'm a report for oakland north, writing a story about sudomesh
* marc - he/him - math
* eenblam - he/they - started out liking math, but didn't like it by the time i finished.
** John and Jeff are now meshing! They also have a spare (configured) node for another neighbor. Jeff's extender is still up and has LoS to Jason's roof. Interested in upgrading Jeff's extender to a NSM5 or a Rocket M5.
** https://github.com/sudomesh/onboarding exists (choose your own adventure onboarding, inspired by mozilla: whatcanidoformozilla.org)
** if you have ideas for pathways, please add them!

=== Meeting Roles ===
* Facilitator/s: eenblam
* Stacktaker: benny
* Timekeeper:
* Notetaker/s: jenny, juul, mai
** URL of this pad: https://peoplesopen.net/notes

== Check in on previous action items ==
Check previous meeting minutes at https://sudoroom.org/wiki/Mesh/Minutes and past action items below:
* review grant's e-mail draft to other community spaces re: a tall building in richmond (mai)
** moved to discussion
* follow up with jonah of the Archive (jenny)
** No reply; will try again
* ask noisebridge / Friendly Local ISP about their laser (eenblam)
** eenblam - Message dispatched!
** Never heard back from FLISP
* calendar item to test the AirFibers on Sep 9 (all)
** Marc - first node arrived today, next node should arrive Friday, but may be delayed
** bump to next week
* check in on Handshake $ (jenny)
** It's in our bank account! Screenshot in rocket.chat. There is a big number in the screenshot.
* summarize consensus-making process from this meeting (benny)
** benny - Didn't do it. I think mai did this in loomio.
** mai - added it to discussion; jorrit added some good points to the discussion
* put 1) grant spending 2) Handshake award on loomio (jenny)
** (#1 was posted by Mai, above: https://www.loomio.org/d/YuC1wIps/how-we-make-decisions)
** https://www.loomio.org/p/0BHnsDu7/what-percentage-of-the-donation-should-go-to-each-group-

== 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-mesh-github-repos
* ben - debugging firmware builds, made some progress. still need to test built firmware on node.
* mai - mary jo and terry are still down
** benny - I can follow up with Chuck again. Making an action item.
* jenny - added labels to disaster.radio issues

=== Node Mounts & Outreach ===
Node Mounts Trello: https://trello.com/invite/b/DtzngKaM/49e1c21fc9da199fcdeceb8623b5117a/node-mounts
* to schedule: jason's (lesley out tonight)
* ben: anything else re: airfibers?
* marc: might need to discuss how to mount / what we need to buy in order to mount the airfiber to top of omni. weighted base would have to be really big. maybe just a pole mounted to the building (platform above disco room). will look into costs for tall weighted base
* email out to lists re: being hop location for Archive link

=== Communications & Events ===
Comms Trello: https://trello.com/invite/b/f3ugMPNU/94033ee6c2cef93fc1b1637b727c902a/sudo-mesh-communications // Events Trello: https://trello.com/invite/b/Y3XfDK85/2b6fcb4fa92788609692a53a96fb4614/peoples-open-events
* benny - made loomio for planning the next BYOI in november (https://www.loomio.org/d/0h914dO3/byoi-fall-2018)
* jenny - heard back from Gunner (re Aspiration conf) about fear of having too many registrations using guest codes in the past, leading to no-shows. They want to be sure folks show up if they register. Opening a Loomio thread for making a donation to the event.
* marc - institute for the future anniversary event invited disaster radio to present / talk to people. The event is mostly for their funders -- $5000 tickets. jenny and i won't be in until the two last days, and grant is working that whole time, so we're looking for one or two people who are interested in coming to the event, and we need to figure out what we're going to show. announcing if people are interested in institute for the future stuff. September 25-27.
* jenny - marc and I will be in Denmark
* mai - I will be in DC from the 23rd-27th
* scott - I might be able to do it

=== Internal Logistics / Finance ===
Internal Logistics & Bureaucracy Trello: https://trello.com/invite/b/LzVQlW3X/1bb8bd543c8633688175365d2554c2c2/internal-logistics-bureaucracy-brainstorms
* Purchase:
** Binoculars?
* Quickbooks Training Workshop next Thursday, 09/13, from 3-5pm. Ping jenny to rsvp if you didn't participate in the Doodle
*

== Next Sunday ==
=== 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: airfiber testing!
* jnny - I heard back from dmitri from sailing club; now awaiting an email from their tech person. Possible site survey on Sunday.
** null - I'm interested in going
* benny - cassady showed interest! we filled out a mount request together.
** is very close to w oak cluster - may have LOS to Hearth or node0 @ LiveLabs

=== 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 (and marc will be here testing airfibers)
* mai - side note: oakland pride is this Sunday
* Notes from this past Sunday's session:
* mai ben and cassady worked on stuff

== Proposal: Handshake Split ==
Please add any proposal needing consent from or action by the group below:
* Loomio decision was 60-10-30 split between Sudo Mesh / Sudo Room / Omni. Consenso?\
* unanimous agreement!

== Discussion: Internet Archive LoS ==
* Draft email to blast to hacker lists: https://peoplesopen.net/pad/p/ia-email-blast
** Where should we send this and who signs up for each list?
** sudo-discuss@lists.sudoroom.org, mesh@lists.sudoroom.org, noisebridge-discuss@lists.noisebridge.net, info@acemonstertoys.org, info@hackermoms.org, cclmembers@googlegroups.com
** https://www.acemonstertoys.org/contact-us/#Slack
** maybe post to Nextdoor in neighborhoods with ideal LOS
* Are we giving the airFibers to those who offer up their place?
* Mai: I think we should require whoever we go with to own the property or have explicit permission from the property owner. And probably sign a lease so we can rest assured that the equipment/bandwidth won't just disappear without us knowing about it.
** eenblam - Some comments made in rocket.chat re: ownership of deployed gear
*** > As is the way with People's Open, you would own and operate the equipment and, of course, have full access to the gigabits of donated bandwidth. An airFiber relay would be at least two devices.
*** Are we giving away two airFibers with the hope that the recipient will indefinitely relay bandwidth for us?
*** I feel like people owning and operating mesh nodes, even a nice rocket+antenna combo, makes sense and is ideal. But relay infrastructure like this feels like a different story (and costs 15x to 20x as much) and (given the nature of the PtP links) isn't a way for them to connect with their immediate community, just with us.
* scott- some amount of notice to take them down?
* juul - how about a month, which is how much notice renters get
* ben - if it's a relay site, cost will be ~$5000 just in backhaul equipment (eg 2 airFibers, a rocket AP, switch, UPS, etc)
* mai - there's some legal thing where if you exchange money the contract is more valid/enforceable
** marc - contracts can't be one-way; there has to be some kind of give-back.
** Seems like there's give-back since they get free bandwidth.
* benny - we can just negotiate that once we have interest
* jenny - we should just delete that particular part for now
* mai - should mention needing explicit permision from property owner in writing? (yes's)
* benny - should we mention that we can give something in return - network assistance, computer assistance, privacy training, etc? Depending on org that responds
* jenny - we could post to NextDoor for the neighborhoods up in the hills
* mai - changes made! if anyone else would like to look, see pad (linked above)
* eve: maybe approach the Ham Radio Club and see if someone would be willing to share their tower
* null: how much does a billboard cost?
** mai: looked into that, prohibitively expensive

== Discussion: How we make decisions aka project proposal process ==
* Loomio discussion: https://www.loomio.org/d/YuC1wIps/how-we-make-decisions
* What do people think of this way of deciding on priorities and projects to spend $ on? This was based on conversations we had on 21+28 Aug

This process is required for purchases > $2000, and for paying people (any sum of money) for their time or for changes to this process:

1) Person has an idea. They add the proposal to the coming Tuesday's meeting pad.
They're strongly encouraged to collaborate with at least one other group member, rather than proposing individual projects.
2) Person's proposal is discussed during the Tues meeting.
3) The proposal passes with a consensus vote with minimum quorum. (n=5)
4) Person puts the proposal on Loomio (literally in the form of a Loomio "proposal") to get approval and consensus from the group members, especially those not present at the meeting.
5) Consensus members have one week to approve, abstain, or block via Loomio.
Anyone can comment/discuss.
6) If approved, it is announced at the following Tues meeting for a final round of discussion if any one requests this.
7) If blocked, person who blocked must present their reasoning at the following Tues meeting. if someone blocks a proposal then the blocker is expected to provide constructive feedback on the content of the proposal and identify why the proposal does not align with the sudomesh mission. Also, the blocker is expected to work with the proposers to come up with a proposal that would reach a consensus vote. Blocking is not getting voted off the island, blocking means that more collaboration is needed to help reach consensus.

marc - I propose an addition: if someone blocks but is completely unresponsive to communication attempts in attempting to resolve the block for an entire week, then the block is lifted.

Agree to revisit our processes quarterly - so next meta-analysis would be December 4th.

Jorrit's suggestions:
* Have at least one sponsor to put in a proposal
* 2-3 days notice before initial in-person proposal
* "block" --> "needs discussion"

marc:
* Counter-proposal: don't consense until *end of the following meeting*, after there has been time for discussion.

Example consensus items:
* Spending lots of money
* Signing a letter (e.g. HOPE) as a group
* Changing wording of our own processes/bylaws
* (Things that are hard to reverse - money we spend, words we can't take back)

* Summary thus far:
** The above process is for purchases > $2000, and for paying people (any sum of money) for their time.
** Compensation ideas:
*** pay people for child care during events
*** pay for translation services
** This will replace the accounting wg guideline for purchases > $2000

* The goals and intention of this decision-making process are:
** give active contributing members opportunities to discuss and give feedback
** encourage collaborative decision-making
** make reasonably quick decisions
** leave a record of discussions

== Action Items ==
* follow up w/ chuck again (benny)
* airfiber mount ideas/status (marc)
* make a loomio thread re: donating to Aspiration (jenny)
* send out email requesting AirFiber hosting - jenny (nextdoor), eve (hams), ?
* draft press release - jenny, you??
** https://docs.google.com/document/d/1-nmocVa7zTuLkWniObF2jikGoL5MI8MD7n2InSDVbwk/edit?usp=sharing
* add new project proposal process proposal to Loomio as a poll (mai)
* add item to agenda re: consensus list membership (mai)

== Breakout Groups ==
At the end of the meeting, break out into small groups to hack on or discuss specific topics.
*

== Last Meeting Notes ==
* https://sudoroom.org/wiki/Mesh/28_August_2018

[[Category:Mesh/Minutes]]

Mesh/Accounting/28 August 2018

2018-08-29T01:32:09Z

Eenblam: init

Sudo Mesh Accounting WG Meeting #5 - 08/28/2018

= Agenda =
* Intros & Intention-setting
* Overview of income, expenses & assets as well as current/draft policies
* Discussion: Buying (a) ladder(s)
* Action Items

= Attendees =
* jenny
* benny
* ben e.
* mai

= Overview Current Moneypaths & Policies =
* Sudo Mesh Projected Budget: https://docs.google.com/spreadsheets/d/1QJetruKfHrO5bpaLDk_smXYpLSvGlzytda_6koMjlCc/edit#gid=0
* Budget/Fundraising
* Sudo Mesh Fiscal Policies & Procedures (DRAFT): https://docs.google.com/document/d/1PeFoJUe4X3ww4mFKUMvbC4A-Yc_6sh5qbYdEgTdJpYQ/edit#
* Internal Logistics & Bureaucracy Trello Board: https://trello.com/b/LzVQlW3X/internal-logistics-bureaucracy-brainstorms

= Discussion: Buying (a) ladder(s) =
* Grant's suggestion - https://www.homedepot.com/p/Cosco-16-ft-Reach-Telescopic-Aluminum-Pinch-Free-Extension-Ladder-with-300-lb-Load-Capacity-Type-IA-Duty-Rating-20313T1ASE/303335494?MERCH=REC-_-PIPHorizontal2_rr-_-303496400-_-303335494-_-N - highly portable, ~$200
* Omni needs a taller ladder (last one was stolen) - Jenny will talk with Robb about best options and potential shared use with Sudo Mesh
* ben - I'm in favor of any ladder purchases, up to (somewhat arbitrarily) 4 ladders
* benny - me too
* jenny buys stuff for now because we don't have cards yet
* mai is in favor of buying up to 2 ladders
* mai submits ladder purchace request via our incredible web form peoplesopen.net/buystuff

= Discussion: Travel and Conference Reg Fees Reimbursements =
* jenny: Maybe we can have some limit for domestic travel vs. international travel for conference (eg up to $200, up to $500)
** this summer for instance - dweb summit registration fees, ournetworks travel
* mai: Ideally we'd approve it before the event. What if anyone who wants to be reimbursed for something puts in a request into peoplesopen.net/buystuff?
* Proposal to present at the general meeting tonight â€”
** For expenses spent on attending conferences to represent Sudo Mesh, they must request beforehand to get approval
** Anyone who wants to be reimbursed for their discounted DWeb summit reg fees is approved
** Anyone who traveled to represent Sudo Mesh at conferences during Summer 2018 can request a stipend/reimbursement of up to $200 for domestic trips and $500 for international trips while still subject to approval from Accounting WG and submission of receipts

= Reviewing accounting wg procedure =
* From June 5th proposal https://sudoroom.org/wiki/Mesh/5_June_2018:
** Up to $500 each Accounting WG member can spend on the card without approval, with their discretion. Above $500, you need pre-approval from Accounting WG, above $2000 we need approval from 5 signatures/email consent from board members
** Ben: need to go through this procedure for the air fibers
** Jenny: both are under 2k actually
** Benny: nice
* Benny updated https://sudoroom.org/wiki/Mesh/Accounting

= Action Items =
* Discuss with Robb about best options for a taller 20+ ft ladder and potential shared use with Sudo Mesh - jenny
* Follow up on Beneficial account - jenny
* Follow up on insurance quote - contingent on updating budget & business plan

= Last Meeting Notes =
https://sudoroom.org/wiki/Mesh/Accounting/12_June_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/Accounting/Template&action=edit
* previous meeting notes are archived here: https://sudoroom.org/wiki/Mesh/Accounting

[[Category:Mesh/Accounting]]

-----

Mesh/pizza

2018-08-22T02:56:43Z

Eenblam: pizza page init

Getting pizza for the meeting? Here are some (mostly) vegetarian pizza toppings meshers enjoy!

* Jenny, pineapple jalapeno
* scott: pineapple/jalapeno
* sierk: i'm fine with all toppings, also pineapple.
* null: i like ranch sauce with extra cheese
* rory: went to cheese board and they had curry potatoes which was a little weird but maybe a new favorite
* eve: mushroom
* blake: achovies
* mai: mushrooms and olives
* ben: pineapple and jalapeno
* grant: (warm) avocado
* marc: danish salad pizza
* cassidy: double-anchovies

Mesh/Network topology

2018-06-17T01:03:39Z

Eenblam: Drop images depicting relay nodes in network topology

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

= Peoplesopen.net Topology =
For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram|network topology diagram]].

= WiFi Topology =

We use 2.4 GHz 802.11g or 802.11n WiFi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for outdoor APs.

We're currently deploying a wireless backbone of point-to-point and point-to-multipoint links. These devices are mounted in high places such as on rooftops, flagpoles, or antenna towers. We currently have firmware support for a variety of Ubiquiti M5 (802.11n) routers, such as NanoBridges, NanoStations, and Rockets. As of June 2018, we're currently working to establish gigabit links with 5GHz and 24GHz Ubiquiti airFiber routers, as well as 60GHz Microtik wireless wires.

See the [[Mesh/Home and extender nodes|Home and extender nodes]] for more info about how these are setup.

All of the outdoor gear is Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.

= Mesh Topology =

All routers run the Babel mesh routing protocol. The street-level 2.4 ghz routers should ideally be able to function in the event that e.g. an earthquake takes out all of the point to point and point to multipoint rooftop nodes (more alignment sensitive) and the mesh should remain functional, though it could become segmented.

The relays / [[VPuN]] servers (see the internet connectivity section) also run Babel, so mesh traffic can flow from one part of the mesh, through the internet, through a relay, and into another part of the mesh if some of the mesh nodes are connected to the internet.

= Internet Connectivity =

There are four primary types of devices in the mesh:

*Clients: E.g. smart phones or laptops connected to the mesh.
:These do not run the meshing protocol.
*Mesh nodes: Wifi routers running OpenWRT.
:This includes home nodes and their extender nodes
*Relays / [[Mesh/VPuN|VPuN servers]]: Professionally hosted servers that relay mesh traffic over the internet.
:These run the meshing protocol. Mesh nodes are connected to them with L2TP tunnels.
*Exit nodes: Co-located servers that appear as the source IP for packets from mesh to internet.
:Both relays and exit nodes serve as a layer of protection between people sharing their internet connections with the mesh. A relay can also be an exit server and this may in fact end up being the case in most instances.

Some mesh routers will be hosted in homes that already have internet connections. If an internet connection is available, a mesh router will open an L2TP tunnel (using the tunneldigger software) to several relay nodes over the internet connection. A relay could be e.g. a VPS without a bandwidth cap. The relays all run Babel and function as part of the mesh through the L2TP tunnels to the mesh nodes. Each relay will have a connection to an exit nodes. The relays allow segments of the mesh that are not connected with wifi to be connected over the internet.

Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.
:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another.
:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.

= Backbone Connections =

== Desired ==

* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.

Mesh/Network topology

2018-06-17T01:02:40Z

Eenblam: Capitalize section headers

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

[[File:Network topology diagram-hi.png|thumb|png (hi), [[Mesh/Diagrams#Network Topology Diagram|see more]]]]
= Peoplesopen.net Topology =
For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram|network topology diagram]].

= WiFi Topology =

[[File:Mesh topology diagram.png|thumb]]

We use 2.4 GHz 802.11g or 802.11n WiFi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for outdoor APs.

We're currently deploying a wireless backbone of point-to-point and point-to-multipoint links. These devices are mounted in high places such as on rooftops, flagpoles, or antenna towers. We currently have firmware support for a variety of Ubiquiti M5 (802.11n) routers, such as NanoBridges, NanoStations, and Rockets. As of June 2018, we're currently working to establish gigabit links with 5GHz and 24GHz Ubiquiti airFiber routers, as well as 60GHz Microtik wireless wires.

See the [[Mesh/Home and extender nodes|Home and extender nodes]] for more info about how these are setup.

All of the outdoor gear is Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.

= Mesh Topology =

All routers run the Babel mesh routing protocol. The street-level 2.4 ghz routers should ideally be able to function in the event that e.g. an earthquake takes out all of the point to point and point to multipoint rooftop nodes (more alignment sensitive) and the mesh should remain functional, though it could become segmented.

The relays / [[VPuN]] servers (see the internet connectivity section) also run Babel, so mesh traffic can flow from one part of the mesh, through the internet, through a relay, and into another part of the mesh if some of the mesh nodes are connected to the internet.

= Internet Connectivity =

There are four primary types of devices in the mesh:

*Clients: E.g. smart phones or laptops connected to the mesh.
:These do not run the meshing protocol.
*Mesh nodes: Wifi routers running OpenWRT.
:This includes home nodes and their extender nodes
*Relays / [[Mesh/VPuN|VPuN servers]]: Professionally hosted servers that relay mesh traffic over the internet.
:These run the meshing protocol. Mesh nodes are connected to them with L2TP tunnels.
*Exit nodes: Co-located servers that appear as the source IP for packets from mesh to internet.
:Both relays and exit nodes serve as a layer of protection between people sharing their internet connections with the mesh. A relay can also be an exit server and this may in fact end up being the case in most instances.

Some mesh routers will be hosted in homes that already have internet connections. If an internet connection is available, a mesh router will open an L2TP tunnel (using the tunneldigger software) to several relay nodes over the internet connection. A relay could be e.g. a VPS without a bandwidth cap. The relays all run Babel and function as part of the mesh through the L2TP tunnels to the mesh nodes. Each relay will have a connection to an exit nodes. The relays allow segments of the mesh that are not connected with wifi to be connected over the internet.

Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.
:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another.
:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.

= Backbone Connections =

== Desired ==

* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.

Mesh/Network topology

2018-06-17T01:02:00Z

Eenblam: /* wifi topology */ Overhaul backbone section. Present tense - we have hardware. Capitalization. Oxford commas.

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

[[File:Network topology diagram-hi.png|thumb|png (hi), [[Mesh/Diagrams#Network Topology Diagram|see more]]]]
= peoplesopen.net topology =
For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram|network topology diagram]].

= WiFi Topology =

[[File:Mesh topology diagram.png|thumb]]

We use 2.4 GHz 802.11g or 802.11n WiFi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for outdoor APs.

We're currently deploying a wireless backbone of point-to-point and point-to-multipoint links. These devices are mounted in high places such as on rooftops, flagpoles, or antenna towers. We currently have firmware support for a variety of Ubiquiti M5 (802.11n) routers, such as NanoBridges, NanoStations, and Rockets. As of June 2018, we're currently working to establish gigabit links with 5GHz and 24GHz Ubiquiti airFiber routers, as well as 60GHz Microtik wireless wires.

See the [[Mesh/Home and extender nodes|Home and extender nodes]] for more info about how these are setup.

All of the outdoor gear is Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.

= mesh topology =

All routers run the Babel mesh routing protocol. The street-level 2.4 ghz routers should ideally be able to function in the event that e.g. an earthquake takes out all of the point to point and point to multipoint rooftop nodes (more alignment sensitive) and the mesh should remain functional, though it could become segmented.

The relays / [[VPuN]] servers (see the internet connectivity section) also run Babel, so mesh traffic can flow from one part of the mesh, through the internet, through a relay, and into another part of the mesh if some of the mesh nodes are connected to the internet.

= internet connectivity =

There are four primary types of devices in the mesh:

*Clients: E.g. smart phones or laptops connected to the mesh.
:These do not run the meshing protocol.
*Mesh nodes: Wifi routers running OpenWRT.
:This includes home nodes and their extender nodes
*Relays / [[Mesh/VPuN|VPuN servers]]: Professionally hosted servers that relay mesh traffic over the internet.
:These run the meshing protocol. Mesh nodes are connected to them with L2TP tunnels.
*Exit nodes: Co-located servers that appear as the source IP for packets from mesh to internet.
:Both relays and exit nodes serve as a layer of protection between people sharing their internet connections with the mesh. A relay can also be an exit server and this may in fact end up being the case in most instances.

Some mesh routers will be hosted in homes that already have internet connections. If an internet connection is available, a mesh router will open an L2TP tunnel (using the tunneldigger software) to several relay nodes over the internet connection. A relay could be e.g. a VPS without a bandwidth cap. The relays all run Babel and function as part of the mesh through the L2TP tunnels to the mesh nodes. Each relay will have a connection to an exit nodes. The relays allow segments of the mesh that are not connected with wifi to be connected over the internet.

Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.
:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another.
:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.

= Backbone Connections =

== Desired ==

* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.

User talk:S3th

2018-06-17T00:28:11Z

Eenblam: Welcome!

'''Welcome to ''Sudo Room''!'''
We hope you will contribute much and well.
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].
Again, welcome and have fun! [[User:Eenblam|Eenblam]] ([[User talk:Eenblam|talk]]) 17:28, 16 June 2018 (PDT)

Template:Mesh nav

2018-06-16T20:40:49Z

Eenblam: Remove diagrams (very stale)

{|style="border-style: solid; border-width: 10px; border-color: #20b24b; background-color: #ffffcc; width: 70%; text-align: center;"
|+ '''''Quick Links''' (see below for more details)''
|-
!Documentation
!Technical
!Outreach
!Operations
!Research
!External Links
|-
|[https://peoplesopen.net/blog/ Blog]
|[[Mesh/Technical_Overview|Overview]]
|[[Mesh/FAQ|FAQ]]
|[[Mesh/Minutes|Minutes]]
|[[Mesh/UserResearch|User Research]]
|[http://peoplesopen.net peoplesopen.net]
|-
|[[Mesh/WalkThrough|Walkthrough]]
|[[Mesh/Home_and_extender_nodes|Hardware]]
|[[Mesh/How_to_help|How to Help]]
|[[Mesh/ToDos|To-Do's]]
|[[Mesh/SFBayArea|SF Bay Area]]
|[https://peoplesopen.net/map.html network map]
|-
|[[Mesh/Press|Press]]
|[[Mesh/Terms|Terms]]
|[[Mesh/Presentations|Presentations]]
|[[Mesh/Legal|Legal]]
|[[Mesh/Interviews with other meshers|Interviews]]
|[https://github.com/sudomesh code on github]
|-
|[[Mesh/History|History]]
|[[Mesh/Server security|Security]]
|[[Mesh/Wishlist|Wishlist]]
|[[Mesh/Inventory|Inventory]]
|[[Mesh/Other mesh projects|Other Meshes]]
|[https://disaster.radio DisasterRadio]
|-
|[[Mesh/Network topology|Net Topology]]
|[[Mesh/Power|Power]]
|[[Mesh/Website|Website]]
|[[Mesh/Meetings|Meetings]]
|[[Mesh/Software tools|Software Tools]]
|
|-
|[https://github.com/sudomesh/sudowrt-firmware Firmware]
|[[Mesh/Backup|Backup]]
|[[Mesh/Design|Design]]
|[[Mesh/Funding|Funding]]
|[[Mesh/Distributed_Services|Local Services]]
|
|-
|
|[[Mesh/Hosting|Hosting]]
|[[Mesh/Swag|Swag]]
|[[Mesh/Decisions|Decisions]]
|[[Mesh/Educational_Resources|Self-Education]]
|
|-
|
|[[Mesh/Mounting|Mounting]]
|
|
|
|
|-
|}

Mesh

2018-06-16T20:34:51Z

Eenblam: Firmware should link to github instead of wiki

<center>{{#setlogo:Meshlogo.png}}
[[File:Sudomesh.jpg|350px]]</center>

'''sudomesh is a group of volunteers operating out of the [https://sudoroom.org sudo room] hackerspace at the [https://omnicommons.org Omni Commons] - a collective of collectives stewarding a large community space in Oakland, California. We develop software and assemble hardware systems to help build open community networks like the [https://peoplesopen.net People's Open Network], a community-owned and -operated non-profit internet infrastructure in Oakland.'''

We're a people-powered project. That means that anyone can join the network if they're willing to contribute by [https://github.com/sudomesh/bugs/issues/new reporting bugs], improving [https://github.com/sudomesh software], fixing hardware, [https://sudoroom.org/wiki/Mesh/WalkThrough setting up a node], [https://peoplesopen.net/blog/new-node-in-the-berkeley-hills/ installing rooftop nodes], telling your friends about us, [https://peoplesopen.net/blog/build-your-own-internet-workshop/ joining for a workshop], bringing pizza to a hack session, donating [[Mesh/Wishlist|equipment]]/[https://www.patreon.com/peoplesopennet money]/[https://blockchain.info/address/12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc Bitcoin], learning with us about how the internet works, or just being patient if something is broken :)

'''Interested in learning more and exploring?''' Check out our [[#Join Us|Join Us]] section. You do not need to be technically skilled to be part of this project. We need people willing to mount gear on rooftops, folks who want to do public outreach, graphic design artists, film-makers, documentarians and so much more! Show up at a monthly general meeting and get involved!

----
__NOTOC__
<div style="margin: 1em auto 1em auto; text-align: center; background: #ffffff; font-size: 10.5pt; padding: 10px; width: 96%; border: 0px solid #376a97;margin-center:10px;">

{| cellspacing="0" width="100%" style="clear: both;"
|colspan="3" style=border: 0px solid black; float:left; padding-left:1em; padding-right:0.5em;"|
{| cellspacing="5" cellpadding="10" width="100%"
|- valign="top"
|style="font-size:90%; padding:10px 10px; background: #FDF4F4; border: 0px solid black;padding-left:1em;padding-right:0.5em;" width="40%" align="left"|
=What does it mean?!=
Imagine if the wifi router in your home connected to the wifi routers in your neighbours' homes and they again connected to their neighbours to form a huge free wireless network spanning the city! That's exactly what a [https://en.wikipedia.org/wiki/Mesh_networking mesh network] is, or at least what it can be. Roads and telephone poles are owned by government or private interests and laying down cable is expensive, but by using wireless signals that hop from building to building we can create a community-owned and -operated, free-as-in-freedom alternative to corporate Internet Service Providers. Community wireless mesh networks are growing around the world, creating local 'internets' that support Net Neutrality and community control of critical infrastructure.

We are spending a lot of time developing [https://github.com/sudomesh/ software] to make it cheap and easy for anyone to be participate in cooperative communications infrastructure, regardless of technical skill.

= Who are you? =
Sudo Mesh is a non-profit organization consisting of a group of unpaid volunteers who are building open technology that helps to connect our neighbors, support local businesses, and enable community collaboration and cultural production. In the event of a natural disaster or state censorship, community mesh networks can be a resilient means of communication and sharing of information.

= Frequently Asked Questions (FAQs)=
* [[Mesh/Decisions|Decisions]] - What decisions have we made, and why?
* [[Mesh/Funding|Funding]] - How the heck do we fund this thing?
* [[Mesh/Legal|Legal]] - How do we use exit nodes, relays and legal structures to protect node owners and ourselves?
* [[Mesh/Hosting|Hosting]] - How are we hosting and what does it cost?
* [[Mesh/Backup|Backup]] - How do we handle backups?
* [[Mesh/Server security|Server Security]] - How do we ensure server security?

= Logistics =
* [[Mesh/Minutes|Meeting Minutes]] - Notes from our weekly meetings dating back to January 2013.
* [[Mesh/Taxes|Taxes]] - Filed taxes for the sudo mesh non-profit

= Research =
* [[Mesh/Other mesh projects|Other mesh projects]] around the world that have inspired us to make our own network!
* [[Mesh/Interviews with other meshers|Interviews]] - we interviewed other experienced meshers
* [[Mesh/Documentation|Other documentation]] - books, articles, wikis, blog posts.
* [[Mesh/Oakland|Oakland]] - information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
* [[Mesh/Other muni networking projects|Municipal projects]] - examples of progressive uses of municipal networks.
* [[Mesh/Decentralized FM/AM radio|Decentralized FM/AM radio]] - Bit of research on adding legal FM/AM transmitters to nodes.
* [http://wiki.tidepools.com Tidepools] - [[User:tunabananas|Jenny Ryan]] designed local use cases for a community mobile mapping application built to run on mesh networks.
* [https://wiki.projectmeshnet.org/Main_Page Project Meshnet] - Extensive wiki on the /r/darknet project, including extensive list of [https://wiki.projectmeshnet.org/Projects projects coordinating with them].
* [http://en.wikipedia.org/wiki/Long-range_Wi-Fi#Notable_links Long Range Wifi] - Info on the longest-range wifi connections ever made.
* [https://github.com/adafruit/Adafruit-WebIDE Adafruit's Web IDE built for Raspberry Pi] but probably good for editing code on any device and ensuring it is managed with a code repo. By default it uses [https://bitbucket.org bitbucket.org] but it could probably be configured for Github.

|style="font-size:90%; padding:10px 10px; background: #F4FDF6; border: 0px solid black;padding-left:1em;padding-right:0.5em;" width="20%"|
<center>
= Our Projects =
[[File:Mesh_Oakland_High_Res.png|center|187px|thumb|Building a community-owned and -operated wireless mesh network in Oakland, California and beyond!|link=https://peoplesopen.net]] 
[[File:Disasterradio.png|center|187px|thumb|link=https://disaster.radio|Disaster-resilient communications network powered by the sun.]] 
[[File:Byoi.png|center|187px|thumb|link=https://buildyourowninter.net|Instructions for building your own internet, plus a global directory of community wireless mesh networks.]]</center> 
[[File:Laptops4all.png|center|187px|thumb|link=https://laptopsforall.org|Upcycling retired/donated laptops to those who can't afford them.]] 

|style="font-size:90%; padding:5px 10px; background:#F4F8FD;border: 0px solid black;padding-left:1em;padding-right:0.5em;" width="40%" align="left"|

<center>
= How To Participate =
</center>
If you want to join the mesh you'll need a mesh router at your home! Currently the best way to get one is to show up at our monthly general meeting as described above. We need more people on the network to improve the quality of the service. When you setup a node, you improve the service for everybody on the network and give more access to your community. We encourage participants to ask their communities to join their networks and create distributed services for them. We have a [[Mesh/User_Guide|user guide]] to help you get on the network!
* Join the [http://lists.sudoroom.org/listinfo/mesh email list]
* Follow us on [https://twitter.com/sudomesh twitter] and like us on [https://www.facebook.com/sudomesh facebook].
* We have weekly meetings from 7:30-9pm at [[Getting_there|sudo room]]. We have focus groups and collaborate on different parts of the project - from design to software development, documentation to hardware hacking, community outreach and climbing rooftops to mount nodes!
* For the sake of time, we don't use Tuesday meetings to introduce folks to the project. If you do not feel ready to jump right in and start contributing, please join us during our "Build Your Own Internet (BYOI)" open hours on Sundays from 1-3pm at [[Getting_there|sudo room]] :D
* Chat with us on [https://peoplesopen.net/chat RocketChat] or [http://www.irchelp.org/irchelp/irctutorial.html IRC]: [http://webchat.freenode.net/?channels=peoplesopen.net #peoplesopen.net] (see also [[IRC | IRC Intro]])
* We generally collaborate on [https://peoplesopen.net/pad/p/notes] at each meeting. Look at our archive of past [[Mesh/Minutes|meeting minutes]]!
* Contribute to the network by installing a mesh node at your location using our handy [https://sudoroom.org/wiki/Mesh/WalkThrough Mesh Node Setup Walkthrough]. This is especially helpful for those who are within range of an existing node (seen as a wireless SSID named "peoplesopen.net").
*Check out our [[Mesh/ToDos|ToDo list]]
*Support us with a small monthly donation on [https://www.patreon.com/peoplesopennet Patreon], here's [[Mesh/Purchases|how we spend it]].
*Send bitcoins to our wallet address: {{bitcoin wallet}}
*Check out our [[Mesh/Wishlist|wishlist]], we have requests!
*Improve our documentation
*Talk to your community about joining the mesh - here are some [[Mesh/Outreach|resources]] for doing so!

== Developers ==

We need hardware and software engineers to help us with our code. We have an overview of [[Mesh/Technical_Overview|technical documentation]] that will be helpful in understanding the network.

If you want to immediately help, check out [https://github.com/sudomesh our code] or [https://github.com/sudomesh/sudowrt-firmware/milestones look at our remaining issues for upcoming milestones].

Here are some of the projects that need attention:

* [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware] - The sudowrt firmware
* [https://github.com/sudomesh/sudowrt-web-ui sudowrt-web-ui] - The new and improved web admin UI for sudowrt nodes
* [https://github.com/sudomesh/ubus-https-forwarder ubus-https-forwarder] - Allow management of extender nodes from home node web UI
* [https://github.com/sudomesh/service-browser The Service Browser] - Web UI for browsing mesh services
* [[Mesh/Distributed Services|Mesh Services]] - Which services should we provide?

== Designers ==

We need artists and designers to make things look nice! We have [[Mesh/Design|design schemes]] we already use, but we're always looking to improve it. We need to improve our presentation content and [[Mesh/Diagrams|diagrams]] too! We've been focused on these areas:
* [[Mesh/Presentations]] - Past presentations, talks, workshops, tutorials and videos
* [[Mesh/Diagrams|Diagrams]] - Diagrams outlining the network topology and technical stack
* [[Mesh/Design|Design]] - Website & logo design; swag for enthusiasts; and marketing inspiration.
|}

----

<center>{{Mesh nav}}</center>

----

''Please note that all contributions to Sudo Room may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Sudo Room:Copyrights for details). Do not submit copyrighted work without permission!''

[[Category:Projects]][[Category:Mesh]]

Mesh/Technical Overview

2018-06-10T22:03:42Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

[[File:Sudomesh home and extender node illustration extra-simplified.png|thumb|Illustration showing how a sudomesh home node can connect to a window-mounted extender node. The device with two antennas is the home node and the device on the outside of the window is an extender node.]]

[[File:Sudomesh home and extender node illustration.png|thumb|Illustration showing a more complicated setup. Here the node operator has connected their personal computer, a small Raspberry Pi computer and two extender nodes: One on the outside of the window and one on the roof (not shown but a can be seen going up and out of the frame). This is definitely an advanced node operator.]]

[[File:Sudomesh home node ethernet ports.png|thumb|A close-up of the wired network ports on the home node and their use.]]

== Home and extender nodes ==

''Note: You can also read the [[home node|non-technical explanation of home nodes and extender nodes]].''

Our mesh has two types of nodes: Home nodes and extender nodes.

The home nodes run the full sudowrt firmware and on its own a bunch of home nodes will make up a fine mesh network. The home node is a normal five-ethernet-port indoor wifi router. An extender node runs a minimal firmware and does nothing on its own. Instead, the extender node basically acts as extra radios when plugged in to a home node. The node operator can put a home node in e.g. their living room and if they later decide they want a high speed directional link to a neighbour then they can put e.g. a Nanobridge M5 running the extender node firmware on their roof and connect it via ethernet to the home node. Or they could put a Nanostation M2 pointed out their window and extend the signal further out into the street or to nearby neighbours. Each extender node extends all three networks (explained in the next section).

For home nodes we are currently only officially supporting the [http://www.tp-link.us/products/details/cat-9_TL-WDR3600.html TP-Link TL-WDR3600]. We are not planning to support anything else for the time being, though if you have a good reason please let us know. For extender nodes we are currently supporting the Ubiquiti Nanobridge M series and the Ubiquiti Nanostation M series.

The mesh is made up mostly of wifi routers using Atheros chipsets and running [https://github.com/sudomesh/sudowrt-firmware our own firmware] based on [http://openwrt.org/ OpenWRT], [http://www.pps.univ-paris-diderot.fr/~jch/software/babel/ Babel] and wlan slovenja's [https://github.com/sudomesh/tunneldigger tunneldigger].

Node-owners can choose to connect the nodes to their existing internet connection using ethernet. If they have Internet access, they can share a portion of it with the mesh. The amount of bandwidth shared is limited with 'tc'. It is chosen at node-configuration time and can be changed using the simple built-in web admin interface.

== The three wifi networks and IP assignment ==

The nodes each run three wifi networks (three SSIDs on the same physical wifi interfaces):

* The Open network with SSID peoplesopen.net is an open access point. Most people will use the network by connecting to this.
* The Mesh network with SSID pplsopen.net-node2node is an ad-hoc network that the nodes use to mesh with each other using Babel
* A private wifi network that is named by the node owner (or a name is generated) and uses WPA2-PSK.

All three of these networks are available on both 2.4 and 5 GHz on the home node. They are also all three available on any extender nodes plugged in to the home node. The three different networks are extended over a single ethernet cable using VLANs.

If a node-owner is sharing internet, then the node will create a layer 2 (L2TP) tunnel to a VPN server on the Internet using tunneldigger. Babel (the mesh routing protocol) will connect over this tunnel to other nodes on the mesh, so the mesh can route traffic over the internet if no wifi path to another node is available (e.g. other nodes are physically too far away). When people connect to the peoplesopen.net access point and try to access the Internet, the traffic will flow through the VPuN, and the source IP of requests will appear to be the VPuN with the sudo mesh organization listed as the abuse contact.

The nodes run DHCP servers and each have a /24 IPv4 subnet in the 100.64.0.0/10 range that is statically assigned by coordination between mesh groups and individuals hosting and administrating their own nodes on People's Open Network (currently only the sudo mesh organization).

The private network does not limit bandwidth and provides access to both direct access to the Internet (if the node owner has hooked the node up to the Internet) and access to the mesh. Each node's private network runs on 172.30.0.0/16 and uses NAT between the private network and the mesh. It does not accept any new incoming connections from the mesh onto the 172.30.0.0/16 subnet.

== Accessing Home Node via SSH ==

Your home node is accessible via the [https://wiki.openwrt.org/doc/uci/dropbear Dropbear] Secure Shell (SSH) server on port 22.

The 4 Ethernet ports that are provided with your router should be configured as follows:

# Private network with DHCP of 172.30.0.x network addresses
# Public network with DHCP of 100.64.x.x network addresses (SudoMesh network)
# NotDHCP for Extender 1
# NotDHCP for Extender 2

This may not apply to your router. For instance, the TP-Link N750 uses the opposite port assignment, with port 3 for private network, and port 4 for public SudoMesh/PeoplesOpen.net network.

=== Network Settings ===

=== Default Build Configuration ===

The IP address of your home node is <tt>172.22.0.1</tt> prior to configuration via the [https://github.com/sudomesh/makenode makenode] utility. You can SSH into the node as <tt>root</tt> using the password 'meshtheplanet' after setting up your computer to use an IP on the 172.22.0.0/16 network.

=== Post Makenode Configuration ===

The private network configuration uses a 172.30.0.0/16 network with DHCP available for connected clients. You can configure your workstation to use the following manual network configuration so that you can SSH into your home node.

* IP Address: 172.30.0.9 (or anything other than 172.30.0.1)
* Netmask: 255.255.255.0
* Gateway: 172.30.0.1

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

The IP of your home node on the private network is <tt>172.30.0.1</tt>, with the root password you specified when running <tt>makenode</tt> to configure it.

ssh root@172.30.0.1
The authenticity of host '172.30.0.1 (172.30.0.1)' can't be established.
RSA key fingerprint is b8:9d:4a:2f:1b:f5:e1:ae:b8:19:5b:70:92:8b:7f:34.
Are you sure you want to continue connecting (yes/no)?

After accepting the key by entering 'yes' and pressing ENTER, it will ask you for the root password.

=== SSH Keys ===

If you'd like to add your ssh key to the router (instead of using a root password), add it to the <tt>configs/authorized_keys</tt> file. You'll see that there are 3 other keys there for our developers. You can remove them if you'd like, but they're currently the only way we can provide remote support. During the alpha test phase we ask that you consider whether you are able to do diagnostics/debugging yourself before you remove them.

== Node flashing and configuration ==

One of our medium-term goals is to be able to sell nodes on our website and minimize the amount of work required to re-flash/configure the nodes and provide documentation for the user. To facilitate this, our current process for new nodes is:

* A new node is flashed either automatically (using e.g. [https://github.com/sudomesh/ubiquiti-flasher ubiquiti-flasher] or [https://github.com/sudomesh/merakiflasher merakiflasher]) or manually with your own tools and the [https://github.com/sudomesh/sudowrt-firmware sudowrt] firmware.
* The node is then configured by a sudo mesh volunteer using our [https://github.com/sudomesh/makenode makenode] software.
* makenode generates SSH keys, SSH root password, web admin password and private wifi password, then it configures the node, saves the info in the [https://github.com/sudomesh/node-database node database] and shuts down the node.
* makenode then automatically [https://github.com/sudomesh/ql570 prints a sticker] containing some basic info including wifi and web admin passwords.
* The sudo mesh volunteer attaches the sticker to the nodes power supply and puts the node back in the box with a set of instructions for how to install and use the node.
* The node is shipped to the new node owner!

== Node management ==

All nodes set up by sudo mesh automatically allow root access using an SSH key held by a few trusted sudo mesh organizers. This is to allow us to update the firmware and troubleshoot network issues. We inform node-owners of this fact and tell them how to prevent sudo mesh from accessing their nodes, but also indicate that they should be ready to manage their own node if they choose to do this.

We don't yet have a solution for node monitoring but we're expecting to use the new version of wlan slovenja's nodewatcher software.

We don't yet have an automatic update solution in place, but we are looking at the software used by Gluon. The Gluon update system is centralized but in the long term we would like to have a decentralized system that works something like this:

* Any number of node-updater servers announce themselves on the mesh and whether or not an update is available.
* The nodes run a future version of mdnssd-min as a daemon that keeps a currently list of node-updaters.
* Once every N hours +/- a random factor, if any node-updaters have updates available, all nodes connect to a randomly chosen node-updater and request an update.
* The node-updaters send the nodes an ipk file with the update and the nodes check the signature and install it if it's signed by a trusted authority.

==Detailed Documentation==
*[[Mesh/Tracking]] - Problems and solutions related to tracking, logging and anonymity
*[[Mesh/WalkThrough]] - Easy how-to for setting up OpenWRT
**[[Mesh/Flashing Extender Antennas]] - How-to for Ubiquiti routers
**[[Mesh/OpenWRT]] - Experiences with the OpenWRT router firmware
*[[Mesh/Firmware]] - Everything related to our firmware
**[[Mesh/Firmware/Overview]] - High level view
**[[Mesh/Firmware/Flash]] - How to install the sudowrt firmware based on openwrt with supported hardware
**[[Mesh/Firmware/Splash page]] - Splash page / Captive Portal
**[[Mesh/Firmware/Bandwidth shaping]] - QoS / Bandwidth shaping
**[[Mesh/Firmware/Zeroconf]] - Issues related to mDNS and DNS-SD
**[[Mesh/Firmware/MTU_issues]] - MTU issues
**[[Mesh/Firmware/Web Admin Development]] - Web admin development
*[[Mesh/Network topology]] - High-level explanation of the mesh network structure
*[[Mesh/Specs]] - Specs sheet on different access points
*[[Mesh/Frequencies]] - Information on different frequencies.
*[[Mesh/Software tools]] - List of useful mesh troubleshooting tools
*[[Mesh/Terms]] - Hidden Node, Fresnal zone, and other jargons
*[[Mesh/Power]] - Stuff about power usage, batteries and solar power.
*[[Mesh/Monitoring]] - notes about how to monitor systems
*[[Mesh/Spectrum]] - Different forms of spectral analysis
*[[Mesh/Hardware support]] - Officially and unofficially supported hardware / routers
*[[Mesh/Relay setup]] - Setting up a relay node
*[[Mesh/Exit setup]] - Setting up an exit node
*[[Mesh/Spectrum mapping]] - The setup we use for mapping local spectrum and wifi usage
**[[Mesh/Spectrum mapping/XO-1 Laptop]] - How to configure an XO-1 laptop for use with our spectrum mapping setup
* [[Mesh/Install]] - physical installation notes/stories
* [[Mesh/Diagrams]] - technical diagrams to support new outreach materials

Mesh/ToDos

2018-06-10T21:51:48Z

Eenblam: Link to bugs repo

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

'''We now use a number of other tools to manage our active tasks. As of June 2018, we use Trello for kanban boards, and we set a weekly list of action items at each Tuesday meeting. Technical issues are reported in related GitHub repos, and larger, network-level issues are discussed in the [https://github.com/sudomesh/bugs bugs repo].'''

Below are a list of To Do items, separated by topical area. If you decide to take one on, please post your name after the item and send a note to the mailing list with your plan of action! We welcome contributions of tasks, also :)

=Community Outreach ToDos=
*Conduct User Research on what sorts of [[Mesh/MeshApps|Local Services]] people would like to have [Jenny, you?]
*Write up a compelling argument for mesh re: disaster preparedness [cite sources] [Jenny, you?]
*Outreach to churches with succinct argument [cite examples, e.g.; Sandy relief]
*Poster/flier at local coffeeshops, bikeshops, co-ops, collectives, community resource spaces, etc;
*Walkabouts/canvassing in E Oakland, Berkeley, Downtown Oakland
*Find folks in El Cerrito / Albany who can help us link up to the Internet Archive's Richmond node
*[https://sudoroom.org/wiki/Mesh/Presentations Presentations / talks / events promo]
*See if people in school system want to work with us to ensure every student has home connectivity
*Convince libraries to share their connectivity

=Operational Logistics=
*Make a project roadmap
*[https://sudoroom.org/wiki/Mesh/Funding Grants and other funds we can apply for]
*Financials [current and projected] [Jenny, you?]
*Time [of volunteers needed to sustain project]
*Tax status (set up 501c3) [Marc, Matt, Jenny]
*[https://sudoroom.org/wiki/Mesh/Funding#Sustainable_Business_Models Business models]

=Marketing / Branding=
*Blog posts [Jenny, you?]
*Articles & Research [Jenny, you?]
*Photo album [OpenPhoto?]
*Design 'pods' for the outdoor routers [eg; birdhouses, planterboxes]
*Infographics
*Videos
*Fliers
*Poems, songs and flags
*Bios, titles and photos of team members

=Technical=
*More brainstorming on [[Mesh/MeshApps|local applications]]
**Timebank
**Sensors - noise, gunshots, pollution [talk to nerds for nature]
**Hosting - Raspberry Pi/Beaglebone black provisioning; mesh app distributions; etc.
*See [[Mesh/Software ToDo|Software ToDo]] for ToDo items related to firmware and software.

Template:Mesh nav

2018-06-10T21:50:03Z

Eenblam: "Firmware" now to links github repo

{|style="border-style: solid; border-width: 10px; border-color: #20b24b; background-color: #ffffcc; width: 70%; text-align: center;"
|+ '''''Quick Links''' (see below for more details)''
|-
!Documentation
!Technical
!Outreach
!Operations
!Research
!External Links
|-
|[https://peoplesopen.net/blog/ Blog]
|[[Mesh/Technical_Overview|Overview]]
|[[Mesh/FAQ|FAQ]]
|[[Mesh/Minutes|Minutes]]
|[[Mesh/UserResearch|User Research]]
|[http://peoplesopen.net peoplesopen.net]
|-
|[[Mesh/WalkThrough|Walkthrough]]
|[[Mesh/Home_and_extender_nodes|Hardware]]
|[[Mesh/How_to_help|How to Help]]
|[[Mesh/ToDos|To-Do's]]
|[[Mesh/SFBayArea|SF Bay Area]]
|[https://peoplesopen.net/map.html network map]
|-
|[[Mesh/Press|Press]]
|[[Mesh/Terms|Terms]]
|[[Mesh/Presentations|Presentations]]
|[[Mesh/Legal|Legal]]
|[[Mesh/Interviews with other meshers|Interviews]]
|[https://github.com/sudomesh code on github]
|-
|[[Mesh/History|History]]
|[[Mesh/Server security|Security]]
|[[Mesh/Wishlist|Wishlist]]
|[[Mesh/Inventory|Inventory]]
|[[Mesh/Other mesh projects|Other Meshes]]
|[https://disaster.radio DisasterRadio]
|-
|[[Mesh/Diagrams|Diagrams]]
|[[Mesh/Power|Power]]
|[[Mesh/Website|Website]]
|[[Mesh/Meetings|Meetings]]
|[[Mesh/Software tools|Software Tools]]
|
|-
|[https://github.com/sudomesh/sudowrt-firmware Firmware]
|[[Mesh/Backup|Backup]]
|[[Mesh/Design|Design]]
|[[Mesh/Funding|Funding]]
|[[Mesh/Distributed_Services|Local Services]]
|
|-
|[[Mesh/Network topology|Net Topology]]
|[[Mesh/Hosting|Hosting]]
|[[Mesh/Swag|Swag]]
|[[Mesh/Decisions|Decisions]]
|[[Mesh/Educational_Resources|Self-Education]]
|
|-
|
|[[Mesh/Mounting|Mounting]]
|
|
|
|
|-
|}

Mesh/Hosting

2018-06-10T21:19:40Z

Eenblam: Link to sudomesh/exitnode and peoplesopen.net/monitor

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

'''Our exit node situation has changed a good bit. Better documentation is available on [https://github.com/sudomesh/exitnode GitHub], and the status of current exitnodes can be found [https://peoplesopen.net/monitor on the monitor].

This page details current and future hosting solutions used by sudomesh.

= Production =

== Exit nodes ==
The exit nodes must live up the the following requirements:

*Minimum 100 mbit unmetered bandwidth
*A processor fast enough to saturate 100 mbit with NAT'ed tunneled traffic
*A subnet or IP that lists sudomesh as the abuse contact
*Tor-friendly or Tor-agnostic provider
*Location close to bay area
*Co-located (optional, but we want this in the long term)

=== Possible providers ===

[http://www.oplink.net/colocation.html Oplink]:

*Location: Texas
*Bandwidth: Unmetered 100 mbit
*Tor-friendliness: Unknown
*Will let us be the abuse contact: Unknown
*Price: $80 per month

== Relay nodes ==

The relay node requirements:

*Minimum 100 mbit unmetered bandwidth
*Ability to saturate 100 mbit with tunnneled traffic
*Location close to bay area

=== Possible providers ===

[http://www.vpscheap.net/enterprise-vds.aspx vpscheap] have virtual servers with the following specs:

*VM technology: Xen
*Bandwidth: Unmetered 100 mbit
*Ram: 1 GB
*Dual CPU
*Disk space: 50 GB
*Location: Chicago
*Price: $16.99 per month

== SSL ==

We use free [http://startssl.com/ StartSSL] certificates.

== DNS ==

Our DNS hosting is via namecheap.com. We own the following domains:

*peoplesopen.net (primary, use this in communications)
*pplsopen.net
*peoplesopennetwork.com
*peoplesopennetwork.net
*peoplesopennetwork.org
*sudomesh.org (primary, use this in communications)
*sudomesh.net
*sudomesh.com
*meshthepla.net
*meshtheplanet.net
*meshtheplanet.org
*meshtheplanet.com

== Web and email ==

We currently have a VPS from vpscheap.com. It is hosting web and email for the following domains:

*peoplesopen.net (and variations)
*sudomesh.org (and variations)

The VPS specs are:

*VM technology: OpenVZ
*Ram: 512 MB
*Swap: 1 GB
*Disk space: 50 GB
*Bandwidth: 20 mbit/sec unmetered
*Operating system: Ubuntu
*Cost: $6 a month

== Backup ==

We currently have a VPS from backupsy.com. The domain backup.sudomesh.org points to the server. All sudomesh servers back up to this server using [http://duplicity.nongnu.org/â€Ž Duplicity] once every 24 hours. The backups are incremental so we can restore to any point in time. We do not yet have a policy for how far back we keep backups. The backups are encrypted and the backups cannot be deleted by anyone other than root on the backup server, so gaining access to a sudomesh server does not mean gaining access to deletion of backups.

The specs for the VPS are:

*VM technology: KVM
*Disk space: 250 GB
*Ram: 512 MB
*Bandwidth: 1000 GB per month
*Operating system: Ubuntu
*Cost: $6 a month
*Note: The ToS only let us use this for backup unless we upgrade our plan.

= Development =

== Exit node ==

We have one exit node for development use. Its hostname is exit1.sudomesh.org.

VPS specs:

*Provider: digitalocean.com
*VM technology: KVM
*Ram: 4G
*Bandwidth: 1Gbps with 4TB transfer limit/month
*IP address: 104.236.181.226
*OS: Debian
*Price: $40 per month

Mesh/San Francisco

2018-06-10T21:08:53Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

= Mesh Projects in San Francisco =
== Derpanat ==
We're building a mesh network called Derpanet!

Mesh nodes are solar-powered, wireless devices which you can put on your roof and forget. Right now we're looking for spots to put them.

As of right now, we don't have nodes anywhere useful - useful would be, has line of sight from the roof of my house in the Glen Park/Noe Valley/Bernal Heights Demilitarized Zone. Jasmine Strong modulararithmetic @ gmail.com

= Historical Community/Mesh Wireless in SF =
Various attempts at SF community wireless have largely failed or lapsed over the years. A semi-detailed history is available on [https://en.wikipedia.org/wiki/San_Francisco_Municipal_Wireless#Wireless_community_networks this Wikipedia article] and summarized below:
* [https://web.archive.org/web/20070913085334/http://sf.meraki.net/ Free The Net] - Meraki, a commercial mesh networking service and hardware manufacturer, experimented with a free network briefly in SF between 2008-2009 and was acquired by Cisco in 2012.
* [https://archive.org/web/sflan.php SF Lan] - Out of the [https://archive.org Internet Archive], began in 2007 with a 50-node experimental network but petered down to 4 nodes by the end of the year. Wikipedia states that "noise level in the ISM bands due to proliferating and competing Wi-Fi signals made many of their long-distance links (several miles) nonfunctional". They were outcompeted in 2010 with the launch of MonkeyBrains, a local ISP that piloted in SF with a free service to residents. The network, though dormant, may soon be revitalized and is considering a munipal fiber and wireless hybrid model.
** From [https://en.wikipedia.org/wiki/San_Francisco_Municipal_Wireless#cite_note-19 Wikipedia]:
<blockquote>The City whipsawed by corporate powers, SFLan ending their experiment, and Meraki's "Free the Net" on hold all provided MonkeyBrains with the motivation to start their 2010 free wifi in the Mission. By the End of 2010, MonkeyBrains exceeded 120Mbit/s of download and 50Mbit/s upload in their wireless pilot.[http://twitpic.com/3imh8h 19]</blockquote>

Mesh/UserResearch

2018-06-10T21:07:58Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

'''Information on our recent outreach, e.g. to LOLspace and the Village in 2018, would be appreciated here.'''

Based on the interviews and research below, a number of [[Mesh/MeshApps/UseCases|Use Cases]] were developed for the mesh.

We have also interviewed a number of [[Mesh/Interviews_with_other_meshers|other community mesh networks]] from around the world.

=Digital Divide Working Group - OpenOakland (2013) =
== Meeting Minutes ==
* [[Mesh/UserResearch/24_Jan_2013|24 January 2013]]
* [[Mesh/UserResearch/06_Feb_2013|06 February 2013]]
* [[Mesh/UserResearch/19_Feb_2013|19 February 2013]]
* [[Mesh/UserResearch/07_March_2013|07 March 2013]]
* [[Mesh/UserResearch/19_March_2013|19 March 2013]]
* [[Mesh/UserResearch/09_May_2013|09 May 2013]]

== Interviews ==
* Kapor Center - 17 April 2013 - [[Mesh/Interviews/KaporCenter|Notes]]
* Kurt from Youth Radio - 22 April 2013 - [[Mesh/Interviews/YouthRadio|Notes]]

=User Research for Tidepools (2013)=
==February==
*'''7th, 5:30-7pm''': Alcides Gutierrez - [http://vaporone.com VaporOne] - Designing a community mesh in Exelsior, San Francisco. [[Mesh/UserResearch/Interviews/Alcides|Interview Notes]]
*'''10th, evening''': George Gleason - CTel - Creating a worker-owned cooperative telephony/mesh network to compete with AT&T. '''Transcription forthcoming''' [[Mesh/UserResearch/Interviews/George|Interview Transcription]]
*'''11th-16th''' Attempts to schedule interview with Cassandra Chen - SOL (Sustaining Ourselves Locally) / Teacher at [http://www.ousd.k12.ca.us/site/default.aspx?PageID=1 Oakland Unified School District] - Works with middle- and high-school youth in East Oakland; has worked on neighborhood mapping projects.
*'''18th, evening''': Jen-Mei Wu - [http://oaklandmakerspace.wordpress.com Liberating Ourselves Locally - Oakland Makerspace] - Founder of a People of Color (POC) run and led makerspace in East Oakland that works alongside several other DIY community-based organizations. [[Mesh/UserResearch/Interviews/LOLspace|Interview Notes]]
*'''22nd''': [[Mesh/UserResearch/Interviews/Bikery|Attempts to schedule interview]] with Matt from the Bikery, who also has a home 510pen node.

==March==
*'''6th''': [[Mesh/UserResearch/Interviews/YouthMovementRecords|Attempted Communication]] with [http://www.youthmovementrecords.org/ Youth Movement Records] - Organization that gets youth involved in music production and community leadership.
*'''6th-13th''': [[Mesh/UserResearch/Interviews/Spike/Communications|Attempts to Schedule Interview]] with Spike at [http://www.urbanstrategies.org/ Urban Strategies] - Oakland organization focused on transforming low-income communities.
*'''14th, 2-3pm''': Angela Woodall - Reporter for the Oakland Tribune passionate about open data and app development, interested in discussing ideas for a crisis response app. [[Mesh/UserResearch/Interviews/Angela|Interview Notes]]
*'''18th, 3-4pm''': Open Garden - Startup focused on developing more robust internet connectivity through creating a network of bluetooth-enabled devices. [[Mesh/UserResearch/Interviews/OpenGarden|Interview Notes]]
*'''19th-22nd''': Sustainable Economies Law Center - "Education, research and advocacy for just and resilient local economies." [[Mesh/UserResearch/Interviews/SELC|Correspondance with Sustainable Economies Law Center]]

==Informants==
*Mark Burdett - [http://510pen.org 510pen] / [http://eff.org EFF] - Resuscitating an East Bay community mesh network, with a number of nodes deployed but currently inactive concentrated in East Oakland. Interested in integrating Tidepools.
*Greg Bloom - Provisions Library - Failed community mesh project in DC, now developing a social services directory to integrate with LocalWiki.
*Beau - The #Fort - Mobile hackerspace out of an ambulance, seeding grassroots pop-up hackerspaces across the U.S. Mobile mesh node.
*Dennis - [http://eastbayjobdevelopers.org East Bay Job Developers] - Dedicated to helping youth, low-income, formerly incarcerated, homeless, and veterans find jobs in the East Bay and learn basic digital literacy skills.
*Bilal Ghalib - [http://gemsi.org GEMSI.org] - Starting and documenting makerspaces across the Middle East.

==Still to reach out to==
*[http://oaklandwiki.org/Oakland_Public_Library_Computer_Education Oakland Public Library Computer Education] - Oakland Public Library branches offer computer education and training. Mesh nodes in public libraries??

=Interview Questions=
==For People Working on Mesh Projects==
*Who is this mesh network for? (What sorts of communities do you personally feel drawn to serving?)
*How are you involved in your communities mesh network? What is your role?
*What is the goal of this network/project? What are some of the problems you're looking to solve with your project?
**(if this is a goal) How will the community mesh network enhance civic participation? face to face interaction?
*What kinds of data do you see as important for residents / community members to have instantly available to them?
**What information do individuals want to share with each other within a community?
*What are the challenges that you see to making a community mesh network happen? What do you need to address these challenges?
*Do you have funding for the project? What is it from?
*What other organizations / projects (or types of organizations / projects ) are you going to be / hoping to collaborate with?

==For Organizations Addressing Access to Technology==
*Who (e.g. groups and communities) does your organization serve?
*What is your service / what do you provide for the community you serve?
*What's your role in the organization?
*How is your organization addressing the issue of access to technology in Oakland? What is your overall goal? How do you work to achieve that goal day to day?
*What technologies / apps are you currently using? What do you use to organize? To socially network online and offline? To spread information? To solve problems?
*What kinds of technologies are being used by the people you serve? What do you they to organize? To socially network online and offline? To spread information? To solve problems?
*What resources do you wish you had access to day to day?
*What kinds of data do you see as important for residents / community members to have instantly available to them?
*What would you need in order to effectively achieve your mission?
*What challenges do you face in achieving your mission? / What are some of the potential barriers to success for the organization?
*What other sorts of organizations / projects are you working with or are you hoping to collaborate with?

[[Category:MeshResearch]]

Mesh/Meetings

2018-06-10T20:58:37Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

'''In the first half of 2018, we've had at least one significant meeting with another organization each month. This page is not reflective of our current outreach.'''

This page documents meetings we've had with other organizations. Looking for sudomesh [https://sudoroom.org/wiki/Mesh/Minutes Meeting Minutes]?

*15 November 2013: [https://sudoroom.org/wiki/Mesh/InternetArchive Meeting #1 with the Internet Archive] [Matt, Jenny, Mitar]

Mesh/Inventory

2018-06-10T20:57:07Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

'''As of June 2018, we just reorganized the mesh cage. A more recent and up-to-date inventory of our materials is underway, but will likely be hosted elsewhere. Link to follow.'''

= current-gen nodes =

== ready for outdoor mounting ==
NOTE: UPDATE WITH NEW DONATIONS AS OF 10/2017
* 1x [[Nanobridge M5 (25 dB version)]]
* 3x [[Nanobridge M5 (22 dB version)]]
* 3x [[Nanostation M5]]
* 1x [[Nanostation M2]]
* 2x [[Rocket M5]] and 2x 90 degree panel antenna (one antenna already on rooftop)

All of these are complete (with PoE).

== ready for indoor use ==

* ~150x [[Western Digital MyNet]] N750s or N600s

All of these are complete (with power supply).

== used gear ==

* Some [[Bullet M2]]s and some [[Bullet M5]]s. Need to count.

= previous-gen nodes =

== used gear ==

* Maybe ~15x [[Picostation 2HP]] ?
* A bunch of [[Bullet 2HP]]

== incomplete gear ==

* More than 100x Meraki sparky (also known as Meraki outdoor)
** No cases, power supplies or antennas (u.fl connector)
** Needs special script for hardware watchdog.
** Flashing takes ~20 mins

= PoE adapters =

* ?

= Cable =

== Ethernet ==
* Maybe 1/4 roll of a 100 foot outdoor UV-protected shielded and grounded CAT6
* A bunch of indoor CAT5 and CAT5E
* Bunch of RJ45 connectors
* Bunch of grounded RJ45 connectors

= Antennas and pigtails =

We have a bunch of high-gain omnis, a bunch of dish (the grid type) antennas, and a few panel antennas. Most of these are N connectors. We need to go through them, check frequency and tag them with frequency.

We have a bunch of u.fl to male N pigtails.

We have a bunch of GPS antennas.

= Tools for node-mounting =

== Big tools ==

* One foldable woodworking table (like [http://www.powertoolsdirect.com/media/catalog/product/cache/1/image/9df78eab33525d08d6e5fb8d27136e95/b/l/black-and-decker-wm626-dual-height-tough-workmate_1.jpg this])

== Hand tools ==

* One decent RJ45 crimper (blue handle) with somewhat worn out cutting blades
* 2x low quality RJ45 crimpers (green handle). Probably OK for crimping but not for cutting or stripping.
* A set of screwdrivers, wire cutter, tongs, and other basic hand tools.

== Power tools ==

* Makita impact driver (battery powered)
* Makita drill (battery powered)
* Makita battery charger
* 3x Makita batteries

== Testing ==

* Two ethernet cable testers (need batteries)

= Consumables for node-mounting =

TODO put stuff like mounting brackets, plumbers tape, screws, silicone, hose clamps, cable staples.

= Other stuff =

* 3x One Laptop Per Child XO Laptop (one power supply)
* Lots of other stuff that needs.

= Less than useful stuff =

* A bunch of random indoor routers that don't support OpenWRT
* A bunch of random indoor routers that do support modern OpenWRT but no two are alike
* A great big stack of the original blue linksys routers. These only support old versions of OpenWRT.

Mesh/Legal

2018-06-10T20:55:10Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

'''We've been a legit 501c3 for years now.'''

= Organization structure =

The mesh organization will be a 501(c)3 but will not own the mesh routers. The mesh hardware will be owned by the community that makes up the mesh.

= Internet sharing =

We're asking node owners to share their Internet connections with the mesh (if they have Internet). This poses two potential problems:

# Legal: Is the node owner liable if mesh users conduct illegal activity over the node owners' Internet connection?
# Terms of service: Some ISPs disallow sharing of Internet connections in their terms of service

== Legal liability ==

The EFF has already done the research on potential legal liability of Internet connection sharing. They have launched a campaign to encourage people to open their wireless access points, the [https://openwireless.org/ Open Wireless Movement]. From the website:

<blockquote>
Will opening my network make me liable for others' illegal actions?

This one is a bit more complicated, but the short answer is, "We don't think so."
</blockquote>

The EFF has more extensive information on this issue [https://openwireless.org/myths-legal here].

In addition to the reassurances by the EFF, sudomesh provides an additional layer of legal protection. All Internet-bound traffic from the mesh network is routed through VPN servers owned and operated by sudomesh (we call them exit nodes). When law enforcement see illegal activity, the source IP address will be listed as operated by sudo mesh, so they will contact us first and we can likely stop most legal inquiries at this point. This means that node owners won't have to deal with things such as routine DMCA notices.

This system was copied from [https://wlan-si.net/â€Ž wlan slovenja], the Slovenia mesh group.

== Terms of service ==

Some ISPs allow sharing of Internet access and others do not. We provide node owners with a list of local ISPs that are known to allow sharing of Internet access and advise them that some ISPs may not allow sharing. The worst case scenario here is that one or more users get their Internet disconnected for terms of service violation.

The ISPs in the East Bay that allow Internet Connection sharing (that we know of) are:

*[http://www.monkeybrains.net/ MonkeyBrains wifi]
*[http://www.sonic.net/ Sonic.net DSL] - [https://wiki.sonic.net/wiki/Category:Policies Policies]
*[http://www.lmi.net/ LMI (Sonic.net reseller) DSL]
*[http://www.netwood.net Netwood DSL]
*[http://www.hughesnet.com Hughes Net Satellite Internet]

= Exit nodes =

The exit nodes will be owned by the 501(c)3.

With regards to running exit nodes, Noisebridge, another 501(c)3, already runs a Tor exit node which should be legally similar to a mesh exit node.

Some links of interest:

*[https://www.noisebridge.net/wiki/Noisebridge_Tor NoiseTor wiki page]
*[http://tor.noisebridge.net/ NoiseTor website]
*[https://www.noisebridge.net/wiki/Tor_FAQ NoiseTor FAQ]
*[https://www.torproject.org/eff/tor-legal-faq.html Tor Project's Legal FAQ]
*[https://www.torproject.org/docs/faq-abuse.html.en Tor Project's Abuse FAQ]
*[https://www.torproject.org/eff/tor-dmca-response.html.en Tor Project's DMCA Response Template]
*[https://www.noisebridge.net/wiki/Noisebridge_Tor/FBI NoiseTor how to deal with the FBI]
*[https://www.torproject.org/eff/tor-legal-faq.html EFF's Tor legal FAQ]
*[https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs EFF's list of Good ISPs]

= Peering agreement =

If nodes are not owned by an organization, then some other way of agreement of how nodes should be operated should be made. One approach is to see each node as being peered with others and create agreements about how the rules the traffic should go over those links. Another is to extend such agreement into a license and also add rules about how the nodes themselves should behave.

*[http://interop.wlan-si.net/wiki/Legal/Licenses List of current existing agreements/licenses]

Mesh/ToDos

2018-06-10T20:53:44Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

'''We now use a number of other tools to manage our active tasks. As of June 2018, we use Trello for kanban boards, and we set a weekly list of action items at each Tuesday meeting.'''

Below are a list of To Do items, separated by topical area. If you decide to take one on, please post your name after the item and send a note to the mailing list with your plan of action! We welcome contributions of tasks, also :)

=Community Outreach ToDos=
*Conduct User Research on what sorts of [[Mesh/MeshApps|Local Services]] people would like to have [Jenny, you?]
*Write up a compelling argument for mesh re: disaster preparedness [cite sources] [Jenny, you?]
*Outreach to churches with succinct argument [cite examples, e.g.; Sandy relief]
*Poster/flier at local coffeeshops, bikeshops, co-ops, collectives, community resource spaces, etc;
*Walkabouts/canvassing in E Oakland, Berkeley, Downtown Oakland
*Find folks in El Cerrito / Albany who can help us link up to the Internet Archive's Richmond node
*[https://sudoroom.org/wiki/Mesh/Presentations Presentations / talks / events promo]
*See if people in school system want to work with us to ensure every student has home connectivity
*Convince libraries to share their connectivity

=Operational Logistics=
*Make a project roadmap
*[https://sudoroom.org/wiki/Mesh/Funding Grants and other funds we can apply for]
*Financials [current and projected] [Jenny, you?]
*Time [of volunteers needed to sustain project]
*Tax status (set up 501c3) [Marc, Matt, Jenny]
*[https://sudoroom.org/wiki/Mesh/Funding#Sustainable_Business_Models Business models]

=Marketing / Branding=
*Blog posts [Jenny, you?]
*Articles & Research [Jenny, you?]
*Photo album [OpenPhoto?]
*Design 'pods' for the outdoor routers [eg; birdhouses, planterboxes]
*Infographics
*Videos
*Fliers
*Poems, songs and flags
*Bios, titles and photos of team members

=Technical=
*More brainstorming on [[Mesh/MeshApps|local applications]]
**Timebank
**Sensors - noise, gunshots, pollution [talk to nerds for nature]
**Hosting - Raspberry Pi/Beaglebone black provisioning; mesh app distributions; etc.
*See [[Mesh/Software ToDo|Software ToDo]] for ToDo items related to firmware and software.

Mesh/Firmware

2018-06-10T20:41:54Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

'''For now, please see the [https://github.com/sudomesh/sudowrt-firmware firmware repo] on GitHub.'''

For the new ToDo see [[Mesh/Software ToDo|Software ToDo]].

= ToDo =

[https://github.com/sudomesh/sudowrt-firmware/issues?q=is%3Aopen+is%3Aissue+milestone%3A%220.3+-+Improved+UI%22 Issues for version 0.3]

Issues for later versions:
* Basic admin web UI for node database that let's you log in and list current nodes.
* fake captive portal working
* service browser working
* hardware watchdog working on ar71xx
* support for manually configured non-openwrt extender nodes
** Allow user to switch ethernet ports into "extender node (manual)" mode
** Only one network (either adhoc or open) can be extended using this mode. The user must be able to select which.
** Set up port forwarding from home node to each manually configured extender node for web UI access, e.g. 1443 to 443 on extender node 1, etc.
*** This can be always-on for e.g. up to 16 ports without causing problems since it is only for traffic destined for the home node IP.
*** There should be links to the extender node web UIs from the home node web UI.
* Apply for internet-routable IPv6 subnet and give each node their own subnet + hand out IPv6 addresses to clients
* extender node firmware working on old atheros chipset
* Remote firmware updates working
** Use either DNS-SD to list and pick an update server at random or IPv6 multi-homing?
* Remote automated root password reset (via h.sudomesh.org)
* IPv6 support for extender nodes
* Figure out how to legally use lower 5 ghz frequencies and ensure fancy back-off features are working
* Run OpenVPN on exit node.

In the future:
* Support TDMA on Linux (Adri is working on FreeBSD support, maybe we can port).

= Stuff we are working on =

<big>Ranked from most to least important</big>

== InternetIsDownRedirect ==

When the node doesn't have internet access, it will redirect traffic to our mesh hosted [[Mesh/Firmware#Splash_page|Splash Page]].

We need something hosted on the node that can check if it has access to the internet. There's a bit of an issue where certain OSes won't connect to APs that don't have internet access. [[User:Juul|Juul]] will look into building a hack that properly manages these requests and redirects them to our node-hosted site.

InternetIsDownRedirect may also have to fake the expected captive portal detection responses? We need to figure out if android/iOS/Mac/Windows will connect to a wifi that does not have internet access.

Status: Implemented except for OS-specific captive portal requests.

== Splash page (Garden Gnome) ==

We can capture OS specific probes in order to specifically redirect captive portal requests without affecting any other network traffic.

Chris (snake_wrangler) was working on it and calling it the Garden Gnome.
[[User:maxb|maxb]] picked up the idea and ran with it in nodejs: https://github.com/sudomesh/garden-gnome

Features:

* Brief info on the mesh
* Link to our website?

Status:

[[User:maxb|maxb]] has implemented it! We need a tiny bit of polishing, especially for corner case browsers.

== Extender node firmware ==

See the [[Mesh/Technical Overview]] to learn about home nodes and extender nodes.

With the extender node firmware we're targeting a variety of hardware (if not chipsets), and we don't want to run any sort of makenode after the firmware has been flashed.

We're doing this by creating a /file/etc/uci-defaults script which will run first boot and can set configs depending on the "board" type:
[https://gist.github.com/max-b/97bd7d59259cfbdfbbb2 uci-defaults script gist]

== Mesh Protocol ==

[http://www.open-mesh.org/projects/batman-adv/wiki BATMAN-adv] was the protocol that we had assumed we'd be able to use. Unfortunately, it looks as though it won't support tunneling over the internet, which is one of the primary features we had been hoping to implement. See [https://lists.sudoroom.org/pipermail/mesh-dev/2014-October/000019.html our mailing list convo].

We're now using [https://github.com/jech/babeld babel]. It's been looking pretty good for our particular applications. There are some security/trust issues that we'd like to investigate further - see http://lists.alioth.debian.org/pipermail/babel-users/2015-April/001973.html for some ideas that babel might incorporate in the future.

Status: Ready, but can be improved

== Multiple virtual network interfaces with their own SSIDs ==

*The Mesh interface: An ad-hock mode, unprotected interface for the mesh nodes to talk to each other with Babel handling routing, ssid: pplsopen-node2node
*The Open interface: An access-point-mode, unprotected interface, for non-mesh devices to connect to the mesh, ssid: peoplesopen.net
*The Private interface: An access-point mode, private interface with WPA2, for the people who own the nodes, ssid: Decided by node owner

Traffic on the private interface should be completely separated from traffic on the non-private interfaces unless a client connected to the private interface requests an IP on the mesh.

Maybe the last one is optional because some people may not need that feature (they already have another access point and they want to keep it), but then how do people administrate the router?

In order to serve a secure web admin config to home users, we'll probably always serve 3 APs with one private WPA encrypted home link so that users can access their admin page.

Status: Implemented

== Web admin interface ==

Development information should be put in [[Mesh/Firmware/Web_Admin_Development|Web Admin Dev]]. This section can remain a wish-list.

A very simple one-page interface. It should do at least the following:

*Display some set of user statistics
:Ideally we could list/graph the number of people who have associated with your mesh node.
:We could also just list/graph the up/down data of people who have been using the mesh.
:[http://lightsquid.sourceforge.net LightSquid] (used by pfSense)

*Set location, name, description.
:But do you want to know the location centrally as well so that you can display nodes on the map? Will people enter this information twice or will you pull this information from nodes and then display on the map? Same for name and description. I would suggest that information is stored only once. In your case on the node itself. So probably you can then pull this information through nodewatcher scripts on nodes and then display nodes the map. Just really should not require people to enter or maintain information on two places because it desyncs very fast. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)
*Let people select how much bandwidth they share.
:They always share 100% when they're not using the connection themselves.
::This works if people are using their private SSIDs on the node. But if the node is connected to their existing home network you might not easily configure such sharing. But maybe there is a way to detect that host network is free and can limits can be increased. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)
:Do any ISPs have bandwidth caps around here? If so, let people specify how many MB to share per month.
:Maybe also a button for temporary increase limits (make them more restrictive) which are then after some time automatically restored.
*Let people change the admin password and the private wifi wpa2 password.
:Probably private SSID as well.
*Donate / "buy routers as presents for your friends"-button.
:One idea we had (but this is probably better for splash screen) is "adopt a node". Where a neighbor who uses a node a lot and depends on the node can donate some money to keep it up, but can then give a nickname or avatar to the node. Or something. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)

Status: [[User:Maxb|Maxb]] implemented a luci-based ui. We decided we hate luci, so we're going to use the ubus uhttpd rpc protocol with a jsonrpc front-end. It's a bit copy-pasta'd from the openwireless router.

Source here:

https://github.com/sudomesh/sudowrt-luci2-webclient

== Remote Updates ==

Once we deploy nodes, we'll want a way to update them as appropriate. The already built node configurator operates along similar lines, but we'd need to do some tweaking in order to make it work on the mesh. Also, we'd want to give the users the options to turn remote updates off. A somewhat decentralized system would be nice as well.

== Watchdog script ==

Node tests itself to see if it has connectivity, etc and resets itself if necessary. OpenWrt supports the hardware watchdog on our PicoStations without any additional hacking, yay!

By default the hardware watchdog will automatically hard-reset the AP if /dev/watchdog is not written to at least once every 60 seconds. A Lua library has been written to interface with the batman-adv kernel module through the batctl command line utility. We need to identify a list of conditions that require a hard-reset and work them into the Lua watchdog script in the openwrt-firmware repository.

The Freifunk group has an awesome watchdog setup, details: http://wiki.freifunk.net/Kamikaze/LuCI/Watchdog

list of possible reset conditions: high sustained load, cron goes down, sshd goes down.

[https://github.com/wlanslovenija/firmware-packages-opkg/tree/master/util/nodewatcher-watchdog nodewatcher watchdog]

Potential use of [https://en.wikipedia.org/wiki/Quilt_%28software%29 Quilt] to update nodes.

== Quality of Service (QoS) ==

We want those who own a node to decide how much internet they share with the network. This software allows users to shape their bandwidth based on type. There's an paper regarding [http://www.scribd.com/doc/155501125/Layer-7-Classificarion-and-Policing-in-the-PfSense layer 7 traffic shaping] too.

Our supported hardware needs a very lightweight software, which is why we've been using [http://lartc.org/manpages/tc.txt tc] (traffic control). It only allows the users to determine how much internet they share with the network.

'''Complete Distributions'''

These have firewall and network management tools included with the distribution.

* [https://www.pfsense.org/ pfSense] - a widely used firewall distribution, but there are most definitely difficulties with it.
* [http://www.zentyal.org/ Zentyal] - a firewall distribution with easy to use graphical interface.
* [http://m0n0.ch/wall/ m0n0wall] - a lightweight firewall distribution meant for embedded systems.

'''Packages'''

These are tools often used in network management distributions.

* [http://www.netfilter.org/ netfilter/iptables] - a set of hooks inside the Linux kernel that allows kernel modules to register callback functions with the network stack.
* [http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2 iproute2] - a collection of utilities for controlling TCP / IP networking and traffic control.
* [http://l7-filter.clearfoundation.com/ l7-filter] (p2p filtering) - identifies packets based on application layer data. It classifies packets to be used with a bandwidth shaper.
* [http://www.ipp2p.org/ ipp2p] (p2p filtering) - identifies peer-to-peer (P2P) data in IP traffic.
* [http://suricata-ids.org/ Suricata] - a high performance network [http://en.wikipedia.org/wiki/Network_intrusion_detection_system intrusion detection system] (IDS), [http://en.wikipedia.org/wiki/Intrusion_prevention_system intrusion prevention system] (IPS), and network security monitoring engine.
* [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls-ipfw.html ipfirewall] (ipfw) - a freeBSD firewall that uses netdummy.
* [http://info.iet.unipi.it/~luigi/dummynet/ netdummy] - a freeBSD traffic shaper and bandwidth manager.
* [http://people.freebsd.org/~mtm/ipfw-classifyd.tar.bz2 ipfw-classifyd] - an application layer classifier for ipfw firewall for freeBSD.

== Virtual Private Network (VPN) ==

The firmware should tunnel all internet traffic from the mesh through a VPN server, unless this feature is specifically disabled. This should not be a single server, as that would be a single point of failure.

* [https://github.com/sudomesh/tunneldigger TunnelDigger] - a lightweight tunneling client/server.
* [https://github.com/heyaaron/openmesher OpenMesher] - another option, but not ideal because of memory constraints on embedded systems.

Here is our [[Mesh/Network_topology|Network Topology]].

== Mesh VPuN ==

If the mesh does not see any other nodes (and maybe even if it does?), and it has internet, then it should connect to another node or two over a [[VPuN]] server. The easy solution is to use the same VPuN servers as for the internet connection.

[[Mesh/Network_topology|Network Topology]]

Status: Implemented

== Location and status reporting ==

Something that reports location and status when polled. I think we can probably get away with using snmp v1.

We developed this format and easy to publish status data from nodes for our [http://dev.wlan-si.net/wiki/Nodewatcher/NodeTelemetryProvider nodewatcher]. OpenWrt packages are [https://github.com/wlanslovenija/firmware-packages-opkg/tree/master/util here]. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:02, 11 July 2013 (PDT)

Nice to have:

*Status info: How many nodes is your node connected to. Is the internet link working.
*An "I don't know what my internet bandwidth is, test it for me"-function.
*Usage statistics (so people can see how many people they helped get internet!)
:This is the most important thing! [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)
:You should add as well graphs on how much bandwidth was consumed by the node. This is useful when hosts see that their Internet is slow and believe that it was because of the node. Then they can check and see if it is really node (which often is not) or maybe just ISP has problems. Important because people like to attribute issues they have to nodes they don't understand. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT)
*Let people put up a bit of info about their node / house / co-op, on a simple web page that people can access only if they're connected to that node. It could be shown as part of the splash page.

Status: Waiting for nodewatcher project to finish

== Intelligent Wifi Channel Switching ==

It would be nice to be able to have the network intelligently determine channels but we don't want a node changing channel if it means other nodes connected to it will have to change as well so it may make sense to only set the channel once on first boot based on which channels have other nodes.

== IPv6 support ==

We should have IPv6 support, but I am ok with launching the mesh with only IPv4 and adding in IPv6 later. We can do without IPv6 but not without IPv4 ([[User:Juul|Juul]] ([[User talk:Juul|talk]]))

= Stuff the firmware could have =

== DNS server ==

Each node could run its own (caching) DNS server.

For now, if you're logged into the private network on a node, going to http://my.node will take you to the web admin interface

Status:

Implemented web admin URL, but no caching DNS server yet.

== RSSI Testing and Logging ==

At intervals, the nodes could conduct RSSI tests and log them with some way to compare and visualize signal strengths over time.

== Caching web proxy ==

We could use [http://www.pps.univ-paris-diderot.fr/~jch/software/polipo/ Polipo] to improve people's browsing experience. Not sure how much cpu and memory this would need. We may not be able to run it on the routers with less than 32 MB ram (e.g. the Bullet 2 HPs).

Maxb has installed polio as a transparent caching proxy on a picostation 2HP. It improved web browsing significantly! However, it sorta breaks "net neutrality". Also - it'll be irrelevant for https and it might break some things (webdav?).

I wonder if you could (as an end user?) enable/disable this kinda proxying? On splash page? We would need MAC, but it would only get logged on the mesh node itself (not network wide....)

== Block ads and tracking ==

We could use e.g. [http://www.pps.univ-paris-diderot.fr/~jch/software/polipo/ Polipo] with the sources from both adblock plus and ghostery. If we implement this, it should be an optional (default off) feature that you can select on the splash page, with a "remember this" that remembers either using a cookie or using your MAC (but then we'd be logging people's MAC addresses :-S). The block should probably be time-limited (e.g. 30 days).

Now that we're running more powerful devices, I wonder if we could actually run this kind of blocking on the actual mesh nodes. That way we could do a "remember this" MAC and only store it on the mesh node itself (NOT network-wide).

= Compatible devices =

We're going to target ar71xx devices with decent storage + processing speed + memory for "router board" nodes.

Right now we're using for "router board" nodes:
WD MyNet N750 and/or TP-Link TL-WDR4300
The MyNets are no longer in production, but the TL-WDR4300 are the exact same board, just with external antennas.

Then we are using [[extender node|extender nodes]] which plug into the home node and just bridge/forward traffic. This could theoretically be any router which supports openwrt. We've begun by targeting a variety of ubiquiti long-distance outdoor radios (Nanostation M line, Bullet M line, Picostation M line, Nanobridge/beam/etc).

We would also like to support non-openwrt routers (like Ubiquiti Airfiber and Nanobeam 802.11ac devices) but these will only be able to extend one of the three networks (Mesh, Public or Private) and will need to use WDS mode to do so (at least for Mesh).

Mesh/Diagrams

2018-06-10T20:41:10Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

On this page are various diagrams to explain the network. At the top are technical diagrams, which can be used as diagrams of reference and record, hopefully improved to always be reflective of the network's essential elements and their relations.

==Outreach Diagrams==
We need more outreach diagrams! Please help!

You can base outreach-focused diagrams on elements of the technical reference diagrams below:

==Reference Diagrams==

Reference diagrams are for documentation and technical reference purposes, which can hopefully be helpful to provide a basis for creating easily understandable, accurate, and engaging [[Mesh/Diagrams#Outreach_Diagrams|outreach diagrams]].

===Network Topology Diagram===
The following diagram describes the essential technical elements of The People's Open Network. Uses the peoplesopen.net [[Mesh/Website#font|font]] and [[Mesh/Website#Color Scheme|color scheme]].

<gallery mode="nolines">
File:Network topology diagram-lo.png|png (lo)
File:Network topology diagram-hi.png|png (hi)
File:Network topology diagram.pdf|pdf
File:Network topology diagram svg.svg|svg
File:Network topology diagram plain.svg|plain svg
</gallery>

The diagram's '''key''' includes the following types of items, which are also described in relation to one another below.

* '''2.4ghz Node'''
** Typical router running mesh firmware used in a node operator's home, office, public space, etc.
* '''5ghz "Backbone" Point-to-Point Node'''
** Special router running mesh firmware as well, but broadcasting and receiving on the 5ghz frequency that can travel longer distances than 2.4ghz, and is regulated by the [http://en.wikipedia.org/wiki/Federal_Communications_Commission FCC] for use in point-to-point connections only. These are therefore helpful to create a "backbone" on the network that can both:
**# connect neighborhoods to one another when reasonable connections with '''2.4ghz Nodes''' are not possible
**# ensure users of '''2.4ghz Nodes''' are within a few hops (through other nodes on a path) to strong and stable connections to the rest of the local network (peoplesopen.net) and substantive internet lines (e.g. a small ISP or donated line from the Internet Archive, etc).
* '''Relay Node''' "Virtual Public Network" (VPuN) Tunnel Server & Client
** Server running linux and the TunnelDigger server and client software to create Virtual Public Network (VPuN) connections over generic internet connections. This tunnel software creates a connection using the internet underneath it, so at this point, traffic to '''Relay Nodes''' is considered public in the same way it is on the public global internet. Simply, the distinction is between passing purely local traffic, and traffic that is virtually local, but must use an internet connection to reach the necessary destinations.
**The term "Virtual Public Network" or VPuN has roots in GNUnet https://gnunet.org/gnunet-vpn and is situated in this historical piece http://www.isaca.org/Journal/Past-Issues/2001/Volume-3/Pages/Virtual-Private-Networking-Confidentiality-on-Public-Networks.aspx. TunnelDigger technically qualifies as "Virtual Private Network" software (with a major lapse in not actually providing access control mechanisms as is the point of most VPN software), but this "private" term is more generic than we can be (see https://en.wikipedia.org/wiki/VPN#Unencrypted_tunnels). Instead, we have opted for a socially and historically situated alternative that is both more descriptive and mission-consistent with sudo mesh's work and the values behind the People's Open Network: ''Virtual Public Network (VPuN)''.
** Note: if, for instance, the '''5ghz Backbone Nodes''' in the diagram above are disconnected (maybe interference one day), then requests across the network (say from one neighborhood to another) can still pass virtually using the internet, out to '''Relay Nodes''' and back down.
* '''Exit Gateway'''
** Same as '''Relay Node''' but designated as a ''gateway'' or the final stop between users on the ''peoplesopen.net'' network and out to the public internet (leaving the Virtual Public Network). The gateway is likely to communicate through '''Relay Nodes''' rather than directly with '''2.4ghz Nodes''' and '''Backbone Nodes'''.

===Node Traffic Diagram===
<gallery mode="nolines">
File:Node traffic diagram-lo.png|png (lo)
File:Node traffic diagram-hi.png|png (hi)
File:Node traffic diagram_pdf.pdf|pdf
File:Node traffic diagram.svg|svg
File:Node traffic diagram plain.svg|plain svg
</gallery>

The diagram's '''key''' includes the following types of items:

* '''2.4ghz Node'''
** Based on same object as [[Mesh/Diagrams#Network Topology Diagram|Network Topology Diagram]]
* '''Power-over-ethernet (POE) power injector (supply)'''
* '''wifi-capable user devices (e.g. laptop, smartphone)'''
* '''network interface to internet (e.g. ISP modem)'''
* '''power''' sources

====Animation====
* Seeking to create something like this: https://commons.wikimedia.org/wiki/File:Torrentcomp_small.gif
* Limited success with this <code>svgani</code> python script: http://www.mbeckler.org/inkscape/svgani/
** Could still make multiple semi-crappy, basic animations this way. Limitations on the string replacement aspect.
* Best bet may actually be to animate by hand using this: http://edutechwiki.unige.ch/en/Using_Inkscape_for_web_animation
** May even be able to convert svg to png frames with this: http://littlesvr.ca/apng/svg2png/
* Sozi may work too: http://sozi.baierouge.fr/

===Network Development===

'''Animation:''' check out this svg animation of the [http://sudomesh.github.io/svg-animations/node_traffic_diagram_animate.svg Network Development Diagram (svg + js, probably only works in modern web browsers)].

This diagram depicts how the network itself and the network's supporting community of active volunteers and '''node-operators''' can grow over time. The final stage of the diagram shows some disconnected nodes in the network, to symbolize how a real network does not remain neatly tied together as it expands.

<gallery mode="nolines">
File:Network development diagram-lo.png|png (lo)
File:Network development diagram-hi.png|png (hi)
File:Network development diagram_pdf.pdf|pdf
File:Network development diagram.svg|svg
File:Network development diagram plain.svg|plain svg
</gallery>

==Animated SVG Diagrams==
Using the [http://sozi.baierouge.fr/ Sozi] extension for [http://inkscape.org/ Inkscape], which more seamlessly implements aspects of [http://sozi.baierouge.fr/pages/tutorial-first.html svg-based animation] visible in a web browser as [http://edutechwiki.unige.ch/en/Using_Inkscape_for_web_animation documented here] with some additional Sozi-based javascript included. The results are quite good and will be posted in [https://github.com/sudomesh/svg-animations this github repository] and listed below:

* [http://sudomesh.github.io/svg-animations/node_traffic_diagram_animate.svg node_traffic_diagram_animate.svg]
* [http://sudomesh.github.io/svg-animations/all_diagrams_animate.svg all_diagrams_animate.svg]

==Draft Diagrams==

* [[Rooftop Dish Antenna Mount]]

==Inspirational Diagrams==

===Wikimedia Commons===
* [https://commons.wikimedia.org/wiki/Topology_(Network) Topology (Network)]
* [https://commons.wikimedia.org/wiki/File:Wireless_mesh_network_diagram.jpg Wireless mesh network diagram.jpg] low-resolution
* [https://commons.wikimedia.org/wiki/Category:Mesh_network Category:Mesh Network]
* [https://commons.wikimedia.org/wiki/File:Internet_map_1024.jpg Internet map 1024.jpg]
* Animations
** From "Mesh Network Basics" in [https://en.wikibooks.org/wiki/Wireless_Mesh_Networks/Mesh_network_basics ''Wireless Mesh Networks''] on WikiBooks:
*** [https://commons.wikimedia.org/wiki/File:Mesh_network_self_healing.gif Mesh network self healing.gif]
*** [https://commons.wikimedia.org/wiki/File:Mesh_network_self_forming.gif Mesh network self forming.gif]
*** [https://commons.wikimedia.org/wiki/File:Mesh_network_multi_hop.gif Mesh network multi hop.gif]

===Wikipedia===
* [https://en.wikipedia.org/wiki/File:NetworkTopologies.svg NetworkTopologies.svg] displays various types of network topologies together
* Animations
** [https://en.wikipedia.org/wiki/File:Torrentcomp_small.gif Torrentcomp small.gif] peer-to-peer algorithm animation (deep)

===WikiBooks===
* [https://en.wikibooks.org/wiki/Wireless_Mesh_Networks Wireless Mesh Networks]

Mesh/Hosting

2018-06-10T20:40:25Z

Eenblam: stale

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

This page details current and future hosting solutions used by sudomesh.

= Production =

== Exit nodes ==
The exit nodes must live up the the following requirements:

*Minimum 100 mbit unmetered bandwidth
*A processor fast enough to saturate 100 mbit with NAT'ed tunneled traffic
*A subnet or IP that lists sudomesh as the abuse contact
*Tor-friendly or Tor-agnostic provider
*Location close to bay area
*Co-located (optional, but we want this in the long term)

=== Possible providers ===

[http://www.oplink.net/colocation.html Oplink]:

*Location: Texas
*Bandwidth: Unmetered 100 mbit
*Tor-friendliness: Unknown
*Will let us be the abuse contact: Unknown
*Price: $80 per month

== Relay nodes ==

The relay node requirements:

*Minimum 100 mbit unmetered bandwidth
*Ability to saturate 100 mbit with tunnneled traffic
*Location close to bay area

=== Possible providers ===

[http://www.vpscheap.net/enterprise-vds.aspx vpscheap] have virtual servers with the following specs:

*VM technology: Xen
*Bandwidth: Unmetered 100 mbit
*Ram: 1 GB
*Dual CPU
*Disk space: 50 GB
*Location: Chicago
*Price: $16.99 per month

== SSL ==

We use free [http://startssl.com/ StartSSL] certificates.

== DNS ==

Our DNS hosting is via namecheap.com. We own the following domains:

*peoplesopen.net (primary, use this in communications)
*pplsopen.net
*peoplesopennetwork.com
*peoplesopennetwork.net
*peoplesopennetwork.org
*sudomesh.org (primary, use this in communications)
*sudomesh.net
*sudomesh.com
*meshthepla.net
*meshtheplanet.net
*meshtheplanet.org
*meshtheplanet.com

== Web and email ==

We currently have a VPS from vpscheap.com. It is hosting web and email for the following domains:

*peoplesopen.net (and variations)
*sudomesh.org (and variations)

The VPS specs are:

*VM technology: OpenVZ
*Ram: 512 MB
*Swap: 1 GB
*Disk space: 50 GB
*Bandwidth: 20 mbit/sec unmetered
*Operating system: Ubuntu
*Cost: $6 a month

== Backup ==

We currently have a VPS from backupsy.com. The domain backup.sudomesh.org points to the server. All sudomesh servers back up to this server using [http://duplicity.nongnu.org/â€Ž Duplicity] once every 24 hours. The backups are incremental so we can restore to any point in time. We do not yet have a policy for how far back we keep backups. The backups are encrypted and the backups cannot be deleted by anyone other than root on the backup server, so gaining access to a sudomesh server does not mean gaining access to deletion of backups.

The specs for the VPS are:

*VM technology: KVM
*Disk space: 250 GB
*Ram: 512 MB
*Bandwidth: 1000 GB per month
*Operating system: Ubuntu
*Cost: $6 a month
*Note: The ToS only let us use this for backup unless we upgrade our plan.

= Development =

== Exit node ==

We have one exit node for development use. Its hostname is exit1.sudomesh.org.

VPS specs:

*Provider: digitalocean.com
*VM technology: KVM
*Ram: 4G
*Bandwidth: 1Gbps with 4TB transfer limit/month
*IP address: 104.236.181.226
*OS: Debian
*Price: $40 per month

Mesh/Network topology

2018-06-10T20:39:04Z

Eenblam: Fix link in stale message

[[Category:Stale]]
'''This page has been marked as [[:Category:Stale|stale]], as it is outdated to the point of providing significant misinformation. Please update it before linking other pages here.'''

[[File:Network topology diagram-hi.png|thumb|png (hi), [[Mesh/Diagrams#Network Topology Diagram|see more]]]]
= peoplesopen.net topology =
For information about the people's open network topology, refer to this [[Mesh/Diagrams#Network Topology Diagram|network topology diagram]].

= wifi topology =

[[File:Mesh topology diagram.png|thumb]]

We use 2.4 ghz 802.11g or 802.11n wifi gear with omni or semi-directional antennas to provide connectivity to devices such as laptops and smartphones at street level and within buildings. We are currently using a variety of gear including Ubiquiti Picostation M2 HP and Ubiquiti Bullet M2 HP routers for the outdoor APs.

A high-speed wireless backbone for the mesh will be provided by 5 ghz 802.11n hardware, usually with point to point or point to multipoint connections mounted in high places such as on rooftops, flagpoles or antenna towers. We currently have a variety of Ubiquiti M5 routers such as airgrids, nanobridges, nanostations and a rocket.

See the [[Mesh/Home and extender nodes|Home and extender nodes]] for more info about how these are setup.

All of the outdoor gear will be Power over Ethernet (PoE), requiring only a single cable for network and power connectivity.

= mesh topology =

All routers run the Babel mesh routing protocol. The street-level 2.4 ghz routers should ideally be able to function in the event that e.g. an earthquake takes out all of the point to point and point to multipoint rooftop nodes (more alignment sensitive) and the mesh should remain functional, though it could become segmented.

The relays / [[VPuN]] servers (see the internet connectivity section) also run Babel, so mesh traffic can flow from one part of the mesh, through the internet, through a relay, and into another part of the mesh if some of the mesh nodes are connected to the internet.

= internet connectivity =

There are four primary types of devices in the mesh:

*Clients: E.g. smart phones or laptops connected to the mesh.
:These do not run the meshing protocol.
*Mesh nodes: Wifi routers running OpenWRT.
:This includes home nodes and their extender nodes
*Relays / [[Mesh/VPuN|VPuN servers]]: Professionally hosted servers that relay mesh traffic over the internet.
:These run the meshing protocol. Mesh nodes are connected to them with L2TP tunnels.
*Exit nodes: Co-located servers that appear as the source IP for packets from mesh to internet.
:Both relays and exit nodes serve as a layer of protection between people sharing their internet connections with the mesh. A relay can also be an exit server and this may in fact end up being the case in most instances.

Some mesh routers will be hosted in homes that already have internet connections. If an internet connection is available, a mesh router will open an L2TP tunnel (using the tunneldigger software) to several relay nodes over the internet connection. A relay could be e.g. a VPS without a bandwidth cap. The relays all run Babel and function as part of the mesh through the L2TP tunnels to the mesh nodes. Each relay will have a connection to an exit nodes. The relays allow segments of the mesh that are not connected with wifi to be connected over the internet.

Each relay is connected to one exit node (tunnel type not yet decided). It does NAT (IP Masquerading) on traffic coming from the mesh and headed for the internet. All traffic coming from the mesh and going to the wider internet goes through an exit node. The source IP of data coming from the mesh thus appears as the IP of one of the exit nodes. This provides a layer of protection such that e.g. abuse complaints will be sent to the mesh organization instead of the individuals who donate some of their internet bandwidth to the mesh.
:Until network has an AS, only one exit node should be made and multiple relay nodes should connect to that exit node (Tunneldigger software can be reused for that). Otherwise clients can have issues when routing protocol decides to move from one exit node to another.
:It is important that nodes are connecting to relays and relays to exit nodes and that no IPs of those connecting to relays and exit nodes is stored.

= Backbone Connections =

== Desired ==

* We have the opportunity to establish a Gigabit link between Oakland and San Francisco, with a connection in San Francisco near the Western most part of 24th street in the [https://goo.gl/maps/TzMBTsadiCL2 Noe Valley] neighborhood. This location has great line of sight with many locations in the East Bay. We would like to establish a relationship with anyone that can grant permission to mount equipment on Laney Tower at [http://www.laney.edu/wp/ Laney College] in Oakland.