Hi Rick, Thanks for your interest!
I'm not very familiar with the GCE provider code, and I don't know which level of maturity it has, so I won't be able to point you to fixes/improvements/missing features in the provider (hope someone else will do :D). What would be really helpful is to have some examples and documentation, which is currently missing, to help adoption. As we get more users using it we'll have better feedback, know what needs to be improved, and know when the provider is production ready (and when we can promote it to the main repo). If no one else says the opposite or knows about more important tasks, it would be really great if you could add some examples to our examples repo [1] (the Rackspace examples are good ones to have a look at) and create the GCE user guide here [2]. That's where most people land when they start exploring jclouds. You will find our how to contribute code and documentation guides in our community page [3] as long as our IRC channel. Thanks again for your interest, and let us know whatever you need, Ignasi [1] https://github.com/jclouds/jclouds-examples [2] http://jclouds.apache.org/guides/ [3] http://jclouds.apache.org/community/ On 4 March 2014 20:39, Rick Wright <ri...@google.com> wrote: > Hi all, > We are looking into ways that we can contribute to the Google provider code > and wanted to know what would be the most useful things we could do to > improve it. Is there functionality that is needed, tests that need to be > written/improved or documentation that needs to be updated? > > We are happy to contribute random fixes/improvements, but if there are > specific things that would be more useful it would probably make sense to > focus on those. > > Thanks for any input that you have, > Rick Wright > @wrigri on github >
