Hammer-cli branding?

Development
1

Is there any work planned for branding of the CLI so we don't reference
Foreman directly in downstream products?

hammer

Usage:
hammer [OPTIONS] SUBCOMMAND [ARG] …

Parameters:
SUBCOMMAND subcommand
[ARG] … subcommand arguments

Subcommands:
shell Interactive Shell
architecture Manipulate Foreman's architectures.
global_parameter Manipulate Foreman's global parameters.
compute_resource Manipulate Foreman's compute resources.
domain Manipulate Foreman's domains.
environment Manipulate Foreman's environments.
fact Search Foreman's facts.
report Browse and read reports.
puppet_class Browse and read reports.
host Manipulate Foreman's hosts.
hostgroup Manipulate Foreman's hostgroups.
location Manipulate Foreman's locations.
medium Manipulate Foreman's installation media.
model Manipulate Foreman's hardware models.
os Manipulate Foreman's operating system.
organization Manipulate Foreman's organizations.
partition_table Manipulate Foreman's partition tables.
proxy Manipulate Foreman's smart proxies.
subnet Manipulate Foreman's subnets.
template Manipulate Foreman's config templates.
user Manipulate Foreman's users.

an easy option would just be to remove the word 'Foreman' from all of
those help texts, eg:

 partition_table               Manipulate partition tables.
 proxy                         Manipulate smart proxies.
 subnet                        Manipulate subnets.
 template                      Manipulate config templates.
 user                          Manipulate users.

Mike

··· -- Mike McCune mmccune AT redhat.com Red Hat Engineering | Portland, OR Systems Management | 650-254-4248
2

All the katello subcommands are labeled as "Foretello" :slight_smile:

··· ----- Original Message ----- > From: "Mike McCune" > To: foreman-dev@googlegroups.com > Sent: Friday, December 6, 2013 5:04:43 PM > Subject: [foreman-dev] hammer-cli branding? > > Is there any work planned for branding of the CLI so we don't reference > Foreman directly in downstream products? > > # hammer > Usage: > hammer [OPTIONS] SUBCOMMAND [ARG] ... > > Parameters: > SUBCOMMAND subcommand > [ARG] ... subcommand arguments > > Subcommands: > shell Interactive Shell > architecture Manipulate Foreman's architectures. > global_parameter Manipulate Foreman's global parameters. > compute_resource Manipulate Foreman's compute resources. > domain Manipulate Foreman's domains. > environment Manipulate Foreman's environments. > fact Search Foreman's facts. > report Browse and read reports. > puppet_class Browse and read reports. > host Manipulate Foreman's hosts. > hostgroup Manipulate Foreman's hostgroups. > location Manipulate Foreman's locations. > medium Manipulate Foreman's installation media. > model Manipulate Foreman's hardware models. > os Manipulate Foreman's operating system. > organization Manipulate Foreman's organizations. > partition_table Manipulate Foreman's partition tables. > proxy Manipulate Foreman's smart proxies. > subnet Manipulate Foreman's subnets. > template Manipulate Foreman's config templates. > user Manipulate Foreman's users. > > an easy option would just be to remove the word 'Foreman' from all of > those help texts, eg: > > partition_table Manipulate partition tables. > proxy Manipulate smart proxies. > subnet Manipulate subnets. > template Manipulate config templates. > user Manipulate users. > > Mike > -- > Mike McCune > mmccune AT redhat.com > Red Hat Engineering | Portland, OR > Systems Management | 650-254-4248 > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. >
3

> From: "Mike McCune" <mmccune@redhat.com>
> To: foreman-dev@googlegroups.com
> Sent: Friday, December 6, 2013 5:04:43 PM
> Subject: [foreman-dev] hammer-cli branding?
>
> Is there any work planned for branding of the CLI so we don't reference
> Foreman directly in downstream products?

I haven't heard of any work on it up to this point, but it seems like it'd make sense to use "Foreman" by default and allow overrides in cli_config.yml.

··· ----- Original Message -----

hammer

Usage:
hammer [OPTIONS] SUBCOMMAND [ARG] …

Parameters:
SUBCOMMAND subcommand
[ARG] … subcommand arguments

Subcommands:
shell Interactive Shell
architecture Manipulate Foreman’s architectures.
global_parameter Manipulate Foreman’s global parameters.
compute_resource Manipulate Foreman’s compute resources.
domain Manipulate Foreman’s domains.
environment Manipulate Foreman’s environments.
fact Search Foreman’s facts.
report Browse and read reports.
puppet_class Browse and read reports.
host Manipulate Foreman’s hosts.
hostgroup Manipulate Foreman’s hostgroups.
location Manipulate Foreman’s locations.
medium Manipulate Foreman’s installation media.
model Manipulate Foreman’s hardware models.
os Manipulate Foreman’s operating system.
organization Manipulate Foreman’s organizations.
partition_table Manipulate Foreman’s partition tables.
proxy Manipulate Foreman’s smart proxies.
subnet Manipulate Foreman’s subnets.
template Manipulate Foreman’s config templates.
user Manipulate Foreman’s users.

an easy option would just be to remove the word ‘Foreman’ from all of
those help texts, eg:

 partition_table               Manipulate partition tables.
 proxy                         Manipulate smart proxies.
 subnet                        Manipulate subnets.
 template                      Manipulate config templates.
 user                          Manipulate users.

Mike

Mike McCune
mmccune AT redhat.com
Red Hat Engineering | Portland, OR
Systems Management | 650-254-4248

–
You received this message because you are subscribed to the Google Groups
“foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

4

That type of single word replacemnet makes localization hard. It would
be great to make the description reference the product name, and then
the subcommand be agnostic to the product.

– bk

··· On 12/06/2013 07:21 PM, Sam Kottler wrote: > > > ----- Original Message ----- >> From: "Mike McCune" >> To: foreman-dev@googlegroups.com >> Sent: Friday, December 6, 2013 5:04:43 PM >> Subject: [foreman-dev] hammer-cli branding? >> >> Is there any work planned for branding of the CLI so we don't reference >> Foreman directly in downstream products? > > I haven't heard of any work on it up to this point, but it seems like it'd make sense to use "Foreman" by default and allow overrides in cli_config.yml.
5

IRC discussion decision was to remove any reference at all. "Manipulate Foreman host." would change to "Manipulate host."

Speak up now with concerns.

··· ----- Original Message ----- > From: "Bryan Kearney" > To: foreman-dev@googlegroups.com > Sent: Saturday, December 7, 2013 9:45:11 AM > Subject: Re: [foreman-dev] hammer-cli branding? > > On 12/06/2013 07:21 PM, Sam Kottler wrote: > > > > > > ----- Original Message ----- > >> From: "Mike McCune" > >> To: foreman-dev@googlegroups.com > >> Sent: Friday, December 6, 2013 5:04:43 PM > >> Subject: [foreman-dev] hammer-cli branding? > >> > >> Is there any work planned for branding of the CLI so we don't reference > >> Foreman directly in downstream products? > > > > I haven't heard of any work on it up to this point, but it seems like it'd > > make sense to use "Foreman" by default and allow overrides in > > cli_config.yml. > > That type of single word replacemnet makes localization hard. It would > be great to make the description reference the product name, and then > the subcommand be agnostic to the product. > > -- bk > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. >
6

+1 for me.

– bk

··· On 12/09/2013 01:38 PM, Tom McKay wrote: > > > ----- Original Message ----- >> From: "Bryan Kearney" >> To: foreman-dev@googlegroups.com >> Sent: Saturday, December 7, 2013 9:45:11 AM >> Subject: Re: [foreman-dev] hammer-cli branding? >> >> On 12/06/2013 07:21 PM, Sam Kottler wrote: >>> >>> >>> ----- Original Message ----- >>>> From: "Mike McCune" >>>> To: foreman-dev@googlegroups.com >>>> Sent: Friday, December 6, 2013 5:04:43 PM >>>> Subject: [foreman-dev] hammer-cli branding? >>>> >>>> Is there any work planned for branding of the CLI so we don't reference >>>> Foreman directly in downstream products? >>> >>> I haven't heard of any work on it up to this point, but it seems like it'd >>> make sense to use "Foreman" by default and allow overrides in >>> cli_config.yml. >> >> That type of single word replacemnet makes localization hard. It would >> be great to make the description reference the product name, and then >> the subcommand be agnostic to the product. >> >> -- bk >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > IRC discussion decision was to remove any reference at all. "Manipulate Foreman host." would change to "Manipulate host." > > Speak up now with concerns. >
7

+1 easiest option that make sense
http://projects.theforeman.org/issues/3841

T.

··· On 12/09/2013 07:38 PM, Tom McKay wrote: > > > ----- Original Message ----- >> From: "Bryan Kearney" >> To: foreman-dev@googlegroups.com >> Sent: Saturday, December 7, 2013 9:45:11 AM >> Subject: Re: [foreman-dev] hammer-cli branding? >> >> On 12/06/2013 07:21 PM, Sam Kottler wrote: >>> >>> >>> ----- Original Message ----- >>>> From: "Mike McCune" >>>> To: foreman-dev@googlegroups.com >>>> Sent: Friday, December 6, 2013 5:04:43 PM >>>> Subject: [foreman-dev] hammer-cli branding? >>>> >>>> Is there any work planned for branding of the CLI so we don't reference >>>> Foreman directly in downstream products? >>> >>> I haven't heard of any work on it up to this point, but it seems like it'd >>> make sense to use "Foreman" by default and allow overrides in >>> cli_config.yml. >> >> That type of single word replacemnet makes localization hard. It would >> be great to make the description reference the product name, and then >> the subcommand be agnostic to the product. >> >> -- bk >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > IRC discussion decision was to remove any reference at all. "Manipulate Foreman host." would change to "Manipulate host." > > Speak up now with concerns. >
8

>
>>
>>
>>
>>> From: "Bryan Kearney" <bryan.kearney@gmail.com>
>>> To: foreman-dev@googlegroups.com
>>> Sent: Saturday, December 7, 2013 9:45:11 AM
>>> Subject: Re: [foreman-dev] hammer-cli branding?
>>>
>>>
>>>>
>>>>
>>>>
>>>>> From: "Mike McCune" <mmccune@redhat.com>
>>>>> To: foreman-dev@googlegroups.com
>>>>> Sent: Friday, December 6, 2013 5:04:43 PM
>>>>> Subject: [foreman-dev] hammer-cli branding?
>>>>>
>>>>> Is there any work planned for branding of the CLI so we don't reference
>>>>> Foreman directly in downstream products?
>>>>>
>>>>
>>>> I haven't heard of any work on it up to this point, but it seems like
>>>> it'd
>>>> make sense to use "Foreman" by default and allow overrides in
>>>> cli_config.yml.
>>>>
>>>
>>> That type of single word replacemnet makes localization hard. It would
>>> be great to make the description reference the product name, and then
>>> the subcommand be agnostic to the product.
>>>
>>> – bk
>>>
>>> –
>>> You received this message because you are subscribed to the Google Groups
>>> "foreman-dev" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to foreman-dev+unsubscribe@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>> IRC discussion decision was to remove any reference at all. "Manipulate
>> Foreman host." would change to "Manipulate host."
>>
>> Speak up now with concerns.
>>
> +1

>
>> +1 for me.
>
>
> – bk
>
> –
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

··· On Tue, Dec 10, 2013 at 4:30 AM, Bryan Kearney wrote: > On 12/09/2013 01:38 PM, Tom McKay wrote: >> ----- Original Message ----- >>> On 12/06/2013 07:21 PM, Sam Kottler wrote: >>>> ----- Original Message -----