Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge in some new directories for improving searchability #127

Open
wants to merge 25 commits into
base: mesh-sync-20190204
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
8c8649f
Add mesh sync notes (#110)
benhylau Feb 11, 2019
73460e3
Create 20190218_mesh-sync-notes.md (#114)
benhylau Feb 21, 2019
7141506
Meet & Greet Drawings!
Shrinks99 Feb 23, 2019
568c579
meetup drawing file name fix
Shrinks99 Feb 23, 2019
6c3e7a7
Create 20190304_mesh-sync-notes.md (#115)
benhylau Mar 6, 2019
4aacfef
Add summary of Toronto Mesh infrastructural services (#113)
benhylau Mar 6, 2019
b60ea34
Update TEMPLATE-HACKMD.md (#118)
benhylau Mar 18, 2019
9b5bacc
Create 20190318_mesh-sync-notes.md (#119)
benhylau Mar 28, 2019
0188c6c
Responsibilties of working group leads
dasanchez May 3, 2019
95ed2dd
Updated Tools and Website lists
dasanchez May 6, 2019
c7a4ead
Merge pull request #120 from tomeshnet/working-lead-description
dasanchez May 16, 2019
ccba6f7
2019-May Planning Session Notes
TimTor May 28, 2019
e0f2cf7
Update coordination-structure.md
TimTor Jun 5, 2019
c89d2a3
Merge pull request #121 from tomeshnet/planning-notes-2019-may
dasanchez Jun 13, 2019
ae97caa
Corrected incorrect name
darkdrgn2k Jun 14, 2019
a5695ad
Create 20190710_mesh-sync-notes.md
darkdrgn2k Aug 1, 2019
f4bfdf2
Update 20190710_mesh-sync-notes.md
darkdrgn2k Aug 1, 2019
dc52653
Update 20190710_mesh-sync-notes.md
darkdrgn2k Aug 1, 2019
f7c0010
Updated mesh notes file with info about The Ramble
Hurricos Aug 4, 2019
4885c0f
Create a digests/ directory for weekly digests for @hurricos
Hurricos Nov 27, 2019
8985f23
Fixups to desc and plans
Hurricos Nov 27, 2019
a31c463
Add index/ and a README for it
Hurricos Nov 27, 2019
2e211ba
Add some hint for how to organize files under `index/`
Hurricos Nov 27, 2019
b4c9579
Dump into index/README.md
Hurricos Nov 27, 2019
6d76e59
Even more updates to the index readme
Hurricos Nov 27, 2019
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions digests/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
===
Digests: A weekly digest for community mesh networking events
===

# Purpose

The documents under this directory are digests by week of different
events in the community internet world (as far as @hurricos saw on
that week). @hurricos intends to publish these digests Friday morning
each week starting 29 Nov 2019.

## How to get on a particular digest

If you want to make sure you're on a particular digest, please send me
an email @ [[email protected]](mailto:[email protected]) before
midnight weekly on Thursday. You can always send me an email if you
want me to see something and put it in here.
177 changes: 111 additions & 66 deletions governance/coordination-structure.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,6 @@ We reflected and discussed on governance during the [November 12 Planning Meetin
- Make use of our decentralized **collaboration tools**:
- Applicable rooms on [our chat](https://chat.tomesh.net/)
- Our [GitHub organization](https://github.com/tomeshnet).

As per the 2018 November Planning Meeting:

- Only people who have been involved with Toronto Mesh for one cycle or longer will be assigned lead roles.

## Decision Making
Expand All @@ -26,107 +23,155 @@ Toronto Mesh uses voting to determine whether we have reached consensus:

## Working Groups

### Responsibilities of Working Group Leads

Central Org
- Organize meetups and planning sessions
- Post event details to the tomesh.net website

Tools
- Maintain the following infrastructure services:
- tomesh.net website server
- chat.tomesh.net Riot UI server for Matrix chat
- matrix.tomesh.net Matrix server
- webmail.tomesh.net Email web client
- y.mirror.tomesh.net and h.mirror.tomesh.net mesh mirrors

Deployment
- Coordinate node deployment efforts

Website
- Maintain the tomesh.net website
- Review pull requests to the [tomesh.net](https://github.com/tomeshnet/tomesh.net) repo

Outreach
- Identify outreach opportunities and share with the rest of the group
- Drive speaking and workshop events

[email protected] Monitoring
- Respond to all messages that arrive to [email protected] address

Code of Conduct Monitoring
- Monitor [email protected] and meetups to make sure members and attendees are following the Code of Conduct

### Cycle VIII (2019 May)

Working group leads established at the May 2019 Planning Meeting:

| Working Group | Lead |
|--------------------------------------------|---------------------|
| **Central Org** (_ongoing_) | Tim |
| **Tools** (_ongoing_) | HeavyMetal |
| **Node Tech** (_ongoing_) | darkdragon2k |
| **Deployment** (_ongoing_) | Tim |
| **Website** (_ongoing_) | dasanchez |
| **Outreach** (_ongoing_) | benhylau, Tim, Ryan |
| **[email protected] Monitoring** (ongoing) | Hank,Tim |
| **Code of Conduct Monitoring** (_ongoing_) | Hank |



### Cycle VII (2018 November)

Working group leads established at the November 2018 Planning Meeting:

| Working Group | Lead |
| --- | --- |
| **Central Org** (_ongoing_) | dasanchez |
| **Tools** (_ongoing_) | HeavyMetal |
| **Deployment** (_ongoing_) | Pedro.S |
| **Website** (_ongoing_) | garry |
| **Outreach** (_ongoing_) | benhylau, Tim, Hank |
| **[email protected] Monitoring** (ongoing) | Hank, benhylau |
| **Code of Conduct Monitoring** (_ongoing_) | Hank |
| Working Group | Lead |
|--------------------------------------------|---------------------|
| **Central Org** (_ongoing_) | dasanchez |
| **Tools** (_ongoing_) | HeavyMetal |
| **Deployment** (_ongoing_) | Pedro.S |
| **Website** (_ongoing_) | garry |
| **Outreach** (_ongoing_) | benhylau, Tim, Hank |
| **[email protected] Monitoring** (ongoing) | Hank, benhylau |
| **Code of Conduct Monitoring** (_ongoing_) | Hank |

### Cycle VI (2018 May)

Sixth working groups with leads established at May 17 Planning Meeting.
Excerpted from [Planning Meeting Notes - May 17, 2017](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20180517_planning-meeting-notes.md)

| Working Group | Lead |
| --- | --- |
| **Central Org** (_ongoing_) | chrisbarless |
| **Tools** (_ongoing_) | chrisbarless |
| **Deployment** (_ongoing_) | Pedro.S |
| **Website** (_ongoing_) | garry |
| **Social Outreach** (_ongoing_) | Kumash |
| **Email Monitoring** (ongoing) | Hank |
| Working Group | Lead |
|---------------------------------|----------------|
| **Central Org** (_ongoing_) | chrisbarless |
| **Tools** (_ongoing_) | chrisbarless |
| **Deployment** (_ongoing_) | Pedro.S |
| **Website** (_ongoing_) | garry |
| **Social Outreach** (_ongoing_) | Kumash |
| **Email Monitoring** (ongoing) | Hank |
| **Code of Conduct** (_ongoing_) | Hank, benhylau |

### Cycle V (2017 November)

Fifth working groups with leads established at November 23 Planning Meeting.
Excerpted from [Planning Meeting Notes - November 23, 2017](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20171123_planning-meeting-notes.md)

| Working Group | Lead |
| --- | --- |
| **Central Org** (_ongoing_) | dasanchez |
| **Tools** (_ongoing_) | benhylau |
| **Deployment** (_ongoing_) | darkdrgn2k |
| **Website** (_ongoing_) | garry |
| **Code of Conduct** (_ongoing_) | dcwalk |
| Working Group | Lead |
|---------------------------------|------------|
| **Central Org** (_ongoing_) | dasanchez |
| **Tools** (_ongoing_) | benhylau |
| **Deployment** (_ongoing_) | darkdrgn2k |
| **Website** (_ongoing_) | garry |
| **Code of Conduct** (_ongoing_) | dcwalk |

### Cycle IV (2017 April)

Fourth working groups with leads established at April 24 Planning Meeting.
Excerpted from [Planning Meeting Notes - April 24, 2017](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20170424_planning-meeting-notes.md)

| Working Group | Lead |
| --- | --- |
| **Central Org** (_ongoing_) | dasanchez |
| (Welcome/Intros) **Onboarding** (_ongoing_) | Pedro.S |
| **Tools** (_ongoing_) | co-lead benhylau, dasanchez, Pedro.S, udit |
| **Website** (_ongoing_) | dcwalk |
| **Virtual Mesh** (_ongoing_) | |
| **Deployment** (_ongoing_) | Pedro.S |
| **Hardware** aka **node.tech** (_ongoing_) | udit |
| **Code of Conduct** (_ongoing_) | dcwalk |
| Working Group | Lead |
|---------------------------------------------|--------------------------------------------|
| **Central Org** (_ongoing_) | dasanchez |
| (Welcome/Intros) **Onboarding** (_ongoing_) | Pedro.S |
| **Tools** (_ongoing_) | co-lead benhylau, dasanchez, Pedro.S, udit |
| **Website** (_ongoing_) | dcwalk |
| **Virtual Mesh** (_ongoing_) | |
| **Deployment** (_ongoing_) | Pedro.S |
| **Hardware** aka **node.tech** (_ongoing_) | udit |
| **Code of Conduct** (_ongoing_) | dcwalk |

### Cycle III (2016 November)

Third working groups with leads established at November 12 Planning Meeting.
Excerpted from [Planning Meeting Notes - November 12, 2016](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20161112_planning-meeting-notes.md)

| Working Group | Lead |
| --- | --- |
| **Central Org** (_ongoing_) | dcwalk |
| (Welcome/Intros) **Onboarding** (_ongoing_) | josh_o |
| **Tools** (_ongoing_) | benhylau |
| **Website** (_ongoing_) | garry |
| **Virtual Mesh** (_ongoing_) | benhylau |
| **Miniconf** (Jan deadline) | dcwalk |
| **Deployment** (Feb deadlines and _ongoing_) | udit |
| **Funding/Grants** (Jan to Mar deadlines and _ongoing_) | anastasia |
| **Code of Conduct** (_ongoing_) | dcwalk, anastasia |
| Working Group | Lead |
|---------------------------------------------------------|-------------------|
| **Central Org** (_ongoing_) | dcwalk |
| (Welcome/Intros) **Onboarding** (_ongoing_) | josh_o |
| **Tools** (_ongoing_) | benhylau |
| **Website** (_ongoing_) | garry |
| **Virtual Mesh** (_ongoing_) | benhylau |
| **Miniconf** (Jan deadline) | dcwalk |
| **Deployment** (Feb deadlines and _ongoing_) | udit |
| **Funding/Grants** (Jan to Mar deadlines and _ongoing_) | anastasia |
| **Code of Conduct** (_ongoing_) | dcwalk, anastasia |

### Cycle II (2016 August)

Second working groups established at August 05 Planning Meeting.
Excerpted from [Planning Meeting Notes - August 5, 2016](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20160805_planning-meeting-notes.md)

| Working Group | Members |
| --- | --- |
| **Prototype** | |
| **Deployment** | |
| **Code of Conduct** | Lee, Nick, Ben, Leandro, Dennis, David, Curtis, Michael, dcwalk |
| **Website** | |
| **Logo** | |
| **Vision Statement** | |
| Working Group | Members |
|----------------------|-----------------------------------------------------------------|
| **Prototype** | |
| **Deployment** | |
| **Code of Conduct** | Lee, Nick, Ben, Leandro, Dennis, David, Curtis, Michael, dcwalk |
| **Website** | |
| **Logo** | |
| **Vision Statement** | |

### Cycle I (2016 April)

First working groups established at April 18 Planning Meeting.
Excerpted from [Planning Meeting Notes - April 18, 2016](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20160418_meeting-notes.md)

| Working Group | Members |
| --- | --- |
| **Hardware** | Ben, Udit, dcwalk |
| **Software** | Ben, Garry |
| **Use Cases for the Mesh** | Udit, Ben, Garry |
| **Outreach** | Vince, Ben |
| **Literacy Development** | Yuri, Matt |
| **Knowledge Management** | Matt, dcwalk |
| **Design** | Matt |
| **Website** | dcwalk, Matt, Garry |
| Working Group | Members |
|----------------------------|---------------------|
| **Hardware** | Ben, Udit, dcwalk |
| **Software** | Ben, Garry |
| **Use Cases for the Mesh** | Udit, Ben, Garry |
| **Outreach** | Vince, Ben |
| **Literacy Development** | Yuri, Matt |
| **Knowledge Management** | Matt, dcwalk |
| **Design** | Matt |
| **Website** | dcwalk, Matt, Garry |
Binary file added images/20190221_meetup-drawings/benhylau.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/20190221_meetup-drawings/dasanchez-1.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/20190221_meetup-drawings/dasanchez-2.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/20190221_meetup-drawings/garrying.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/20190221_meetup-drawings/makeworld.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/20190221_meetup-drawings/shrinks99.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/20190221_meetup-drawings/tim.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
8 changes: 8 additions & 0 deletions index/Media.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
===
Media: Simple things you can share with almost anyone
===

# Sudoroom's propaganda repo
https://github.com/sudomesh/propaganda
- Plenty of links here for stuff like stickers

95 changes: 95 additions & 0 deletions index/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,95 @@
===
Index: An index against over everything community mesh
===

# Preface
For now this is where @hurricos is dumping different lists of sites
and what they're up to. @hurricos intends in the long-run to create or
contribute to a Mediawiki-based wiki to act as an "index" or
"directory" for anyone to get anywhere in the space of community
network projects.

## How should they be organized?
Put things into markdown by category (think: Mediawiki-based
Categories, like at the bottom of the [Mediawiki page for
categories](https://www.mediawiki.org/wiki/Help:Categories))

For now though I'm just stubbing in headers and listing the categories
below it in this readme. Organize it later.

# Media
- Simple things you can share with almost anyone

## Sudoroom's propaganda repo
https://github.com/sudomesh/propaganda
- Plenty of links here for stuff like stickers

## Tomesh / dasanchez' Presentation resources
https://github.com/tomeshnet/tomesh.101/tree/master/presentations
- Great for presenting?? @hurricos hasn't checked this

# Mailing lists

## Sudoroom's mesh mailing list
https://sudoroom.org/pipermail/mesh/
- Fairly active it appears!

## Spinics linux wireless mailing list
https://www.spinics.net/lists/linux-wireless/
- This is good for getting a pulse on how existing hardware is being
maintained under Linux

## OpenWrt mailing list
https://lists.infradead.org/pipermail/openwrt-devel/
- OpenWrt is very popular and this mailing list is used by everyone
for everything.

# Hardware documentation

## Wikidevi
https://wikidevi.com
- This is dead since Hallowe'en 2019. This was the best resource for
hardware info. The database logic that M86 created in it was
migrated by and large to TechinfoDepot.

## Techinfodepot
http://en.techinfodepot.shoutwiki.com/wiki/Main_Page
- This is the inheritor of M86's
wikidevi. [DarkShadow](http://en.techinfodepot.shoutwiki.com/wiki/User:DarkShadow)
is the primary maintainer.
- @hurricos uses Firefox; he right clicked the search button on the
left and "Add Keyword for this Search..." to "tech" so that he could
search-bar "Tech Qualcomm Atheros" to get to [this
page](http://en.techinfodepot.shoutwiki.com/wiki/Qualcomm_Atheros). This
is incredibly useful whenever you need to find information about a
particular chipset, SoC, vendor, driver, architecture. This is where
everyone should put their data about hardware.


## Tomesh's stuff on Github
https://github.com/tomeshnet/documents/tree/master/technical
- These are mostly basically lab reports. Very very useful because
they show practical implementations.

## (How to take pictures of hardware)
You should take pictures of hardware in very bright, very
point-source, very "angled" light. This makes it very clear to see the
stuff printed on the chip on top. See for example [this
picture](http://en.techinfodepot.shoutwiki.com/wiki/File:Meraki_MR24_PCB_Back.jpg)
taken by @hurricos on a Motorola Moto X Pure Edition (an $80 phone
these days). You can spot stuff even normal eyes can't see can't see.

# Mesh groups

## Tomesh
https://tomesh.net
- @hurricos / @darkdrgn2k / @benhylau, etc
- Toronto

## Massmesh
https://massmesh.org/
- @hurricos isn't sure what they're really up to

## btvmesh
https://btvmesh.net/
- @hurricos' project; Not really off the ground yet
Loading