(blog): Add D&I blog post from writing sample (#21381)

* Add D&I blog post from writing sample

* Remove final comment, swap quotes

* chore: format

* Edit based on initial questions

* Update title

* Add 'oss' to typo-ci excluded words

* Apply suggestions from code review

Co-Authored-By: Marcy Sutton <marcy@gatsbyjs.com>

* lower-case SWAG

Co-Authored-By: Marcy Sutton <marcy@gatsbyjs.com>

* Add Coraline's blurb

* Add avatar

* chore: format

* Update date

* Add Hui Jing

* Update publish date to March 5th

Co-authored-by: GatsbyJS Bot <mathews.kyle+gatsbybot@gmail.com>
Co-authored-by: Marcy Sutton <marcy@gatsbyjs.com>
Co-authored-by: Hashim Warren <hashimwarren@gmail.com>

.typo-ci.yml

@@ -36,3 +36,4 @@ excluded_words:
   - xxs
   - agadoo
   - hevc
+  - oss

docs/blog/2020-02-17-changing-the-oss-status-quo/index.md

@@ -0,0 +1,44 @@
+---
+title: "Changing the Open Source Status Quo"
+date: 2020-03-05
+author: Aisha Blake
+excerpt: "How can we increase the diversity of open source contributors? As maintainers, we need to listen to a diverse group of community members and make thoughtful changes to create a truly inclusive project."
+tags:
+  - open-source
+  - community
+---
+
+In business and in our individual careers, so many of us rely heavily on open source software. We need it but open source isn't as open as it's often made out to be. Too many projects are unfriendly, even openly hostile, to new contributors. This effect, combined with the intersection of many underrepresented identities in tech, effectively shuts people out of the process. Black, indigenous, and people of color (BIPOC) and women are at some of the most visible of these intersections. There are many more. Consider _who_ contributes to open source.
+
+The status quo is made and remade every time we as maintainers add to our documentation. Every time we, as maintainers, engage with the community via social media, issue queues, and our documentation, we help decide who contributes. We contribute to their safety and their productivity. Right now, barriers to contribution are severely limiting our industry's capacity to create and sustain open source projects.
+
+There's an opportunity here. There are thousands of highly skilled potential contributors ready, willing, and able to contribute to open source projects but they need to know that they'll be safe in doing so. A handful of projects are intentionally focusing on this work and making incredible strides towards a more inclusive open source community.
+
+Gatsby's most admirable quality is the company's commitment to that community. Yes, it's a great tool but what use is any tool that is too difficult to use or too obscure for most people to access?
+
+- One of Gatsby's core values is "You Belong Here". We back it up with a clear code of conduct that we consistently reference and enforce.
+- The documentation is vast, includes specifics around contributing, and provides materials that make it easy for people outside of the core team to teach as well as learn.
+- New contributors who have had a PR merged in are invited to the GitHub organization and offered swag as a thank you.
+- There are even a limited number of one-on-one mentorship opportunities available.
+
+Consider your own community and adopt the strategies that are feasible for your project. Who comes back to contribute more than once? Who is heard when making decisions as a group? Who feels empowered to speak publicly about your project? When interpersonal issues arise, who is believed? Take the time to examine your project's processes and documentation. What's missing? What's out-of-date?
+
+Tear down as many barriers to entry as you can identify. The more people are encouraged and prepared to participate, the more likely it becomes that you'll be able to share the burden of maintenance across a wider team.
+
+At the same time, listen to people in marginalized groups. Show up, sit down, and stay quiet. Support individual contributors and affinity groups. Participate in those groups where your presence doesn't introduce a safety concern. (Ask if you have any doubts, and maybe even if you don't.) You could do this by sponsoring an event like the [Blacks in Technology Conference](https://bitcon.tech/) or attending a local Lesbians Who Tech event. Once you're there, avoid centering your own experience. Absorb as much as you can from the experiences of others and educate yourself on how to be the best ally possible. Keep in mind that you don't get to _decide_ that you are an ally. We all have to earn trust over time.
+
+Here are some truly wonderful folks who are already sharing valuable resources and insights:
+
+<!-- Updating as I get responses from people! -->
+
+- [Kim Crayton](https://twitter.com/KimCrayton1) founded the #causeascene movement, which is all about disrupting the status quo throughout the industry. She speaks freely and clearly about injustice in tech and how to fight against it. If you're ready to put in the work to make your organization more inclusive, reach out about her [tech leadership coaching](https://hashtagcauseascene.com/coaching/).
+- [EJ Mason](https://twitter.com/codeability) is an accessibility professional. They're a skilled web developer, writer, and speaker who also posts honestly about living and working in tech as a disabled person. You can learn about how Accessibility is a Hydra during their upcoming session at [REFACTR.TECH](https://www.refactr.tech/).
+- [Coraline Ada Ehmke](https://twitter.com/CoralineAda) has worked for decades and created not only tools but entire _communities_ to help make open source (and tech in general) safer and more inclusive. Perhaps you've already adopted her [Contributor Covenant](https://www.contributor-covenant.org/). You can see her perform original music discussing online harassment at this year's [&lt;title of conf&gt;](https://www.titleofconf.org/).
+- [Amy Wibowo](https://twitter.com/sailorhg) is the brilliant mind and keen eye behind [BubbleSort Zines](https://shop.bubblesort.io/). Her soft, playful aesthetic is both an expression of her own creativity and an invitation to "people who don't think computer science is for them."
+- [Léonie Watson](https://twitter.com/LeonieWatson) is one of the strongest advocates of web accessibility out there. As a member of the W3C Advisory Board and co-Chair of the W3C Web Applications Working Group, she's played a huge role in guiding the way we all build for the web. Consider supporting the conference she organizes, [Inclusive Design 24](https://inclusivedesign24.org/), this year.
+- [Hui Jing Chen](https://twitter.com/hj_chen) is an accomplished designer, developer, and speaker. Her passion for the web, and CSS in particular, shines through in everything she creates. Several of her talks focus on [non-English web typography](https://www.youtube.com/watch?v=yLQHDGRLOwQ&feature=youtu.be) and she regularly shares her unique perspective on everything from internationalization to web specifications via [her blog](https://www.chenhuijing.com).
+  <!-- - [Tatiana Mac](https://twitter.com/TatianaTMac) -->
+  <!-- - [Brianna Wu](https://twitter.com/BriannaWu) -->
+  <!-- - [Fen Slattery](https://twitter.com/sublimemarch) -->
+
+Follow them, listen to what they have to say, and use your privilege as a maintainer to amplify their messages. Keep an open mind and you'll discover challenges you never knew existed, refine your vocabulary around diversity and inclusion, and establish a resilient community of open source contributors.

docs/blog/author.yaml

@@ -388,3 +388,7 @@
   bio: Engineer on TypeScript at Microsoft
   avatar: avatars/orta-therox.jpg
   twitter: "@orta"
+- id: Aisha Blake
+  bio: Teacher, speaker, and community organizer who learned to code via Neopets. Loves theater, karaoke, and dogs.
+  avatar: avatars/aisha-blake.jpg
+  twitter: "@AishaBlake"