-
Notifications
You must be signed in to change notification settings - Fork 4
Initial set up #1
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
Conversation
The "Check Markdown" workflow failure is expected:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me. 👍
352bfb1
to
09aee79
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that all the content in this readme is pretty clean and clear
I left only a suggestion to explain better that the contributor has several options to contribute to our projects, depending on the level of impact and involvement required.
a19e3fb
to
69b0e0b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@per1234 I added a couple of comments to clarify that an issue is always needed before starting an RFC. I added a section called "Implementation" to describe what happens after an RFC is approved.
As usual, you can adjust the wording as you prefer 👍
Add CI and documentation.
Notable elements: