Search results
Jump to navigation
Jump to search
- "We provide technical, organizational and, in the future, financial support to community groups s *** Our solution includes materials for reproducing the design (technical documentation, tutorials), and curricula for skills such as cable crimping, node mounting24 KB (3,922 words) - 11:59, 21 February 2018
- * Mai - recapping--had a meeting earlier in the year about high level technical, operational, organizational, and fund-raising sides of the organization. C * documentation with community outreach - mai, jnny, grant29 KB (4,950 words) - 21:55, 16 April 2018
- === Bugs/Technical === *** Would be good to have a more technical workshop and a more discussion-y workshop23 KB (3,743 words) - 22:09, 2 April 2018
- ...be participate in cooperative communications infrastructure, regardless of technical skill. * [[Mesh/Documentation|Other documentation]] - books, articles, wikis, blog posts.11 KB (1,687 words) - 21:16, 19 January 2024
- ==Technical== ==Documentation==3 KB (494 words) - 04:21, 7 February 2014
- ''Note: You can also read the [[home node|non-technical explanation of home nodes and extender nodes]].'' ...ze 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:11 KB (1,877 words) - 21:30, 16 June 2018
- 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 ...ms! Please help! You can base outreach-focused diagrams on elements of the technical reference diagrams below:8 KB (1,205 words) - 23:33, 1 July 2018
- === Bugs/Technical === ** jenny: Do you mean the walkthrough page? or technical overview?12 KB (1,992 words) - 15:33, 10 February 2019
- * link to a helpful documentation page =Documentation page (REDO)=5 KB (899 words) - 16:06, 30 October 2017
- == Documentation == (c) (1) (ii) of the Rights in Technical Data and Computer7 KB (904 words) - 21:11, 5 January 2014
- === Bugs/Technical === ** jorrit -that was the technical part, this is the organizational part20 KB (3,433 words) - 20:36, 14 February 2018
- === Bugs/Technical === ...building. To accomplish what we're trying to do, we'll need to hack on our documentation between now and then23 KB (3,766 words) - 17:43, 18 March 2018
- =Documentation= *We need good documentation for Deekoo's build server proxy3 KB (539 words) - 00:57, 4 April 2014
- ...are, Babel, new IP range), April (organizingz), Chris (doin stuff), Jenny (documentation, outreach, etc), Benny (saw about it on the website and liked the friendly =Technical Updates=6 KB (875 words) - 23:32, 26 February 2015
- =Technical= ** They're interested and are hiring someone more technical who will liason with us1 KB (149 words) - 16:17, 2 October 2014
- See Also: [[Mesh#Technical_Documentation | Technical Documentation]], [[Mesh/Monitoring | Monitoring]] [[Category:Technical]]3 KB (457 words) - 01:23, 20 February 2015
- ...d in helping myself getting more familiar with the mesh network by writing documentation. ..., social engineers, teachers - we need everyone! don't reduce them to "non-technical people"11 KB (1,998 words) - 08:33, 29 March 2017
- ...byoi is Jan 27, bought the domain buildyourowninter.net, good place to put documentation and guides and what not. **** mai: both in technical terms and plain terms8 KB (1,377 words) - 22:51, 6 February 2018
- === Bugs/Technical === * marc - not formally logged, but seems like there's no documentation on the 24 hour password reset bug with autoconf.17 KB (2,835 words) - 11:11, 11 July 2018
- * Eve: reread the documentation through or someone putting up a node * Dan - found about this through Tyler and HAM stuff - technical electronics, some hackings. Part of 2600 HOPE Network. Strong TV background4 KB (593 words) - 19:40, 24 September 2019