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

Promote carlos (@nzlosh) from contributor to maintainer #4945

Closed
wants to merge 1 commit into from

Conversation

blag
Copy link
Contributor

@blag blag commented May 12, 2020

@nzlosh has regularly made contributions to the StackStorm project for over two years, but in just the last six months:

Additionally, he has created two personal packs:

And he has also weighed in on the discussion to transition st2chatops to something Python based. In fact, he did the majority of the homework for that proposal to begin with.

Being part of Technical Steering Committee (TSC) @StackStorm/maintainers provide significant and reliable value to the project helping it grow and improve through development and maintenance.

In recognition of his contributions and efforts to improve StackStorm as a product and as a community, I would like to propose that he be officially promoted from Contributor to Maintainer status and be given a seat/vote on the TSC.

@blag blag added proposal size/XS PR that changes 0-9 lines. Quick fix/merge. TSC:voting Items related to Technical Steering Committee voting labels May 12, 2020
@blag blag requested review from a team as code owners May 12, 2020 23:20
@punkrokk punkrokk added this to the 3.2.1 milestone May 13, 2020
@arm4b
Copy link
Member

arm4b commented May 13, 2020

I think we know @nzlosh for his help to the project in general, StackStorm-Exchange and Chatops community for many years and really grateful to have such a consistent Contributor!

However StackStorm Project Maintenance expects deeper level of dedication and involvement and also has responsibilities comparing to Contributor.
In general, this includes fixing st2 bugs from the backlog, triaging stackstorm issues, reviewing other's contributed PRs, conducing releases, attending TSC meetings, writing tests, supporting CI/CD, helping other Contributors, working on PRs with priority based on the project Roadmap items, updating documentation, learning the st2 core code deeper, shoulder a proportional share of community work: Slack, Forum, GH Issues, Releases. See Maintainer Responsibilities: https://github.com/StackStorm/st2/blob/master/GOVERNANCE.md#maintainer-responsibilities for the full list.


@nzlosh Do you want to become a Maintainer and work towards the How to become a Maintainer requirements?
Based on the project Governance are you willing to dedicate at least 1 day/week for the StackStorm core/project maintenance and cope with the Maintainer Responsibilities?

@arm4b arm4b removed this from the 3.2.1 milestone May 13, 2020
@nzlosh
Copy link
Contributor

nzlosh commented May 14, 2020

Hi @armab,

As already mentioned, I contribute through community support, err-stackstorm and pack development which represents more than a 1 day per week, so I'm confident I can adjust priorities to accord at least a day per week to the Core development process.

I would like to shift focus to the St2 core and gain a deeper understanding of the development processes and methods used to deliver StackStorm. My profession is primarily system engineering, so I may be lighter in developer experience than other maintainers, but I hope the work I've contributed to the community convinces you that I'm sufficiently motivated and capable to become a maintainer and work towards the maintainer requirements.

@@ -39,14 +39,15 @@ Being part of Technical Steering Committee (TSC) [@StackStorm/maintainers](https
- Systems, ST2 Exchange. [Case Study](https://stackstorm.com/case-study-bitovi/).
* Nick Maludy ([@nmaludy](https://github.com/nmaludy)) <<[email protected]>>
- Community, Core, Systems, StackStorm Exchange, Puppet deployment. [Case Study](https://stackstorm.com/case-study-dmm/).
* Carlos ([@nzlosh](https://github.com/nzlosh))
Copy link
Member

@arm4b arm4b May 14, 2020

Choose a reason for hiding this comment

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

@blag @nzlosh We'll need a working email here to follow the same format for TSC members.

Copy link
Contributor

Choose a reason for hiding this comment

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

We can use [email protected].

@@ -39,14 +39,15 @@ Being part of Technical Steering Committee (TSC) [@StackStorm/maintainers](https
- Systems, ST2 Exchange. [Case Study](https://stackstorm.com/case-study-bitovi/).
* Nick Maludy ([@nmaludy](https://github.com/nmaludy)) <<[email protected]>>
- Community, Core, Systems, StackStorm Exchange, Puppet deployment. [Case Study](https://stackstorm.com/case-study-dmm/).
* Carlos ([@nzlosh](https://github.com/nzlosh))
- Chatops, Errbot, Community, Discussions, StackStorm Exchange
Copy link
Member

Choose a reason for hiding this comment

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

As I understand at least st2 core needs to be added to this list.

Any other areas of interest? WDYT @nzlosh ?

Copy link
Contributor

Choose a reason for hiding this comment

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

Focusing on the st2 core along with the existing subjects should be enough for now.

Copy link
Member

Choose a reason for hiding this comment

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

Awesome!
As discussed internally, we'd like to see first more pro-active effort and contribution activity to the st2 core platform. Can you work a bit to improve the https://github.com/StackStorm/st2/commits?author=nzlosh?

@stale
Copy link

stale bot commented Sep 12, 2020

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.

@stale stale bot added the stale label Sep 12, 2020
@cognifloyd cognifloyd removed the stale label Jul 23, 2021
@cognifloyd
Copy link
Member

Replaced by #5342

@cognifloyd cognifloyd closed this Aug 24, 2021
@arm4b arm4b deleted the promote-carlos branch August 24, 2021 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal size/XS PR that changes 0-9 lines. Quick fix/merge. TSC:voting Items related to Technical Steering Committee voting
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants