> I do not want the perfect to be the enemy of the good. I agree, but I think we can still put a little thought into where this and, indeed (as you say) related types of admin tools should go before we need to accuse ourselves of "striving for immediate perfection". I don't think the code needs to be any bigger or fatter for that.
I just don't think jclouds itself, which (unless I'm missing something) currently doesn't have the "blobstore-tools" we're talking about, or indeed _any_ other kind of tooling, is the right place. Indeed, Adrian made the move the _opposite_ way around (taking administrative stuff _out_ of jclouds) a while ago, and that still seems like a good choice for me. Unless everyone else strongly feels this belongs in jclouds, or we find another "natural" home, I could imagine this being the first entry in a new "jclouds-admin" or "jclouds-tools" repo (sorry, @zack-shoylev ;-)). That will allow us to get this out there immediately, and we can still figure out whether karaf or cli should move there as a separate step. Hopefully that way we can start with something good without worrying about being perfect straight away? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/239#issuecomment-30869343
