Proposal: Add @winem to the StackStorm Contributors [skip ci]#4942
Merged
Proposal: Add @winem to the StackStorm Contributors [skip ci]#4942
Conversation
Member
|
👍 from me! |
nmaludy
approved these changes
May 8, 2020
LindsayHill
approved these changes
May 8, 2020
Member
|
Agree |
m4dcoder
approved these changes
May 8, 2020
blag
approved these changes
May 8, 2020
bigmstone
approved these changes
May 12, 2020
mickmcgrath13
approved these changes
May 12, 2020
Member
Author
|
We've got @winem welcome to the StackStorm Contributors! |
Contributor
|
Thank you! I'm glad to be part of this lovely community and looking forward to many more contributions. :) |
This file contains hidden or 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
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.
I'd like to propose adding @winem to the list of StackStorm Contributors.
During the past half year he was helping StackStorm project via bug reports, PR fixes, PR reviews, release testing efforts as well as actively supporting community in Slack and Forums.
Github PRs:
good first issue.good first issueSSH connect timeout is too long (60s) #4715st2st2docsst2docsst2docs.Release Testing:
v3.2devStackStorm v3.2dev pre-release Testing community#6 and not just reporting bugs to st2 core and documentation, but also shipping PRs to fix them. That's the most valued attitude.Forums:
Not to forget about being active in Slack Community and guiding StackStorm newcomers which is very helpful!