https://omnicommons.org/mediawiki/api.php?action=feedcontributions&feedformat=atom&user=Ashleyq007 2026-04-30T11:49:46Z User contributions MediaWiki 1.37.2 https://omnicommons.org/mediawiki/index.php?title=2014/05/03_Omni_Hackathon/Internal_communications_/_working_groups_/_process&diff=387 2014-05-03T22:37:49Z

<p>Ashleyq007: </p> <hr /> <div>5/3/14<br /> <br /> what tools are being used for communication in our current groups?<br /> <br /> Daniel (Sudo Room)<br /> going to meetings - more helpful than scanning emails<br /> calendar - finding out what’s going on<br /> word of mouth<br /> example from healthy food organization - <br /> creating charger space/data drop to entice high school kids to choose healthy meal options located within tech-savvy area as opposed to more popular crappy food in non-tech location<br /> <br /> Sarah (Live Space)<br /> email<br /> simple, basic forms of communication<br /> making communication styles available to as wide of an audience as possible <br /> so that everyone makes use of the tool, not only the ‘tech savvy’<br /> showing up and participating in meetings geared toward fostering communication<br /> regularly scheduled focus groups<br /> multiple ways for people to plug-in<br /> live space: emails; google group<br /> whatever main form of communication tools are decided upon, <br /> it’s very important to have training and education sessions so that everyone learns how <br /> How can I help with this? Something for tracking ‘to-do’s,’ <br /> point people toward a task that needs to be done across the groups<br /> <br /> Matt<br /> guiding principal: what’s the goal for this working group?<br /> make communication and infrastructure that is inclusive to many experiences<br /> multiple forms of receiving information<br /> patterns related to design (of hacker spaces in Germany)<br /> communications patterns - you are hackers<br /> need a wiki, IRC, email/message boards<br /> documentation, synchronous communication, &amp; asynchronous communication<br /> but this is suboptimal; take it one step further<br /> what will bring this all together in a way that will make its work more consistently <br /> and optimize, making the communications infrastructure both productive and empowering for everyone involved<br /> issue tracking<br /> <br /> email lists are not an expectation that all members of the group are reading it<br /> communicating important information needs to take place across every format so that all are included<br /> <br /> ultimately email isn’t the best way to communicate!<br /> <br /> different functions/ operations we’d like to take place<br /> <br /> wikis<br /> forums/decision making sessions<br /> tracking issues/work orders<br /> resourcing/resource sharing<br /> collectively writing documents<br /> etherpad/google docs/synchronous <br /> <br /> Outcomes - <br /> Tool List - research tools and form comparative option<br /> asana<br /> lumio - OWS; less contingent on old ways of thinking<br /> recently crowd funded<br /> consensus based<br /> tracks individual status/feeling regarding a specific topic<br /> slack.com<br /> conceptboard<br /> decentralized twitter-type system<br /> <br /> Charge the communications working group with the responsibilities of <br /> outlining the communications infrastructure and sharing the intention <br /> and use (understanding of the flow) and build a curriculum around its <br /> use to implement education on the use of this tool<br /> <br /> Ultimate outcome<br /> <br /> working group requirements:<br /> 1. accountability<br /> 2. one point person coordinating the wg providing vision and <br /> tangible goals toward making progress towards area of their work<br /> 3. responsible for maintaining a list of the actions corresponding to their progress<br /> 4. notes for all meetings<br /> 5. publicly announced meeting times</div>

Ashleyq007 https://omnicommons.org/mediawiki/index.php?title=2014/05/03_Omni_Hackathon/Internal_communications_/_working_groups_/_process&diff=386 2014-05-03T22:30:44Z

<p>Ashleyq007: Agreed upon basic requirements regarding the internal communications infrastructure for all Omni working groups.</p> <hr /> <div>Omni Hackathon Internal Communication<br /> <br /> what tools are being used for communication in our current groups?<br /> <br /> Daniel<br /> going to meetings - more helpful than scanning emails<br /> calendar - finding out what’s going on<br /> word of mouth<br /> example from healthy food organization - creating charger space/data drop to entice high school kids to choose healthy meal options located within tech-savvy area as opposed to more popular crappy food in non-tech location<br /> <br /> Sarah<br /> email<br /> simple, basic forms of communication<br /> making communication styles available to as wide of an audience as possible so that everyone makes use of the tool, not only the ‘tech savvy’<br /> showing up and participating in meetings geared toward fostering communication<br /> regularly scheduled focus groups<br /> multiple ways for people to plug-in<br /> live space: emails; google group<br /> whatever main form of communication tools are decided upon, it’s very important to have training and education sessions so that everyone learns how <br /> How can I help with this? Something for tracking ‘to-do’s,’ point people toward a task that needs to be done across the groups<br /> <br /> Matt<br /> guiding principal<br /> what’s the goal for this working group/<br /> make communication and infrastructure that is inclusive to different types of experience<br /> multiple forms of receiving information<br /> patterns related to design (of hackerspaces in Germany)<br /> communications patterns - you are hackers<br /> need a wiki, IRC, and email<br /> documentation, synchronous communication, &amp; asynchronous communication<br /> point being, don’t build things you don’t need to build<br /> baseline of saying documentation, synch comm &amp; synch comm; but this is suboptimal; take it one step further<br /> what will bring this all together in a way that will make its work more consistently and optimize 2<br /> making the communications infrastructure both productive and empowering for everyone involved<br /> issue tracking<br /> <br /> email lists are not an expectation that all members other group are reading it<br /> communicating important information needs to take place across every format so that all are included<br /> <br /> ultimately email isn’t the best way to communicate;<br /> <br /> different functions/ operations we’d like to take place<br /> <br /> wikis<br /> forums.decision makers<br /> tracking issues/work orders<br /> resourcing/resource sharing<br /> collectively writing documents<br /> etherpad/google docs/synchronous <br /> <br /> Outcomes - <br /> Tool List - research tools and form comparative option<br /> asana<br /> loomio (lumio) - OWS; less contingent on old ways of thinking<br /> recently crowd funded<br /> consensus based<br /> tracks individual status/feeling regarding a specific topic<br /> slack.com<br /> conceptboard<br /> decentralized twitter-type system<br /> <br /> Charge the communications working group with the responsibilities of outlining the communications infrastructure and sharing the intention and use (understanding of the flow) and build a curriculum around its use to implement education on the use of this tool<br /> <br /> Ultimate outcome<br /> <br /> working group requirements:<br /> <br /> 1. accountability<br /> 2. one point person coordinating the wg providing vision and tangible goals toward making progress towards area of their work<br /> 3. responsible for maintaining a list of the actions corresponding to their progress<br /> 4. notes for all meetings<br /> 5. publicly announced meeting times</div>

Ashleyq007