Re: [foreman-dev] Smart or Foreman Proxy? Let's do Foreman Smart Proxy

2016-11-03 Thread Lukas Zapletal
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,

Re: [foreman-dev] Smart or Foreman Proxy? Let's do Foreman Smart Proxy

2016-11-02 Thread Tomas Strachota
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"),

Re: [foreman-dev] Smart or Foreman Proxy? Let's do Foreman Smart Proxy

2016-10-17 Thread Lukas Zapletal
> 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

Re: [foreman-dev] Smart or Foreman Proxy? Let's do Foreman Smart Proxy

2016-10-17 Thread Dominic Cleal
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

Re: [foreman-dev] Smart or Foreman Proxy? Let's do Foreman Smart Proxy

2016-10-14 Thread Daniel Lobato Garcia
On 10/14, 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. It doesn't help that ManageIQ also refers to 'smart proxy' on their docs :)

[foreman-dev] Smart or Foreman Proxy? Let's do Foreman Smart Proxy

2016-10-14 Thread Lukas Zapletal
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"