Difference between revisions of "Mesh"

From Sudo Room
Jump to navigation Jump to search
(fine-tuned mission, less 'free' more sharing and building alternatives)
(added 'logistics' section and some tidying)
Line 19: Line 19:
* Follow us on [https://twitter.com/sudomesh twitter] and like us on [https://www.facebook.com/sudomesh facebook].
* Follow us on [https://twitter.com/sudomesh twitter] and like us on [https://www.facebook.com/sudomesh facebook].
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* We have '''weekly hack nights''' on Tuesdays and Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]]. The first three Thursdays of the month are work nights -- help us change the internet!
* Learn more at our general meetings, which are the last Thursdays of every month. We have focus groups and we collaborate on different parts of the or join the mailing list for details.
* Learn more at our general meetings, which are the last Thursdays of every month. We have focus groups and we collaborate on different parts of the project - from design to software development, documentation to community outreach and of course, community outreach and climbing rooftops to mount nodes!
* Chat with us on [http://www.irchelp.org/irchelp/irctutorial.html IRC]: [http://webchat.freenode.net/?channels=peoplesopen.net #peoplesopen.net]
* Chat with us on [http://www.irchelp.org/irchelp/irctutorial.html IRC]: [http://webchat.freenode.net/?channels=peoplesopen.net #peoplesopen.net]
* We generally collaborate on [https://pad.riseup.net/p/sudomesh meeting notes] at each meeting. Look at our archive of past [[Mesh/Minutes|meeting minutes]]!
* We generally collaborate on [https://pad.riseup.net/p/sudomesh meeting notes] at each meeting. Look at our archive of past [[Mesh/Minutes|meeting minutes]]!
Line 27: Line 27:
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 user introduction to help you get involved!
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 user introduction to help you get involved!


*Check out our [[Mesh/ToDos]|action items]]
*Check out our [[Mesh/ToDos|action items]]
*Support us with a small weekly donation on [https://www.gittip.com/sudomesh/ gittip], here's [[Mesh/Purchases|how we spend it]].
*Support us with a small weekly donation on [https://www.gittip.com/sudomesh/ gittip], here's [[Mesh/Purchases|how we spend it]].
*Send bitcoins to our wallet address: {{bitcoin wallet}}
*Send bitcoins to our wallet address: {{bitcoin wallet}}
*Check out our [[Mesh/Wishlist]|wishlist]], we have requests!  
*Check out our [[Mesh/Wishlist|wishlist]], we have requests!  
*Come to our meetings in Oakland! (listed above)
*Come to our meetings in Oakland! (listed above)
*Improve our documentation
*Improve our documentation
Line 43: Line 43:
== Be a Designer ==  
== Be a Designer ==  


We need artists and designers to make things look nice! We have [[Mesh/Design|design scheme]] we already use, but we're always looking to improve it. We need to improve our presentation content and [[Mesh/Diagrams|diagrams]] too!
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!


= Frequently Asked Questions (FAQs)=
= Frequently Asked Questions (FAQs)=
 
*[[Mesh/Challenges]] - What sort of challenges and problems do we face?
*[[Mesh/Decisions]] - What decisions have we made, and why?
*[[Mesh/Funding]] - How the heck do we fund this thing?
*[[Mesh/Legal]] - How do we use exit nodes, relays and legal structures to protect node owners and ourselves?
*[[Mesh/Legal]] - How do we use exit nodes, relays and legal structures to protect node owners and ourselves?
*[[Mesh/Hosting]] - How are we hosting and what does it cost?
*[[Mesh/Hosting]] - How are we hosting and what does it cost?
*[[Mesh/Backup]] - How do we handle backups?
*[[Mesh/Backup]] - How do we handle backups?
*[[Mesh/Server security]] - How do we ensure server security?
*[[Mesh/Server security]] - How do we ensure server security?
*[[Mesh/Naming]] - What do we call ourselves?
 
=Logistics=
*[[Mesh/Checkouts]] - Who took what gear home.
*[[Mesh/Donations]] - What's been donated to the group.
*[[Mesh/Inventory]] - Continually-updated inventory of our hardware and gear.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Marketing]] - Inspiration and links to marketing materials in progress.
*[[Mesh/Naming]] - What do we call ourselves? A lineage of bikeshedding.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.
*[[Mesh/Purchases]] - Details on our purchases, made by either individuals or through our crowdfunded money.
*[[Mesh/Inventory]] - What we currently have.
*[[Mesh/Donations]] - List of donations
*[[Mesh/Decisions]] - Decisions on how to operate
*[[Mesh/Challenges]] - Challenges faced. Problems to be solved.
*[[Mesh/Checkouts]] - Who took what gear home
*[[Mesh/Funding]] - Ideas on funding structures and list of grants to apply for.


= Research =
= Research =
Line 66: Line 67:
*[[Mesh/Documentation]] - Books, articles, wikis, blog posts.
*[[Mesh/Documentation]] - Books, articles, wikis, blog posts.
*[[Mesh/Oakland]] - Information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
*[[Mesh/Oakland]] - Information and resources pertaining to Oakland community organizations, wireless initiatives, policy and research initiatives
*[[Mesh/Other muni networking projects]] - Examples of progressive uses of muni-networks
*[[Mesh/Other muni networking projects]] - Examples of progressive uses of municipal networks.


= Other Firmware and Networks =
= Other Firmware and Networks =


*[[Mesh/Freifunk]] - network based out of Germany.  
*[[Mesh/Freifunk]] - Germany - Home of the creators of batman-adv (the routing protocol we use) and one of the longest-running mesh networks in the world.
*[[Mesh/Commotion]] - network based out of
*[[Mesh/Commotion]] - A very well-documented project from the Open Technology Institute creating a simple-to-deploy mesh firmware and setup for small community meshes around the world.


=Web Resources=
=Web Resources=

Revision as of 03:28, 18 July 2014

Feb 21: Launched "Snow Crash" release candidate v.0.1.0 - now deploying the first batch of experimental nodes!  

We are an all-volunteer organization building the People's Open Network, a community-owned and operated non-profit internet infrastructure in Oakland.

A mesh network is a way of freely sharing internet connectivity with ones neighbors and creating a community-owned 'internet' that doesn't necessarily have to be connected to the Internet as we know it now. It consists of routers running software that allow them to communicate with other routers around them. The users who join the network enable others to be on the network and support net neutrality. Community wireless mesh networks are growing around the world as alternatives to the existing system, creating local 'internets' rather than being dependent on the infrastructure developed by large Internet Service Providers and companies that mine and sell your personal information.

The software we've created is open source and we're using it to develop free internet for Oakland and the surrounding areas. Our mission in building the network is to connect our neighbors, support local businesses, and enable community collaboration and cultural production. In the event of disaster or censorship, a mesh network can be a resilient means of communication and sharing of information.

Dishes in Action
Quick Links (see below for more details)
Documentation Technical Outreach Operations Research External Links
Install Instructions Overview FAQ Minutes User Research peoplesopen.net
Net Topology Hardware Blog To-Do's SF Bay Area network map
Presentations Power How to Help Legal Interviews code on github
History Security Wishlist Inventory Other Meshes DisasterRadio
Press Backup Website Meetings Software Tools BuildYourOwnInter.Net
Firmware Hosting Propaganda Funding Local Services
Mounting Decisions Self-Education
Next gen

 

Join Us

  • Join the email list!
  • Follow us on twitter and like us on facebook.
  • We have weekly hack nights on Tuesdays and Thursdays, 7:30-11:00pm at sudo room. The first three Thursdays of the month are work nights -- help us change the internet!
  • Learn more at our general meetings, which are the last Thursdays of every month. We have focus groups and we collaborate on different parts of the project - from design to software development, documentation to community outreach and of course, community outreach and climbing rooftops to mount nodes!
  • Chat with us on IRC: #peoplesopen.net
  • We generally collaborate on meeting notes at each meeting. Look at our archive of past meeting minutes!

How to Help

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 user introduction to help you get involved!

  • Check out our action items
  • Support us with a small weekly donation on gittip, here's how we spend it.
  • Send bitcoins to our wallet address: 12RxU4DpLpdWcmEBn7Tj325CCXBwt5i9Hc
  • Check out our wishlist, we have requests!
  • Come to our meetings in Oakland! (listed above)
  • Improve our documentation
  • Talk to your community about joining the mesh

Be a Developer

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

If you want to immediately help, check out our code!

Be a Designer

We need artists and designers to make things look nice! We have design schemes we already use, but we're always looking to improve it. We need to improve our presentation content and diagrams too!

Frequently Asked Questions (FAQs)

Logistics

  • Mesh/Checkouts - Who took what gear home.
  • Mesh/Donations - What's been donated to the group.
  • Mesh/Inventory - Continually-updated inventory of our hardware and gear.
  • Mesh/Marketing - Inspiration and links to marketing materials in progress.
  • Mesh/Naming - What do we call ourselves? A lineage of bikeshedding.
  • Mesh/Purchases - Details on our purchases, made by either individuals or through our crowdfunded money.

Research

Other Firmware and Networks

  • Mesh/Freifunk - Germany - Home of the creators of batman-adv (the routing protocol we use) and one of the longest-running mesh networks in the world.
  • Mesh/Commotion - A very well-documented project from the Open Technology Institute creating a simple-to-deploy mesh firmware and setup for small community meshes around the world.

Web Resources