new draft of Voluntary to Implement explicit principle #227
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is another attempt at a minimum addition in the same "voice" as our other principles to satisfy what appears to be a rough "can live with" consensus overlap in opinions in issue #177, re-using wording from Open-Stand as noted in comment #177 (comment) without objection.
cwilso
approved these changes
Jan 10, 2025
fantasai
reviewed
Jan 10, 2025
Vision/Vision.bs
Outdated
| @@ -158,6 +158,9 @@ Markup Shorthands: markdown yes | |||
| <li id=free-impl> | |||
| **Free to Implement**: Our standards are rooted in a strong royalty-free patent policy | |||
| and open copyright licenses. | |||
| <li id=voluntary-impl> | |||
| **Voluntary to Implement**: Our standards span many use-cases and diverse industries, | |||
| are thus developed to be voluntarily adopted, and success is determined by the market. | |||
There was a problem hiding this comment.
Suggested change
| are thus developed to be voluntarily adopted, and success is determined by the market. | |
| are thus developed to be voluntarily adopted, | |
| with their success determined by the market. |
There was a problem hiding this comment.
I added the line break but disagree with wordsmithing the text as you suggested, text which I copied from open-stand .
fantasai
reviewed
Jan 10, 2025
Vision/Vision.bs
Outdated
Comment on lines
162
to
163
| **Voluntary to Implement**: Our standards span many use-cases and diverse industries, | ||
| are thus developed to be voluntarily adopted, and success is determined by the market. |
There was a problem hiding this comment.
I'm not following the logic of the "and thus", it feels like a non-sequitur... maybe you can explain a bit better?
There was a problem hiding this comment.
different use-cases and industries have different needs (or lack thereof) for different standards, thus it makes logical sense to make them all voluntary to allow adoption as needed by use-cases. that's obvious enough that it doesn't merit growing the text. or others may create lengthier guides that expand upon the principles
mgendler
approved these changes
Jan 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is another attempt at a minimum addition in the same "voice" as our other principles to satisfy what appears to be a rough "can live with" consensus overlap in opinions in issue #177, re-using wording from Open-Stand as noted in comment #177 (comment) without objection.