Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Add OpenSauced Community Maintainers Guidelines #242

Closed
2 of 6 tasks
adiati98 opened this issue Feb 1, 2024 · 3 comments · Fixed by #243 or #245
Closed
2 of 6 tasks

Docs: Add OpenSauced Community Maintainers Guidelines #242

adiati98 opened this issue Feb 1, 2024 · 3 comments · Fixed by #243 or #245
Assignees
Labels
📝 documentation 💡 feature A label to note if work is a feature released

Comments

@adiati98
Copy link
Member

adiati98 commented Feb 1, 2024

Type of feature

🍕 Feature

Current behavior

We have an "OpenSauced Maintainers Guide" containing information for people interested in becoming maintainers. But we also need guidelines about the expectations and responsibilities of maintainers, particularly Community Maintainers, to be on the same page in maintaining the repositories.

Suggested solution

Add an "OpenSauced Community Maintainers Guidelines" with details 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.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributing Docs

  • I agree to follow this project's Contribution Docs
@adiati98 adiati98 added 💡 feature A label to note if work is a feature 📝 documentation labels Feb 1, 2024
@adiati98 adiati98 self-assigned this Feb 1, 2024
@adiati98
Copy link
Member Author

adiati98 commented Feb 1, 2024

@BekahHW does the suggested solution here align with our discussion?

Copy link
Contributor

github-actions bot commented Feb 3, 2024

🎉 This issue has been resolved in version 1.63.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link
Contributor

github-actions bot commented Feb 5, 2024

🎉 This issue has been resolved in version 1.63.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📝 documentation 💡 feature A label to note if work is a feature released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant