Hi, team (primarily Everett, Jeremy, Zach) jclouds has the blessing and burden of being a warehouse for OpenStack apis. Some of these are highly reused, others, less so. One thing I've watched over years is us slavishly implementing some really bad designs. It is one thing for a enterprise cloud.. we kindof expect those to suck, and the engagement model doesn't lead towards things getting better. But, OpenStack?!
Is there any avenue folks can think of where we can help OpenStack not design terrible apis? Or things that make jclouds live with custom code forever? What if we were a datapoint that fed back into their design? What if instead of slavishly implementing things that make us cringe, we opened an issue with the corresponding project saying.. I think I can help! For example, back in the day, I found a snafu on an api design in swift. I opened a bug https://bugs.launchpad.net/swift/+bug/1232787 They fixed it. We have a unique opportunity to help improve the quality of OpenStack vs propagate poor quality. Can folks with influence start pushing back with suggestions? It not only helps us have less edge-case code or senseless boilerplate, but it will also help improve the reputation of OpenStack. -A
