Makes sense for providers especially, but also for api groups where there's a clear owner for all. For example, we aren't with the same luxury on aws or azure yet.
On Mon, Oct 6, 2014 at 1:57 PM, Everett Toews <everett.to...@rackspace.com> wrote: > Any objections to using wildcards for brevity’s sake where it makes sense? > > e.g. > > openstack-* > elastichosts-* > rackspace-* > hpcloud-* > cloudsigma2-* > > Probably doesn’t make sense for aws providers/apis as stewardship of them > isn’t uniform. > > Everett > > > On Oct 6, 2014, at 2:03 PM, Andrew Gaul <g...@apache.org> wrote: > >> Following on to the steward discussion[1], I created a wiki of all the >> jclouds modules on our wiki: >> >> https://wiki.apache.org/jclouds/Stewards >> >> I would like to assign stewards for all modules; please add yourself to >> the ones which interest you. This process may identify some orphan >> providers and hopefully we can source a steward from the community or >> vendor. Otherwise we may schedule that module for removal. >> >> [1] http://mail-archives.apache.org/mod_mbox/jclouds-dev/201410.mbox/browser >> >> -- >> Andrew Gaul >> http://gaul.org/ >
