-
Notifications
You must be signed in to change notification settings - Fork 4
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
Final part of #230: clarity + the flow of information #265
Conversation
Clean up the flow of information from README → CONTRIBUTING → doc/developers. * Remove repetition of information particularly in developers docs. * Simplify the language in README (with assistance from ChatGPT!) * Move some of the guidelines in CONTRIBUTING into templates for PRs, bug reports and feature requests and then just reference the templates. * Other grammar and consistency tweaks.
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.
One actual consideration re:MATLAB + Doxygen; the rest are grammar things (although my grammar is terrible so you're welcome to reject them).
Tweaks, clarity, and avoid repeating words and clarity. Co-authored-by: Will Graham <[email protected]>
about: Create a report to help us improve | ||
title: '' | ||
labels: 'bug' | ||
assignees: '' |
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.
So also to note: we could add a default assignee here. I opted not to because I get notifications for all activity (so critical bugs shouldn't go under the radar).
We can set this up for Peter at handover too.
Cleans up the flow of information between...
README → CONTRIBUTING → doc/developers.
And simplify README (which is also the new landing page home since #231).
Dependencies
Changes:
reports and feature requests and then just reference the templates.
Reviewer notes
Picky comments about clarity are very welcome.
Presumably, some of the changes in the chain of #236 .. #262 will mean bits of this become obsolete. But I try to document how things are on the current
main
.