Promote carlos (@nzlosh) from contributor to maintainer

[blag]

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

• He created and singlehandedly maintains the Python-based err-stackstorm, an alternative to Node.js-based st2chatops with hubot-stackstorm. His project is so successful that it was given its own #err-stackstorm channel in our Slack community.
• He created and regularly maintains the PowerDNS pack
• Contributed documentation and examples to the syslog client pack
• Helps develop the Consul pack
• Has made a few contributions to other packs
  • stackstorm-icinga2
  • stackstorm-salt
• Contributes patches to (his) upstream projects:
  • Errbot
  • err-backend-discord
• And is involved in spreading StackStorm support to Debian systems (this is greatly complicated by Debian Buster lacking Python 3.6 and MongoDB 4.0 packages):
  • Debian 10 Buster using Python 3.7 #4844
  • WIP - Add Python3.7 to CI pipeline #4855
  • Add Debian 10 Buster support. st2packaging-dockerfiles#75
  • https://forum.stackstorm.com/t/is-python3-7-officially-supported-by-stackstorm/938/10
• Has reported and investigated issues with Orquesta and ActionChain
• He has posted in the StackStorm forums:
  • https://forum.stackstorm.com/t/test-stackstorm-alias-output/1129
  • https://forum.stackstorm.com/t/slack-extra-feature-to-get-different-colours/413
  • https://forum.stackstorm.com/t/dynamic-action-workflows-pattern/515
  • https://forum.stackstorm.com/t/support-for-bigpanda/1069
  • https://forum.stackstorm.com/t/orquesta-workflow-json-actions-items/1090
    As well as helped numerous people in #community.

Additionally, he has created two personal packs:

• https://github.com/nzlosh/stackstorm_ldap
• https://github.com/nzlosh/stackstorm_livestatus

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.

[arm4b]

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?

[nzlosh]

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.

[arm4b]

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

[nzlosh]

We can use [email protected].

[arm4b]

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

Any other areas of interest? WDYT @nzlosh ?

[nzlosh]

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

[arm4b]

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]

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.

[cognifloyd]

Replaced by #5342