├── .gitignore ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── collaborating-better.md ├── comms.md ├── faq.md ├── github-for-documentation.md ├── images └── money-diagram.jpg ├── money.md ├── project-kitchen.md ├── roomio.md └── welcoming-new-contributors.md /.gitignore: -------------------------------------------------------------------------------- 1 | *.DS_Store 2 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # This is an [OPEN Open Source Project](http://openopensource.org/) 2 | 3 | ----------------------------------------- 4 | 5 | ## What? 6 | 7 | Individuals making significant and valuable contributions are given 8 | commit-access to the project to contribute as they see fit. This project 9 | is more like an open wiki than a standard guarded open source project. 10 | 11 | ## Rules 12 | 13 | There are a few basic ground-rules for contributors: 14 | 15 | 1. **No `--force` pushes** or modifying the Git history in any way. 16 | 1. **Non-master branches** ought to be used for ongoing work. 17 | 1. **External API changes and significant modifications** ought to be subject to an **internal pull-request** to solicit feedback from other contributors. 18 | 1. Internal pull-requests to solicit feedback are *encouraged* for any other non-trivial contribution but left to the discretion of the contributor. 19 | 1. Contributors should attempt to adhere to the prevailing code-style. 20 | 21 | ## Releases 22 | 23 | Declaring formal releases remains the prerogative of the project maintainer. 24 | 25 | ## Changes to this arrangement 26 | 27 | This is an experiment and feedback is welcome! This document may also be 28 | subject to pull-requests or changes by contributors where you believe 29 | you have something valuable to add or change. 30 | 31 | Get a copy of this manifesto as [markdown](https://raw.githubusercontent.com/openopensource/openopensource.github.io/master/Readme.md) and use it in your own projects. 32 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 2, June 1991 3 | 4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc., 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | Preamble 10 | 11 | The licenses for most software are designed to take away your 12 | freedom to share and change it. By contrast, the GNU General Public 13 | License is intended to guarantee your freedom to share and change free 14 | software--to make sure the software is free for all its users. This 15 | General Public License applies to most of the Free Software 16 | Foundation's software and to any other program whose authors commit to 17 | using it. (Some other Free Software Foundation software is covered by 18 | the GNU Lesser General Public License instead.) You can apply it to 19 | your programs, too. 20 | 21 | When we speak of free software, we are referring to freedom, not 22 | price. Our General Public Licenses are designed to make sure that you 23 | have the freedom to distribute copies of free software (and charge for 24 | this service if you wish), that you receive source code or can get it 25 | if you want it, that you can change the software or use pieces of it 26 | in new free programs; and that you know you can do these things. 27 | 28 | To protect your rights, we need to make restrictions that forbid 29 | anyone to deny you these rights or to ask you to surrender the rights. 30 | These restrictions translate to certain responsibilities for you if you 31 | distribute copies of the software, or if you modify it. 32 | 33 | For example, if you distribute copies of such a program, whether 34 | gratis or for a fee, you must give the recipients all the rights that 35 | you have. You must make sure that they, too, receive or can get the 36 | source code. And you must show them these terms so they know their 37 | rights. 38 | 39 | We protect your rights with two steps: (1) copyright the software, and 40 | (2) offer you this license which gives you legal permission to copy, 41 | distribute and/or modify the software. 42 | 43 | Also, for each author's protection and ours, we want to make certain 44 | that everyone understands that there is no warranty for this free 45 | software. If the software is modified by someone else and passed on, we 46 | want its recipients to know that what they have is not the original, so 47 | that any problems introduced by others will not reflect on the original 48 | authors' reputations. 49 | 50 | Finally, any free program is threatened constantly by software 51 | patents. We wish to avoid the danger that redistributors of a free 52 | program will individually obtain patent licenses, in effect making the 53 | program proprietary. To prevent this, we have made it clear that any 54 | patent must be licensed for everyone's free use or not licensed at all. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | GNU GENERAL PUBLIC LICENSE 60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 61 | 62 | 0. This License applies to any program or other work which contains 63 | a notice placed by the copyright holder saying it may be distributed 64 | under the terms of this General Public License. The "Program", below, 65 | refers to any such program or work, and a "work based on the Program" 66 | means either the Program or any derivative work under copyright law: 67 | that is to say, a work containing the Program or a portion of it, 68 | either verbatim or with modifications and/or translated into another 69 | language. (Hereinafter, translation is included without limitation in 70 | the term "modification".) Each licensee is addressed as "you". 71 | 72 | Activities other than copying, distribution and modification are not 73 | covered by this License; they are outside its scope. The act of 74 | running the Program is not restricted, and the output from the Program 75 | is covered only if its contents constitute a work based on the 76 | Program (independent of having been made by running the Program). 77 | Whether that is true depends on what the Program does. 78 | 79 | 1. You may copy and distribute verbatim copies of the Program's 80 | source code as you receive it, in any medium, provided that you 81 | conspicuously and appropriately publish on each copy an appropriate 82 | copyright notice and disclaimer of warranty; keep intact all the 83 | notices that refer to this License and to the absence of any warranty; 84 | and give any other recipients of the Program a copy of this License 85 | along with the Program. 86 | 87 | You may charge a fee for the physical act of transferring a copy, and 88 | you may at your option offer warranty protection in exchange for a fee. 89 | 90 | 2. You may modify your copy or copies of the Program or any portion 91 | of it, thus forming a work based on the Program, and copy and 92 | distribute such modifications or work under the terms of Section 1 93 | above, provided that you also meet all of these conditions: 94 | 95 | a) You must cause the modified files to carry prominent notices 96 | stating that you changed the files and the date of any change. 97 | 98 | b) You must cause any work that you distribute or publish, that in 99 | whole or in part contains or is derived from the Program or any 100 | part thereof, to be licensed as a whole at no charge to all third 101 | parties under the terms of this License. 102 | 103 | c) If the modified program normally reads commands interactively 104 | when run, you must cause it, when started running for such 105 | interactive use in the most ordinary way, to print or display an 106 | announcement including an appropriate copyright notice and a 107 | notice that there is no warranty (or else, saying that you provide 108 | a warranty) and that users may redistribute the program under 109 | these conditions, and telling the user how to view a copy of this 110 | License. (Exception: if the Program itself is interactive but 111 | does not normally print such an announcement, your work based on 112 | the Program is not required to print an announcement.) 113 | 114 | These requirements apply to the modified work as a whole. If 115 | identifiable sections of that work are not derived from the Program, 116 | and can be reasonably considered independent and separate works in 117 | themselves, then this License, and its terms, do not apply to those 118 | sections when you distribute them as separate works. But when you 119 | distribute the same sections as part of a whole which is a work based 120 | on the Program, the distribution of the whole must be on the terms of 121 | this License, whose permissions for other licensees extend to the 122 | entire whole, and thus to each and every part regardless of who wrote it. 123 | 124 | Thus, it is not the intent of this section to claim rights or contest 125 | your rights to work written entirely by you; rather, the intent is to 126 | exercise the right to control the distribution of derivative or 127 | collective works based on the Program. 128 | 129 | In addition, mere aggregation of another work not based on the Program 130 | with the Program (or with a work based on the Program) on a volume of 131 | a storage or distribution medium does not bring the other work under 132 | the scope of this License. 133 | 134 | 3. You may copy and distribute the Program (or a work based on it, 135 | under Section 2) in object code or executable form under the terms of 136 | Sections 1 and 2 above provided that you also do one of the following: 137 | 138 | a) Accompany it with the complete corresponding machine-readable 139 | source code, which must be distributed under the terms of Sections 140 | 1 and 2 above on a medium customarily used for software interchange; or, 141 | 142 | b) Accompany it with a written offer, valid for at least three 143 | years, to give any third party, for a charge no more than your 144 | cost of physically performing source distribution, a complete 145 | machine-readable copy of the corresponding source code, to be 146 | distributed under the terms of Sections 1 and 2 above on a medium 147 | customarily used for software interchange; or, 148 | 149 | c) Accompany it with the information you received as to the offer 150 | to distribute corresponding source code. (This alternative is 151 | allowed only for noncommercial distribution and only if you 152 | received the program in object code or executable form with such 153 | an offer, in accord with Subsection b above.) 154 | 155 | The source code for a work means the preferred form of the work for 156 | making modifications to it. For an executable work, complete source 157 | code means all the source code for all modules it contains, plus any 158 | associated interface definition files, plus the scripts used to 159 | control compilation and installation of the executable. However, as a 160 | special exception, the source code distributed need not include 161 | anything that is normally distributed (in either source or binary 162 | form) with the major components (compiler, kernel, and so on) of the 163 | operating system on which the executable runs, unless that component 164 | itself accompanies the executable. 165 | 166 | If distribution of executable or object code is made by offering 167 | access to copy from a designated place, then offering equivalent 168 | access to copy the source code from the same place counts as 169 | distribution of the source code, even though third parties are not 170 | compelled to copy the source along with the object code. 171 | 172 | 4. You may not copy, modify, sublicense, or distribute the Program 173 | except as expressly provided under this License. Any attempt 174 | otherwise to copy, modify, sublicense or distribute the Program is 175 | void, and will automatically terminate your rights under this License. 176 | However, parties who have received copies, or rights, from you under 177 | this License will not have their licenses terminated so long as such 178 | parties remain in full compliance. 179 | 180 | 5. You are not required to accept this License, since you have not 181 | signed it. However, nothing else grants you permission to modify or 182 | distribute the Program or its derivative works. These actions are 183 | prohibited by law if you do not accept this License. Therefore, by 184 | modifying or distributing the Program (or any work based on the 185 | Program), you indicate your acceptance of this License to do so, and 186 | all its terms and conditions for copying, distributing or modifying 187 | the Program or works based on it. 188 | 189 | 6. Each time you redistribute the Program (or any work based on the 190 | Program), the recipient automatically receives a license from the 191 | original licensor to copy, distribute or modify the Program subject to 192 | these terms and conditions. You may not impose any further 193 | restrictions on the recipients' exercise of the rights granted herein. 194 | You are not responsible for enforcing compliance by third parties to 195 | this License. 196 | 197 | 7. If, as a consequence of a court judgment or allegation of patent 198 | infringement or for any other reason (not limited to patent issues), 199 | conditions are imposed on you (whether by court order, agreement or 200 | otherwise) that contradict the conditions of this License, they do not 201 | excuse you from the conditions of this License. If you cannot 202 | distribute so as to satisfy simultaneously your obligations under this 203 | License and any other pertinent obligations, then as a consequence you 204 | may not distribute the Program at all. For example, if a patent 205 | license would not permit royalty-free redistribution of the Program by 206 | all those who receive copies directly or indirectly through you, then 207 | the only way you could satisfy both it and this License would be to 208 | refrain entirely from distribution of the Program. 209 | 210 | If any portion of this section is held invalid or unenforceable under 211 | any particular circumstance, the balance of the section is intended to 212 | apply and the section as a whole is intended to apply in other 213 | circumstances. 214 | 215 | It is not the purpose of this section to induce you to infringe any 216 | patents or other property right claims or to contest validity of any 217 | such claims; this section has the sole purpose of protecting the 218 | integrity of the free software distribution system, which is 219 | implemented by public license practices. Many people have made 220 | generous contributions to the wide range of software distributed 221 | through that system in reliance on consistent application of that 222 | system; it is up to the author/donor to decide if he or she is willing 223 | to distribute software through any other system and a licensee cannot 224 | impose that choice. 225 | 226 | This section is intended to make thoroughly clear what is believed to 227 | be a consequence of the rest of this License. 228 | 229 | 8. If the distribution and/or use of the Program is restricted in 230 | certain countries either by patents or by copyrighted interfaces, the 231 | original copyright holder who places the Program under this License 232 | may add an explicit geographical distribution limitation excluding 233 | those countries, so that distribution is permitted only in or among 234 | countries not thus excluded. In such case, this License incorporates 235 | the limitation as if written in the body of this License. 236 | 237 | 9. The Free Software Foundation may publish revised and/or new versions 238 | of the General Public License from time to time. Such new versions will 239 | be similar in spirit to the present version, but may differ in detail to 240 | address new problems or concerns. 241 | 242 | Each version is given a distinguishing version number. If the Program 243 | specifies a version number of this License which applies to it and "any 244 | later version", you have the option of following the terms and conditions 245 | either of that version or of any later version published by the Free 246 | Software Foundation. If the Program does not specify a version number of 247 | this License, you may choose any version ever published by the Free Software 248 | Foundation. 249 | 250 | 10. If you wish to incorporate parts of the Program into other free 251 | programs whose distribution conditions are different, write to the author 252 | to ask for permission. For software which is copyrighted by the Free 253 | Software Foundation, write to the Free Software Foundation; we sometimes 254 | make exceptions for this. Our decision will be guided by the two goals 255 | of preserving the free status of all derivatives of our free software and 256 | of promoting the sharing and reuse of software generally. 257 | 258 | NO WARRANTY 259 | 260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY 261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN 262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES 263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED 264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS 266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE 267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, 268 | REPAIR OR CORRECTION. 269 | 270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR 272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, 273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING 274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED 275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY 276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER 277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE 278 | POSSIBILITY OF SUCH DAMAGES. 279 | 280 | END OF TERMS AND CONDITIONS 281 | 282 | How to Apply These Terms to Your New Programs 283 | 284 | If you develop a new program, and you want it to be of the greatest 285 | possible use to the public, the best way to achieve this is to make it 286 | free software which everyone can redistribute and change under these terms. 287 | 288 | To do so, attach the following notices to the program. It is safest 289 | to attach them to the start of each source file to most effectively 290 | convey the exclusion of warranty; and each file should have at least 291 | the "copyright" line and a pointer to where the full notice is found. 292 | 293 | {description} 294 | Copyright (C) {year} {fullname} 295 | 296 | This program is free software; you can redistribute it and/or modify 297 | it under the terms of the GNU General Public License as published by 298 | the Free Software Foundation; either version 2 of the License, or 299 | (at your option) any later version. 300 | 301 | This program is distributed in the hope that it will be useful, 302 | but WITHOUT ANY WARRANTY; without even the implied warranty of 303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 304 | GNU General Public License for more details. 305 | 306 | You should have received a copy of the GNU General Public License along 307 | with this program; if not, write to the Free Software Foundation, Inc., 308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. 309 | 310 | Also add information on how to contact you by electronic and paper mail. 311 | 312 | If the program is interactive, make it output a short notice like this 313 | when it starts in an interactive mode: 314 | 315 | Gnomovision version 69, Copyright (C) year name of author 316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 317 | This is free software, and you are welcome to redistribute it 318 | under certain conditions; type `show c' for details. 319 | 320 | The hypothetical commands `show w' and `show c' should show the appropriate 321 | parts of the General Public License. Of course, the commands you use may 322 | be called something other than `show w' and `show c'; they could even be 323 | mouse-clicks or menu items--whatever suits your program. 324 | 325 | You should also get your employer (if you work as a programmer) or your 326 | school, if any, to sign a "copyright disclaimer" for the program, if 327 | necessary. Here is a sample; alter the names: 328 | 329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program 330 | `Gnomovision' (which makes passes at compilers) written by James Hacker. 331 | 332 | {signature of Ty Coon}, 1 April 1989 333 | Ty Coon, President of Vice 334 | 335 | This General Public License does not permit incorporating your program into 336 | proprietary programs. If your program is a subroutine library, you may 337 | consider it more useful to permit linking proprietary applications with the 338 | library. If this is what you want to do, use the GNU Lesser General 339 | Public License instead of this License. 340 | 341 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # guides 2 | 3 | This is an experimental new collection of "how Enspiral works" content. Stay tuned for updates. 4 | 5 | ## Foundational articles: 6 | 7 | * [How Money Works at Enspiral](https://github.com/enspiral/guides/blob/master/money.md) 8 | * [Collaborating Better](https://github.com/enspiral/guides/blob/master/collaborating-better.md) 9 | * [Communications Guidelines](https://github.com/enspiral/guides/blob/master/comms.md) 10 | * [Using GitHub for documentation at Enspiral](https://github.com/enspiral/guides/blob/master/github-for-documentation.md) 11 | * [Welcoming new Contributors](https://github.com/enspiral/guides/blob/master/welcoming-new-contributors.md) 12 | 13 | **About these articles** 14 | 15 | A "foundational article" is a landing page - an introduction to the concept, then a series of links to stories and recipes with more detailed information. 16 | 17 | A **_Recipe_** is a piece of instructional ‘how-to’ content that gives enough detail that people can follow the process. The form we’ll be testing includes the following fields : 18 | 19 | 1. Title 20 | 2. Purpose of practice 21 | 3. Where it’s practiced (e.g. what Enspiral teams / ventures?) 22 | 4. Credits (developer / lineage) 23 | 5. Methodology 24 | 25 | A **_Story_** is a narrative form which reveals the context and purpose from which the process or practice emerged. There are several different forms it could take e.g. **[I-Story](https://medium.com/enspiral-tales/a-new-cultural-tech-8a5a092035af)** and we can provide framing questions to get the juicy bits out e.g. 26 | 27 | * What was the problem you were grappling with? 28 | * What were your breakthroughs in relating to that challenge? 29 | * How did that change how you operate - what you did and how you did it? 30 | * What impact has this change in practice had? 31 | * What are the learning edges right now? 32 | 33 | ## Contributing 34 | 35 | `enspiral/guides` is an **OPEN Open Source Project**. This means that: 36 | 37 | > Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project. 38 | 39 | See the [contribution guide](./CONTRIBUTING.md) for more details and the [Using GitHub for documentation at Enspiral](https://github.com/enspiral/guides/blob/master/github-for-documentation.md) guide for simple and fun video instructions to learn to use GitHub for this purpose. 40 | -------------------------------------------------------------------------------- /collaborating-better.md: -------------------------------------------------------------------------------- 1 | # Collaborating Better at Enspiral 2 | 3 | A collection of practices we use at Enspiral to enable us to collaborate better together 4 | 5 | * **[Recipe : Roomio](https://github.com/enspiral/guides/blob/master/roomio.md)** - make great group decisions during in-person meetings 6 | * **[Recipe : Project Kitchen](https://github.com/enspiral/guides/blob/master/project-kitchen.md)** - improve projects and initiatives with group intelligence 7 | -------------------------------------------------------------------------------- /comms.md: -------------------------------------------------------------------------------- 1 | ## Enspiral Communications Guide 2 | 3 | In many ways, the sum total of all our communication is what defines the existence of Enspiral - it’s the connections between us all. There are a variety of different channels that are used in constantly evolving ways. 4 | 5 | This guide is here to give an overview of the channels we've officially decided to adopt, the policies we've set, and to give you some tips for how best to communicat with the network. 6 | 7 | These comms channels are hosted by the Enspiral Foundation and are open to all contributors (or wider). If you are a contributor but lack access to something, contact foundation@enspiral.com 8 | 9 | # Channels and Tools 10 | 11 | **[Loomio](https://www.loomio.org/g/1xCPyY46/enspiral) - Decisions** 12 | 13 | Our tool for decision making. The assumption is everyone will see everything. A proposal passed on Loomio becomes network policy. 14 | 15 | Posting on Loomio in the main Enspiral group sends a notification out to everyone (nearly 300 people around the world), and so should be used judiciously. Tends to get noisy if we over-use it. 16 | 17 | Two categories of content appropriate for Loomio: a topic that could lead to a decision that affects the whole network, or important information everyone really needs to discuss. 18 | 19 | Feel free to start subgroups on Loomio if you'd like a more targeted collaboration space with a subset of Enspiral people. 20 | 21 | **[Slack](http://enspiral.slack.com) - Daily Comms** 22 | 23 | Daily chatting, realtime comms, quick questions, intersting links. There is a #watercooler channel for general discussion, and many channels for teams, projects, locations, and topics, or you can create your own! 24 | 25 | **[Chalkle](http://www.chalkle.com/enspiral) - Events/Classes** 26 | 27 | Enspiral's Chalkle Channel is where events and classes are posted that everyone is welcome to attend. If you'd like to host one, feel free! They can be free or you can charge. Chalkle events are visible on the public internet, but only 'followers' of the channel (including all contributors) will get a direct invitation. [More info](https://docs.google.com/document/d/1Phe94mRRo5yMpxiNiZiiX-sRKpsDQcDTbh9J7sdjIBY/edit?usp=sharing). 28 | 29 | **[Cobudget](beta.cobudget.co/#/groups/41) - Collaborative Funding** 30 | 31 | Our tool for budgeting and financial decision making. Enspiral's discretionary budget is distributed using a democratic process. All contributors are welcome to raise buckets (funding requests) and comment on buckets. If your message is about spending collective money, it probably makes sense to post it here as a bucket or comment. 32 | 33 | **Enspiral News - Broadcast** 34 | 35 | Every two weeks, a newsletter goes out to all Enspiral contributors via Mailchimp. It has info from ventures, media coverage, updates on decisions and happenings, and inspirational animal gifs. 36 | 37 | To get something published in News, email news@enspiral.com or post in the #enspiral-news Slack channel. If you want to reach the whole network with non-urgent infomation, this is the way. 38 | 39 | **Google Apps** 40 | 41 | * Email - Everyone at Enspiral is entitled to an Enspiral email address if they need one to represent Enspiral to clients or the public. Email is great for one-on-one or small group correspondence, or one-way announcements. 42 | 43 | * Calendar - Great for your own planning and for private events and meetings where you have a specific guest list in mind. If you want to put out an open invitation, use [Chalkle](http://www.chalkle.com/enspiral] instead. 44 | 45 | * Drive - We use Drive (Docs, Sheets, Forms) extensively, but we're moving all 'official' documentation off it and onto GitHub. If a team you're working with uses Drive, you'll be invited to the relevant folders/docs. 46 | 47 | **Facebook & Twitter** 48 | 49 | Enspiral has a [facebook page](https://www.facebook.com/Enspiral) and Twitter (@enspiral) - to get something posted here, contact news@enspiral.com. If you have friends who want to keep up with Enspiral but aren’t in the network itself, tell them to like/follow. 50 | 51 | **[Blog - Enspiral Tales](http://blog.enspiral.com)** 52 | 53 | Enspiral has a publication on Medium called Enspiral Tales that many people are actively contributing to. Generally, we welcome content from anyone in the network. The Fairy Blogmother is currently Rich Bartlett - talk to him if you’re interested in blogging. 54 | 55 | 56 | ## Comms Tips and Guidelines 57 | 58 | We operate in an attention economy, and as a participatory network it's like we all have a debit card attached to the collective attention bank account. Getting the attention people at Enspiral is expensive! Here's some advice about making it count. 59 | 60 | **This is YOUR Space** 61 | 62 | We are all greatly enriched by all of our engagement. Your voice is welcome. Your perspective is valued. Your interests are interesting. The best thing you can do to give and receive value is *participate*. 63 | 64 | **Pick your Channel Wisely** 65 | 66 | Know the various channels available and consciously decide where to post. Within a given tool, post to the right group or channel. 67 | 68 | Basically: 69 | * General communication goes on Slack. You will reach whoever opts in to read when you happen to post. 70 | * Topics requiring a decision by the network go on Loomio 71 | * Events go on Chalkle 72 | * One-way announcements to contributors go in News 73 | * Public info goes on Facebook and Twitter 74 | 75 | Messages relevant only to a limited group of people should be emailed directly, or posted in a specific slack channel or Loomio subgroup. 76 | 77 | **Subject Lines are a Channel** 78 | 79 | Put all the relevant info you can very concisely in the subject line (or discussion title on Loomio). Messages on Loomio trigger an email hundreds of people, many of whom will look no further than the subject line. Who, what, where, why, when. 80 | 81 | **Key Details in the First Message** 82 | 83 | Put all the relevant details in the body of the message, Chalkle event description, calendar invite, etc. You often only have one shot to reach people. Most will never click through to look at followup comments. Make sure the key info is in the initial post. 84 | 85 | **Include Links, Make it Easy** 86 | 87 | If you want people to click through to other content, include links! People will not go searching for facebook events, google docs, etc, on their own. Put everything they need right in front of people. 88 | 89 | **Tag Specific People** 90 | 91 | If a post is relevant to specific people, tag them (on Slack or Loomio) to help them notice it's there. People will often respond directly to stuff they are tagged in, which can increase engagement. Don’t post a comment that is just tagging a name though - that means the person will get an email notification that simply says their name. You want them to get a message too. 92 | 93 | **Be Very Sparing with @Channel tags** 94 | 95 | In Slack, @channel or @everyone notifications will send notifications to everyone in that channel - please use this sparingly for very important or time sensitive information, especially in large channels. Don't use @channel in #watercooler unless it's something that literally affects everyone. 96 | 97 | **Get Permissions Right** 98 | 99 | If you’re linking to something on Google Drive (or any other site), make sure you check the sharing settings before you hit send! It’s very common to be given a link only to be told “you don’t have permission” when you try to view it. Most people won’t come back and try again, so get it right the first time. 100 | 101 | **Include *All* Context** 102 | 103 | Write everything message as if to someone who has never heard of it before, especially network-wide messages. Don’t assume people already know any context, since your audience has diverse levels of engagement. We want invitations to engagement to be as accessible as possible. Be aware of Enspiral jargon and assumptions. Assume everyone is hearing about everything for the first time, every time - because many people will be. Include links to relevant background info or previous discussions so people can catch themselves up. 104 | 105 | **Make it Count** 106 | 107 | Send out as few messages as possible, and use each one to the max. Consider how precious people’s time is. Our attention is a commons we share - if we start overusing it, we'll degrade it for everyone. Do a quick search to see if there’s already an existing thread on the topic before posting a new one. On Slack, use @ tagging, channels, and DMs strategically - e.g. check the channel list for appropriate groups before posting niche questions in #watercooler. 108 | 109 | **Ask for Help** 110 | 111 | Realize that any time you’re communicating to large groups of people, you are doing comms work. If you’re not sure, or not very experienced with comms work, just check in with someone who can help you think through your message and how you’re delivering it to make sure it’s maximally effective. 112 | 113 | **Keep it brief** 114 | ‘nough said! 115 | 116 | 117 | ## Slack Tips 118 | 119 | Channels are like chat rooms, and they’re preceded by a #hashtag. You can browse the list and join/leave as many as you fancy. If a topic is missing, create it and invite people in. Keep your titles short and descriptive so someone browsing the list knows exactly what’s up (#cool-shit, #enspiral-space, #accounting-help, #dev-chat, etc) 120 | 121 | If you mention a channel by # in another channel, it will create a link to that channel. This is useful when moderating and directing users to more appropriate channels (e.g. hey, I think this conversation is better suited for #enspiral-space!) 122 | 123 | Private channels are invite-only groups - useful for small projects, teams with commercially sensitive information, safe spaces, or planning surprise parties. Anyone can create one and invite others. 124 | 125 | Direct Messages (DMs) are one-on-one private messages - use these to ask a question of a single individual, or continue an exciting conversation out of a public channel to avoid dominating it. 126 | 127 | Emoji are the best part of Slack! You can react to posts (just like a Facebook or Twitter like, only better because you can have pandas, poop, lazar kiwi, or Rich’s face instead of thumbs and stars!) or express your feelings. 128 | 129 | Slack has a ton of useful shortcuts - from markdown for formatting text to adding ¯\_(ツ)_/¯ to your messages. Type / to see a list of them. 130 | 131 | Slackbot is your helpful robot friend. They’ll help you setup your account, and you can also use them as a reminder service. Send Slackbot a message in the format ‘remind me to [do a thing] at [a time]’ to set reminders. Slackbot is pretty smart, and understands both relative and absolute time (e.g. in two hours, tomorrow at 10 am, Monday at noon, or 28 February 2020 will all work). 132 | 133 | We have a free account, which means we can only view our last 10,000 messages (across all channels). If you need to save important conversations or decisions, make sure you take screenshots or otherwise document what happened! 134 | 135 | ## If you need help... 136 | 137 | Contact news@enspiral.com to reach Jess, our comms maven. 138 | 139 | Drop into the #enspiral_help channel on Slack 140 | -------------------------------------------------------------------------------- /faq.md: -------------------------------------------------------------------------------- 1 | # Enspiral FAQ 2 | ### A place where questions about Enspiral get deposited for public view 3 | --- 4 | **How do I contribute to this FAQ?** 5 | 6 | You can contribute questions and answers to this FAQ by either postiing an Issue in this repo or making a Pull Request on this file. For instructions see our **[Guide to using GitHub for Documentation](https://github.com/enspiral/guides/blob/master/github-for-documentation.md)** 7 | -------------------------------------------------------------------------------- /github-for-documentation.md: -------------------------------------------------------------------------------- 1 | # Using GitHub for documentation at Enspiral (we've made it easy!) 2 | 3 | **To live our values of open collaboration and our intention to Open Source as much of our organisational model and systems, Enspiral has decided to use GitHub as the primary place to host our org documentation.** 4 | 5 | A core goal with this decision is to make it easy and accessible for many people to contribute to documentation at Enspiral. Most people see GitHub as a place for coders and techies so we've made this guide and videos to demystify the platform - a help guide for using GitHub for documentation rather than code. 6 | 7 | ## Contents 8 | 9 | 1. What is GitHub and why use it for documentation? 10 | 2. GitHub terminology 11 | 3. Signing up and visiting the Repo 12 | 4. Contributing to documentation by making a Pull Request 13 | 5. Discussing the Repo by posting Issues 14 | 6. Master Markdown 15 | 7. Practice now! 16 | 17 | ---- 18 | ## What is GitHub and why use it for documentation? 19 | 20 | [![What and Why GitHub](http://i.imgur.com/xXdWtWD.png?1)](https://vimeo.com/148974050) 21 | 22 | Click to view video 23 | 24 | ---- 25 | ## GitHub terminology 26 | 27 | * **Repository (Repo)** - Essentially a projects folder. A repository contains all of the project files (including documentation), and stores each file's revision history. 28 | 29 | * **Master** - the master copy version of a repository. This is the official 'source or truth'. 30 | 31 | * **Fork** - when you are a contributor to a repo and click to edit the file it will make a personal copy of the master for you that sits under your GitHub account. Forks allow you to freely make changes to a project without affecting the master. Forks remain attached to the master, allowing you to submit a pull request to the master's author to update with your changes. 32 | 33 | * **Pull Request** - proposed changes to a repository submitted by a user and accepted or rejected by a repository's collaborators. Like issues, pull requests each have their own discussion forum. 34 | 35 | * **Issue** - suggested improvements, tasks or questions related to a repository. Issues can be created by anyone for public repositories, and are moderated by repository collaborators. Each issue has its own discussion forum where people can comment to solve the problem the issue identifies. 36 | 37 | * **Collaborator** - a person with read and write access to a repository who has been invited to contribute by the repository owner. They can make edits to the Master branch without needing to submit a pull request and approve pull requests contributors have submitted. 38 | 39 | * **Contributor** - someone who has contributed to a project by having a pull request merged by a repo collaborator but does not have collaborator access. 40 | 41 | * **Organisations** - a group of two or more users that typically mirror real-world organizations. They are administered by users and can contain both repositories and teams. 42 | 43 | **For a full glossary of GitHub terminonology see https://help.github.com/articles/github-glossary/** 44 | 45 | 46 | 47 | ---- 48 | ## Signing up and visiting the Repo 49 | 50 | [![Visiting the Repo](http://i.imgur.com/dDXpLbs.png?1)](https://vimeo.com/148974051) 51 | 52 | Click to view video 53 | 54 | ---- 55 | ## Contributing to documentation by making a Pull Request 56 | 57 | [![Making a Pull Request](http://i.imgur.com/y7NI7mk.png?1)](https://vimeo.com/148985367) 58 | 59 | Click to view video 60 | 61 | ---- 62 | ## Discussing the Repo by posting Issues 63 | 64 | [![Posting Issues](http://i.imgur.com/YsaWxbO.png?1)](https://vimeo.com/148974049) 65 | 66 | Click to view video 67 | 68 | ---- 69 | ## Master Markdown 70 | 71 | Markdown is the simple formatting language used on GitHub to add rich features to your documents. To use Markdown in your documentation, add .md to your file name. 72 | 73 | ![](http://i.imgur.com/ozsdIoo.png?1) 74 | 75 | * **[GitHub Mastering Markdown Guide](https://guides.github.com/features/mastering-markdown/#examples)** 76 | * **[Markdown Live Preview](http://markdownlivepreview.com/)** 77 | 78 | 79 | ---- 80 | ## Practice now! 81 | 82 | [![Practice now](http://i.imgur.com/IwFlrHf.png?1)](https://vimeo.com/148974048) 83 | 84 | Click to view video 85 | -------------------------------------------------------------------------------- /images/money-diagram.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/enspiral/guides/c6be8ec95d06d49c666cd1e8dbca1b2e9e9ba317/images/money-diagram.jpg -------------------------------------------------------------------------------- /money.md: -------------------------------------------------------------------------------- 1 | # How money works at Enspiral 2 | 3 | *Money moves like water when you don’t have a boss* 4 | 5 | We reckon that decentralising the control of money is one of the most strategic things we can do to make the world a better place. 6 | 7 | Financial literacy is power. In any organisation, the people that understand the flows of money have a huge influence on where that money gets spent. So we’ve invested in enhancing that literacy for everyone in the network. 8 | 9 | At Enspiral we have developed a menagerie of tools and practices to translate that lofty ambition into a practical reality. 10 | 11 | Most of us are freelancers earning our own money, but we all put some of that money "in the middle": a collective resource that we manage collaboratively. 12 | 13 | As we’ve developed our tools and processes, we’ve seen that an increasing number of people have access to spend the money, and more people are contributing as well. 14 | 15 | ![](https://github.com/enspiral/guides/blob/master/images/money-diagram.jpg) 16 | 17 | ## How money comes in 18 | 19 | The main sources of collective funds at Enspiral are from Services (freelancers and teams contributing around 20% of their income), Ventures (each venture has a unique agreement with the Foundation as to how much they contribute), and grants (e.g. Lifehack Project, Namaste Foundation). 20 | 21 | * Story : Voluntary contributions create effective governance mechanism 22 | * Story : [Variable contributions at Enspiral](http://joshuavial.com/variable-contributions-enspiral/) 23 | * Recipe : Voluntary contributions as a freelancer with Enspiral Services 24 | * Recipe : Voluntary contributions as a Venture - Xero code vs. manual allocations 25 | * Story : I hold this piece of the puzzle e.g. Charmaine 26 | 27 | ## Our internal economy 28 | 29 | We have a core piece of digital infrastructure called "my.enspiral" - it’s our homemade bank that holds our internal economy. Money can flow between different people and projects in Enspiral Services without ever leaving our collective bank account. 30 | 31 | * Story : my.enspiral: how we made our homemade bank legal 32 | 33 | ## How money gets spent 34 | 35 | **Enspiral Foundation** 36 | 37 | Each month collective funds are up for grabs. Any contributor can propose a project for funds to be spent on and the Members (shareholders of the Enspiral Foundation) each get an equal portion to spend. In this way we are investing our profits as a network back into our social mission. 38 | 39 | * Recipe : [Collaborative funding (Foundation)](#recipe--collaborative-funding-with-the-enspiral-foundation) 40 | * Story : [MiX Prize Collab funding](http://www.managementexchange.com/story/collaborative-funding-dissolve-authority-empower-everyone-and-crowdsource-smarter-transparent) 41 | * Recipe : writing a good collab funding bucket proposal 42 | * Recipe : fixed expenses for Foundation 43 | 44 | **Enspiral Services** 45 | 46 | * Recipe : Collaborative funding (Services) 47 | * Story : Incubation of Cobudget through collab funding 48 | * Story : Overdrafts and loans - how we help each other out through hard times 49 | * Wiki : [How to invoice](https://github.com/enspiral/services/wiki/Client-invoicing) 50 | * Recipe : Fixed expenses for Services 51 | 52 | **Ventures** 53 | 54 | Lots of our Ventures have come up with creative ways of playing with money too. 55 | 56 | * Story : accounting for sweat equity without accruing a big debt on the books (Loomio points, Craftworks fairy gold) 57 | * Story : how to get investment capital when you’re not a profit-maximising company (Loomio, EDA) 58 | * Recipe : Self determined salaries (incl. video from EDA) 59 | # Recipe : Collaborative Funding with the Enspiral Foundation 60 | 61 | * * * 62 | 63 | 64 | *Collaborative Funding with the Enspiral Foundation is our monthly process of deciding how to spend the ‘profit’ left over in Collective Funds each month. * 65 | 66 | Practiced in : Enspiral Foundation 67 | 68 | Developers : Alanna Krause, Joshua Vial, Simon Tegg, Derek Razo 69 | 70 | Inspiration : Kim Stanley Robinson's novel "Pacific Edge" 71 | 72 | * * * 73 | 74 | 75 | **Methodology :** 76 | 77 | 1. In the middle of each month, Enspiral Services Contributors and Members are invited to submit what we call Bucket Proposals through our collaborative funding software [Cobudget](http://cobudget.co/). A proposal outlines a project that an Enspiralite wants to happen. The description consists of what they want to do and how it would benefit to the network. It’s their pitch to internal investors. 78 | 79 | 2. At the end of each month, Enspiral Ventures [contribute revenue](https://docs.google.com/spreadsheets/d/1TBTikOU27tXRb1H05LbZLyUUwYEV3Ph04gXlvDi9hE0/edit#gid=0) to the Enspiral Foundation collectuve funds as per their unique [Venture Agreement](https://github.com/enspiral/agreements/blob/master/agreements/ventures.md). Other sources of income to collective funds are through grant fund-holding e.g. [Lifehack Project](http://lifehackhq.co/), [Namaste Grant](http://www.namaste.org/blog/enspiral-open-source-society). 80 | 81 | 3. Core fixed expenses agreed through [Loomio](https://www.loomio.org/) decisions such as legal, accounting, tax, staffing are subtracted. 82 | 83 | 4. Bucket proposals are collated into a menu of options for investment. 84 | 85 | 5. Enspiral Ventures who had contributed revenue maintain control of their monthly contribution and decide within their organisation what they would like it spent on. This is sometimes done by a process of delegation (one person in the Venture is responsible for allocating), through [Dot-Voting](http://dotmocracy.org/dot-voting) on Loomio, or group decision made by consensus. 86 | 87 | 6. Contributions that have come from other sources (e.g. grant fund-holding) are split equally between Enspiral Members (shareholders of the Enspiral Foundation) to invest. 88 | 89 | 7. At the start of the new month, investment opens for one week for Ventures and Members to decide how to spend their contributions. Any funds that are not spent during this period get transferred to Reserves. Funds held in Reserves require a Loomio decision to be spent. 90 | 91 | 8. At the close of this period, people who have proposed buckets are informed by email that they have funds accessible. Buckets Sponsors that didn’t reach their target are given three options : 92 | 93 | 1. Cancel the bucket, send allocated funds to reserves 94 | 95 | 2. Progress the bucket with the amount of funds they received 96 | 97 | 3. Hold the funds and propose the bucket again next round 98 | 99 | 9. Funds are released to Bucket Sponsors on completion of the project proposed and a short report on the outcome of the project is sent back to the Collaborative Funding team to be collated into our Collaborative Funding Annual Reports. 100 | 101 | # Recipe : Collaborative Funding with Enspiral Services 102 | 103 | 104 | *Collaborative Funding with Enspiral Services is our monthly process of deciding how to spend the ‘profit’ left over in Collective Funds each month. * 105 | 106 | Practiced in : Enspiral Foundation 107 | 108 | Developers : Alanna Krause, H 109 | 110 | Inspiration : 111 | 112 | 113 | **Methodology :** 114 | 115 | In the middle of each month, Enspiral [Contributors](https://github.com/enspiral/agreements/blob/master/agreements/people.md#contributors) and [Members](https://github.com/enspiral/agreements/blob/master/agreements/people.md#members) are invited to submit what we call Bucket Proposals through our collaborative funding software [Cobudget](http://cobudget.co/). A proposal outlines a project that an Enspiralite wants to happen. The description consists of what they want to do and how it would benefit to the network. It’s their pitch to internal investors. 116 | 117 | *Bucket proposals consist of a title, description, who is managing it (sponsor) and what is the target amount of money required to complete the project.* 118 | 119 | * * * 120 | 121 | 122 | At the end of each month, Enspiral Ventures [contribute revenue](https://docs.google.com/spreadsheets/d/1TBTikOU27tXRb1H05LbZLyUUwYEV3Ph04gXlvDi9hE0/edit#gid=0) to the Enspiral Foundation collectuve funds as per their unique [Venture Agreement](https://github.com/enspiral/agreements/blob/master/agreements/ventures.md). Other sources of income to collective funds are through grant fund-holding e.g. [Lifehack Project](http://lifehackhq.co/), [Namaste Grant](http://www.namaste.org/blog/enspiral-open-source-society). 123 | 124 | Core fixed expenses agreed through [Loomio](https://www.loomio.org/) decisions such as legal, accounting, tax, staffing are subtracted. 125 | 126 | Bucket proposals are collated into a menu of options for investment. 127 | 128 | Enspiral Ventures who had contributed revenue maintain control of their monthly contribution and decide within their organisation what they would like it spent on. This is sometimes done by a process of delegation (one person in the Venture is responsible for allocating), through [Dot-Voting](http://dotmocracy.org/dot-voting) on Loomio, or group decision made by consensus. 129 | 130 | Contributions that have come from other sources (e.g. grant fund-holding) are split equally between Enspiral Members (shareholders of the Enspiral Foundation) to invest. 131 | 132 | At the start of the new month, investment opens for one week for Ventures and Members to decide how to spend their contributions. Any funds that are not spent during this period get transferred to Reserves. Funds held in Reserves require a Loomio decision to be spent. 133 | 134 | At the close of this period, people who have proposed buckets are informed by email that they have funds accessible. Buckets Sponsors that didn’t reach their target are given three options : 135 | 136 | 1. Cancel the bucket, send allocated funds to reserves 137 | 138 | 2. Progress the bucket with the amount of funds you received 139 | 140 | 3. Hold the funds and propose the bucket again next round 141 | 142 | Funds are released to Bucket Sponsors on completion of the project proposed and a short report on the outcome of the project is sent back to the Collaborative Funding team to be collated into our Collaborative Funding Annual Reports. 143 | 144 | -------------------------------------------------------------------------------- /project-kitchen.md: -------------------------------------------------------------------------------- 1 | # Recipe : Project Kitchen 2 | 3 | > **The Project Kitchen methodology was developed by Seb Paquet and is an energising process for efficiently giving mutual support to projects through enabling group intelligence. We've also found this invaluable for cross-pollinating between different initiatives in the network. It can be done in-person or online using Google Hangouts or similar platform.** 4 | 5 | ---- 6 | ## Project Kitchen background 7 | 8 | Project Kitchens are a socially curated, facilitated, and efficient way of moving projects forward. 9 | 10 | The format brings together a small number of people who have projects they would like assistance with and puts one project at a time under the spotlight for around 25 minutes. Generally 3-4 projects can be covered in a 2-hour Kitchen. A Chef facilitates; with the role of creating an atmosphere of trust, keeping things rolling, and avoiding wasting time through the process. 11 | 12 | The Project Kitchen method gives participants concrete ideas and encouragement for moving forward in their projects or ventures, a better idea of other participants’ contexts and needs, and generates a stronger sense of togetherness. As a bonus, it sharpens listening skills and ability to ask for help. It feels fun and is time-efficient. 13 | 14 | ---- 15 | ## Project Kitchen process 16 | 17 | 1. **Check-ins** - Each person in the group is invited to respond to the question 'How are you and why have you come today?' This gets everyone present. 18 | 19 | 2. **Overview of Project Kitchen** - The Chef describes the Project Kitchen - how it developed, what it's designed to do, and a high level view of how it's going to roll. 20 | 21 | 3. **Notes document** - We create a Google Doc, share with participants and 2-3 people offer to write up notes for the session. These notes are often hugely valuable to distribute further than the group who attends the Project Kitchen as they have concise information about what different people are working on and what they would like help with. 22 | 23 | 4. **Who has projects?** Ask the group who has projects they would like help with. Four is ideal for a 2-hour session. If you have more projects than this then the group can make a decision of what projects to prioritise [see also : [Roomio](insert link here)]. Once you've decided what projects to engage in, the Project Kitchen choreography can begin with the first project. 24 | 25 | 5. **Choreography** 26 | * **Context :** Project holder talks about their project - giving the context the group needs to understand what they're working on and what burning question or issue they might like the group's brains on. **[4 mins]** 27 | 28 | * **Q&A :** The group asks the project holder rapid-fire questions to get more of the background. Both the questions and answers should be as concise as possible to maximise the number of questions answered. The Chef can intervene if someone is talking rather than questioning. **[4 mins]** 29 | 30 | * **Burning question :** The project holder articulates a focussed question or issue that they would like the group's help with. **[1 min]** 31 | 32 | * **Discussion :** The group holds a generative discussion of ideas to help the project holder with their identified issue. The project holder is not allowed to speak - they can only take notes. The Chef helps the discussion stay focussed and makes sure there is room for everyone's voice to be heard. **[8 mins]** 33 | 34 | * **Harvest :** The project holder reflects back to the group what was valuable and actionable from their discussion. **[3 mins]** 35 | 36 | * **Rinse and repeat :** Process is repeated for other projects on the table. 37 | 38 | 39 | 6. **Check-out** - Each person in the group is invited to talk briefly about their experience of the Project Kitchen process and what value they got out of it. 40 | -------------------------------------------------------------------------------- /roomio.md: -------------------------------------------------------------------------------- 1 | # Recipe : Roomio 2 | 3 | > **Roomio is our in-person version of [Loomio](http://www.loomio.org). We use it to make group decisions by consensus in meetings when everyone affected by the decision is in the room. Below are the principles and process involved.** 4 | 5 | ---- 6 | ## Roomio principles 7 | We've found holding these cultural principles (mindset) dramatically improves the process of group decision-making. 8 | 9 | 1. **If you are operating in a group decision-making space then you are thinking in the interest of the group** — not just yourself as an individual. A key frame here is not ‘what do I want?’ or ‘what should we do?’, but instead ‘what makes sense here?’. This of course doesn’t mean that we become self-sacrificing, but that you blend your interest with that of the group. 10 | 11 | 2. **Difference as a resource ** -  if someone disagrees it’s because they have found a legitimate problem with the proposal that they want to be part of solving. Difference is a strength not a weakness. Dissent is valuable. At Enspiral the expectation that comes with disagreeing with a proposal is that you become invested in finding a better solution that works for everyone. 12 | 13 | 3. **Creative reconciliation** - compromising is a lose:lose situation. Instead reach for creative reconciliation. This potential that comes with effective group work — the potential to create new possibilities that no one person could have come up with on their own — is the whole deal. This is why we do collaboration — because we believe that groups are more generative and intelligent that individuals. But this means you need to hold loosely to what you propose, to be open to a better solution which means a different definition of success - you don’t win when you’re the one who comes up with the great idea, you win when the group becomes authentically generative. 14 | 15 | 4. **Feelings are information too** - create explicit invitations to express feelings — even if they are inarticulate, they are a valuable source of intelligence. We’re conditioned in the workplace to pretend like “I haven’t got feelings. I left them at home! I’m at work now and I have my special uniform on that says No Feelings.” But this forces people to become less than human, which is detrimental fostering the care and high trust that lubricates group work. 16 | 17 | 5. **Humans flourish in flexibility**  -  a community is not a monolithic thing — it is full of contradictions and there are no solutions that are going to fit everyone perfectly. Humans need flexibility to be able to flourish and show up with their full selves. Working in group intelligence is as inherently messy as any other human endeavour and pretending otherwise is just going to get you into trouble. 18 | 19 | ---- 20 | ## Roomio process 21 | 22 | 1. Sit with the group in a circle. 23 | 24 | 2. **Context :** Someone sets the context for the discussion - giving everyone the relevant information they need to be feeding into the decision-making process. 25 | 26 | 3. **Round of responses :** Invite a round of responses. Any person can start and then pick a direction to continue. People have the option to pass and the group will check in with them when everyone else has spoken to see if they would like to speak. Responses can involve both questions and statements / opinions. 27 | 28 | 4. **Generative discussion :** Once everyone has spoken, the room opens for anyone to speak, with the intention of starting to pull the common thread of the responses and give directionality to the conversation. People speak as they are moved to. The facilitator (usually the person who gave the discussion context) watches for who is speaking and who isn't, and makes space those more reserved voices to contribute. 29 | 30 | 5. **Proposal :** The discussion reaches a point of convergence and someone in the group raises a proposal. They articulate this to the group and check in to make sure everyone understands what they are proposing. 31 | 32 | 6. **Voting :** The group is invited to vote. This is done with hand signals adapted from [Occupy General Assembly](https://en.wikipedia.org/wiki/General_assembly_(Occupy_movement)#Methods). There is a count to three and everyone makes the signal for their vote. 33 | + **Thumbs up** = Agree (want proposal to go ahead) 34 | + **Thumb on side** = Abstain (happy for group to decide) 35 | + **Thumbs down** = Disagree (think we can do better) 36 | + **Hand up** = Block (vetoes the decision) 37 | 38 | 7. **Creating Agreement :** Everyone is invited to make a comment about their vote if they choose. If someone has blocked the decision cannot be passed and so it is up to that person to explain why they have blocked - their concern and what they think would improve the proposal. Although decisions can be passed with people disagreeing, in practice these people are usually invited to improve the proposal. Once a new proposal has been formulated and articulated, the voting happens again. Sometimes a proposal will be iterated on a few times before agreement is reach. This can often be the most productive thing to happen in the group. 39 | 40 | -------------------------------------------------------------------------------- /welcoming-new-contributors.md: -------------------------------------------------------------------------------- 1 | # Welcoming new Contributors to Enspiral - a suggested process 2 | 3 | Every new [Contributor](https://github.com/enspiral/agreements/blob/master/agreements/people.md#contributors) to Enspiral is invited in by an Enspiral [Member](https://github.com/enspiral/agreements/blob/master/agreements/people.md#members). They are then assigned an official Buddy to be an additional support in welcoming them into the network. Existing Enspiral Members and Contributors can volunteer to be on the Buddy roster for 6-month periods ([see this Loomio decision](https://www.loomio.org/d/UOR1h9Px/evolving-the-buddy-system-for-new-enspiral-contributors-who-wants-to-be-on-the-enspiral-welcoming-crew-)). 4 | 5 | The first duty of being an Enspiral Buddy is to schedule in a meeting or skype call with the new Contributor. While they are free for the conversation to take any form they feel is most useful and meaningful, here's a process which has been tested as effective for helping orient new Contributors. 6 | 7 | ## Part 1 : The Interview 8 | This is where you ask the new Contributor about how they've come into the network, why they're here and what they'd like to contribute. It's a great idea to document their answers in a Google Doc or other format so they have it for their personal record. It's possible that this information could also be used at a later date to populate an online profile for the Contributor. 9 | 10 | **Questions :** 11 | 12 | 1. What attracted you to Enspiral? 13 | 2. What is your intention coming in? What would success look like to you? 14 | 3. What do you think you might like to contribute? What skills are you bringing? 15 | 16 | ## Part 2 : Building connections 17 | Based on what you learned in Part 1, suggest three people in the network that the new Contributor might like to connect with. Then empower them to make contact - this could be as simple as saying 'I'd recommend just pinging them on skype - I think they'd be really open to talking with you' or it could involve a personal introduction - either over email or in person. 18 | 19 | ## Part 3 : Tour of the house 20 | If both parties are based in Wellington this could include Enspiral Space, otherwise it will just be a tour of our online spaces. The idea with this part is that it’s the difference between getting given keys to a house and left to your own devices, and being given a personal tour about how everything works. It might also be worth referring them to the **[Enspiral Comms Guide](comms.md)** at this time. 21 | 22 | * **Enspiral website** - where to find essential info. Includes info.enspiral.com and Orientation Doc there. 23 | 24 | * **Slack** - what channels they might like to join, what the pattern of interaction is, filling out their profiles. 25 | 26 | * **Loomio** - what discussions are happening at the moment they might be interested in. Advice around commenting, starting discussions and attention economy. 27 | 28 | * **Cobudget** - show them how to propose buckets and encourage them to comment on ideas other people have posted. 29 | 30 | * **Chalkle** - ensure they've been able to log in and understand they can post events there. 31 | 32 | --------------------------------------------------------------------------------