In the github comments for the PR Matt also mentioned amazon RDS support. I wanted to ask if somebody has any work in progress for it, as it seems to be the conceptual equivalent of trove.
Support: I believe Everett, Jeremy, and mostly myself would be on the list of people committed to supporting this API. Support needed of course being proportional to the users (and user cases) the API would have, that's a good problem to have (I would think). Other API demands/priority: Because I am new to jclouds I would appreciate it if you can be more specific, as that would be educational. What are the project's high priorities re:APIs? I have noticed in a lot of OS projects resources available are not necessarily (or easily) aligned with high priority demands. How do you think jclouds should address this? What/where are the guidelines? My biased personal take (having been a heavy consumer of java OS projects for some time, mostly for prototyping) is that I want all the features in my SDKs as soon as possible. Thanks Matt! - for starting the discussion. -Zack ________________________________________ From: [email protected] [[email protected]] on behalf of Matt Stephenson [[email protected]] Sent: Monday, July 29, 2013 2:03 PM To: [email protected] Subject: [DISCUSS] Trove API promotion into jclouds from jclouds-labs-openstack 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. We still have a good deal of other apis that there is more demand for to be promoted up. What value do we gain by promoting this as the only api of it's kind into jclouds now? Who in the community is using this in labs today? How comfortable are we as a community in supporting this and working on issues related to it? Thanks, Matt
