John, Tough decision but I agree it's probably the right one to make. As a standalone service, it should reduce the the number of issues due to reduced number of config options (adapters to storage engines, etc). I would imagine a fair number of users are standing up a service around Ruote anyway and for those who aren't, having Ruote or Flon as a service would lead to better integration practices.
I don't think Ruote being written in Ruby was as much of the problem as Ruote being a library for workflows. Being a library/gem allowed the most flexibility integrating Ruote but probably caused most of the confusion about how to use properly. Were Ruote a stand-alone service, it really wouldn't matter which language it was written in. I would be very interested in watching and participating in the evolution of ruote 3 or flon also. Let us know how we can help. Doug -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
