docs: add Community Maintainers Guidelines

[adiati98]

Description

This PR adds Community Maintainers Guideline with changes as follow:

In the contributing folder inside docs:

• Create a subfolder called opensauced-maintainers-guide.
• Create a community-maintainers-guide.md and add the guidelines content here.
• Move maintainers-guide.md into the new folder.
• Update the sidebars.js.

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Tickets & Documents

Closes #242

Mobile & Desktop Screenshots/Recordings

Steps to QA

Added to documentation?

• 📜 README.md
• 📓 docs.opensauced.pizza
• 🍕 dev.to/opensauced
• 📕 storybook
• 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[netlify]

👷 Deploy request for docs-open pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	979e8da

[adiati98]

@BekahHW I adjusted some wording, so I need your review for all and please let me know if I need to fix anything. Thank you!

[BekahHW]

@adiati98 what does this mean - Issues outside the good first issue can be assigned max. 2 times per contributor. Suggest they check other repositories for more issues.

[adiati98]

@BekahHW after worked on this, I have these ideas:

• Change the title and sidebar_label in the maintainers-guide.md from "OpenSauced Maintainers Guide" to "Becoming OpenSauced Maintainer". Because most content in this page are information about how to become OpenSauced maintainer.
  

  docs/docs/contributing/maintainers-guide.md

  Lines 3 to 4 in 943d2e4

  	title: "OpenSauced Maintainers Guide"
  	sidebar_label: "OpenSauced Maintainers Guide"

• Remove the "Committing and Merging Changes" section in the maintainers-guide.md because this is not necessary here. It's already covered in the "Community Maintainers Guidelines".
  

  docs/docs/contributing/maintainers-guide.md

  Lines 47 to 52 in 943d2e4

  	## Committing and Merging Changes
  	1. For commit and pull request standards, please refer to the [introduction to contributing](../contributing/introduction-to-contributing.md).
  	2. Before merging in changes, always run the project locally if UI changes were made.
  	3. **Squash and merge commits** when you merge in a PR.

• Looking at the chapters, maybe we can change the title of "Contributing Guide" to "OpenSauced Guide" or "OpenSauced Guidelines"?

  

[BekahHW]

@adiati98 this is good to go once the clarification is made

[adiati98]

@adiati98 what does this mean - Issues outside the good first issue can be assigned max. 2 times per contributor. Suggest they check other repositories for more issues.

@BekahHW Issues that are not good first issue can only be assigned max. 2 times per contributor in the community repos. And we can suggest to other repos for more issues. I refer to your reply here. Or maybe I get it wrong? 😅

[BekahHW]

@adiati98 what does this mean - Issues outside the good first issue can be assigned max. 2 times per contributor. Suggest they check other repositories for more issues.

@BekahHW Issues that are not good first issue can only be assigned max. 2 times per contributor in the community repos. And we can suggest to other repos for more issues. I refer to your reply here. Or maybe I get it wrong? 😅

Ah, ok. People can take on more than two issues but not at a time. So, for example if they have an issue in guestbook and one in intro, they can't have one in pizza-verse.

My biggest concern is that contributors ask to take on issues across repos and don't finish them. I want them to contribute. But I want them to complete them.

So maybe more like:

Issues outside the good first issue can be assigned max. 2 times per contributor at a time. We love contributions, but we want to equip contributors to succeed by giving them time to complete issues. Through experience, we've found that two issues at a time allows them to focus on completing the issue and supports maintainers by not having issues open for long periods of time.

[adiati98]

@adiati98 what does this mean - Issues outside the good first issue can be assigned max. 2 times per contributor. Suggest they check other repositories for more issues.

@BekahHW Issues that are not good first issue can only be assigned max. 2 times per contributor in the community repos. And we can suggest to other repos for more issues. I refer to your reply here. Or maybe I get it wrong? 😅

Ah, ok. People can take on more than two issues but not at a time. So, for example if they have an issue in guestbook and one in intro, they can't have one in pizza-verse.

My biggest concern is that contributors ask to take on issues across repos and don't finish them. I want them to contribute. But I want them to complete them.

So maybe more like:

Issues outside the good first issue can be assigned max. 2 times per contributor at a time. We love contributions, but we want to equip contributors to succeed by giving them time to complete issues. Through experience, we've found that two issues at a time allows them to focus on completing the issue and supports maintainers by not having issues open for long periods of time.

@BekahHW I updated the wording as per your suggestion.

One last thing, should I change the file name as what you mentioned earlier from community-maintainers-guide.md to community-maintainers.md?

Once it confirmed, I can fix it and let you know or you can merge this PR.

[github-actions]

🎉 This PR is included in version 1.63.0 🎉

The release is available on:

• GitHub release
• ghcr.io container (@latest dist-tag)

Your semantic-release bot 📦🚀