Hi Chris, Thanks for explaining that moving the provider in a point-release could be problematic. We certainly don't want it that badly. I did know we had some sizeable PRs sitting out there too as a bit of a sticky situation.
It's also likely a very good thing for Danny to come up to speed more before it goes into core so Google is in a better position to help out new users. ...assuming going into core creates a landslide of new Google provider users. :) Please do continue to let us know what things we can do to help benefit you folks and jclouds users. Cheers, Eric On Wed, Oct 15, 2014 at 11:57 AM, Chris Custine <chris.cust...@gmail.com> wrote: > Hi Eric, > Thanks for your insight on Google’s interest and involvement. This is a > well timed message because we have been discussing some of the pains and > successes regarding provider maintenance and how we can involve the right > people in order to do this better. The issue at hand is that the provider > base has grown quite large and most of the developers have a specific slice > of jclouds and providers that they monitor and maintain, so there are gaps > where providers and functionality get less exposure and sometimes grow > stale. Other times, we get a great contribution and some short term > maintenance from a vendor or interested party, and then they disappear and > over time the code grows stale if nobody else has context and picks it up. > > I don’t speak for the entire community here, but I for one am excited > about your interest and willingness to commit resources to maintain and > enhance the GCE provider and related code. I think this is exactly the > type of example we want to call out as a model for future providers and > ongoing maintenance of existing ones. > > As for promoting GCE from labs to jclouds main repo, it was a community > decision to hold back on this release because it could be confusing to move > a provider in a bugfix release, and there were several pending PRs that > really needed to be merged before this made it to a production ready > release and we didn’t have enough time to get that all in and properly > tested anyway. Once 1.8.1 is released we will be discussing how and when > to get the GCE provider promoted and will let you know. > > Thanks again for your support on GCE, > Chris > > -- > Chris Custine > > > On October 15, 2014 at 12:03:34 PM, Eric Johnson (erjoh...@google.com) > wrote: > > +dev since apparently I don't know how to use gmail... > > On Wed, Oct 15, 2014 at 10:43 AM, Eric Johnson <erjoh...@google.com> > wrote: > > > Hi folks, > > > > As you're all likely aware, Google was very much hoping to get promoted > > out of labs [https://issues.apache.org/jira/browse/JCLOUDS-172] in > 1.8.1. > > Internally, we've tried a few different ways of contributing to the > feature > > coverage and quality of the google lab (feature PRs over the summer, > docs / > > examples). Most recently, a colleague of mine, Dan Broudy, is ramping up > on > > the project to be the primary owner from Google. The goal is that > between > > the two of us, the Jclouds community at large will have real people to > > contact for feature requests, bug reports / fixes, and help in general > and > > we've even offered to be listed on > > https://wiki.apache.org/jclouds/Stewards. > > > > It looks like the 1.8.1 ship is about to leave dock [ > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12327548&styleName=Html&projectId=12314430&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C05e0b2cce69ea1018324801735805624361873ff%7Clout]. > > > It looks like you've also been discussing release cadence and there is a > > chance you could go to 6-month releases. I'm wondering if there is > anything > > else we could do to amend the list to get 172 added this time around? > Dan > > and I can spend a lot of cycles on it right now if you have a short list > of > > things you'd like to see from us. > > > > Thanks for considering. (...and sorry if this request is a social faux > > pas) > > Eric > > /nick erjohnso on #jclouds if you want to yell at me privately. :) > > > >
