Fork Or Contribute?

[thompcd]

I have a production app using Stateless and would like to add features to use it similarly to your use cases here with pre-defined connectors from a library.

I am having difficultly understanding all of the moving pieces, but it looks like you've done a lot of great work here! I've got a couple of question about the project:

1. Is there a reason the project has gone stale? Is it in need of a major overhaul that isn't apparent to me or is it not meeting its use case?
2. If I were to adopt this into my production app, should I anticipate using a fork the entire time or will a maintainer accept pull requests?
3. Are there any larger scale projects or demos published to get a broader understanding of how to develop the different pieces of the ecosystem?
4. Would you consider my use case a good candidate to use your ecosystem? Key details:

• Hardware library containing lots of MQTT, REST & serial controlled hardware
• Third party uses state machine designer GUI which exposes available hardware in library, creates flow logic using hardware, outputs serialized schematic to version control
• State machine player MVVM app binds to loaded state machine to display interactive instructions

Hope to hear from you, I'll be playing with this for the next couple days. I've got the basic demos off the ground already, just trying to bootstrap something with a few pieces of hardware now. Thanks!