It seems we have two target audiences here. Developers who work on OpenStack and developers who write apps to use it. In the long run I think we need to optimize for both of these groups.
If we want developers to write applications to use OpenStack in python we likely need a "common" python SDK. Note, I'm not a fan of the term client because it's not the common language for this group of developers. On Fri, Jan 17, 2014 at 10:26 AM, John Dennis <jden...@redhat.com> wrote: > >> Keeping them separate is awesome for *us* but really, really, really > >> sucks for users trying to use the system. > > > > I agree. Keeping them separate trades user usability for developer > > usability, I think user usability is a better thing to strive for. > > I don't understand how multiple independent code bases with a lot of > overlapping code/logic is a win for developers. The more we can move to > single shared code the easier code comprehension and maintenance > becomes. From a software engineering perspective the amount of > duplicated code/logic in OpenStack is worrisome. Iterating towards > common code seems like a huge developer win as well as greatly enhancing > robustness in the process. > > -- > John > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
