search

jclouds / legacy-jclouds-labs

https://jclouds.apache.org
0 stars 18 forks source link

rename google-compute to google-compute-engine #5

Closed jclouds closed 9 years ago

jclouds commented 11 years ago

gce seems to be a term people understand. it is also shorter in config, package names, etc.

@dralves @mattstep any opinions?

dralves commented 11 years ago

i personally prefer gce, but last time we had this discussion your (correct IMO) reasoning was that looking for google compute on google yielded meaningful results while gce does not...

codefromthecrypt commented 11 years ago

yeah I remember. I notice this trend has shifted in recent months, though, probably due to more people being able to use the account.

codefromthecrypt commented 11 years ago

that said, gce is still terribly un googlable.. let's get more feedback?

mattstep commented 11 years ago

I would suggest the full name, google-compute-engine, that's what the product teams at Google are using.

Matt

On Sun, Mar 10, 2013 at 10:55 AM, Adrian Cole notifications@github.comwrote:

that said, gce is still terribly un googlable.. let's get more feedback?

— Reply to this email directly or view it on GitHubhttps://github.com/jclouds/jclouds-labs/issues/5#issuecomment-14685579 .

codefromthecrypt commented 11 years ago

+1 let's do this for 1.6.0-rc.2

dralves commented 11 years ago

should we change only the provider name and related properties or change the whole namespace (e.g. s/GoogleCompute/GoogleComputeEngine)?

codefromthecrypt commented 11 years ago

If vote for consistency across the board including class names.

gaul commented 9 years ago

Done in 3474c2651f59de9b15f13facb60c923988309e63.