Skip to content
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

doc: linkify names in strategic initiatives #445

Merged
merged 1 commit into from
Feb 13, 2018

Conversation

MylesBorins
Copy link
Contributor

Refs: #442

MylesBorins added a commit to MylesBorins/TSC that referenced this pull request Dec 15, 2017
This build on top of nodejs#445 and restructures how we layout strategic
initiatives. By breaking it out of a table we will be able to include
much more details.

One of the added details here is the inclusion of stakeholders,
individuals outside of the champion who are actively involved in
an initiative. I have only added these for `Modules` at this time
but we should like expand this before landing.

The hope is that this will improve communication and discoverability
as well as offer a new opportunity to recognize significant work.

Refs: nodejs#442
@MylesBorins MylesBorins mentioned this pull request Dec 15, 2017
MylesBorins added a commit to MylesBorins/TSC that referenced this pull request Dec 15, 2017
This build on top of nodejs#445 and restructures how we layout strategic
initiatives. By breaking it out of a table we will be able to include
much more details.

One of the added details here is the inclusion of stakeholders,
individuals outside of the champion who are actively involved in
an initiative. I have only added these for `Modules` at this time
but we should like expand this before landing.

The hope is that this will improve communication and discoverability
as well as offer a new opportunity to recognize significant work.

Refs: nodejs#442
MylesBorins added a commit to MylesBorins/TSC that referenced this pull request Dec 15, 2017
This build on top of nodejs#445 and restructures how we layout strategic
initiatives. By breaking it out of a table we will be able to include
much more details.

One of the added details here is the inclusion of stakeholders,
individuals outside of the champion who are actively involved in
an initiative. I have only added these for `Modules` at this time
but we should like expand this before landing.

The hope is that this will improve communication and discoverability
as well as offer a new opportunity to recognize significant work.

Refs: nodejs#442
| V8 Currency | Michaël Zasso | |
| Initiative | Champion | Links |
|-------------------|-----------------------------------------------------------|------------------------------------------------------------------|
| http2 | [James Snell][jasnell] | |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add the handle to the text as well in case people are looking for handles to mention? Like James Snell ([@jasnell][])

Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mhdawson
Copy link
Member

mhdawson commented Feb 8, 2018

@MylesBorins this needs a rebase and then I think it can land.

@MylesBorins MylesBorins merged commit a942ad6 into nodejs:master Feb 13, 2018
MylesBorins added a commit to MylesBorins/TSC that referenced this pull request Feb 13, 2018
This build on top of nodejs#445 and restructures how we layout strategic
initiatives. By breaking it out of a table we will be able to include
much more details.

One of the added details here is the inclusion of stakeholders,
individuals outside of the champion who are actively involved in
an initiative. I have only added these for `Modules` at this time
but we should like expand this before landing.

The hope is that this will improve communication and discoverability
as well as offer a new opportunity to recognize significant work.

Refs: nodejs#442
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants