doc: add minutes for meeting 16 jan #271
Merged
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
mmarchini
approved these changes
Jan 17, 2019
richardlau
approved these changes
Jan 18, 2019
meetings-other/2019-01-16.md
Outdated
|
|
||
| ## Announcements | ||
|
|
||
| * No accouncements this week. |
There was a problem hiding this comment.
Suggested change
| * No accouncements this week. | |
| * No announcements this week. |
meetings-other/2019-01-16.md
Outdated
| * Diagnostics Best Practices Guide content definition meeting [#254](https://github.com/nodejs/diagnostics/issues/254) | ||
|
|
||
| * Baseline issue to discuss “Best practices” - https://github.com/nodejs/diagnostics/issues/211 | ||
| * First question is how we structure the Best parctices guide. |
There was a problem hiding this comment.
Suggested change
| * First question is how we structure the Best parctices guide. | |
| * First question is how we structure the Best practices guide? |
meetings-other/2019-01-16.md
Outdated
| * Gireesh, one issue is that there may be a lot of deployment variations so hard to | ||
| start there. On the other hand production deployments will still need the steps to get | ||
| There. | ||
| * Michael, starting with symptom provides common basis that can be used to build base content |
There was a problem hiding this comment.
Suggested change
| * Michael, starting with symptom provides common basis that can be used to build base content | |
| * Michael, starting with symptom provides common basis that can be used to build base content. |
meetings-other/2019-01-16.md
Outdated
| and then having a second layer with additional guidance for specific deployment | ||
| environments. | ||
|
|
||
| * Next question is how to prioritize the content |
There was a problem hiding this comment.
Suggested change
| * Next question is how to prioritize the content | |
| * Next question is how to prioritize the content? |
meetings-other/2019-01-16.md
Outdated
| * Matheus, start with symptom then narrow down to deployment scenarios. (same as Michael) | ||
| * Gireesh, one issue is that there may be a lot of deployment variations so hard to | ||
| start there. On the other hand production deployments will still need the steps to get | ||
| There. |
There was a problem hiding this comment.
Suggested change
| There. | |
| there. |
|
@richardlau - thanks; I am also not sure if there could be other meetings of this class, kept it separately as I think this is different from WG meetings - the proceedings that run up to this meeting, the people that involved etc. However I am open to move the file if there are more (and strong) opinions for it. |
PR-URL: nodejs#271 Reviewed-By: Matheus Marchini <mat@mmarchini.me> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Michael Dawson <Michael_Dawson@ca.ibm.com>
gireeshpunathil
force-pushed
the
minutesjan16
branch
from
df33470 to
3f1c93c
Compare
|
landed as 3f1c93c |
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.
No description provided.