GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — doc: add technical values document by mhdawson · Pull Request #35145 · nodejs/node

Conversation

@mhdawson

@mhdawson mhdawson commented Sep 10, 2020

Copy link
Copy Markdown
Member

As part of the next-10 we found
we needed to capture the project's technical values/priorities as
a starting point before discussing key technologies/areas for the
next 10 years of Node.js

This is a first cut that the team put together. The discussion
took place in a few meetings as well as this
PR. We believe the doc
should live in the core node repository as it is intended to
reflect the agreement of the collaborator base.

I think this is a good starting point but we also
acknowledge that only a small subset of the Node.js collaborators
have participated/commented so far. This PR should be a good
way to get additional review/input from the larger set
of Node.js collaborators.

Signed-off-by: Michael Dawson [email protected]

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

bricss and puzpuzpuz reacted with thumbs up emoji
All reactions
  • 👍 2 reactions
@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to Node.js documentation. label Sep 10, 2020
@mhdawson mhdawson added the tsc-agenda Issues and PRs to discuss during Technical Steering Committee meetings. label Sep 10, 2020
gittysachin
gittysachin reviewed Sep 10, 2020
View reviewed changes

@gittysachin gittysachin left a comment

Copy link
Copy Markdown

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.

Would be great to have the technical values/prioritization document before the key discussion about new technology implementation or any area of future Node.js

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@mhdawson

mhdawson commented Sep 10, 2020

Copy link
Copy Markdown
Member Author

@gittysachin that was what we ended up thinking based on the discussion in the next-10 team and what led to the creation of this initial version of that.

gittysachin reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mmarchini

mmarchini commented Sep 10, 2020

Copy link
Copy Markdown
Contributor

this feels like one of those times where @nodejs/collaborators is appropriate

mhdawson reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

boneskull
boneskull approved these changes Sep 10, 2020
View reviewed changes
trivikr
trivikr approved these changes Sep 10, 2020
View reviewed changes
lholmquist
lholmquist approved these changes Sep 10, 2020
View reviewed changes
richardlau
richardlau approved these changes Sep 10, 2020
View reviewed changes
BethGriggs
BethGriggs approved these changes Sep 10, 2020
View reviewed changes
antsmartian
antsmartian approved these changes Sep 10, 2020
View reviewed changes
watilde
watilde approved these changes Sep 11, 2020
View reviewed changes
Qard
Qard approved these changes Sep 11, 2020
View reviewed changes
ruyadorno
ruyadorno approved these changes Sep 11, 2020
View reviewed changes
Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

devsnek
devsnek reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

@Trott

Trott commented Sep 11, 2020

Copy link
Copy Markdown
Member

I think we should be exceptionally stingy with the root-level all-caps file and would prefer this go in doc/guides/technical-values.md or similar.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

puzpuzpuz
puzpuzpuz approved these changes Sep 11, 2020
View reviewed changes
Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Trott
Trott reviewed Sep 11, 2020
View reviewed changes
Comment thread TECHNICAL_VALUES_AND_PRIORITIZATION.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

@mhdawson

mhdawson commented Sep 14, 2020

Copy link
Copy Markdown
Member Author

@Trott I think I'm ok with it being in guides since it does have a visible path through the README.md

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Qard
Qard approved these changes Sep 14, 2020
View reviewed changes
@GeoffreyBooth

GeoffreyBooth commented Sep 15, 2020

Copy link
Copy Markdown
Member

Two thoughts:

  1. What is “API currency”?

  2. I see and appreciate the reference to Web APIs. I’m not sure if we need to say anything more, but I think perhaps the biggest driver of Node’s popularity has been the fact that it’s a JavaScript runtime and there’s tremendous value in having code that can run in both browsers and on the server, or at least that apps can share the same language between client and server. I think maintaining compatibility with the browser environments as much as possible is an important technical value to maintain.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

joyeecheung
joyeecheung approved these changes Sep 15, 2020
View reviewed changes
rexagod
rexagod approved these changes Sep 15, 2020
View reviewed changes
@mhdawson mhdawson mentioned this pull request Sep 17, 2020
Prioritizing Technical Values nodejs/next-10#5
Closed
mhdawson
mhdawson commented Sep 17, 2020
View reviewed changes
Comment thread doc/guides/technical-values.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

@mhdawson
Update doc/guides/technical-values.md
3bc5746
mhdawson
mhdawson commented Sep 17, 2020
View reviewed changes
Comment thread doc/guides/technical-values.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

@mhdawson
Update doc/guides/technical-values.md
5cdf202
@mhdawson mhdawson added the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Sep 17, 2020
@mhdawson

mhdawson commented Sep 17, 2020 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member Author

@GeoffreyBooth updated to use clearer wording for "currency",

In terms of:

I see and appreciate the reference to Web APIs. I’m not sure if we need to say anything more, but I think perhaps the biggest driver of Node’s popularity has been the fact that it’s a JavaScript runtime and there’s tremendous value in having code that can run in both browsers and on the server, or at least that apps can share the same language between client and server. I think maintaining compatibility with the browser environments as much as possible is an important technical value to maintain.

I think we discussed that in the next-10 meetings and stopped short of mentioning that specifically. Since you mentioned as "thoughts" as opposed to an objection I'm going to land the current text and maybe you can PR in a suggested addition that covers that and we can use the PR to discuss.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mhdawson

mhdawson commented Sep 17, 2020

Copy link
Copy Markdown
Member Author

As doc only I guess I did not need to request the CI, linters seem to have complete so I think I'm good to land.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@github-actions github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Sep 17, 2020
@nodejs-github-bot

nodejs-github-bot commented Sep 17, 2020

Copy link
Copy Markdown
Collaborator

CI: https://ci.nodejs.org/job/node-test-pull-request/33157/

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

mhdawson added a commit that referenced this pull request Sep 17, 2020
@mhdawson
doc: add technical values document
fe293e9
As part of the [next-10](https://github.com/nodejs/next-10) we found
we needed to capture the project's technical values/priorities as
a starting point before discussing key technologies/areas for the
next 10 years of Node.js

This is a first cut that the team put together. The discussion
took place in a few meetings as well as this
[PR](nodejs/next-10#11). We believe the doc
should live in the core node repository as it is intended to
reflect the agreement of the collaborator base.

I think this is a good starting point but we also
acknowledge that only a small subset of the Node.js collaborators
have participated/commented so far. This PR should be a good
way to get additional review/input from the larger set
of Node.js collaborators.

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: #35145
Reviewed-By: Christopher Hiller <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Beth Griggs <[email protected]>
Reviewed-By: Anto Aravinth <[email protected]>
Reviewed-By: Daijiro Wachi <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Ruy Adorno <[email protected]>
Reviewed-By: Andrey Pechkurov <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Ash Cripps <[email protected]>
Reviewed-By: Ben Coe <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Pranshu Srivastava <[email protected]>
@mhdawson

mhdawson commented Sep 17, 2020

Copy link
Copy Markdown
Member Author

Landed in fe293e9

Going to leave open until we hear back with @GeoffreyBooth that he's ok with my suggested approach to his comment on browser compatibility in case I need to take some other action.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mhdawson mhdawson mentioned this pull request Sep 17, 2020
Values/directions document for core nodejs/next-10#2
Closed
@GeoffreyBooth

GeoffreyBooth commented Sep 17, 2020

Copy link
Copy Markdown
Member

Landed in fe293e9

Going to leave open until we hear back with @GeoffreyBooth that he’s ok with my suggested approach to his comment on browser compatibility in case I need to take some other action.

Yes, it’s not an objection, just a suggestion. Was there a reason it was left out when you discussed it in those meetings?

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mhdawson

mhdawson commented Sep 18, 2020

Copy link
Copy Markdown
Member Author

@GeoffreyBooth If I remember correctly it came down being related to your comment I’m not sure if we need to say anything more and that there is not necessarily agreement across the project that compatibility with the browser environments is always the right path so we just left it at what was there.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mhdawson mhdawson mentioned this pull request Sep 21, 2020
Node.js Technical Steering Committee (TSC) Meeting 2020-09-24 nodejs/TSC#929
Closed
ruyadorno pushed a commit that referenced this pull request Sep 21, 2020
@mhdawson @ruyadorno
doc: add technical values document
92a14d3
As part of the [next-10](https://github.com/nodejs/next-10) we found
we needed to capture the project's technical values/priorities as
a starting point before discussing key technologies/areas for the
next 10 years of Node.js

This is a first cut that the team put together. The discussion
took place in a few meetings as well as this
[PR](nodejs/next-10#11). We believe the doc
should live in the core node repository as it is intended to
reflect the agreement of the collaborator base.

I think this is a good starting point but we also
acknowledge that only a small subset of the Node.js collaborators
have participated/commented so far. This PR should be a good
way to get additional review/input from the larger set
of Node.js collaborators.

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: #35145
Reviewed-By: Christopher Hiller <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Beth Griggs <[email protected]>
Reviewed-By: Anto Aravinth <[email protected]>
Reviewed-By: Daijiro Wachi <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Ruy Adorno <[email protected]>
Reviewed-By: Andrey Pechkurov <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Ash Cripps <[email protected]>
Reviewed-By: Ben Coe <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Pranshu Srivastava <[email protected]>
@ruyadorno ruyadorno mentioned this pull request Sep 21, 2020
V14.12.0 proposal #35285
Merged
4 tasks done
@mhdawson

mhdawson commented Sep 21, 2020

Copy link
Copy Markdown
Member Author

Going to close, @GeoffreyBooth just let me know if I should do anything else to follow up on your comments.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@mhdawson mhdawson closed this Sep 21, 2020
addaleax pushed a commit that referenced this pull request Sep 22, 2020
@mhdawson @addaleax
doc: add technical values document
d81db1d
As part of the [next-10](https://github.com/nodejs/next-10) we found
we needed to capture the project's technical values/priorities as
a starting point before discussing key technologies/areas for the
next 10 years of Node.js

This is a first cut that the team put together. The discussion
took place in a few meetings as well as this
[PR](nodejs/next-10#11). We believe the doc
should live in the core node repository as it is intended to
reflect the agreement of the collaborator base.

I think this is a good starting point but we also
acknowledge that only a small subset of the Node.js collaborators
have participated/commented so far. This PR should be a good
way to get additional review/input from the larger set
of Node.js collaborators.

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: #35145
Reviewed-By: Christopher Hiller <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Beth Griggs <[email protected]>
Reviewed-By: Anto Aravinth <[email protected]>
Reviewed-By: Daijiro Wachi <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Ruy Adorno <[email protected]>
Reviewed-By: Andrey Pechkurov <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Ash Cripps <[email protected]>
Reviewed-By: Ben Coe <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Pranshu Srivastava <[email protected]>
@GeoffreyBooth GeoffreyBooth mentioned this pull request Sep 23, 2020
doc: add compatibility/interop technical value #35323
Closed
2 tasks done
@codebytere codebytere mentioned this pull request Sep 28, 2020
v12.19.0 proposal #35401
Merged
joesepi pushed a commit to joesepi/node that referenced this pull request Jan 8, 2021
@mhdawson @joesepi
doc: add technical values document
85d4a7d
As part of the [next-10](https://github.com/nodejs/next-10) we found
we needed to capture the project's technical values/priorities as
a starting point before discussing key technologies/areas for the
next 10 years of Node.js

This is a first cut that the team put together. The discussion
took place in a few meetings as well as this
[PR](nodejs/next-10#11). We believe the doc
should live in the core node repository as it is intended to
reflect the agreement of the collaborator base.

I think this is a good starting point but we also
acknowledge that only a small subset of the Node.js collaborators
have participated/commented so far. This PR should be a good
way to get additional review/input from the larger set
of Node.js collaborators.

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: nodejs#35145
Reviewed-By: Christopher Hiller <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Beth Griggs <[email protected]>
Reviewed-By: Anto Aravinth <[email protected]>
Reviewed-By: Daijiro Wachi <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Ruy Adorno <[email protected]>
Reviewed-By: Andrey Pechkurov <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Ash Cripps <[email protected]>
Reviewed-By: Ben Coe <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Pranshu Srivastava <[email protected]>
@mscdex mscdex mentioned this pull request Sep 27, 2021
doc: add initial list of technical priorities #40235
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Trott Trott Trott approved these changes
@joyeecheung joyeecheung joyeecheung approved these changes
@trivikr trivikr trivikr approved these changes
@BethGriggs BethGriggs BethGriggs approved these changes
@gireeshpunathil gireeshpunathil gireeshpunathil approved these changes
@richardlau richardlau richardlau approved these changes
@tniessen tniessen tniessen approved these changes
@watilde watilde watilde approved these changes
@ruyadorno ruyadorno ruyadorno approved these changes
@Qard Qard Qard approved these changes
+9 more reviewers
@gittysachin gittysachin gittysachin left review comments
@devsnek devsnek devsnek left review comments
@puzpuzpuz puzpuzpuz puzpuzpuz approved these changes
@rexagod rexagod rexagod approved these changes
@AshCripps AshCripps AshCripps approved these changes
@bcoe bcoe bcoe approved these changes
@antsmartian antsmartian antsmartian approved these changes
@lholmquist lholmquist lholmquist approved these changes
@boneskull boneskull boneskull approved these changes
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

doc Issues and PRs related to Node.js documentation. tsc-agenda Issues and PRs to discuss during Technical Steering Committee meetings.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

19 participants

@mhdawson @mmarchini @Trott @GeoffreyBooth @nodejs-github-bot @bcoe @Qard @ruyadorno @boneskull @lholmquist @antsmartian @watilde @tniessen @joyeecheung @richardlau @devsnek @gireeshpunathil @BethGriggs @trivikr
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.