892
edits
Difference between revisions of "Mesh"
Jump to navigation
Jump to search
no edit summary
| Line 1: | Line 1: | ||
You can usually read about our progress on our [[Mesh/Blog|Blog]] or by perusing our [[Mesh/Minutes|meeting minutes]] but we've been in '''deep development mode''' for a while and are just now emerging. The 0.2 firmware release is very imminent and we will resume our regularly schedules meetings and blog updates post release ([[User:Juul|Juul]] July 2nd 2015) | |||
<br> | <br> | ||
'''We are an all-volunteer organization building the People's Open Network, a community-owned and operated non-profit internet infrastructure in Oakland.''' | '''We are an all-volunteer organization building the People's Open Network, a community-owned and operated non-profit internet infrastructure in Oakland.''' | ||
People's Open Network is a [http://en.wikipedia.org/wiki/Mesh_networking mesh network] based out of Oakland, California. | |||
Imagine if the wifi router in your home connected to the wifi routers in your neighbour’s homes and they again connected to their neighbours to form a huge free wireless network spanning the city! That's exactly what a mesh network is, or at least what it can be. Roads and telephone poles are owned 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. | |||
sudo mesh is a non-profit organization consisting of a group of unpaid volunteers who are building People's Open Network. 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. | |||
We are spending a lot of time developing [https://github.com/sudomesh/ software] to make it cheap and easy for anyone to be part of People's Open Network, regardless of technical skill. | |||
| Line 17: | Line 20: | ||
* 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]. | ||
* Learn more at our general meetings, which are the last Tuesdays of every month at [[Getting_there|sudo room]]. 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! | * Learn more at our general meetings, which are the last Tuesdays of every month at [[Getting_there|sudo room]]. 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! | ||
* We have '''weekly meetings'' on Tuesdays and '''weekly hacknights''' on Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]], but do not | * We have '''weekly meetings'' on Tuesdays and '''weekly hacknights''' on Thursdays, 7:30-11:00pm at [[Getting_there|sudo room]], but at these events we do not spend time introducing new people to the project. If you do not feel ready to jump right in and start contributing, please show up for our general meetings (mentioned above) where we specifically take time to intro new volunteers and answer questions :D | ||
* 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 37: | Line 40: | ||
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. | 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] | 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]. | ||
* [https://github.com/sudomesh/ | Here are some of the projects that need attention: | ||
* [https:// | |||
* [[Mesh/Firmware|Firmware]] - The sudowrt firmware | |||
* [https://github.com/sudomesh/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 == | == Designers == | ||