doc: initial version of strategic initiatives #399

mhdawson · 2017-10-26T22:27:54Z

I have likely missed some and included some which are not appropriate. But a first cut to trigger discussion

@nodejs/tsc

Related to #390 and #278

mhdawson · 2017-10-26T22:31:39Z

If/when we agree to land this will also add link on README.md

MylesBorins · 2017-10-26T22:39:31Z

The tsc readme or project readme? If the latter should we open a parallel pr?

…

On Oct 26, 2017 6:31 PM, "Michael Dawson" ***@***.***> wrote: If/when we agree to land this will also add link on README.md — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#399 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV_iHGy7ode0HFTMQg0oHKYtOLeZkks5swQhMgaJpZM4QITds> .

vsemozhetbyt · 2017-10-26T22:40:49Z

Strategic-Initiatives.md

+| N-API             | Michael Dawson  | https://github.com/nodejs/abi-stable-node                        |
+| OpenSSL Evolution | Rod Vagg        | https://github.com/nodejs/TSC/issues/364                         |
+| Workers           | Anna Henningson | https://github.com/nodejs/worker                                 |
+| Error Messages    | James Snell     | https://github.com/nodejs/node/issues/11273i                     |


A nit: 11273i -> 11273

vsemozhetbyt · 2017-10-26T22:41:38Z

Strategic-Initiatives.md

+| CVE Management    | Michael Dawson  | https://github.com/nodejs/security-wg/issues/33                  |
+| Core Promise APIs | James Snell     |                                                                  | 
+| TSC Governance    | Myles Borins    | https://github.com/nodejs/TSC/issues/383                         |
+| New Streams APIs  | James Snell     | https://github.com/ nodejs/node#16414                            | 


A nit: https://github.com/ nodejs/node#16414 -> https://github.com/nodejs/node/pull/16414 ?

Space is fixed, but the URL is still wrong?

vsemozhetbyt · 2017-10-26T22:44:24Z

Strategic-Initiatives.md

+if the update is `nothing new`) as a way to ensure they are active
+and have the support needed.
+
+# Current Intiatives


A nit: Intiatives -> Initiatives

vsemozhetbyt · 2017-10-26T22:45:16Z

Strategic-Initiatives.md

+| Core Promise APIs | James Snell     |                                                                  | 
+| TSC Governance    | Myles Borins    | https://github.com/nodejs/TSC/issues/383                         |
+| New Streams APIs  | James Snell     | https://github.com/ nodejs/node#16414                            | 
+| Diagnotics        | Michael Dawson  | Happy to have other volunteers but will work to restart          |


A nit: Diagnotics -> Diagnostics

mscdex · 2017-10-27T00:17:25Z

Strategic-Initiatives.md

+# Strategic Initiatives
+
+At any one time the Node.js project has a number of strategic initiatives
+underway.  The goal of the TSC is to have a `champion` for each of these


Minor nit: I think we should avoid using backticks for things that aren't (code) keywords. Perhaps use italics, bold, or quotes instead (here and elsewhere in this document).

....Or use nothing. The word champion does not need the scare quotes here or any other typographic addition.

Ok changed to remove backticks.

Trott · 2017-10-27T06:13:36Z

Strategic-Initiatives.md

+| Diagnotics        | Michael Dawson  | Happy to have other volunteers but will work to restart          |
+| Moderation        | Rich Trot       |                                                                  |
+| Async Hooks       | Trevor Norris   |                                                                  |
+| V8 Currency       | MichaëZasso    |                                                                  |


Michaël Zasso

Will try, the special characters always mess me up.

Trott · 2017-10-27T06:15:21Z

I don't know if they're strategic, but if so, you can put me down for collaborator onboarding and new contributor onramp.

Trott · 2017-10-27T06:15:45Z

Joyee for automation? Rod for build/CI?

joyeecheung · 2017-10-27T06:27:42Z

@Trott

Joyee for automation? Rod for build/CI?

Sure!

| Automation       | Joyee Cheung   |  https://github.com/nodejs/automation   |

mhdawson · 2017-10-27T15:46:11Z

In terms of build/automation I was not quite sure whether we should add areas covered by Working Groups. I'm happy to add those as well if people think that makes sense. Would include Build, Benchmarking, Release etc...

mhdawson · 2017-10-27T15:47:48Z

@MylesBorins I agree adding to node core readme probably also makes sense for visibility. I'll submit a PR to do that as well once this one lands.

mhdawson · 2017-10-27T16:11:52Z

@Trott any chance you can push a commit to fix M Zasso's name. I tried my usual tricks of copying from other docs but did not work...

mhdawson · 2017-10-27T16:12:16Z

Went ahead an added the WG's as well so people can see how it looks

mhdawson · 2017-10-27T16:12:52Z

@vsemozhetbyt @mscdex @Trott pushed commits to address comments.

mhdawson · 2017-10-27T16:16:42Z

@MylesBorins added commit to add reference in README.md for TSC. Once this lands will open PR to do the same in the core node repo.

MylesBorins · 2017-10-31T04:06:50Z

Great work on this @mhdawson

I'd like to suggest that we keep the scope of initiatives to projects as opposed to working groups themselves. For example, James' work on a new lower level streams implementation is a much tighter scope than streams wg.

I would also like to suggest that we keep the number of initiatives that we are working on small and encourage individuals to add their initiatives. If people are not openly taking responsibility for an initiative in this thread it likely should not be included.

There are likely opportunities for the champion to not be a member of the TSC, we might want to account for that. A redesign of the nodejs.org website may be an example of that.

I've marked this for the agenda, we should discuss it on Wednesday

mhdawson · 2017-10-31T14:10:35Z

I'm in agreement that it is best to omit WG's for now. Will remove and we can disuss further in the meeting

mhdawson · 2017-11-08T14:57:53Z

I'd proposed that people suggest what they think the list should be (or specific additions/removals from the list above). In the absence of any other concrete suggestions we could just start with the current list so that we don't stall out for too long as there has not been much discussion over the last week (I do know people have been busy though)

Fishrock123 · 2017-11-08T16:34:55Z

I would suggest swapping @jasnell on the Streams API work for myself. He's already got a lot of things to champion and I both don't mind taking this one and have kinda been doing that role to begin with-ish?

Fishrock123 · 2017-11-14T22:58:59Z

Well?

fhinkel · 2017-11-15T19:49:48Z

Strategic-Initiatives.md

+| CVE Management    | Michael Dawson  | https://github.com/nodejs/security-wg/issues/33                  |
+| Core Promise APIs | James Snell     |                                                                  | 
+| TSC Governance    | Myles Borins    | https://github.com/nodejs/TSC/issues/383                         |
+| New Streams APIs  | James Snell     | https://github.com/nodejs/node/pull/16414                        | 


I think this should be @Fishrock123 instead of @jasnell?

@Fishrock123 and @jasnell ... we're both working two different sides of this.

fhinkel · 2017-11-15T19:51:11Z

LGTM with the change for Streams API.

Should this doc include a list of past initiatives? If so, I'd like to add myself for fixing the vm module 😊

MylesBorins · 2017-11-15T20:08:55Z

I think we should drop diagnostics + automation. If there are specific initiatives within those groups (such as a commit queue or specific diagnostics efforts) those would make sense to include

Collab onboarding + collab on ramp seem like a single initiative to me, thoughts @Trott

Trott · 2017-11-15T21:17:56Z

Collab onboarding + collab on ramp seem like a single initiative to me, thoughts @Trott

Sure. We can always split them up later if we need to.

Fishrock123 · 2017-11-15T22:18:23Z

Removing from the agenda as there is no progress to discuss.

Fishrock123 · 2017-11-15T23:04:34Z

Fwiw, we went over these live and got updates on each in the TSC meeting for #418 which can be found in the last half of https://youtu.be/eSgqJg7pu_M

mhdawson · 2017-11-16T20:25:03Z

Pushed update to address comments. @fhinkel can you give me a link to add for the vm link.

@Fishrock123 can you give me a link to add for the streams 2? From what I can tell from the discussion they are really 2 different initiatives so listing them separately is what I was thinking makes sense.

Once I get those 2 I'll land and we can iterate as we move forward.

fhinkel · 2017-11-17T10:14:07Z

@mhdawson Here's the link to the commit that fixed most of the vm issues: #399

Can you add a current initiative, please:
Initiative: C++ smart pointers
Champion: Franziska Hinkelmann
Links: https://github.com/nodejs/node/blob/master/CPP_STYLE_GUIDE.md#ownership-and-smart-pointers

jasnell · 2017-11-17T15:16:40Z

@mhdawson ... re: streams, they are not two different initiatives... there are just two sides to one initiative.. that is, reworking streams on both the C++ and JS side.

mhdawson · 2017-11-17T18:47:09Z

@fhinkel the the first link seems to be for this PR as opposed to the vm issues.

mhdawson · 2017-11-17T18:48:10Z

@fhinkel is the initiative to move to using smart pointers or something else ?

mhdawson · 2017-11-17T18:52:21Z

@fhinkel I hope you don't mind but I'm going to go ahead and land, can you submit a Pr to add the new initiative and add the missing link for the past vm initiative ? Alternatively if you send me that info I can open a new PR to update for that.

PR-URL: #399 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>

mhdawson · 2017-11-17T18:56:14Z

Landed as cf87134

mhdawson · 2017-11-17T18:58:02Z

See I missed removing one line, opening a PR to fix.

mhdawson added 2 commits October 26, 2017 18:25

doc: initial version of strategic initiatives

0cc1d5e

squash: misc fixup

72c4db6

jasnell approved these changes Oct 26, 2017

View reviewed changes

squash: misc fixup

44db0fc

vsemozhetbyt reviewed Oct 26, 2017

View reviewed changes

mscdex reviewed Oct 27, 2017

View reviewed changes

Trott reviewed Oct 27, 2017

View reviewed changes

squash: address comments

542a0ce

vsemozhetbyt approved these changes Oct 27, 2017

View reviewed changes

squash: address comments

f188e02

squash: look at me updating in GitHub's interface!

7ef00af

mhdawson mentioned this pull request Oct 30, 2017

Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-11-01 #402

Closed

MylesBorins mentioned this pull request Oct 31, 2017

Reintroduce standup for initiatives #403

Closed

MylesBorins added the tsc-agenda label Oct 31, 2017

squash: address comments

2b49065

mhdawson mentioned this pull request Nov 8, 2017

Volunteers to run TSC meeting Nov 8 and 15 #409

Closed

Trott mentioned this pull request Nov 8, 2017

Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-11-08 #413

Closed

Trott mentioned this pull request Nov 14, 2017

Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-11-15 #418

Closed

fhinkel approved these changes Nov 15, 2017

View reviewed changes

fhinkel reviewed Nov 15, 2017

View reviewed changes

Fishrock123 removed the tsc-agenda label Nov 15, 2017

squash: address comments

6808b2d

squash: address comments

82a2596

mhdawson closed this Nov 17, 2017

mhdawson deleted the initiatives branch August 14, 2019 17:00

doc: initial version of strategic initiatives #399

doc: initial version of strategic initiatives #399

Conversation

mhdawson commented Oct 26, 2017

mhdawson commented Oct 26, 2017

MylesBorins commented Oct 26, 2017 via email

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Trott Oct 27, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Trott commented Oct 27, 2017

Trott commented Oct 27, 2017

joyeecheung commented Oct 27, 2017

mhdawson commented Oct 27, 2017

mhdawson commented Oct 27, 2017

mhdawson commented Oct 27, 2017

mhdawson commented Oct 27, 2017

mhdawson commented Oct 27, 2017

mhdawson commented Oct 27, 2017

MylesBorins commented Oct 31, 2017

mhdawson commented Oct 31, 2017

mhdawson commented Nov 8, 2017

Fishrock123 commented Nov 8, 2017

Fishrock123 commented Nov 14, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

fhinkel commented Nov 15, 2017

MylesBorins commented Nov 15, 2017

Trott commented Nov 15, 2017

Fishrock123 commented Nov 15, 2017

Fishrock123 commented Nov 15, 2017

mhdawson commented Nov 16, 2017

fhinkel commented Nov 17, 2017

jasnell commented Nov 17, 2017

mhdawson commented Nov 17, 2017

mhdawson commented Nov 17, 2017

mhdawson commented Nov 17, 2017

mhdawson commented Nov 17, 2017

mhdawson commented Nov 17, 2017

Trott Oct 27, 2017 •

edited

Loading