Eugen

Noticed that interesting concept of passing artifacts within the workflow from Argo when we looked at it a few weeks ago. This is a good feature request and use cases...

@guzzijones Could you please document your findings in respective https://docs.stackstorm.com/ section?

> A winner is selected using [Shulze variant of Condorset method](https://en.wikipedia.org/wiki/Schulze_method). Talking about Voting mechanism, seen that in other projects too :+1: LFN Chair Election Process (https://wiki.lfnetworking.org/display/LN/2020+TAC+Chair+Election) has a good...

Updated previous ^^ comment to take into account the voting points. Also, do we need Private or Public voting? - In case of Public one, - I agree with @dzimine...

@amanda11 From what I understand Voting Mechanism is up to TSC to decide. We however can do our research and find more examples of TSC Chair voting for the LF/CNCF...

In the past, we thought to make it the default driver, but eventually, switched to Redis as recommended default which provided the best experience. I've found https://github.com/StackStorm/st2/pull/4608 and https://github.com/openstack/tooz/compare/master...StackStorm:etcd3_driver_fixes?expand=1 from...

We're bundling `Redis` with the st2 core at this moment as a default coordination backend, which is shipped with all the official installation methods and e2e tested. We then recommend...

I hear that including other coordination backend dependencies like `etcd3gw` in st2 requirements.txt is a no-go at this moment. Let's leave this open. Maybe we'll see more community requests in...

Also yeah, we've missed the point that `tenacity` is the `tooz` dependency in the first place, not specific to `etcd3gw` pip or any other backend. https://github.com/openstack/tooz/blob/master/requirements.txt#L9 @khushboobhatia01 Could you please...

@khushboobhatia01 As a follow-up to this, could you please create a PR to pin the tenacity dependency? I'd think it will be helpful for everyone.