-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
Improving our contributions document #91
Conversation
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 agree with #90 (comment) in that using details is quite bad. Especially the usage of details here is not to provide details but to make headers/sorting. That can be done with exactly that, headers. I assume GitHub supports an index at the top as well? If not, maybe this document could fit in the docs pages.
Thanks for all of your comments. Combining this feedback with much more of my lived experience working on the 0.2 docs, I've completely redone this document. Let me know if any issues persist here. I'm trying to get the reading time for contributors down. |
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.
Overall quite a good rewrite, just got some smaller notes on specific items.
The security-sensitive issue section has disappeared now, though. I think it's worth keeping that in.
See #90 - this PR is all about making our contribution document easier to understand!