On 01/03/2013 12:33 PM, Matt Wagner wrote:
On Thu, Jan 03, 2013 at 12:11:37PM +0000, Angus Thomas wrote:
<snip>
Here's the list, current names on the left, and the new name on the right:
Image Template -> Component Outline
I'm still not sure what a 'Component' is, nor how an Outline and
Blueprint differ, but I'm not going to protest it.
The reason it's a "component" outline is that in the original "new
terms" list prior to 1.0 they wanted to rename instances to components
-- so this was an "instance outline" -- i.e. image template. I'm not
clear at all on intended difference in meaning between "outline" and
"blueprint"
Deployable -> AppForm Blueprint
Deployment -> AppForm
My thoughts on the term 'AppForm' aside, I like this approach.
"Deployable" and "Deployment" frequently get mixed up, even
(especially?) by people who know how they differ. Having a $foo and a
$foo Blueprint makes this much more intuitive and easy to keep straight,
at least for me.
Pool Family/Environment-> Cloud Environment
Pool -> Resource Zone
Provider -> Cloud Resource Provider
Hardware Profile -> Hardware Profile
Provider Realm -> Provider Realm
Frontend Realm -> Frontend Realm
Image -> Image
Assembly -> Assembly
Instance -> Instance
Catalog -> Catalog
Config Server -> Config Server
Please respond with +1 or objections.
+1 from me. I don't love some of these names, but I think overall
they are less-bad than current names, and converging on consistent
terminology with the product is a big win.
-- Matt
