diff --git a/docs/contributing/docs-writing-process.md b/docs/contributing/docs-writing-process.md index 08080cc1b5f26..bf03b82dc3ef9 100644 --- a/docs/contributing/docs-writing-process.md +++ b/docs/contributing/docs-writing-process.md @@ -57,7 +57,7 @@ Here are some tips for gathering information on a given topic within Gatsby: 3. You can also search the web for additional examples outside of the Gatsby GitHub org or docs site. Be sure to check Gatsby versions and only reference the most current examples unless for a specific purpose. -4. In the event there is no information available to write a greenfield doc after trying all the above steps, such as for a new integration, try interviewing Gatsby core team members to help to produce an outline and content tips. See [Pair Programming program](/contributing/pair-programming/). +4. In the event there is no information available to write a greenfield doc after trying all the above steps, such as for a new integration, try asking Gatsby core team members to help to produce an outline and content tips. Please open a [documentation issue](https://github.com/gatsbyjs/gatsby/issues/new/choose) for this then. 5. **For Gatsby inkteam members:** You can also search in the Gatsby Slack internally for related information. It’s possible other team members have discussed the issue, or even compiled trouble points into a doc. Look and ask around as part of your discovery work. @@ -90,7 +90,6 @@ Apply feedback from pull request reviews in order for them to be accepted. Furth - [How to File an Issue](/contributing/how-to-file-an-issue/) - [Gatsby Style Guide](/contributing/gatsby-style-guide/) - [Markdown Syntax Doc](/docs/how-to/routing/mdx/markdown-syntax/) -- [Pair Programming](/contributing/pair-programming/) for interviewing the core team only - [Blog Post Guidelines](/contributing/blog-contributions/) - [Docs site setup instructions](/contributing/docs-contributions/#docs-site-setup-instructions) - [How to Open a Pull Request](/contributing/how-to-open-a-pull-request/) diff --git a/docs/contributing/gatsby-governance-model.md b/docs/contributing/gatsby-governance-model.md index c18b3ac55320c..2cd1e61b4d209 100644 --- a/docs/contributing/gatsby-governance-model.md +++ b/docs/contributing/gatsby-governance-model.md @@ -56,7 +56,6 @@ Here are some relevant docs and resources for contributors: - [How to file an issue](/contributing/how-to-file-an-issue/) - [Request-for-comment (RFC) process](/contributing/rfc-process/) - [Community Maintainers Meeting](/contributing/community/#community-maintainers-meeting) -- [Pair programming sessions](/contributing/pair-programming/) ## Engage with the Gatsby team diff --git a/docs/contributing/how-to-contribute.md b/docs/contributing/how-to-contribute.md index 049fa2241829a..c09d7990ac6d8 100644 --- a/docs/contributing/how-to-contribute.md +++ b/docs/contributing/how-to-contribute.md @@ -8,8 +8,4 @@ We want contributing to Gatsby to be fun, enjoyable, and educational for anyone If you are worried or don't know where to start, check out our [where to participate](/contributing/where-to-participate/) page. You can reach out with questions to [@AskGatsbyJS](https://twitter.com/askgatsbyjs) on Twitter, and anyone from the Gatsby team on [Discord](https://gatsby.dev/discord). You can also [submit an issue](/contributing/how-to-file-an-issue/) and a maintainer can give you guidance! -## Pair programming - -Gatsby.js offers free [pair programming sessions](/contributing/pair-programming/) to the community, if there's something you'd like to work on together. Get in touch with us if you have a question about contributing or an idea for something to pair on! - diff --git a/docs/contributing/how-to-write-a-stub.md b/docs/contributing/how-to-write-a-stub.md index ab08fd4920238..d3420d3f9fefd 100644 --- a/docs/contributing/how-to-write-a-stub.md +++ b/docs/contributing/how-to-write-a-stub.md @@ -20,11 +20,6 @@ pull request gets accepted. If you have any questions about titles or other details related to creating stubs, feel free to ask us on a relevant GitHub issue. -## Community Pair Programming Sessions - -If you create a stub or see an existing one on the Gatsby.js site and feel interested in filling out the content, check out the Gatsby.js -[Pair Programming program](/contributing/pair-programming/). We would love to work with you in your open source contributing journey! - ## Converting a Stub to a Doc To change a stub into a living-breathing document, remove the `issue` entry from a stub's frontmatter (a fancy name for Markdown metadata) and replace the boilerplate content with diff --git a/docs/contributing/pair-programming.md b/docs/contributing/pair-programming.md deleted file mode 100644 index d8dfa1dfc765a..0000000000000 --- a/docs/contributing/pair-programming.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: Open Community Pair Programming Sessions ---- - -The best part of open source is the community, and every community is stronger when it works together. To help build the strongest community possible, Gatsby is offering free [45 minute pair programming sessions][form] to anyone and everyone in the open source community. - -## How community pair programming sessions work - -1. Select or create [an issue](https://github.com/gatsbyjs/gatsby/issues) you would like to work on and work on it yourself. -2. [Create a pull request](/contributing/how-to-open-a-pull-request/) when you encounter any problem. -3. Fill in your details in [the pair programming request form][form]. -4. You’ll be paired with a Gatsby team member and we'll establish a good time to pair on [Zoom](https://zoom.us). -5. We'll help you with your pull request or issue! -6. The video of your pairing session will be available on our [YouTube channel](https://www.youtube.com/channel/UCjnp770qk7ujOq8Q9wiC82w/videos). - -### What we expect in pair programming sessions - -These sessions are intended for people who would like to contribute to Gatsby. We will pair program together to solve an issue or pull request related to Gatsby. - -If you're interested in support for a commercial Gatsby project, please [get in touch via the contact page](/contact-us/). - -We also expect the following from pair programming participants: - -- These sessions work best when you have a specific goal for the session. You should choose an issue or pull request that you'd like to work on. -- If you're new to building with Gatsby we recommend [working through the tutorial](/docs/tutorial/) before your session. If you get stuck part way through that's a great time to book a pairing session. -- If you're new to contributing to open source we recommend following the ["Setting Up Your Local Dev Environment" guide](/contributing/setting-up-your-local-dev-environment/) before your session. -- All participants are expected to adhere to [Gatsby’s code of conduct](/contributing/code-of-conduct/) -- We will ask if it’s okay to record your session; you are _not_ required to let us record and we will work to find another solution that works for you. However, we think it's really valuable to surface these pairing sessions so more people can learn from them and they have a wider reach. -- Check out our [previous sessions](https://www.youtube.com/playlist?list=PLCU2qJekvcN1f4CRTTMMW6XliGio1NcUD) to see if we've already covered what you're looking to learn! This list will grow over time and we're really excited to have lasting learning artifacts for contributing to Gatsby. Our very first recording was not an actual pairing session but was an [introduction to Gatsby's repository and internals](https://www.youtube.com/watch?v=9wM3pFtyTHw) and is a tremendous resource. - -## How to sign up - -Fill in the [request a pairing session form][form] to reserve your spot. The Gatsby team will be notified. You should get an email shortly with next steps. - -[Reserve your spot today][form] and let’s build something amazing together! - -[form]: https://airtable.com/shrtYlQjqQARrmJH4 diff --git a/docs/contributing/why-contribute-to-gatsby.md b/docs/contributing/why-contribute-to-gatsby.md index 5b6d2fa9b8bd7..cf79c724930a0 100644 --- a/docs/contributing/why-contribute-to-gatsby.md +++ b/docs/contributing/why-contribute-to-gatsby.md @@ -6,7 +6,7 @@ There are many reasons to contribute to Gatsby.js and open source software in ge - **Growing your community.** Working with Gatsby.js in open source can connect you with people working on similar things. You can get help or give help, and you might even make an IRL acquaintance! It has happened. -- **Improving your skills.** When you work on a Gatsby issue or pull request, inevitably you'll learn more about how something works in the project; either by asking questions and gathering info or by digging deeper into the code yourself. Gatsby.js also offers free [pair programming sessions](/contributing/pair-programming/) to the community, if there's something you'd like to work on together. There's a skill-building benefit to contributing to OSS! +- **Improving your skills.** When you work on a Gatsby issue or pull request, inevitably you'll learn more about how something works in the project; either by asking questions and gathering info or by digging deeper into the code yourself. There's a skill-building benefit to contributing to OSS! - **Getting free swag!** By participating in the repo on GitHub, you can become eligible for free swag that the Gatsby team offers as a way to say thank you. With 5 contributions, you can advance to a second level with even more swag options! Learn more about this [sweet swag deal](/contributing/contributor-swag/). diff --git a/docs/docs/conceptual/gatsby-core-philosophy.md b/docs/docs/conceptual/gatsby-core-philosophy.md index 35b6fd762506d..3119969b1617c 100644 --- a/docs/docs/conceptual/gatsby-core-philosophy.md +++ b/docs/docs/conceptual/gatsby-core-philosophy.md @@ -161,7 +161,6 @@ Some things we do in order to create an inclusive, welcoming community include: - Friendlier robots - Implicit trust - Active gratitude -- [Active mentorship](/contributing/pair-programming/) We’ve built an active community with thousands of contributors, and we want to live the example of what a great open source community can be.