On Tue, Jul 29, 2014 at 04:16:52AM +0200, Andrew Phillips wrote: > One of the main "cons", certainly w.r.t. labs, was: > > * code of vastly different degrees of maturity/up-to-dateness in the same repo > > I certainly wouldn't want to include a whole bunch of the current > labs providers in core, since they're either simply broken and/or > hopelessly out of date. > > If I had to make a choice, I would probably lean towards removing > them and merging the rest, but there have been discussions every now > and them of people perhaps being willing to pick them up.
What if we continue to use the labs repository as a staging area but stop releasing it? This will allow development of new providers to proceed and user testing via snapshots but not impact the release process. Obviously, this will require migrating the mature providers to core, which we seem to agree should happen anyway. > As regards karaf and cli: would they belong in core, or in tools or > elsewhere? They're really more downstream consumers of jclouds than > *parts* of jclouds themselves. Honestly I do not understand karaf and see it as something outside of the main jclouds project. As for cli, we should replace it with something friendlier and lightweight such as: https://github.com/andrewgaul/jclouds/tree/blobstore-cli -- Andrew Gaul http://gaul.org/
