Hi, I'm Josh Wulf, Camunda's Developer Advocate for Zeebe. I am committed to empower developers to be productive and happy creating systems using Zeebe.
I usually work from Brisbane, Australia (GMT +10). I'm available in the Zeebe Slack, and in the Zeebe User Forums.
Along with the core developers of Zeebe who hang out in the Zeebe Slack, I'm available to help you get up to speed with your Zeebe development. Part of my role is solving these problems not only for you, but also for other developers in the future. The core devs make Zeebe a great orchestration engine for microservices, and I'm accountable for making it easy and fun to program against for developers.
We don't have an SLA on support for Zeebe, and this support channel is a community initiative. At some point in the future, we plan to offer an enterprise edition of Zeebe that will include a support SLA. If enterprise support for Zeebe is something you're interested in, you can reach out to Zeebe PM Mike Winters (michael.winters@camunda.com) for more information.
In the meantime:
If you have a quick, simple question, just go ahead and ask away!
For more complex issues, the best way is to provide a "minimal reproducer" that demonstrates the issue that you are having, and post the link.
Here are two examples of a minimal reproducer:
A minimal reproducer has the following elements:
- A clear description of the issue.
- The minimum amount of code needed to demonstrate the issue.
- The steps to reproduce it.
I speak JavaScript, TypeScript, C#, Go, Java, and Kotlin - so I can easily work with reproducers in those languages. If you are programming in something else like Scala, Haskell, Q#, or Arnold C it may take me a little longer, and I might need to ask some questions to get it to run - but I can figure that out too.
The beauty of a minimal reproducer is that it gives us an unambiguous point of reference, and you might even find you resolve the issue yourself while creating the reproducer (happens to me frequently!).