Search results
Jump to navigation
Jump to search
- * 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
- ...lination with other Organizations that work in the building''' : Technical Documentation for 3D Printing | [[Community Democracy Project]] | [[http://thepublicschoo ...conceptual level suitable for the curious layperson and go deeper into the technical details according to your interests.27 KB (4,201 words) - 21:42, 30 August 2022
- See Also: [[Mesh#Technical_Documentation | Technical Documentation]], [[Mesh/Bandwidth Quotas | Bandwidth Quotas]] [[Category:Technical]]10 KB (1,208 words) - 13:36, 30 December 2015
- *** eenblam - +1. I think Github is critical for software contributions (and documentation for said software), but I don't want people to be shut out unnecessarily fo ...would happen on loomio so we could keep track of people's points and have documentation re: why we decided to move forward with whatever process we decided to give15 KB (2,486 words) - 12:43, 12 September 2018
- === Bugs/Technical === ** Documentation: Node mounting guide, community outreach guide,14 KB (2,295 words) - 11:55, 21 February 2018
- ** robb - we have a pile of older Android tablets with documentation on them ...2 of us can go. Having two pairs of eyes / brains is good, especially for documentation.13 KB (2,178 words) - 12:17, 23 January 2019
- = Technical Specifications = = Documentation =4 KB (530 words) - 00:15, 12 November 2017
- Have been documenting more recently. wiki.ninux.org/Guide (their documentation) is divided into levels based on knowledge of user. ...he whole package - documentation from organization to tutorials, social to technical5 KB (761 words) - 22:31, 7 April 2015
- * juul recruited 2 new people for Disaster Radio, to help with design / documentation * rad: how to convince people who are non-technical to join?4 KB (692 words) - 15:26, 30 October 2017
- This script is in the process of being deprecated, below is ongoing documentation this deprecation. For more technical details on the internals of the home node, see the [[Mesh/Technical_Overvie11 KB (1,754 words) - 23:04, 13 November 2019
- === Bugs/Technical === ...land mesh to vidchat with us telling us what they found most useful in our documentation/resources?11 KB (1,804 words) - 16:27, 31 May 2018
- =Documentation= =Technical=3 KB (542 words) - 01:02, 4 April 2014
- === Bugs/Technical === ...ject end date? Requiring at the least a follow-up report linking to public documentation of work done.11 KB (1,794 words) - 12:42, 18 October 2018
- ...f the City and mobile access to real-time data was not seen as a necessary technical requirement by most groups, however both were particular priorities of City ''Community events/gathering organizing; skill-sharing; documentation''18 KB (2,642 words) - 15:41, 3 May 2018
- === Bugs/Technical === ** eenblam will be here this sunday -- interested in doing work on documentation + educational materials following up discussions at last BYOI9 KB (1,483 words) - 14:57, 2 June 2019
- Writing (documentation + press releases): *https://tails.boum.org/contribute/how/documentation/9 KB (1,271 words) - 16:21, 24 August 2018
- *Presentation on Saturday was rad! We now have video documentation. *Could say we don't log NAT because the technical requirements are too high7 KB (1,077 words) - 15:52, 22 September 2013
- See Also: [[Mesh#Technical_Documentation | Technical Documentation]]2 KB (290 words) - 23:55, 13 March 2014
- * Jwentwistle added a bunch of documentation to [[Mesh/BATMAN-adv]] * Jwentwistle created [[Mesh/Technical Overview]]18 KB (2,765 words) - 17:51, 9 June 2018
- =Documentation= =Technical=2 KB (357 words) - 23:00, 27 May 2014