On Jul 29, 2013, at 2:03 PM, Matt Stephenson wrote: > We currently have an outstanding set of pull requests for this, prior to us > discussing this on dev. I'm personally not in favor of promoting it at > this time because I feel it's a bit too immature at this time.
Software gains maturity by being released to a wider audience and by being used. And what we have here is more than a minimum viable product. It's complete, working support for the OpenStack Trove/Rackspace Cloud Databases API. > We still > have a good deal of other apis that there is more demand for to be promoted > up. It's not an either/or situation amongst the APIs. If an API is complete, it can be promoted. > What value do we gain by promoting this as the only api of it's kind into > jclouds now? We gain a wider audience. We gain the experience of seeing how people use it and what problems they run into. We gain the insights and experience that are necessary to create higher level abstractions. All of those things that helps software mature. Just because an implementation from another provider isn't ready, doesn't mean we should hold back on releasing software. We need to start somewhere. In general, the value of jclouds increases for our users because we'll have complete and maintained support for another cloud API. > Who in the community is using this in labs today? Naturally we (Rackspace) are. There are also examples and doc ready to go. Having a "labs" label on something will prevent many from adopting it. > How comfortable are we as a community in supporting this and working on > issues related to it? I can say with complete conviction that, as a part of this community, Zack, Jeremy, and myself are 100% committed to supporting it and working on issues related to it. Regards, Everett
