Reconciling names

Dan Macpherson dmacpher at redhat.com
Mon Jan 7 02:50:25 UTC 2013


----- Original Message -----
> As discussed previously (
> https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-October/012923.html
> ) there's a significant cost associated with the divergence of names
> between Aeolus and Red Hat's Cloudforms.
> 
> The Aeolus community loses out in several ways:
> 
> - Users of Cloud Engine are using terminology which doesn't apply
> upstream, putting a barrier between the Aeolus project and a good
> number
> of the users of our software.
> - As part of the productisation process, Red Hat translates all the
> strings in Conductor into nine different languages.[1] If the use of
> terms could be reconciled, Aeolus Conductor would immediately support
> nine languages, rather than supporting one.
> - The work required to maintain a separate set of terms for the Cloud
> Engine product is tedious and error-prone and falls entirely on
> people
> who are key contributors to Aeolus, and whose time could be better
> spent.
> 
> Several rounds of shuttle diplomacy between the Aeolus community and
> Red
> Hat's product managers are now complete, and we have arrived at a
> final
> set of
> converged names. The final list is a significant set of changes from
> the
> current set of names used in Cloudforms, in response to the feedback
> from the Aeolus community.
> 
> Here's the list, current names on the left, and the new name on the
> right:
> 
> Image Template -> Component Outline
> Deployable -> AppForm Blueprint
> Deployment -> AppForm
> 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.
> 
> If you're new to the party, and are wondering if some of the new
> names
> could be changed, the answer is, "Probably not, at this stage". It
> has
> taken several rounds of discussion to get to this point. I'd strongly
> urge that we accept these names wholesale.
> 
> Of course, the applications will continue to evolve, and names may
> well
> change in future, but we shouldn't miss this opportunity to reconcile
> the Aeolus project's names with Cloudforms.
> 
> Please note that, as discussed in the Brno dev converence, we need to
> use the final set of names everywhere:
> 
> - API
> - CLI
> - Controller names etc.
> - Web UI
> - Docs, Blogs, discussions
> 
> So, there is going to be work to do to fix the entire application to
> use
> the correct names.
> 
> 
> 
> Angus
> 
> 
> 
> 

I think it's already been decided, but +1 too


More information about the aeolus-devel mailing list