1 00:00:00,000 --> 00:00:08,469 foreign 2 00:00:00,500 --> 00:00:08,469 [Music] 3 00:00:10,980 --> 00:00:16,379 good morning and welcome to day two of 4 00:00:14,340 --> 00:00:18,960 everything open where we are going to 5 00:00:16,379 --> 00:00:21,480 hear about boosting your Project's trust 6 00:00:18,960 --> 00:00:23,820 signals with great docs from Felicity 7 00:00:21,480 --> 00:00:25,380 brand Felicity is a technical writer and 8 00:00:23,820 --> 00:00:27,539 editor who is passionate about open 9 00:00:25,380 --> 00:00:29,939 source and is a firm believer in the 10 00:00:27,539 --> 00:00:31,740 power of non-code contributions to open 11 00:00:29,939 --> 00:00:33,940 source 12 00:00:31,740 --> 00:00:36,260 yeah 13 00:00:33,940 --> 00:00:38,160 [Laughter] 14 00:00:36,260 --> 00:00:40,320 Felicity will be talking about the 15 00:00:38,160 --> 00:00:42,420 benefits to your open source project of 16 00:00:40,320 --> 00:00:44,210 having great documentation please make 17 00:00:42,420 --> 00:00:47,879 her welcome 18 00:00:44,210 --> 00:00:50,399 [Applause] 19 00:00:47,879 --> 00:00:53,460 all right I've got my mic on 20 00:00:50,399 --> 00:00:55,860 hi welcome thank you for coming 21 00:00:53,460 --> 00:00:57,840 so today I'll be talking about how to 22 00:00:55,860 --> 00:00:59,520 boost your Project's trust signals 23 00:00:57,840 --> 00:01:02,520 with great Docs 24 00:00:59,520 --> 00:01:04,559 so I begin today by acknowledging the 25 00:01:02,520 --> 00:01:06,960 traditional custodians of the land where 26 00:01:04,559 --> 00:01:09,780 I live and work and on which We Gather 27 00:01:06,960 --> 00:01:11,159 today the warandiri people and I pay my 28 00:01:09,780 --> 00:01:12,600 respects to their Elders past and 29 00:01:11,159 --> 00:01:15,060 present 30 00:01:12,600 --> 00:01:18,180 so I also just need to pop my public 31 00:01:15,060 --> 00:01:21,500 speaking stress bubble if we're not 32 00:01:18,180 --> 00:01:23,700 making mistakes we're not learning so 33 00:01:21,500 --> 00:01:26,299 I'm allowed to make mistakes everyone 34 00:01:23,700 --> 00:01:26,299 okay 35 00:01:27,840 --> 00:01:33,420 um I want to explain that I've used the 36 00:01:29,640 --> 00:01:36,840 term docs in my title very broadly 37 00:01:33,420 --> 00:01:39,240 I mean docs yes but I also mean much 38 00:01:36,840 --> 00:01:41,280 more than documentation I'm talking 39 00:01:39,240 --> 00:01:45,140 about any kind of content or language 40 00:01:41,280 --> 00:01:45,140 used in and around your project 41 00:01:50,040 --> 00:01:52,799 So today we're talking about trust 42 00:01:51,540 --> 00:01:56,399 signals 43 00:01:52,799 --> 00:01:59,299 how you can broadcast informational cues 44 00:01:56,399 --> 00:01:59,299 to help make 45 00:01:59,579 --> 00:02:05,159 I've made a mistake gang 46 00:02:02,579 --> 00:02:06,960 our first one okay 47 00:02:05,159 --> 00:02:08,580 I've got to go back 48 00:02:06,960 --> 00:02:12,200 to 49 00:02:08,580 --> 00:02:12,200 my slide number 50 00:02:14,400 --> 00:02:19,379 g'day 51 00:02:15,739 --> 00:02:23,220 I'm Phil citybrand AKA flickster 52 00:02:19,379 --> 00:02:26,099 I identify as a technical writer I call 53 00:02:23,220 --> 00:02:29,879 myself a technical Communicator I work 54 00:02:26,099 --> 00:02:32,700 as a communications consultant 55 00:02:29,879 --> 00:02:35,580 um I work at open strategy Partners I do 56 00:02:32,700 --> 00:02:40,080 a lot of writing and Technical editing 57 00:02:35,580 --> 00:02:41,580 mentoring writer enablement and training 58 00:02:40,080 --> 00:02:45,360 so I discovered open source pretty 59 00:02:41,580 --> 00:02:48,599 recently in 2019 when I took part in 60 00:02:45,360 --> 00:02:50,760 Google's first season of docs you may 61 00:02:48,599 --> 00:02:52,379 have heard of their summer of code it 62 00:02:50,760 --> 00:02:54,180 was a similar program but for technical 63 00:02:52,379 --> 00:02:56,519 writing 64 00:02:54,180 --> 00:02:59,040 and that's where I discovered I'm 65 00:02:56,519 --> 00:03:01,700 intrinsically motivated so me and open 66 00:02:59,040 --> 00:03:04,440 source are a perfect match really 67 00:03:01,700 --> 00:03:07,200 the two open source projects I hang out 68 00:03:04,440 --> 00:03:11,159 at typo III 69 00:03:07,200 --> 00:03:13,440 which is an Enterprise open source CMS a 70 00:03:11,159 --> 00:03:15,739 bit like David Hasselhoff really big in 71 00:03:13,440 --> 00:03:19,739 Germany 72 00:03:15,739 --> 00:03:22,319 I am a member of the association I 73 00:03:19,739 --> 00:03:24,959 co-authored a book about that product 74 00:03:22,319 --> 00:03:25,560 available at all good bookstores 75 00:03:24,959 --> 00:03:27,300 um 76 00:03:25,560 --> 00:03:28,920 and actually one of the association 77 00:03:27,300 --> 00:03:31,200 board members is here at the conference 78 00:03:28,920 --> 00:03:34,580 today so if you're interested let me 79 00:03:31,200 --> 00:03:37,560 know when I can introduce you 80 00:03:34,580 --> 00:03:38,879 so the other project I hang out at as is 81 00:03:37,560 --> 00:03:41,700 called the good docs project I 82 00:03:38,879 --> 00:03:43,260 co-founded that um where a team of 83 00:03:41,700 --> 00:03:45,480 technical writers and developers 84 00:03:43,260 --> 00:03:47,819 creating templates for open source 85 00:03:45,480 --> 00:03:50,220 projects so we're still young and 86 00:03:47,819 --> 00:03:52,319 growing it's really cool over there come 87 00:03:50,220 --> 00:03:54,500 and join us if you want to hang out and 88 00:03:52,319 --> 00:03:56,700 help us create Docs 89 00:03:54,500 --> 00:03:58,620 there's a pretty cool working group 90 00:03:56,700 --> 00:04:01,799 looking at trying to automate spinning 91 00:03:58,620 --> 00:04:05,780 up a minimum viable dock set so if that 92 00:04:01,799 --> 00:04:05,780 floats your boat come and say hi 93 00:04:06,299 --> 00:04:10,739 so here's where I work open strategy 94 00:04:08,400 --> 00:04:12,900 Partners or OSP 95 00:04:10,739 --> 00:04:16,079 we're a Content marketing agency for 96 00:04:12,900 --> 00:04:19,320 tech product and service companies 97 00:04:16,079 --> 00:04:21,060 so why is trust a thing for me 98 00:04:19,320 --> 00:04:22,320 as a tech writer 99 00:04:21,060 --> 00:04:23,880 coming from working in large 100 00:04:22,320 --> 00:04:25,680 organizations 101 00:04:23,880 --> 00:04:28,199 where there is a tech department and a 102 00:04:25,680 --> 00:04:30,720 marketing department they're very siled 103 00:04:28,199 --> 00:04:32,040 right never the twain shall meet 104 00:04:30,720 --> 00:04:33,840 and 105 00:04:32,040 --> 00:04:37,440 now I work for a tech marketing agency 106 00:04:33,840 --> 00:04:40,460 how do I sleep at night so OSP was 107 00:04:37,440 --> 00:04:42,960 co-founded by two two Founders 108 00:04:40,460 --> 00:04:45,300 Tracy Evans has a really strong 109 00:04:42,960 --> 00:04:47,340 marketing and business background and 110 00:04:45,300 --> 00:04:49,560 Jeffrey McGuire really strong in Tech 111 00:04:47,340 --> 00:04:51,720 and Communications 112 00:04:49,560 --> 00:04:55,139 and between them they focused on this 113 00:04:51,720 --> 00:04:57,419 gaping Chasm this problem of buzzword 114 00:04:55,139 --> 00:04:59,699 bingo that you get particularly around 115 00:04:57,419 --> 00:05:01,380 marketing and Tech 116 00:04:59,699 --> 00:05:04,320 so you might have heard this phrase 117 00:05:01,380 --> 00:05:06,720 developers are allergic to marketing 118 00:05:04,320 --> 00:05:08,220 and their counter to that is this 119 00:05:06,720 --> 00:05:09,180 communication framework that we use 120 00:05:08,220 --> 00:05:12,479 called 121 00:05:09,180 --> 00:05:15,360 authentic communication and it it has 122 00:05:12,479 --> 00:05:17,580 three main tenets of empathy Clarity and 123 00:05:15,360 --> 00:05:19,860 Trust 124 00:05:17,580 --> 00:05:22,820 and so the idea is that we write and 125 00:05:19,860 --> 00:05:25,440 speak clearly and accurately about tech 126 00:05:22,820 --> 00:05:27,780 we are producing a lot of content you 127 00:05:25,440 --> 00:05:29,160 know we do a lot of writing about 128 00:05:27,780 --> 00:05:31,560 technology 129 00:05:29,160 --> 00:05:34,259 Technical Solutions features products 130 00:05:31,560 --> 00:05:35,820 Services okay and we know that we need 131 00:05:34,259 --> 00:05:37,139 to understand the tech to be able to 132 00:05:35,820 --> 00:05:38,759 talk about it 133 00:05:37,139 --> 00:05:41,340 we use empathy to understand our 134 00:05:38,759 --> 00:05:43,080 technical audience 135 00:05:41,340 --> 00:05:45,360 and to know what their challenges are 136 00:05:43,080 --> 00:05:47,580 and that builds Trust 137 00:05:45,360 --> 00:05:49,259 so trust is important if you want to be 138 00:05:47,580 --> 00:05:51,060 a credible Authority 139 00:05:49,259 --> 00:05:53,039 and if you want people to take action 140 00:05:51,060 --> 00:05:55,160 which is basically what marketing is all 141 00:05:53,039 --> 00:05:55,160 about 142 00:06:00,780 --> 00:06:04,800 this is Francis fry 143 00:06:03,060 --> 00:06:07,500 she gave her a well-known Ted Talk 144 00:06:04,800 --> 00:06:09,960 famously worked at Uber she talks about 145 00:06:07,500 --> 00:06:12,240 building trust and she says 146 00:06:09,960 --> 00:06:14,100 you can only trust me and Trust what I'm 147 00:06:12,240 --> 00:06:17,160 saying if what I'm saying has logical 148 00:06:14,100 --> 00:06:18,840 rigor if it makes sense 149 00:06:17,160 --> 00:06:20,460 and you can only trust me and Trust what 150 00:06:18,840 --> 00:06:21,479 I'm saying if I'm being my authentic 151 00:06:20,460 --> 00:06:25,080 self 152 00:06:21,479 --> 00:06:27,660 if you can feel that I am being myself 153 00:06:25,080 --> 00:06:29,639 and thirdly we can only we can only have 154 00:06:27,660 --> 00:06:32,699 trust if I have empathy for you if I'm 155 00:06:29,639 --> 00:06:34,440 putting myself in your shoes 156 00:06:32,699 --> 00:06:37,199 and all that is to say that there's a 157 00:06:34,440 --> 00:06:39,419 human element so say you've built a 158 00:06:37,199 --> 00:06:42,120 fantastic Tech solution to a known 159 00:06:39,419 --> 00:06:44,580 problem you can't just rely on the tech 160 00:06:42,120 --> 00:06:48,440 speaking for itself there's a human 161 00:06:44,580 --> 00:06:48,440 trust element at Play 162 00:06:58,979 --> 00:07:02,759 So today we're talking about trust 163 00:07:00,900 --> 00:07:04,919 signals how you can broadcast 164 00:07:02,759 --> 00:07:07,199 informational cues 165 00:07:04,919 --> 00:07:09,060 to help make that trust connection 166 00:07:07,199 --> 00:07:11,400 as humans in the world we all make 167 00:07:09,060 --> 00:07:13,560 decisions every day Guided by our gut 168 00:07:11,400 --> 00:07:16,340 feelings based on our sense of trust in 169 00:07:13,560 --> 00:07:16,340 a product or service 170 00:07:17,340 --> 00:07:22,440 as an open source project owner or 171 00:07:19,259 --> 00:07:25,620 maintainer if you gain a holistic view 172 00:07:22,440 --> 00:07:28,620 of how your project presents externally 173 00:07:25,620 --> 00:07:31,020 you can make informed mindful choices to 174 00:07:28,620 --> 00:07:32,880 control and curate the message that 175 00:07:31,020 --> 00:07:35,160 you're Broadcasting 176 00:07:32,880 --> 00:07:37,319 and some of the most powerful signals 177 00:07:35,160 --> 00:07:39,560 come from documentation content and 178 00:07:37,319 --> 00:07:39,560 language 179 00:07:43,199 --> 00:07:48,180 so here's what I want to cover today 180 00:07:46,199 --> 00:07:50,699 what signals are why they matter 181 00:07:48,180 --> 00:07:54,060 different types how you can influence 182 00:07:50,699 --> 00:07:55,560 them and some practical resources 183 00:07:54,060 --> 00:07:58,199 there's some interesting Research into 184 00:07:55,560 --> 00:08:01,199 trust trust signals and how they 185 00:07:58,199 --> 00:08:03,060 influence decision making 186 00:08:01,199 --> 00:08:05,699 so what I really want you to walk away 187 00:08:03,060 --> 00:08:07,500 with today is the understanding of how 188 00:08:05,699 --> 00:08:09,840 you can influence signals that your 189 00:08:07,500 --> 00:08:11,940 project is sending out and some tools to 190 00:08:09,840 --> 00:08:14,639 help you get started doing that 191 00:08:11,940 --> 00:08:16,440 so I'm going to talk a little bit about 192 00:08:14,639 --> 00:08:18,780 trust I'm going to talk a lot about 193 00:08:16,440 --> 00:08:22,220 signals and then I'll give you some 194 00:08:18,780 --> 00:08:22,220 resources to help you get started 195 00:08:23,400 --> 00:08:27,979 so what even are trust signals 196 00:08:32,580 --> 00:08:38,880 they're visible cues that help you make 197 00:08:35,279 --> 00:08:41,520 Rich inferences about the health culture 198 00:08:38,880 --> 00:08:43,919 Vitality of a product or project 199 00:08:41,520 --> 00:08:46,140 and they inform our decisions to take 200 00:08:43,919 --> 00:08:49,019 action whether to download test 201 00:08:46,140 --> 00:08:50,519 contribute participate and so on 202 00:08:49,019 --> 00:08:52,800 and it all happens in the blink of an 203 00:08:50,519 --> 00:08:55,080 eye we're all making big and small and 204 00:08:52,800 --> 00:08:58,980 micro decisions every day 205 00:08:55,080 --> 00:09:01,200 everything is giving out signals 206 00:08:58,980 --> 00:09:02,700 but so just to try and put some scope 207 00:09:01,200 --> 00:09:05,000 around it here in this room today we're 208 00:09:02,700 --> 00:09:08,279 talking about open source projects 209 00:09:05,000 --> 00:09:10,320 it's good to know about your signals 210 00:09:08,279 --> 00:09:12,720 because as a project owner or maintainer 211 00:09:10,320 --> 00:09:15,360 or contributor you can get out in front 212 00:09:12,720 --> 00:09:16,620 of them and control or curate the 213 00:09:15,360 --> 00:09:18,120 message that your project is 214 00:09:16,620 --> 00:09:19,680 broadcasting 215 00:09:18,120 --> 00:09:22,820 and that's a good thing because then you 216 00:09:19,680 --> 00:09:22,820 can achieve your goals 217 00:09:26,399 --> 00:09:31,380 here's an example we've got some docs on 218 00:09:29,279 --> 00:09:33,300 the left side there release notes readme 219 00:09:31,380 --> 00:09:35,459 code of conduct 220 00:09:33,300 --> 00:09:38,160 on the right we've got some numbers of 221 00:09:35,459 --> 00:09:39,959 things Stars downloads 222 00:09:38,160 --> 00:09:42,240 Community activity 223 00:09:39,959 --> 00:09:44,940 so different things can be signals 224 00:09:42,240 --> 00:09:48,680 and signals aren't positive or negative 225 00:09:44,940 --> 00:09:48,680 in themselves they're just information 226 00:09:48,779 --> 00:09:53,339 open source projects by their nature are 227 00:09:51,480 --> 00:09:54,540 very open 228 00:09:53,339 --> 00:09:56,940 um so there's a wealth of information 229 00:09:54,540 --> 00:09:58,800 available to people when it comes to 230 00:09:56,940 --> 00:10:01,080 evaluating and decision making you know 231 00:09:58,800 --> 00:10:03,480 you can see the release history you can 232 00:10:01,080 --> 00:10:06,420 see who worked on stuff uh I don't need 233 00:10:03,480 --> 00:10:08,540 to explain open source to you 234 00:10:06,420 --> 00:10:08,540 um 235 00:10:09,060 --> 00:10:12,060 so we're going to take a look at 236 00:10:10,620 --> 00:10:15,300 different types of signals in a minute 237 00:10:12,060 --> 00:10:18,000 but I wanted to look at first I want to 238 00:10:15,300 --> 00:10:19,980 look at why they matter 239 00:10:18,000 --> 00:10:22,399 um why are we even talking about trust 240 00:10:19,980 --> 00:10:22,399 signals 241 00:10:24,959 --> 00:10:29,040 trust plays an important role in 242 00:10:26,940 --> 00:10:30,300 decision making whether we realize it or 243 00:10:29,040 --> 00:10:32,279 not 244 00:10:30,300 --> 00:10:36,000 Stephen Covey wrote a book called Speed 245 00:10:32,279 --> 00:10:38,700 Of Trust and he says work gets done 246 00:10:36,000 --> 00:10:40,680 with and through people 247 00:10:38,700 --> 00:10:42,480 there's nothing more impactful on people 248 00:10:40,680 --> 00:10:43,920 their work and their performance than 249 00:10:42,480 --> 00:10:45,720 Trust 250 00:10:43,920 --> 00:10:47,940 and he breaks down elements of trust 251 00:10:45,720 --> 00:10:50,240 into two categories competence and 252 00:10:47,940 --> 00:10:50,240 character 253 00:10:52,200 --> 00:10:56,459 so competence addresses the questions 254 00:10:54,000 --> 00:10:58,440 can you solve my problem can you solve 255 00:10:56,459 --> 00:11:00,300 it better than the alternatives 256 00:10:58,440 --> 00:11:02,640 so that might be if you're evaluating 257 00:11:00,300 --> 00:11:06,120 open source projects this code looks 258 00:11:02,640 --> 00:11:08,399 okay there's competence there 259 00:11:06,120 --> 00:11:10,560 on the other side character addresses 260 00:11:08,399 --> 00:11:11,459 the question do your values align with 261 00:11:10,560 --> 00:11:13,380 mine 262 00:11:11,459 --> 00:11:15,600 do you have a diverse culture 263 00:11:13,380 --> 00:11:17,760 how do you treat user data do you 264 00:11:15,600 --> 00:11:19,680 communicate authentically 265 00:11:17,760 --> 00:11:21,120 so that might inform your decision to 266 00:11:19,680 --> 00:11:24,079 get involved in a community or 267 00:11:21,120 --> 00:11:24,079 contribute to a project 268 00:11:28,560 --> 00:11:33,180 so why are you here what outcomes are 269 00:11:30,720 --> 00:11:34,140 you after with your project 270 00:11:33,180 --> 00:11:35,519 um 271 00:11:34,140 --> 00:11:37,880 let's look at a few scenarios of 272 00:11:35,519 --> 00:11:41,459 decision making in open source 273 00:11:37,880 --> 00:11:43,940 maybe you've built 274 00:11:41,459 --> 00:11:46,920 a great solution that solves a problem 275 00:11:43,940 --> 00:11:48,660 you want people to use it so maybe your 276 00:11:46,920 --> 00:11:50,760 goal is downloads okay so Stephen 277 00:11:48,660 --> 00:11:53,279 covey's trust model 278 00:11:50,760 --> 00:11:54,779 the competence section people are going 279 00:11:53,279 --> 00:11:57,000 to use your trust signals to decide 280 00:11:54,779 --> 00:11:59,519 whether or not to use your code can it 281 00:11:57,000 --> 00:12:01,500 solve my problem 282 00:11:59,519 --> 00:12:03,779 another example maybe you just need more 283 00:12:01,500 --> 00:12:06,360 people to help you you want to increase 284 00:12:03,779 --> 00:12:08,640 contributions you want folks to decide 285 00:12:06,360 --> 00:12:11,420 to engage with your project so you want 286 00:12:08,640 --> 00:12:13,740 patches bug fixes merge requests 287 00:12:11,420 --> 00:12:16,200 signals are going to tell people how 288 00:12:13,740 --> 00:12:17,880 engaged the maintainers are how active 289 00:12:16,200 --> 00:12:20,220 the project is 290 00:12:17,880 --> 00:12:22,200 should they invest their time fixing a 291 00:12:20,220 --> 00:12:24,779 bug 292 00:12:22,200 --> 00:12:26,700 and a third example maybe you want to 293 00:12:24,779 --> 00:12:28,320 grow your community so now we're looking 294 00:12:26,700 --> 00:12:31,260 at Stephen covey's 295 00:12:28,320 --> 00:12:33,660 character trust traits What type of 296 00:12:31,260 --> 00:12:36,600 community surrounds this project are 297 00:12:33,660 --> 00:12:39,980 they organized welcoming inclusive do 298 00:12:36,600 --> 00:12:39,980 their values align with mine 299 00:12:40,740 --> 00:12:44,880 so whatever your goals there are things 300 00:12:43,019 --> 00:12:47,459 you can do to 301 00:12:44,880 --> 00:12:50,240 control or curate your signals to help 302 00:12:47,459 --> 00:12:50,240 you achieve them 303 00:12:53,339 --> 00:12:57,440 we're going to take a look at exam at an 304 00:12:55,200 --> 00:12:57,440 example 305 00:12:57,779 --> 00:13:02,399 of trust signals in play 306 00:13:00,060 --> 00:13:05,160 so this is a very general staircase to 307 00:13:02,399 --> 00:13:06,240 contribution each of the steps on this 308 00:13:05,160 --> 00:13:08,160 staircase 309 00:13:06,240 --> 00:13:09,899 will have Associated signals that 310 00:13:08,160 --> 00:13:13,560 influence decision making to keep people 311 00:13:09,899 --> 00:13:15,540 stepping along the journey 312 00:13:13,560 --> 00:13:18,240 so let's imagine a simple example of 313 00:13:15,540 --> 00:13:20,820 contributing a bug fix to a project 314 00:13:18,240 --> 00:13:23,820 starts with attention so maybe there's a 315 00:13:20,820 --> 00:13:25,620 social media post or Word of Mouth 316 00:13:23,820 --> 00:13:29,040 so next comes interest I have that 317 00:13:25,620 --> 00:13:31,380 problem that's interesting to me 318 00:13:29,040 --> 00:13:33,540 now we're starting to look at signals I 319 00:13:31,380 --> 00:13:36,680 look up the project I find it on gitlab 320 00:13:33,540 --> 00:13:36,680 I read the readme 321 00:13:36,899 --> 00:13:42,600 next comes trust in the technology so I 322 00:13:39,600 --> 00:13:43,860 download it I try it it works it solved 323 00:13:42,600 --> 00:13:45,899 my problem yay 324 00:13:43,860 --> 00:13:47,399 but 325 00:13:45,899 --> 00:13:50,279 there's a bug 326 00:13:47,399 --> 00:13:52,620 whoa I don't know do I invest my 327 00:13:50,279 --> 00:13:54,120 precious time in fixing this thing is it 328 00:13:52,620 --> 00:13:56,040 worth it 329 00:13:54,120 --> 00:13:58,440 okay so maybe I decide to spend five 330 00:13:56,040 --> 00:14:00,720 minutes looking around the repo 331 00:13:58,440 --> 00:14:02,760 I can see issues are being responded to 332 00:14:00,720 --> 00:14:04,500 people seem to be talking to each other 333 00:14:02,760 --> 00:14:06,480 in a rational manner 334 00:14:04,500 --> 00:14:08,279 maybe I dig a bit further oh they've got 335 00:14:06,480 --> 00:14:10,079 a feature roadmap okay that's cool so 336 00:14:08,279 --> 00:14:12,779 people are using it patches are getting 337 00:14:10,079 --> 00:14:15,000 put in there's some kind of future plan 338 00:14:12,779 --> 00:14:17,100 okay I've decided I'll contribute a fix 339 00:14:15,000 --> 00:14:18,480 now I just need to find out how to do 340 00:14:17,100 --> 00:14:20,459 that 341 00:14:18,480 --> 00:14:21,779 do they have a contributors guide no 342 00:14:20,459 --> 00:14:23,220 that's okay 343 00:14:21,779 --> 00:14:25,139 it's covered in the readme okay there's 344 00:14:23,220 --> 00:14:27,360 an issue template great so this project 345 00:14:25,139 --> 00:14:29,459 is organized it's active it solved my 346 00:14:27,360 --> 00:14:30,540 problem I'm going to contribute a patch 347 00:14:29,459 --> 00:14:34,019 and you know what maybe I'll stick 348 00:14:30,540 --> 00:14:37,459 around and see if I can help anyone else 349 00:14:34,019 --> 00:14:37,459 so that's one example 350 00:14:37,980 --> 00:14:42,800 obviously there are other examples and 351 00:14:40,620 --> 00:14:47,300 different signals will be associated 352 00:14:42,800 --> 00:14:47,300 with different Journeys so um 353 00:14:50,940 --> 00:14:56,639 yep that's all I wanted to say haha uh 354 00:14:53,519 --> 00:14:57,360 so different staircases for different 355 00:14:56,639 --> 00:15:00,779 um 356 00:14:57,360 --> 00:15:03,959 user Journeys uh 357 00:15:00,779 --> 00:15:06,000 like downloading or 358 00:15:03,959 --> 00:15:07,019 joining a community different signals 359 00:15:06,000 --> 00:15:09,320 are going to be important for those 360 00:15:07,019 --> 00:15:09,320 parts 361 00:15:10,680 --> 00:15:14,579 all right so we're going to take a look 362 00:15:12,120 --> 00:15:17,220 at types of trust signals and there's 363 00:15:14,579 --> 00:15:20,279 two types spoilers 364 00:15:17,220 --> 00:15:20,279 um Sue 365 00:15:21,060 --> 00:15:27,540 we've got some direct signals 366 00:15:23,699 --> 00:15:29,100 the highly visual visible Clues so I say 367 00:15:27,540 --> 00:15:31,139 that because they're usually built into 368 00:15:29,100 --> 00:15:33,800 a user interface if you think of GitHub 369 00:15:31,139 --> 00:15:33,800 or gitlab 370 00:15:34,079 --> 00:15:38,040 lots of numbers on the landing page for 371 00:15:36,120 --> 00:15:39,300 any repo so these are quick and easy to 372 00:15:38,040 --> 00:15:42,480 consume 373 00:15:39,300 --> 00:15:44,100 and they make an immediate impression so 374 00:15:42,480 --> 00:15:45,839 looking at these they're almost 375 00:15:44,100 --> 00:15:47,180 quantitative there's a lot of numbers 376 00:15:45,839 --> 00:15:50,279 there 377 00:15:47,180 --> 00:15:52,500 and you might use these direct queues to 378 00:15:50,279 --> 00:15:54,360 make quick decisions about the quality 379 00:15:52,500 --> 00:15:56,760 or the current state of play of a 380 00:15:54,360 --> 00:16:00,740 project this code looks okay 381 00:15:56,760 --> 00:16:00,740 I'll install it and move on with my life 382 00:16:05,880 --> 00:16:12,300 the next set by contrast are indirect 383 00:16:10,019 --> 00:16:14,180 you have to work harder to glean 384 00:16:12,300 --> 00:16:16,620 information from these signals so 385 00:16:14,180 --> 00:16:17,660 they're inferred from browsing through 386 00:16:16,620 --> 00:16:20,279 content 387 00:16:17,660 --> 00:16:22,139 they aren't Quant they're much more 388 00:16:20,279 --> 00:16:24,480 qualitative 389 00:16:22,139 --> 00:16:28,260 normally found in docs in issue threads 390 00:16:24,480 --> 00:16:30,899 in conversation content and language 391 00:16:28,260 --> 00:16:33,240 so people can gauge the tone of the 392 00:16:30,899 --> 00:16:35,940 community your cultures and attitudes 393 00:16:33,240 --> 00:16:39,060 around things like respect inclusion 394 00:16:35,940 --> 00:16:42,060 diversity accessibility 395 00:16:39,060 --> 00:16:43,380 and you might use these indirect cues to 396 00:16:42,060 --> 00:16:45,120 make decisions from a longer term 397 00:16:43,380 --> 00:16:47,000 perspective is this project worth 398 00:16:45,120 --> 00:16:49,620 investing my time 399 00:16:47,000 --> 00:16:51,360 going back to Stephen Covey do their 400 00:16:49,620 --> 00:16:53,579 values aligned with mine 401 00:16:51,360 --> 00:16:56,240 will I participate will I contribute 402 00:16:53,579 --> 00:16:56,240 will I engage 403 00:16:59,399 --> 00:17:02,639 so if you haven't been paying attention 404 00:17:00,959 --> 00:17:03,779 until now here's a good time to tune 405 00:17:02,639 --> 00:17:05,100 back in 406 00:17:03,779 --> 00:17:07,439 um 407 00:17:05,100 --> 00:17:09,120 an important attribute of signals is 408 00:17:07,439 --> 00:17:11,819 their production cost 409 00:17:09,120 --> 00:17:13,679 signals that are costlier to produce are 410 00:17:11,819 --> 00:17:15,660 considered more reliable because they 411 00:17:13,679 --> 00:17:17,699 are harder to fake 412 00:17:15,660 --> 00:17:20,400 this principle comes from signal Theory 413 00:17:17,699 --> 00:17:23,540 and it applies across Fields like 414 00:17:20,400 --> 00:17:23,540 biology and economics 415 00:17:24,720 --> 00:17:27,780 so in our example of an open source 416 00:17:26,760 --> 00:17:29,580 project 417 00:17:27,780 --> 00:17:31,500 it might be that you could get a bot to 418 00:17:29,580 --> 00:17:34,620 artificially increase the number of 419 00:17:31,500 --> 00:17:36,660 forks of stars on your repo 420 00:17:34,620 --> 00:17:38,520 so although those signals are highly 421 00:17:36,660 --> 00:17:40,679 visible and quick to consume 422 00:17:38,520 --> 00:17:42,840 hey this Project's popular 423 00:17:40,679 --> 00:17:44,640 they're not going to be as persuasive or 424 00:17:42,840 --> 00:17:47,340 carry that same weight as an indirect 425 00:17:44,640 --> 00:17:51,360 signal things that are costlier to 426 00:17:47,340 --> 00:17:52,919 produce like documentation so a high 427 00:17:51,360 --> 00:17:55,200 quality readme 428 00:17:52,919 --> 00:17:58,080 takes a little bit of time and effort 429 00:17:55,200 --> 00:18:00,299 and is a really powerful signal 430 00:17:58,080 --> 00:18:02,400 being organized enough to have clear and 431 00:18:00,299 --> 00:18:03,660 useful labels on your issues that takes 432 00:18:02,400 --> 00:18:05,400 time 433 00:18:03,660 --> 00:18:07,320 so there's a high production cost for 434 00:18:05,400 --> 00:18:09,059 those indirect signals but they have 435 00:18:07,320 --> 00:18:11,539 more meaning and they're considered more 436 00:18:09,059 --> 00:18:11,539 reliable 437 00:18:11,820 --> 00:18:14,720 wow 438 00:18:15,440 --> 00:18:20,460 so what does that mean it means you 439 00:18:18,720 --> 00:18:22,980 should invest your time in improving 440 00:18:20,460 --> 00:18:25,980 your indirect signals put the work in 441 00:18:22,980 --> 00:18:27,840 now take some action get out in front of 442 00:18:25,980 --> 00:18:31,160 your signals and control 443 00:18:27,840 --> 00:18:31,160 what you're Broadcasting 444 00:18:31,559 --> 00:18:36,120 and the investment you make into that 445 00:18:33,539 --> 00:18:40,740 higher production cost will flow through 446 00:18:36,120 --> 00:18:40,740 to impact your other signals 447 00:18:41,520 --> 00:18:45,260 okay let's say you're sold 448 00:18:46,380 --> 00:18:50,700 before you dive in uh 449 00:18:49,260 --> 00:18:52,080 just need to point out that it's 450 00:18:50,700 --> 00:18:53,100 important to know that context is 451 00:18:52,080 --> 00:18:55,500 important 452 00:18:53,100 --> 00:18:57,660 so the same signal can mean different 453 00:18:55,500 --> 00:19:01,460 things to different people same signal 454 00:18:57,660 --> 00:19:01,460 can be both attractive and unattractive 455 00:19:03,059 --> 00:19:07,559 for example a detailed contributor's 456 00:19:05,280 --> 00:19:09,419 guide might excite some new contributors 457 00:19:07,559 --> 00:19:12,000 lose detailed instructions for them to 458 00:19:09,419 --> 00:19:13,620 follow takes them to their happy place 459 00:19:12,000 --> 00:19:16,080 or it might be totally off-putting to 460 00:19:13,620 --> 00:19:20,240 other people at work uh too much process 461 00:19:16,080 --> 00:19:20,240 overhead and high bar to participation 462 00:19:20,340 --> 00:19:24,840 so what's meaningful is going to vary 463 00:19:22,260 --> 00:19:26,280 from person to person and it depends on 464 00:19:24,840 --> 00:19:27,720 your goals as a project what you're 465 00:19:26,280 --> 00:19:29,160 trying to achieve what you think is 466 00:19:27,720 --> 00:19:30,780 important 467 00:19:29,160 --> 00:19:33,539 you might really love process it's how 468 00:19:30,780 --> 00:19:36,240 you work it's what you value 469 00:19:33,539 --> 00:19:38,039 and it's a trust signal so 470 00:19:36,240 --> 00:19:39,539 that's setting expectations for a 471 00:19:38,039 --> 00:19:44,580 newcomer 472 00:19:39,539 --> 00:19:46,380 uh at this point I'll just mention chaos 473 00:19:44,580 --> 00:19:48,539 um this is the community health 474 00:19:46,380 --> 00:19:49,679 analytics for open source software a 475 00:19:48,539 --> 00:19:52,380 project 476 00:19:49,679 --> 00:19:54,480 at the Linux foundation and they're 477 00:19:52,380 --> 00:19:57,360 focused on creating a neutral set of 478 00:19:54,480 --> 00:19:58,740 reference metrics to analyze open source 479 00:19:57,360 --> 00:20:01,320 Community Health 480 00:19:58,740 --> 00:20:02,880 and health in this case plays into trust 481 00:20:01,320 --> 00:20:04,980 and Trust signals 482 00:20:02,880 --> 00:20:06,419 so that neutralness is kind of important 483 00:20:04,980 --> 00:20:08,760 because different things can mean 484 00:20:06,419 --> 00:20:10,500 different things to different people 485 00:20:08,760 --> 00:20:12,840 based on their role and what they're 486 00:20:10,500 --> 00:20:14,880 trying to achieve so check out chaos if 487 00:20:12,840 --> 00:20:17,240 you're interested in diving deeper into 488 00:20:14,880 --> 00:20:17,240 that 489 00:20:19,500 --> 00:20:23,340 okay we finally reached the Practical 490 00:20:21,179 --> 00:20:24,919 steps let's look at what you can do so 491 00:20:23,340 --> 00:20:27,780 there are three things I'll talk about 492 00:20:24,919 --> 00:20:29,760 one is doing an audit the second is 493 00:20:27,780 --> 00:20:33,020 defining your values and lastly we'll 494 00:20:29,760 --> 00:20:33,020 look at content and language 495 00:20:35,760 --> 00:20:39,000 so in order it gives you an idea of what 496 00:20:37,559 --> 00:20:40,980 your project signals are going to say to 497 00:20:39,000 --> 00:20:43,140 a newcomber or an outsider basically you 498 00:20:40,980 --> 00:20:44,940 make a list you decide what's important 499 00:20:43,140 --> 00:20:47,720 to you and you think about what you're 500 00:20:44,940 --> 00:20:47,720 trying to achieve 501 00:20:48,000 --> 00:20:51,960 but where you where do you start okay so 502 00:20:50,460 --> 00:20:55,020 to help you we're going to look at a 503 00:20:51,960 --> 00:20:57,480 study this study was published in 2019 504 00:20:55,020 --> 00:20:59,039 it has a long name the signals that 505 00:20:57,480 --> 00:21:02,280 potential contributors look for when 506 00:20:59,039 --> 00:21:04,320 choosing open source projects 507 00:21:02,280 --> 00:21:06,299 and this study came up with a list of 508 00:21:04,320 --> 00:21:07,620 key signals that people use to inform 509 00:21:06,299 --> 00:21:08,820 their decision about whether or not 510 00:21:07,620 --> 00:21:10,919 they're going to contribute to something 511 00:21:08,820 --> 00:21:13,220 in this case specifically a GitHub 512 00:21:10,919 --> 00:21:13,220 project 513 00:21:14,220 --> 00:21:17,520 so this is going to give you some idea 514 00:21:15,900 --> 00:21:19,740 of what to include in your audit 515 00:21:17,520 --> 00:21:23,240 checklist it wasn't an exhaustive study 516 00:21:19,740 --> 00:21:23,240 but you've got to start somewhere 517 00:21:24,360 --> 00:21:28,860 and this is just about contributing so 518 00:21:26,820 --> 00:21:31,100 um bear that in mind so looking at this 519 00:21:28,860 --> 00:21:31,100 list 520 00:21:31,380 --> 00:21:35,100 even if you think your project is pretty 521 00:21:33,059 --> 00:21:37,260 well covered it won't hurt to do a quick 522 00:21:35,100 --> 00:21:39,740 audit of what you've got and look for 523 00:21:37,260 --> 00:21:42,179 opportunities for improvement 524 00:21:39,740 --> 00:21:45,059 for example you might think or your 525 00:21:42,179 --> 00:21:46,880 repos have a readme it exists tick 526 00:21:45,059 --> 00:21:49,080 that's a direct signal so yay for you 527 00:21:46,880 --> 00:21:50,700 but you know let's look deeper what's 528 00:21:49,080 --> 00:21:52,500 the quality of your readme is it 529 00:21:50,700 --> 00:21:55,559 structured what language have you used 530 00:21:52,500 --> 00:21:56,940 that's an indirect signal and it's where 531 00:21:55,559 --> 00:21:59,659 people are going to infer more meaning 532 00:21:56,940 --> 00:21:59,659 about your project 533 00:22:01,140 --> 00:22:05,760 so I did just want to touch briefly on 534 00:22:03,780 --> 00:22:07,260 all of these so except for website I 535 00:22:05,760 --> 00:22:09,419 don't want to focus on websites because 536 00:22:07,260 --> 00:22:11,460 I don't think it's appropriate for every 537 00:22:09,419 --> 00:22:15,539 project to have one leave that up to you 538 00:22:11,460 --> 00:22:17,220 but read me it's a Project's welcome mat 539 00:22:15,539 --> 00:22:20,039 people expect a standard set of 540 00:22:17,220 --> 00:22:22,080 information included here the what the 541 00:22:20,039 --> 00:22:25,740 why of your project how to install it 542 00:22:22,080 --> 00:22:29,520 and use it contact information maybe how 543 00:22:25,740 --> 00:22:32,520 you're accepting contributions if at all 544 00:22:29,520 --> 00:22:34,679 popularity that's a direct signal it 545 00:22:32,520 --> 00:22:36,539 turns out people actually care how many 546 00:22:34,679 --> 00:22:38,940 stars you've got according to this study 547 00:22:36,539 --> 00:22:41,000 popularity is important 548 00:22:38,940 --> 00:22:41,000 um 549 00:22:41,039 --> 00:22:47,460 it it can according to the study it can 550 00:22:44,280 --> 00:22:49,559 imply high levels of contribution so the 551 00:22:47,460 --> 00:22:53,039 way you would influence your popularity 552 00:22:49,559 --> 00:22:55,140 is not really by docs it's more PR so 553 00:22:53,039 --> 00:22:57,600 you'd probably be going to events giving 554 00:22:55,140 --> 00:23:00,419 talks industry participation 555 00:22:57,600 --> 00:23:03,200 so stars are important to you that's 556 00:23:00,419 --> 00:23:03,200 where you can focus 557 00:23:04,140 --> 00:23:08,580 looking at activity uh recency of 558 00:23:07,260 --> 00:23:10,020 commits 559 00:23:08,580 --> 00:23:12,480 distribution is there an even 560 00:23:10,020 --> 00:23:13,919 distribution of contribution is it 561 00:23:12,480 --> 00:23:15,840 always the same for you people that's 562 00:23:13,919 --> 00:23:18,679 neither good nor bad it's just an 563 00:23:15,840 --> 00:23:18,679 informational cue 564 00:23:19,799 --> 00:23:24,120 average response time on issues that's 565 00:23:21,960 --> 00:23:26,059 your direct signal and responsiveness 566 00:23:24,120 --> 00:23:28,440 that's your indirect so 567 00:23:26,059 --> 00:23:30,480 what they mean by that is conversational 568 00:23:28,440 --> 00:23:33,240 threads any kind of language and 569 00:23:30,480 --> 00:23:35,580 attitude how people are talking to each 570 00:23:33,240 --> 00:23:37,260 other are they being snarky how people 571 00:23:35,580 --> 00:23:40,700 are being treated 572 00:23:37,260 --> 00:23:40,700 in that responsiveness 573 00:23:42,780 --> 00:23:47,100 and number of open issues and unmerged 574 00:23:45,419 --> 00:23:48,600 pull requests so that's your direct 575 00:23:47,100 --> 00:23:50,220 signal because it's a number 576 00:23:48,600 --> 00:23:52,140 um 577 00:23:50,220 --> 00:23:55,500 and their reasons that's your indirect 578 00:23:52,140 --> 00:23:57,900 signal so you may have loads of open PRS 579 00:23:55,500 --> 00:23:59,640 open issues and that may be fine because 580 00:23:57,900 --> 00:24:00,500 they all have valid reasons for being 581 00:23:59,640 --> 00:24:03,539 open 582 00:24:00,500 --> 00:24:05,400 and if that's indicated in the thread in 583 00:24:03,539 --> 00:24:08,240 respectful language there's your 584 00:24:05,400 --> 00:24:08,240 indirect trust signal 585 00:24:09,260 --> 00:24:13,200 contributor guidelines so a great 586 00:24:11,280 --> 00:24:14,700 contributor workflow reduces the 587 00:24:13,200 --> 00:24:17,100 friction between discovering something 588 00:24:14,700 --> 00:24:19,080 you'd like to fix and fixing it so it 589 00:24:17,100 --> 00:24:21,240 doesn't have to be its own document can 590 00:24:19,080 --> 00:24:23,640 be a section of your readme 591 00:24:21,240 --> 00:24:25,200 as long as it's thorough 592 00:24:23,640 --> 00:24:27,120 and this study found that for some 593 00:24:25,200 --> 00:24:28,620 people the lack of any kind of 594 00:24:27,120 --> 00:24:31,799 contributed contribution guidelines 595 00:24:28,620 --> 00:24:33,539 gives an immediate negative impression 596 00:24:31,799 --> 00:24:36,240 so that might be something you decide is 597 00:24:33,539 --> 00:24:38,880 a priority for you bonus points for 598 00:24:36,240 --> 00:24:42,200 non-code contribution workflows and 599 00:24:38,880 --> 00:24:42,200 again that depends on your goals 600 00:24:44,760 --> 00:24:49,919 Scaffolding in this study refers to use 601 00:24:47,460 --> 00:24:52,260 of labels and templates for issues 602 00:24:49,919 --> 00:24:54,240 templates for pull requests or merge 603 00:24:52,260 --> 00:24:57,620 requests and this shows that the project 604 00:24:54,240 --> 00:24:57,620 is organized it has structure 605 00:24:59,400 --> 00:25:03,900 code quality obviously code quality is 606 00:25:01,559 --> 00:25:05,280 an important marker for project use and 607 00:25:03,900 --> 00:25:07,260 the way you can show that is by 608 00:25:05,280 --> 00:25:09,000 embedding badges in your readme to 609 00:25:07,260 --> 00:25:10,380 demonstrate that the code base is fully 610 00:25:09,000 --> 00:25:12,059 tested 611 00:25:10,380 --> 00:25:14,460 according to this study contributors 612 00:25:12,059 --> 00:25:17,100 looked for readable well-structured code 613 00:25:14,460 --> 00:25:18,179 with few dependencies 614 00:25:17,100 --> 00:25:20,960 so that may be something that's 615 00:25:18,179 --> 00:25:20,960 important for you 616 00:25:21,780 --> 00:25:26,100 and Community tone so if you're browsing 617 00:25:24,120 --> 00:25:28,140 a repo you're diving into docs issue 618 00:25:26,100 --> 00:25:30,240 threads look at the language used in 619 00:25:28,140 --> 00:25:33,380 those docs it's going to demonstrate the 620 00:25:30,240 --> 00:25:33,380 social norms of the project 621 00:25:36,600 --> 00:25:42,179 so if all that feels overwhelming I'm 622 00:25:40,200 --> 00:25:44,340 just going to give a Shameless pug for 623 00:25:42,179 --> 00:25:46,500 open strategy Partners we do offer a 624 00:25:44,340 --> 00:25:48,779 trust and vibrancy signal audit service 625 00:25:46,500 --> 00:25:49,620 where we will do all this hard work for 626 00:25:48,779 --> 00:25:50,220 you 627 00:25:49,620 --> 00:25:52,440 um 628 00:25:50,220 --> 00:25:54,900 we'll analyze your project look at these 629 00:25:52,440 --> 00:25:58,520 signals and give you a report on areas 630 00:25:54,900 --> 00:25:58,520 that you can focus on 631 00:26:01,260 --> 00:26:05,400 okay so you've done your audit what's 632 00:26:02,820 --> 00:26:06,900 next before you take action you might 633 00:26:05,400 --> 00:26:08,480 want to think about your goals think 634 00:26:06,900 --> 00:26:11,460 about what you value 635 00:26:08,480 --> 00:26:12,779 decide who and how you want to be 636 00:26:11,460 --> 00:26:14,820 and you don't have to spend a lot of 637 00:26:12,779 --> 00:26:15,960 time it doesn't have to be exhaustive 638 00:26:14,820 --> 00:26:17,880 but it's going to help you make 639 00:26:15,960 --> 00:26:21,559 decisions about how you write talk 640 00:26:17,880 --> 00:26:21,559 communicate in your project 641 00:26:21,600 --> 00:26:25,700 so a code of conduct is a really good 642 00:26:23,100 --> 00:26:25,700 way to do this 643 00:26:26,940 --> 00:26:30,179 code of conduct should not only state 644 00:26:28,740 --> 00:26:32,340 the rules of the conduct but should 645 00:26:30,179 --> 00:26:34,380 explain why they exist 646 00:26:32,340 --> 00:26:35,700 for example we enforce these rules 647 00:26:34,380 --> 00:26:37,799 because we want to accomplish these 648 00:26:35,700 --> 00:26:39,480 goals 649 00:26:37,799 --> 00:26:41,940 um 650 00:26:39,480 --> 00:26:44,520 if you don't have time to choose your 651 00:26:41,940 --> 00:26:46,440 values and document them check out the 652 00:26:44,520 --> 00:26:48,480 freely available contributor Covenant 653 00:26:46,440 --> 00:26:50,520 which is a code of conduct you can use 654 00:26:48,480 --> 00:26:52,620 and is adopted by many notable open 655 00:26:50,520 --> 00:26:55,020 source projects it's a really Light Lift 656 00:26:52,620 --> 00:26:56,940 we'll set you up pretty quickly 657 00:26:55,020 --> 00:26:58,620 so if you do that one thing when you 658 00:26:56,940 --> 00:27:01,100 leave here today that's a trust signal 659 00:26:58,620 --> 00:27:01,100 right there 660 00:27:03,419 --> 00:27:06,600 all right the third thing uh you've done 661 00:27:05,400 --> 00:27:08,700 your audit you've worked out what you 662 00:27:06,600 --> 00:27:11,880 value now comes the hard part 663 00:27:08,700 --> 00:27:14,159 no one likes working on ducks 664 00:27:11,880 --> 00:27:15,260 except for me I'm a tech writer so ducks 665 00:27:14,159 --> 00:27:17,580 are hard 666 00:27:15,260 --> 00:27:19,580 make it easy on yourself get yourself a 667 00:27:17,580 --> 00:27:22,500 whole bunch of templates 668 00:27:19,580 --> 00:27:24,539 GitHub and git lab obviously have a 669 00:27:22,500 --> 00:27:26,460 whole raft of templates they provide 670 00:27:24,539 --> 00:27:28,919 lots of resources to improve project and 671 00:27:26,460 --> 00:27:32,460 Community Health signals 672 00:27:28,919 --> 00:27:34,799 if you're starting from zero uh 673 00:27:32,460 --> 00:27:36,720 come to my projects the good my project 674 00:27:34,799 --> 00:27:37,620 the good Ducks project 675 00:27:36,720 --> 00:27:39,480 um 676 00:27:37,620 --> 00:27:41,220 we have software and Community templates 677 00:27:39,480 --> 00:27:43,620 to kick-start your docs they're written 678 00:27:41,220 --> 00:27:45,360 in markdown they're in a git lab repo go 679 00:27:43,620 --> 00:27:47,640 and help yourself 680 00:27:45,360 --> 00:27:49,620 each template has a companion guide that 681 00:27:47,640 --> 00:27:51,020 drills down and explains what to include 682 00:27:49,620 --> 00:27:53,700 in each section 683 00:27:51,020 --> 00:27:54,900 written and reviewed by Tech writers so 684 00:27:53,700 --> 00:27:58,500 you can be confident you're getting 685 00:27:54,900 --> 00:28:00,480 quality if you really want to nerd out 686 00:27:58,500 --> 00:28:02,760 with other Tech writers check out write 687 00:28:00,480 --> 00:28:06,320 the docs community 688 00:28:02,760 --> 00:28:06,320 that's a free open community 689 00:28:06,360 --> 00:28:11,820 and they have a massive slack workspace 690 00:28:08,940 --> 00:28:14,400 with multitude of channels devoted to 691 00:28:11,820 --> 00:28:16,980 Tech Solutions 692 00:28:14,400 --> 00:28:19,440 and process about tech writing so if 693 00:28:16,980 --> 00:28:22,500 you're interested in automating docs doc 694 00:28:19,440 --> 00:28:25,020 says code documenting apis Pros linters 695 00:28:22,500 --> 00:28:27,539 maybe you're learning Tech writing maybe 696 00:28:25,020 --> 00:28:29,940 your managing writers go and check out 697 00:28:27,539 --> 00:28:31,500 that Community because there's a wealth 698 00:28:29,940 --> 00:28:32,940 of resources there and friendly people 699 00:28:31,500 --> 00:28:34,320 to help you 700 00:28:32,940 --> 00:28:36,299 so I've listed a couple of other 701 00:28:34,320 --> 00:28:37,020 resources there that I like 702 00:28:36,299 --> 00:28:38,940 um 703 00:28:37,020 --> 00:28:40,679 and I've got links to all of these later 704 00:28:38,940 --> 00:28:41,400 that I can share with you 705 00:28:40,679 --> 00:28:43,799 um 706 00:28:41,400 --> 00:28:45,960 so you can grab them for yourself if you 707 00:28:43,799 --> 00:28:47,520 know of other good resources please 708 00:28:45,960 --> 00:28:48,960 shoot them through to me because I 709 00:28:47,520 --> 00:28:51,140 really like collecting this kind of 710 00:28:48,960 --> 00:28:51,140 stuff 711 00:28:51,779 --> 00:28:54,320 oh yeah 712 00:28:57,779 --> 00:29:01,440 so you've written some really good docs 713 00:28:59,159 --> 00:29:03,419 now you want to set expectations around 714 00:29:01,440 --> 00:29:05,880 how you want other people to talk and 715 00:29:03,419 --> 00:29:07,980 write in your project 716 00:29:05,880 --> 00:29:11,659 so you can do this with a contributor's 717 00:29:07,980 --> 00:29:11,659 guide and or a code of conduct 718 00:29:13,980 --> 00:29:17,820 I really like how Symphony does this so 719 00:29:15,840 --> 00:29:19,740 this is from Symphony um 720 00:29:17,820 --> 00:29:22,760 they bake their language guidance into 721 00:29:19,740 --> 00:29:22,760 their contributors guide 722 00:29:22,980 --> 00:29:26,760 they have a great page called respectful 723 00:29:24,899 --> 00:29:29,159 review comments and I encourage you to 724 00:29:26,760 --> 00:29:31,320 go check it out it's basically guidance 725 00:29:29,159 --> 00:29:33,840 for anyone who's reviewing code and 726 00:29:31,320 --> 00:29:35,640 leaving feedback in their project and I 727 00:29:33,840 --> 00:29:38,159 just wanted to point out these two 728 00:29:35,640 --> 00:29:40,020 sentences to you because 729 00:29:38,159 --> 00:29:40,620 they really pack a punch 730 00:29:40,020 --> 00:29:42,840 um 731 00:29:40,620 --> 00:29:45,299 the setting expectations really clearly 732 00:29:42,840 --> 00:29:47,159 to anyone who's doing a code review in 733 00:29:45,299 --> 00:29:49,200 their project 734 00:29:47,159 --> 00:29:50,640 so firstly you don't have to be formal 735 00:29:49,200 --> 00:29:51,899 great 736 00:29:50,640 --> 00:29:53,520 and we don't expect you to have 737 00:29:51,899 --> 00:29:55,860 error-free English 738 00:29:53,520 --> 00:29:57,840 so you can make mistakes yay 739 00:29:55,860 --> 00:30:00,000 so those two things right there are 740 00:29:57,840 --> 00:30:04,159 making the reviewer comfortable 741 00:30:00,000 --> 00:30:04,159 chillax we're not expecting perfection 742 00:30:04,320 --> 00:30:09,419 the next two things make the receiver of 743 00:30:07,500 --> 00:30:11,399 feedback comfortable 744 00:30:09,419 --> 00:30:12,659 so don't swear that's a pretty easy rule 745 00:30:11,399 --> 00:30:14,940 to follow 746 00:30:12,659 --> 00:30:17,520 and be respectful so anyone who's 747 00:30:14,940 --> 00:30:18,899 submitting a bug fix knows going into 748 00:30:17,520 --> 00:30:20,940 the review process that they're not 749 00:30:18,899 --> 00:30:23,779 going to get sworn at and they'll be 750 00:30:20,940 --> 00:30:23,779 treated with respect 751 00:30:25,860 --> 00:30:29,460 so those two sentences encapsulate so 752 00:30:28,020 --> 00:30:31,559 much they're setting a baseline this is 753 00:30:29,460 --> 00:30:34,200 the absolute minimum bar we at Symphony 754 00:30:31,559 --> 00:30:37,640 need if you a Community member are going 755 00:30:34,200 --> 00:30:37,640 to comment on someone else's bug fix 756 00:30:37,760 --> 00:30:41,460 so I really like how they've done that I 757 00:30:39,960 --> 00:30:43,679 do encourage you to go and check out 758 00:30:41,460 --> 00:30:45,299 their contributors guide and just take a 759 00:30:43,679 --> 00:30:47,899 leaf out of their book I think they've 760 00:30:45,299 --> 00:30:47,899 done it really well 761 00:30:51,419 --> 00:30:54,620 so you can go further 762 00:30:54,720 --> 00:30:58,559 my animation you've said expectations 763 00:30:57,000 --> 00:31:00,720 now you might like to help the community 764 00:30:58,559 --> 00:31:02,460 meet those expectations and this is 765 00:31:00,720 --> 00:31:05,100 probably more for advanced players okay 766 00:31:02,460 --> 00:31:06,960 you can do this with a style guide or a 767 00:31:05,100 --> 00:31:10,200 writer's guide it doesn't have to be 768 00:31:06,960 --> 00:31:12,720 lengthy so this is an example from typo3 769 00:31:10,200 --> 00:31:14,460 so that's a large mature project 770 00:31:12,720 --> 00:31:16,919 there's a lot of content that gets 771 00:31:14,460 --> 00:31:19,020 produced around that product 772 00:31:16,919 --> 00:31:20,640 we got a couple of websites we've got 773 00:31:19,020 --> 00:31:22,559 blogs we've got events presentations 774 00:31:20,640 --> 00:31:25,380 obviously Docs 775 00:31:22,559 --> 00:31:28,320 so typo3 has a guide that says 776 00:31:25,380 --> 00:31:30,600 when you're talking or writing about our 777 00:31:28,320 --> 00:31:31,740 project here's the way that we want you 778 00:31:30,600 --> 00:31:33,120 to do it 779 00:31:31,740 --> 00:31:35,100 here are the guidelines and rules that 780 00:31:33,120 --> 00:31:36,120 we want you to follow and that's a trust 781 00:31:35,100 --> 00:31:38,340 signal 782 00:31:36,120 --> 00:31:40,380 because it shows that 783 00:31:38,340 --> 00:31:44,480 people have thought about it 784 00:31:40,380 --> 00:31:44,480 and they're cultivating their culture 785 00:31:45,240 --> 00:31:49,559 they're cultivating the culture that 786 00:31:46,980 --> 00:31:52,799 reflects their values and it makes 787 00:31:49,559 --> 00:31:54,840 people feel confident and safe so if I'm 788 00:31:52,799 --> 00:31:56,880 coming to this project new I'm thinking 789 00:31:54,840 --> 00:31:58,260 do their values align with mine 790 00:31:56,880 --> 00:32:00,960 and I'm looking at this and I'm thinking 791 00:31:58,260 --> 00:32:02,520 huh actually they kind of do they're 792 00:32:00,960 --> 00:32:06,679 organized they know what they care about 793 00:32:02,520 --> 00:32:06,679 they have guidelines like unfollow 794 00:32:07,500 --> 00:32:11,100 and we don't have to all share all of 795 00:32:09,779 --> 00:32:12,659 the same values 796 00:32:11,100 --> 00:32:14,340 um just enough to make a trust 797 00:32:12,659 --> 00:32:16,580 connection and Trigger that decision 798 00:32:14,340 --> 00:32:16,580 making 799 00:32:19,500 --> 00:32:22,860 okay check it out we're almost wrapping 800 00:32:21,659 --> 00:32:25,980 up so 801 00:32:22,860 --> 00:32:28,559 this is what I talked about 802 00:32:25,980 --> 00:32:30,240 be aware of what you're broadcasting and 803 00:32:28,559 --> 00:32:31,860 you can influence the signals that your 804 00:32:30,240 --> 00:32:33,480 project is putting out 805 00:32:31,860 --> 00:32:35,159 so what I want you to walk away with 806 00:32:33,480 --> 00:32:37,500 today is the knowledge that you can take 807 00:32:35,159 --> 00:32:40,140 action there are things you can do there 808 00:32:37,500 --> 00:32:43,200 are templates and resources to help you 809 00:32:40,140 --> 00:32:44,880 so you can take stock of 810 00:32:43,200 --> 00:32:47,700 how you're communicating your technical 811 00:32:44,880 --> 00:32:49,260 competence and Community character 812 00:32:47,700 --> 00:32:51,840 you can do a trust signal audit 813 00:32:49,260 --> 00:32:54,059 articulate your values and put effort 814 00:32:51,840 --> 00:32:56,100 into creating docs and using language 815 00:32:54,059 --> 00:32:58,799 that reflects those values 816 00:32:56,100 --> 00:33:01,860 and that will flow through to entice 817 00:32:58,799 --> 00:33:03,980 newcomers to your project and 818 00:33:01,860 --> 00:33:07,200 Happy Days 819 00:33:03,980 --> 00:33:08,700 so I've listed all of the research for 820 00:33:07,200 --> 00:33:12,179 this talk and the references and 821 00:33:08,700 --> 00:33:14,159 resources I used on a blog post which 822 00:33:12,179 --> 00:33:16,740 hopefully that link is not broken if it 823 00:33:14,159 --> 00:33:21,260 is broken you can find that on the open 824 00:33:16,740 --> 00:33:21,260 strategy partners website blog 825 00:33:22,980 --> 00:33:29,059 and that wraps it up team thank you very 826 00:33:25,620 --> 00:33:29,059 much thank you 827 00:33:29,580 --> 00:33:32,059 thank you 828 00:33:34,919 --> 00:33:39,539 thank you for listening I know that 40 829 00:33:37,140 --> 00:33:41,519 minutes is a long time to pay attention 830 00:33:39,539 --> 00:33:43,799 um and uh yeah please get in touch if 831 00:33:41,519 --> 00:33:45,539 you want to talk more and if you know of 832 00:33:43,799 --> 00:33:48,240 any other templates or resources please 833 00:33:45,539 --> 00:33:51,120 please share them with me okay 834 00:33:48,240 --> 00:33:54,720 okay fantastic thank you so much uh does 835 00:33:51,120 --> 00:33:57,860 anybody have any questions for Felicity 836 00:33:54,720 --> 00:33:57,860 I can see one 837 00:33:58,980 --> 00:34:03,360 thank you so much for that 838 00:34:00,600 --> 00:34:04,980 um looking specifically at one 839 00:34:03,360 --> 00:34:07,140 particular class of people you might be 840 00:34:04,980 --> 00:34:08,339 trying to engage if you have a project 841 00:34:07,140 --> 00:34:09,780 that has plenty of technical 842 00:34:08,339 --> 00:34:11,760 contributors and you're looking to 843 00:34:09,780 --> 00:34:13,980 attract more documentation contributors 844 00:34:11,760 --> 00:34:16,619 to or you know in in the rest of that 845 00:34:13,980 --> 00:34:18,899 space to help go from we've got to read 846 00:34:16,619 --> 00:34:21,119 me too we've got a really good readme 847 00:34:18,899 --> 00:34:23,159 what sort of trust signals would you 848 00:34:21,119 --> 00:34:26,179 advise that documentation people in 849 00:34:23,159 --> 00:34:26,179 particular are looking for 850 00:34:31,500 --> 00:34:34,520 that's a good one 851 00:34:40,740 --> 00:34:46,560 well I mean I guess so you're asking me 852 00:34:43,740 --> 00:34:48,440 about as well so as a technical writer I 853 00:34:46,560 --> 00:34:51,300 would say I would like a writer's guide 854 00:34:48,440 --> 00:34:52,800 but that's tricky if you're a highly 855 00:34:51,300 --> 00:34:54,359 technical group of people you've 856 00:34:52,800 --> 00:34:55,619 probably never put together a writer's 857 00:34:54,359 --> 00:34:57,540 guide before 858 00:34:55,619 --> 00:35:00,660 um maybe just a really great read me 859 00:34:57,540 --> 00:35:02,580 would be in enough I guess a writer 860 00:35:00,660 --> 00:35:04,760 would be looking to see that 861 00:35:02,580 --> 00:35:07,580 people cared 862 00:35:04,760 --> 00:35:10,500 about their dogs 863 00:35:07,580 --> 00:35:13,320 without necessarily having the capacity 864 00:35:10,500 --> 00:35:16,260 to do the docs but certainly in circles 865 00:35:13,320 --> 00:35:18,900 I move in there are often Tech writers 866 00:35:16,260 --> 00:35:20,760 and also young or new upcoming Tech 867 00:35:18,900 --> 00:35:22,560 writers who are looking for open source 868 00:35:20,760 --> 00:35:25,680 projects to contribute to so it's almost 869 00:35:22,560 --> 00:35:26,400 like we need a matchmaking service there 870 00:35:25,680 --> 00:35:29,119 um 871 00:35:26,400 --> 00:35:29,119 to get them together 872 00:35:31,980 --> 00:35:37,800 if I might give an observation here but 873 00:35:35,420 --> 00:35:40,619 I participated in a project that 874 00:35:37,800 --> 00:35:42,540 actually has from your assessment quite 875 00:35:40,619 --> 00:35:45,060 a good set of trust 876 00:35:42,540 --> 00:35:46,140 and we've managed to acquire a couple of 877 00:35:45,060 --> 00:35:47,900 people who are interested in 878 00:35:46,140 --> 00:35:50,280 documentation 879 00:35:47,900 --> 00:35:52,800 and indeed very good at it one of them 880 00:35:50,280 --> 00:35:54,380 wrote a style guide for us 881 00:35:52,800 --> 00:35:58,320 but 882 00:35:54,380 --> 00:36:01,140 they often feel somewhat lonely within 883 00:35:58,320 --> 00:36:04,560 the team because very technical people 884 00:36:01,140 --> 00:36:06,660 don't like writing documentation and 885 00:36:04,560 --> 00:36:08,099 it's worse than that they often won't 886 00:36:06,660 --> 00:36:10,800 even just hand it to the technical 887 00:36:08,099 --> 00:36:13,320 people to handle in some 888 00:36:10,800 --> 00:36:15,420 sufficient detail at least for those 889 00:36:13,320 --> 00:36:17,820 technical those writers those people 890 00:36:15,420 --> 00:36:19,500 with that writing inclination to be able 891 00:36:17,820 --> 00:36:21,480 to turn it into lovely language and and 892 00:36:19,500 --> 00:36:23,880 put it up on the website or in the repo 893 00:36:21,480 --> 00:36:26,640 or you can read me and so on so it can 894 00:36:23,880 --> 00:36:30,599 feel very lonely in an entirely 895 00:36:26,640 --> 00:36:34,619 technical group to be the person with 896 00:36:30,599 --> 00:36:36,180 the urge to document yes because you can 897 00:36:34,619 --> 00:36:38,640 find yourself struggling to get people 898 00:36:36,180 --> 00:36:41,040 to give you the content yeah in a form 899 00:36:38,640 --> 00:36:44,160 you can use to tidy up and make pretty 900 00:36:41,040 --> 00:36:46,020 Yeah Yeah It's Tricky 901 00:36:44,160 --> 00:36:48,300 I don't have a good answer for that it's 902 00:36:46,020 --> 00:36:51,359 the lot of the technical writer's life I 903 00:36:48,300 --> 00:36:53,040 think and we all I suppose I can only 904 00:36:51,359 --> 00:36:56,220 speak for myself we develop strategies 905 00:36:53,040 --> 00:36:56,820 to try and combat that challenge 906 00:36:56,220 --> 00:37:00,900 um 907 00:36:56,820 --> 00:37:02,880 no easy answers um uh I would my advice 908 00:37:00,900 --> 00:37:05,400 to a lonely 909 00:37:02,880 --> 00:37:06,660 writer person would be to get involved 910 00:37:05,400 --> 00:37:07,940 with the write the docs Community 911 00:37:06,660 --> 00:37:12,300 because 912 00:37:07,940 --> 00:37:15,300 then you can find your people obviously 913 00:37:12,300 --> 00:37:18,420 um yeah it's a challenge yes I don't 914 00:37:15,300 --> 00:37:19,740 know um I I see and hear and feel the 915 00:37:18,420 --> 00:37:21,800 pain of that 916 00:37:19,740 --> 00:37:21,800 um 917 00:37:22,619 --> 00:37:30,660 yeah foreign 918 00:37:26,119 --> 00:37:32,160 softwares have like a um like a Wiki 919 00:37:30,660 --> 00:37:34,140 system or something built into them like 920 00:37:32,160 --> 00:37:37,140 it helps go Wiki and all that 921 00:37:34,140 --> 00:37:38,820 but I guess the question I've got is do 922 00:37:37,140 --> 00:37:41,280 you prefer to have the documentation 923 00:37:38,820 --> 00:37:44,160 with the code or separate it out and 924 00:37:41,280 --> 00:37:46,320 tell someone to go visit the wiki so 925 00:37:44,160 --> 00:37:50,220 would you prefer like using a whole 926 00:37:46,320 --> 00:37:52,500 bunch of dot MD files or have a bigger 927 00:37:50,220 --> 00:37:56,880 wiki page 928 00:37:52,500 --> 00:37:58,619 interesting I would my my immediate 929 00:37:56,880 --> 00:38:00,180 answer to that would be maybe do some 930 00:37:58,619 --> 00:38:04,700 user research and find out how people 931 00:38:00,180 --> 00:38:06,839 are consuming that information so um 932 00:38:04,700 --> 00:38:08,640 and that would hopefully tell you 933 00:38:06,839 --> 00:38:11,940 whether you want to put your effort into 934 00:38:08,640 --> 00:38:13,260 putting docs on the wiki or some other 935 00:38:11,940 --> 00:38:16,079 way so you need to find out how they 936 00:38:13,260 --> 00:38:17,760 want to consume the docs I don't know if 937 00:38:16,079 --> 00:38:19,820 I've really answered your question there 938 00:38:17,760 --> 00:38:19,820 um 939 00:38:24,540 --> 00:38:28,200 thank you Felicity amazing talk super 940 00:38:26,820 --> 00:38:29,220 inspiring 941 00:38:28,200 --> 00:38:30,660 um 942 00:38:29,220 --> 00:38:33,900 you said you're really passionate about 943 00:38:30,660 --> 00:38:36,480 non-code contribution hi me too 944 00:38:33,900 --> 00:38:41,460 um what do you what have you seen works 945 00:38:36,480 --> 00:38:44,660 best to invite and and cultivate your 946 00:38:41,460 --> 00:38:44,660 non-code contributors 947 00:38:44,720 --> 00:38:50,820 huh yeah I I've only ever had good 948 00:38:48,240 --> 00:38:52,140 experiences so my limited experience 949 00:38:50,820 --> 00:38:54,119 with 950 00:38:52,140 --> 00:38:55,980 um open source project has been very 951 00:38:54,119 --> 00:38:57,540 supportive and welcoming of non-code 952 00:38:55,980 --> 00:38:58,859 contributions so I don't know if I know 953 00:38:57,540 --> 00:39:01,200 the answer but I'm sure someone in this 954 00:38:58,859 --> 00:39:03,720 room wouldn't 955 00:39:01,200 --> 00:39:05,220 um of how to do that yeah I guess you 956 00:39:03,720 --> 00:39:07,440 just need to somehow 957 00:39:05,220 --> 00:39:08,780 well I guess the first thing to do would 958 00:39:07,440 --> 00:39:11,579 be to 959 00:39:08,780 --> 00:39:14,820 include a non-cone contributor workflow 960 00:39:11,579 --> 00:39:17,780 in your contribution guidelines um 961 00:39:14,820 --> 00:39:17,780 hmm 962 00:39:23,280 --> 00:39:28,320 so well I'm part of a big open source 963 00:39:26,820 --> 00:39:30,480 project and we have all of our 964 00:39:28,320 --> 00:39:32,700 documentation online in GitHub and 965 00:39:30,480 --> 00:39:34,680 people can submit bug reports and pull 966 00:39:32,700 --> 00:39:36,660 requests to that as well is that the 967 00:39:34,680 --> 00:39:38,940 most appropriate workflow for 968 00:39:36,660 --> 00:39:41,339 writing contributions or is some other 969 00:39:38,940 --> 00:39:43,380 workflow better 970 00:39:41,339 --> 00:39:45,920 I would say yes if you've got some 971 00:39:43,380 --> 00:39:49,619 dedicated people 972 00:39:45,920 --> 00:39:52,260 actioning those 973 00:39:49,619 --> 00:39:53,940 right okay so 974 00:39:52,260 --> 00:39:56,099 I hear what you're saying okay so for 975 00:39:53,940 --> 00:39:57,780 typo3 uh we have a similar setup so 976 00:39:56,099 --> 00:39:59,820 we've got our docs and there's a little 977 00:39:57,780 --> 00:40:02,220 edit on GitHub button on every 978 00:39:59,820 --> 00:40:04,320 documentation page and 979 00:40:02,220 --> 00:40:06,060 um we will occasionally see people 980 00:40:04,320 --> 00:40:10,140 submit 981 00:40:06,060 --> 00:40:12,420 um through that you may need to 982 00:40:10,140 --> 00:40:15,960 um if I were you I would I would just 983 00:40:12,420 --> 00:40:18,420 publicize that maybe make it really uh 984 00:40:15,960 --> 00:40:20,460 known I know in typo3 we made a little 985 00:40:18,420 --> 00:40:22,320 video about it we kind of got the head 986 00:40:20,460 --> 00:40:24,599 of product to say this is what you can 987 00:40:22,320 --> 00:40:26,460 do it's really great you know 988 00:40:24,599 --> 00:40:28,680 trying to encourage people to do that 989 00:40:26,460 --> 00:40:31,560 that comes with its own challenges as 990 00:40:28,680 --> 00:40:34,339 well some of some of the issues that do 991 00:40:31,560 --> 00:40:34,339 come through on 992 00:40:34,619 --> 00:40:37,079 um you know submitting changes on docs 993 00:40:36,240 --> 00:40:39,839 pages 994 00:40:37,079 --> 00:40:41,520 aren't valuable sometimes um yeah so you 995 00:40:39,839 --> 00:40:42,599 really do need a team at the back of 996 00:40:41,520 --> 00:40:44,300 that 997 00:40:42,599 --> 00:40:49,579 um 998 00:40:44,300 --> 00:40:49,579 Yeah It's Tricky ducks are hard 999 00:40:53,099 --> 00:40:57,839 yeah I just want to comment uh on what 1000 00:40:55,560 --> 00:40:59,940 Felicity said as well I mean in the type 1001 00:40:57,839 --> 00:41:02,040 of three Community we've had two 1002 00:40:59,940 --> 00:41:05,400 important things that have helped people 1003 00:41:02,040 --> 00:41:08,099 contribute uh and that is the edit on 1004 00:41:05,400 --> 00:41:09,900 GitHub button and having a documentation 1005 00:41:08,099 --> 00:41:13,140 team that takes care of the community 1006 00:41:09,900 --> 00:41:15,119 aspect of being a documentation 1007 00:41:13,140 --> 00:41:17,940 contributor that it is extremely 1008 00:41:15,119 --> 00:41:21,119 important because what keeps people back 1009 00:41:17,940 --> 00:41:23,599 often is the first step over the 1010 00:41:21,119 --> 00:41:27,420 threshold and actually doing your first 1011 00:41:23,599 --> 00:41:29,420 uh contribution just like with code 1012 00:41:27,420 --> 00:41:29,420 um 1013 00:41:29,579 --> 00:41:35,660 do we have time for one more question 1014 00:41:31,619 --> 00:41:35,660 Amy folks one more 1015 00:41:36,480 --> 00:41:40,079 well in that case 1016 00:41:38,460 --> 00:41:43,700 um would you all join me in thanking 1017 00:41:40,079 --> 00:41:43,700 Felicity once again peace 1018 00:41:45,900 --> 00:41:49,590 [Applause]