Well, concerning #4, there will be differences in the command-line
interface (as perceived by users), particularly for the Gateway/WAN
(command) support.

On Thu, May 21, 2015 at 1:50 PM, Edin Zulich <[email protected]> wrote:

>
> +1 keep gfsh for both.
>
>
> My reasons:
>
> 1. There is no legal requirement (or any other for that matter) to change
> the name
> 2. The argument for distinguishing between a geode and gemfire
> installation is weak. Some of us have and switch between multiple
> installations of GemFire all the time. There are very simple shell
> environment based mechanisms to deal with this.
> 3. Impact on existing customers should be seriously considered
> 4. Last but not least, the artifact itself is not going to be any
> different between geode and gemfire. Choosing to call it differently in
> gemfire might imply that there is something different about it, when, in
> fact, there isn’t.
>
> Edin
>
>
> On May 21, 2015, at 12:22 PM, Lynn Hughes Godfrey <
> [email protected]> wrote:
>
> > +1 to calling the interactive shell "geode"
> >
> > On Thu, May 21, 2015 at 10:57 AM, Vincent Ford <[email protected]> wrote:
> >
> >> +1 to calling the interactive shell "geode"
> >>
> >> *Vince Ford*
> >> GemFire Sustenance Engineering
> >> Beaverton, OR USA
> >> 503-533-3726 (office)
> >> http://www.pivotal.io
> >> Open Source Project Geode
> >> https://network.pivotal.io/products/project-geode
> >>
> >> On Thu, May 21, 2015 at 10:53 AM, Rajesh Kumar <[email protected]>
> wrote:
> >>
> >>> +1
> >>>
> >>> On Thu, May 21, 2015 at 11:03 PM, Bruce Schuchardt <
> >> [email protected]
> >>>>
> >>> wrote:
> >>>
> >>>> +1
> >>>>
> >>>> Le 5/21/2015 10:05 AM, Brian Dunlap a écrit :
> >>>>
> >>>>> Here's my $0.02:
> >>>>>
> >>>>> I like geode for geode and gfsh for Gemfire.
> >>>>>
> >>>>>
> >>>>>    - At Southwest Airlines, we have a ton of existing environment
> >>>>>    management scripts
> >>>>>    - It's important for users to not cross the streams - - >
> >> explicit =
> >>>>>    good
> >>>>>    - Managing gfsh vs. gsh in existing scripts is error prone.
> >> (think
> >>>>>    about troubleshooting classpath for gfsh vs gsh)
> >>>>>    - We have 50+ developers with gfsh on a PC classpath.  We don't
> >> want
> >>>>> to
> >>>>>    teach them gsh vs. gfsh
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>> Brian -
> >>>>>
> >>>>> On Thu, May 21, 2015 at 11:53 AM, pulkit chandra <
> >>>>> [email protected]>
> >>>>> wrote:
> >>>>>
> >>>>> +1 Gsh.
> >>>>>>
> >>>>>> If called GoSH I won't mind that either :) .
> >>>>>>
> >>>>>> Best Regards,
> >>>>>> *Pulkit Chandra*
> >>>>>>
> >>>>>>
> >>>>>> On Thu, May 21, 2015 at 12:33 PM, Namrata Thanvi <
> [email protected]
> >>>
> >>>>>> wrote:
> >>>>>>
> >>>>>> +1 for gsh
> >>>>>>>
> >>>>>>>
> >>>>>>> Regards,
> >>>>>>> Namrata
> >>>>>>>
> >>>>>>> On Thu, May 21, 2015 at 9:05 PM, Roman Shaposhnik <
> >>> [email protected]
> >>>>>>>>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>> On Thu, May 21, 2015 at 8:32 AM, Tushar Khairnar
> >>>>>>>> <[email protected]> wrote:
> >>>>>>>>
> >>>>>>>>> +1 for gsh
> >>>>>>>>>
> >>>>>>>> +1 to gsh (although I do reserve the right to pronounce it as GoSH
> >>> ;-))
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> Roman.
> >>>>>>>>
> >>>>>>>>
> >>>>
> >>>
> >>
>
>


-- 
-John
503-504-8657
john.blum10101 (skype)

Reply via email to