-
Notifications
You must be signed in to change notification settings - Fork 49
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
Some criteria based on rough consensus #157
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.
Just many nits; I follow and agree with the overall lines.
I'd like to suggest that technical objections to the criteria should be taken up in the referenced issues in order to better preserve the rationale in context of how they came through. |
Important formatting question: can we make sure we line-break at 80 chars, which is best practice for GitHub-hosted source code and specs? Having essentially "one line per paragraph" leads to way too many UI problems in reviewing. |
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.
My nits have been addressed.
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.
👍
Commits include some of the criteria from the issues based on rough consensus. Topics vary but some emphasis on "resource access".
The request for review is to confirm what's captured here is accurate ie. the raw criteria. Text needs to be revised and re-organised in the spec but that is intended to be addressed in a future PR.
Edit: I'd like to suggest that technical objections to the criteria should be taken up in the referenced issues in order to better preserve the rationale in context of how they came through.