From: Angus Thomas <athomas(a)redhat.com>
Date: Tue, 26 Jul 2011 12:36:16 +0100
If nobody is advocating an Orchestrator application, which users would
interact with instead of Conductor in those cases, then I'm happy.
Speaking as somebody who's in charge only of underpinnings, that
sentiment sounds right to me. I keep hearing that regardless of what
underlying implementations are kicking around, the product goal is to
present a fairly seamless user experience.
In terms of whether it makes sense to split the project into two
logical pieces, sure, if that makes sense. My main question is who's
responsible for driving which piece(s) and making sure that all the
tidbits get accounted for?