we have Smart Proxy in the Foreman Core, WebUI/API/CLI and also in our
Core documentation, but in the installer and package name it's
foreman-proxy. This creates confusion.
I suggest to "communicate" it from now on with new official name:
Foreman Smart Proxy
This will help us to "teach" our users that this is essentially the same
thing. The suggested changes are easy and non-intrusive:
Rename "Smart Proxy" to "Foreman Smart Proxy" in our documentation
Rename "Smart Proxy" to "Foreman Smart Proxy" in our codebase
Controller names, API/CLI and internals all stays with "smart-proxy" of
course, the idea is only to logically connect these terms.
This was brought at (*) and I would like to bring it here for broad
discussion:
> Hello,
>
> we have Smart Proxy in the Foreman Core, WebUI/API/CLI and also in our
> Core documentation, but in the installer and package name it's
> foreman-proxy. This creates confusion.
This appears more inconsistent than the current situation, as there will
now be three terms, differing between the UI names ("Foreman Smart
Proxy"), API/module names ("smart proxy"), and package names ("foreman
proxy").
If only the installer module name and package name differ from
everything else, it would make more sense to rename them to "smart
proxy" so all three are the same.
···
On 14/10/16 08:34, Lukas Zapletal wrote:
> Hello,
>
> we have Smart Proxy in the Foreman Core, WebUI/API/CLI and also in our
> Core documentation, but in the installer and package name it's
> foreman-proxy. This creates confusion.
>
> I suggest to "communicate" it from now on with new official name:
>
> Foreman Smart Proxy
>
> This will help us to "teach" our users that this is essentially the same
> thing. The suggested changes are easy and non-intrusive:
>
> * Rename "Smart Proxy" to "Foreman Smart Proxy" in our documentation
> * Rename "Smart Proxy" to "Foreman Smart Proxy" in our codebase
>
> Controller names, API/CLI and internals all stays with "smart-proxy" of
> course, the idea is only to logically connect these terms.
> This appears more inconsistent than the current situation, as there will
> now be three terms, differing between the UI names ("Foreman Smart
> Proxy"), API/module names ("smart proxy"), and package names ("foreman
> proxy").
That's indeed a very true statement, I'll add that the new term aims to
be the glue between the other two.
I filed a patch just to see how it looks like, I haven't renamed
everything, but basically just index/show/edit/new page titles and
that's it.
But I get your point, it also does not look great at first sight
(basically because I am used to what we had until now).
> If only the installer module name and package name differ from
> everything else, it would make more sense to rename them to "smart
> proxy" so all three are the same.
I am not aware of anything else, but we also have directories like
/etc/foreman-proxy and logs and stuff. This could bite.
To be honest, I'd rather kill "Smart Proxy" than "Foreman Proxy" if I
had to choose just one.
>
> > This appears more inconsistent than the current situation, as there will
> > now be three terms, differing between the UI names ("Foreman Smart
> > Proxy"), API/module names ("smart proxy"), and package names ("foreman
> > proxy").
>
> That's indeed a very true statement, I'll add that the new term aims to
> be the glue between the other two.
I think I agree with Dominic, a third standard to fix two other standards
is a common mistake.
> To be honest, I'd rather kill "Smart Proxy" than "Foreman Proxy" if I
> had to choose just one.
+1 to that, Foreman Proxy would be my choice.
Greg
···
On 17 October 2016 at 14:12, Lukas Zapletal wrote:
>>
>> > This appears more inconsistent than the current situation, as there will
>> > now be three terms, differing between the UI names ("Foreman Smart
>> > Proxy"), API/module names ("smart proxy"), and package names ("foreman
>> > proxy").
>>
>> That's indeed a very true statement, I'll add that the new term aims to
>> be the glue between the other two.
>
> I think I agree with Dominic, a third standard to fix two other
> standards is a common mistake.
>
>> To be honest, I'd rather kill "Smart Proxy" than "Foreman Proxy" if I
>> had to choose just one.
>
> +1 to that, Foreman Proxy would be my choice.
+1 for Foreman Proxy
···
On 10/17/2016 03:26 PM, Greg Sutcliffe wrote:
> On 17 October 2016 at 14:12, Lukas Zapletal > wrote:
IMHO the "Smart" word does not add any useful information to the reader.
···
On Wednesday, November 2, 2016 at 11:30:35 AM UTC+2, Tomas Strachota wrote:
>
> On 10/17/2016 03:26 PM, Greg Sutcliffe wrote:
> > On 17 October 2016 at 14:12, Lukas Zapletal > > <mailto:lz...@redhat.com >> wrote:
> >>
> >> > This appears more inconsistent than the current situation, as there
> will
> >> > now be three terms, differing between the UI names ("Foreman Smart
> >> > Proxy"), API/module names ("smart proxy"), and package names
> ("foreman
> >> > proxy").
> >>
> >> That's indeed a very true statement, I'll add that the new term aims to
> >> be the glue between the other two.
> >
> > I think I agree with Dominic, a third standard to fix two other
> > standards is a common mistake.
> >
> >> To be honest, I'd rather kill "Smart Proxy" than "Foreman Proxy" if I
> >> had to choose just one.
> >
> > +1 to that, Foreman Proxy would be my choice.
>
> +1 for Foreman Proxy
>
> >
> > Greg
> >
> > --
> > 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...@googlegroups.com
> > <mailto:foreman-dev+unsubscribe@googlegroups.com >.
> > For more options, visit https://groups.google.com/d/optout.
>
>
All right, all right. I get that, no Foreman Smart Proxy.
I am not starting rename from Smart proxy to Foreman proxy tho. At
least not this time.
LZ
···
On Thu, Nov 3, 2016 at 8:17 AM, Martin Bačovský wrote:
> +1 for Foreman Proxy
>
>
> On Nov 3, 2016 8:12 AM, wrote:
>>
>> +1 for Foreman Proxy
>>
>> IMHO the "Smart" word does not add any useful information to the reader.
>>
>> On Wednesday, November 2, 2016 at 11:30:35 AM UTC+2, Tomas Strachota >> wrote:
>>>
>>> On 10/17/2016 03:26 PM, Greg Sutcliffe wrote:
>>> > On 17 October 2016 at 14:12, Lukas Zapletal >> > > wrote:
>>> >>
>>> >> > This appears more inconsistent than the current situation, as there
>>> >> > will
>>> >> > now be three terms, differing between the UI names ("Foreman Smart
>>> >> > Proxy"), API/module names ("smart proxy"), and package names
>>> >> > ("foreman
>>> >> > proxy").
>>> >>
>>> >> That's indeed a very true statement, I'll add that the new term aims
>>> >> to
>>> >> be the glue between the other two.
>>> >
>>> > I think I agree with Dominic, a third standard to fix two other
>>> > standards is a common mistake.
>>> >
>>> >> To be honest, I'd rather kill "Smart Proxy" than "Foreman Proxy" if I
>>> >> had to choose just one.
>>> >
>>> > +1 to that, Foreman Proxy would be my choice.
>>>
>>> +1 for Foreman Proxy
>>>
>>> >
>>> > Greg
>>> >
>>> > --
>>> > 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...@googlegroups.com
>>> > .
>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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/d/optout.
>
> --
> 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/d/optout.
