> We should commit these immediately and move them afterwards if a substantial > objection arises.
I certainly agree that we don't want to hold this up - I'd rather get the tools used too. But I also don't think the jclouds team should have to pick up development responsibility for what I would consider external tools such as the jclouds-karaf, jclouds-cli, blobstore-bench or blobstore-cli. Putting them inside the jclouds/jclouds repo would, to me, indicate that the team does indeed pick up that responsibility. For the release and verification scripts - sure - but I personally am not sure about the others. If we want them used _now_ while we continue this discussion (and hopefully come to some conclusion, finally!), could we submit blobstore-bench and blobstore-cli against jclouds-labs? I'd definitely vote to merge them there immediately ;-) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/459#issuecomment-52259155
