The Squishy Side of Open Source Presented by Keeley Hammond & Scott Hanselman 

Introduce yourself: ● Name ● Experience with open source ● What do you want to take away? 

Overview of OSS 

What does an open source maintainer do? 

Software is hard enough; working with people is harder. Why This Workshop Exists: 

No content

Good The 

Source: https://twitter.com/GeoffreyHuntley/status/904482853768933377 

Source: https://github.com/PrismJS/prism/pull/609 

Source: https://github.com/keymanapp/keyboards/pull/52 

● Keep requests clear and direct ● Ask questions, but be patient ● Understand the time commitments of maintainers. ● Take criticism well ● Say thank you ● Consider language barriers What Makes Them Good? 

BAD The 

(Source) ...How could this have been handled better? 

Source: https://github.com/vcflib/vcflib/issues/206 

Source: https://github.com/MahApps/MahApps.Metro.IconPacks/issues/49 

Source: https://github.com/Fody/PropertyChanged/issues/270 

Source: https://github.com/RolandPheasant/TailBlazer/pull/105 

● Clearly state the issue. ● Keep your PRs simple and clear. ● Consider if your use case is going to be a common one, or unique to you. ● Read contributing docs / existing issues before submitting a PR. ● Include replication instructions if possible. ● Don’t drop the F-bomb 27 times in your issue description. Learn from the Bad 

UGLY The :( 

Source: https://github.com/bonecode/BCEditor/issues/46 

Source: https://github.com/NuGet/NuGetGallery/pull/4437 

Source: https://github.com/opal/opal/issues/941 

Source: https://twitter.com/sarahmei/status/899880200577499136 

Dealing with “Ugliness”: ● It’s not your fault. ● Consider language barriers or misunderstandings ● Find supportive allies ● Codes of Conduct. ● Stop contributing to that community. 

Good The (v.2.0.0) 

Source: https://twitter.com/GeoffreyHuntley/status/904482853768933377 

Source: https://twitter.com/GeoffreyHuntley/status/904482853768933377 <- <- 

Source: https://github.com/nodejs/node/pull/14062 <- Nice, Gave clarity 

Source: https://github.com/Tyrrrz/YoutubeExplode/issues/34 <- from the OP <- the OP 

➔ You are wanted in open source. ➔ Read. Absorb. Understand. ➔ Keep PRs and communication clear and focused. ➔ Be welcoming. Small acts of kindness go far. ➔ Ask questions. ➔ Look for Codes of Conduct ➔ Don’t assume malice… but when malice happens, report it. Remember: 

Credits/Thank You Photos ● Cover: Ex Machina, Universal Pictures ● Slide 2: Vladislav Klapin on Unsplash ● Multiple: The Good, The Bad and The Ugly, Sergio Leone ● Slide 14: Peter Feghali on Unsplash ● Slide 21: rawpixel.com on Unsplash ● Slide 21: Tran Mau Tri Tam on Unsplash ● Credits: Cat Mapper (Max Ogden) on Unsplash ● Thanks: Hanny Naibaho on Unsplash People Geoffrey Huntley (@GeoffreyHuntley) Marc Durdin (@MarcDurdin) Roland Pheasant (@RolandPheasant) Chris Tomkins-Tinch (@tomkinsc) Alexey Golub (@Tyrrrz) Lea Verou (@LeaVerou) Richa Khandelwal (@richak) Daniel R. Bradley (@danielrbradley) Jeff Bryner (@0x7eff) Mozilla Microsoft Women Who Code Portland 

Special Thanks To: @wwcodeportland @mozilla 

Questions & Contact Scott Hanselman @shanselman Keeley Hammond @keeleyhammond