On 04/21/2016 10:05 AM, Hayes, Graham wrote:
On 21/04/2016 15:39, Michael Krotscheck wrote:
[...]
New: js-openstacklib
This new project will be incubated as a single, gate-tested JavaScript
API client library for the OpenStack API’s. Its audience is software
engineers who wish to build their own user interface using modern
javascript tools. As we cannot predict downstream use cases, special
care will be taken to ensure the project’s release artifacts can
eventually support both browser and server based applications.
Philosophically, we will be taking a page from the
python-openstackclient book, and avoid creating a new project for each
of OpenStack’s services. We can make sure our release artifacts can be
used piecemeal, however trying to maintain code consistency across
multiple different projects is a hard lesson that others have already
learned for us. Let’s not do that again.
I'd love to chat about js-openstacklib supporting clouds.yaml files for
config.
python-openstackclient does require the creation of a new repo for each
project (unless you are one of the chosen few).
Does this mean you will accept all projects to the library, or just
selected projects?
Not being a person who is doing the work on this, I would counsel
accepting all projects to the library. We have done that in shade and
os-client-config and have not had any problems with it.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
