AWS SIG Proposal #3
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
robzienert
reviewed
May 25, 2019
robzienert
reviewed
May 25, 2019
robzienert
reviewed
May 25, 2019
aglover
added
the
committee/steering
|
FYI @spinnaker/sc |
pstout
reviewed
May 29, 2019
pstout
reviewed
May 29, 2019
imosquera
force-pushed
the
sig-aws
branch
6 times, most recently
from
a618350
to
f3f9a81
Compare
|
Seems like all of the suggestions and feedback have been incorporated into this proposal. My vote is a +1. |
pstout
reviewed
Jun 2, 2019
|
While there are two minor editorial suggestions from me outstanding that I think would clarify the vision, I am fine with the proposal. My vote is also +1. |
|
+1 thank you. |
|
+1 |
1 similar comment
|
+1 |
|
@imosquera can you please address @pstout comments? I can merge this ASAP. |
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.