doc: add initial version of values and prios doc #11
Update VALUES_AND_PRIORITIZAION.md
Co-authored-by: Christopher Hiller <[email protected]>
- Loading branch information
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -30,7 +30,7 @@ We value ensuring that developers are productive and enjoy developing with Node. | |||||
| - Enabling/supporting external packages to ensure overall developer experience | ||||||
|
|
||||||
| ### Stability | ||||||
| To avoid introducing churn into Node.js' ecosystem, we value stability and consistency across releases and avoid breaking changes. Some key elements of this include: | ||||||
| - Backwards compatibility | ||||||
| - Predictable and stable releases | ||||||
| - A strong safety net (testing etc.) | ||||||
|
||||||
| - A strong safety net (testing etc.) | |
| - A strong safety net--explicitly testing how changes in Node.js affect userland packages |
Member
Author
There was a problem hiding this comment.
@boneskull how about
A strong safety net, including explicitly testing how changes in Node.js affect userland packages.
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.
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.
It's kind of unclear what is meant by this
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.
What we were trying to say was that developer experience for the Node.js ecosystem is not only about the APIs provided directly by Node.js itself but also those provided by external packages as well. In that context it is important to provide APIs, or whatever else is needed to support external packages in helping the overall developer experience.
Any suggestions on how to better capture that that they short version we had?
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.
maybe something like "Enable better developer experiences in packages and applications built upon Node.js"?