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

chore : Added code of conduct and contribution guidelines #6

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Ayush7614
Copy link

This PR Contains
Fix #5
Added Contribution Guidelines
Added Code of Conduct

@Ayush7614
Copy link
Author

cc @RomanHotsiy

@ivana-isadora
Copy link

Thank you for this contribution, @Ayush7614!

There are a few issues with it, though. Contributing guidelines and code of conduct for this project should align with existing guidelines and CoC in other Redocly OSS projects. We should not use an entirely different CoC just for this project, because Redocly already has an official CoC that all its OSS projects should follow.

Additionally, there's a lot of phrasing in existing contributing guidelines that can be reused for this project to make its style more consistent with the rest.

I suggest you take a look at these resources from other Redocly OSS projects and adjust your PR accordingly:

If you have any questions, let us know.

@Ayush7614
Copy link
Author

Thank you for this contribution, @Ayush7614!

There are a few issues with it, though. Contributing guidelines and code of conduct for this project should align with existing guidelines and CoC in other Redocly OSS projects. We should not use an entirely different CoC just for this project, because Redocly already has an official CoC that all its OSS projects should follow.

Additionally, there's a lot of phrasing in existing contributing guidelines that can be reused for this project to make its style more consistent with the rest.

I suggest you take a look at these resources from other Redocly OSS projects and adjust your PR accordingly:

If you have any questions, let us know.

Done @skadinna

@ivana-isadora
Copy link

Great! 🥳 Thank you so much, @Ayush7614 💪

Let's have @RomanHotsiy and/or @adamaltman look at your PR too, and then we can merge once they've approved it.

@Ayush7614
Copy link
Author

cc @adamaltman @RomanHotsiy

@Ayush7614
Copy link
Author

Great! 🥳 Thank you so much, @Ayush7614 💪

Let's have @RomanHotsiy and/or @adamaltman look at your PR too, and then we can merge once they've approved it.

@skadinna any channnel for communication like slack, discord or gitter any one where i have project ideas and also discuss project for google season of docs 22?

@ivana-isadora
Copy link

@skadinna any channnel for communication like slack, discord or gitter any one where i have project ideas and also discuss project for google season of docs 22?

We're waiting to see if Google will approve our application for Season of Docs 2022. The list of accepted organizations will be published next week, and we'll start reaching out to interested candidates after that. If you have a proposal you'd like us to consider, send an email to [email protected]

You can find some useful advice on how to put together a proposal here: https://developers.google.com/season-of-docs/docs/tech-writer-statement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Added Contribution and Contributing Guidelines
3 participants