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 :) http://talk.manageiq.org/t/where-to-run-the-smart-proxy/836 > I suggest to "communicate" it from now on with new official name: > > Foreman Smart Proxy +1 will make an effort to use that term. > > 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: > > (*) https://github.com/theforeman/rfcs/pull/23/files#r83370195 > > -- > Later, > Lukas #lzap Zapletal > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Daniel Lobato Garcia @dLobatog blog.daniellobato.me daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 Keybase: https://keybase.io/elobato -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
