Where should geode example code live

[Kirk Lund <kl...@apache.org>]

We have some example code that's not in geode-examples.
geode-core-1.0.0-incubating.jar currently contains this package with
examples:

org.geode.gemfire.security.templates

Given that template means something a bit different from example, I'd like
to rename this package to examples. Is this acceptable?

Going forward, this community needs to spend some considerable effort in
improving modularity of geode. The geode-core module should contain only
the bare essentials that are always necessary when using geode. Optional
features and the like should move to their own modules. Along the same line
of thought, examples should move to geode-examples or some similar
sub-module (or even a separate repo). That sub-module should generate a jar
that can be added to the classpath for purposes of demoing or trying out
geode (kicking the tires). I'd like the community to come up with
additional ideas on how to facilitate demoing and also make it easier in
general to try out geode for the first time.

-Kirk

Re: Where should geode example code live

[Udo Kohlmeyer <uk...@pivotal.io>]

+1


On 11/11/16 9:13 am, Jacob Barrett wrote:
> +1
>
> On Thu, Nov 10, 2016 at 11:22 AM Swapnil Bawaskar <sb...@pivotal.io>
> wrote:
>
>> +1
>>
>> On Thu, Nov 10, 2016 at 11:12 AM, Kirk Lund <kl...@pivotal.io> wrote:
>>
>>> Yep! Replace "gemfire" with "geode"
>>>
>>> On Thu, Nov 10, 2016 at 11:07 AM, Kevin Duling <kd...@pivotal.io>
>> wrote:
>>>> +1
>>>>
>>>> Shouldn't that be org.apache.geode.security.examples?
>>>>
>>>> On Thu, Nov 10, 2016 at 11:03 AM, Jinmei Liao <ji...@pivotal.io>
>> wrote:
>>>>> +1 for both renaming it now and moving it to a separate module going
>>>>> forward.
>>>>>
>>>>> On Thu, Nov 10, 2016 at 10:58 AM, Kirk Lund <kl...@apache.org>
>> wrote:
>>>>>> We have some example code that's not in geode-examples.
>>>>>> geode-core-1.0.0-incubating.jar currently contains this package
>> with
>>>>>> examples:
>>>>>>
>>>>>> org.geode.gemfire.security.templates
>>>>>>
>>>>>> Given that template means something a bit different from example,
>> I'd
>>>>> like
>>>>>> to rename this package to examples. Is this acceptable?
>>>>>>
>>>>>> Going forward, this community needs to spend some considerable
>> effort
>>>> in
>>>>>> improving modularity of geode. The geode-core module should contain
>>>> only
>>>>>> the bare essentials that are always necessary when using geode.
>>>> Optional
>>>>>> features and the like should move to their own modules. Along the
>>> same
>>>>> line
>>>>>> of thought, examples should move to geode-examples or some similar
>>>>>> sub-module (or even a separate repo). That sub-module should
>>> generate a
>>>>> jar
>>>>>> that can be added to the classpath for purposes of demoing or
>> trying
>>>> out
>>>>>> geode (kicking the tires). I'd like the community to come up with
>>>>>> additional ideas on how to facilitate demoing and also make it
>> easier
>>>> in
>>>>>> general to try out geode for the first time.
>>>>>>
>>>>>> -Kirk
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Cheers
>>>>>
>>>>> Jinmei
>>>>>

Re: Where should geode example code live

[Jacob Barrett <jb...@pivotal.io>]

+1

On Thu, Nov 10, 2016 at 11:22 AM Swapnil Bawaskar <sb...@pivotal.io>
wrote:

> +1
>
> On Thu, Nov 10, 2016 at 11:12 AM, Kirk Lund <kl...@pivotal.io> wrote:
>
> > Yep! Replace "gemfire" with "geode"
> >
> > On Thu, Nov 10, 2016 at 11:07 AM, Kevin Duling <kd...@pivotal.io>
> wrote:
> >
> > > +1
> > >
> > > Shouldn't that be org.apache.geode.security.examples?
> > >
> > > On Thu, Nov 10, 2016 at 11:03 AM, Jinmei Liao <ji...@pivotal.io>
> wrote:
> > >
> > > > +1 for both renaming it now and moving it to a separate module going
> > > > forward.
> > > >
> > > > On Thu, Nov 10, 2016 at 10:58 AM, Kirk Lund <kl...@apache.org>
> wrote:
> > > >
> > > > > We have some example code that's not in geode-examples.
> > > > > geode-core-1.0.0-incubating.jar currently contains this package
> with
> > > > > examples:
> > > > >
> > > > > org.geode.gemfire.security.templates
> > > > >
> > > > > Given that template means something a bit different from example,
> I'd
> > > > like
> > > > > to rename this package to examples. Is this acceptable?
> > > > >
> > > > > Going forward, this community needs to spend some considerable
> effort
> > > in
> > > > > improving modularity of geode. The geode-core module should contain
> > > only
> > > > > the bare essentials that are always necessary when using geode.
> > > Optional
> > > > > features and the like should move to their own modules. Along the
> > same
> > > > line
> > > > > of thought, examples should move to geode-examples or some similar
> > > > > sub-module (or even a separate repo). That sub-module should
> > generate a
> > > > jar
> > > > > that can be added to the classpath for purposes of demoing or
> trying
> > > out
> > > > > geode (kicking the tires). I'd like the community to come up with
> > > > > additional ideas on how to facilitate demoing and also make it
> easier
> > > in
> > > > > general to try out geode for the first time.
> > > > >
> > > > > -Kirk
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Cheers
> > > >
> > > > Jinmei
> > > >
> > >
> >
>

Re: Where should geode example code live

[Swapnil Bawaskar <sb...@pivotal.io>]

+1

On Thu, Nov 10, 2016 at 11:12 AM, Kirk Lund <kl...@pivotal.io> wrote:

> Yep! Replace "gemfire" with "geode"
>
> On Thu, Nov 10, 2016 at 11:07 AM, Kevin Duling <kd...@pivotal.io> wrote:
>
> > +1
> >
> > Shouldn't that be org.apache.geode.security.examples?
> >
> > On Thu, Nov 10, 2016 at 11:03 AM, Jinmei Liao <ji...@pivotal.io> wrote:
> >
> > > +1 for both renaming it now and moving it to a separate module going
> > > forward.
> > >
> > > On Thu, Nov 10, 2016 at 10:58 AM, Kirk Lund <kl...@apache.org> wrote:
> > >
> > > > We have some example code that's not in geode-examples.
> > > > geode-core-1.0.0-incubating.jar currently contains this package with
> > > > examples:
> > > >
> > > > org.geode.gemfire.security.templates
> > > >
> > > > Given that template means something a bit different from example, I'd
> > > like
> > > > to rename this package to examples. Is this acceptable?
> > > >
> > > > Going forward, this community needs to spend some considerable effort
> > in
> > > > improving modularity of geode. The geode-core module should contain
> > only
> > > > the bare essentials that are always necessary when using geode.
> > Optional
> > > > features and the like should move to their own modules. Along the
> same
> > > line
> > > > of thought, examples should move to geode-examples or some similar
> > > > sub-module (or even a separate repo). That sub-module should
> generate a
> > > jar
> > > > that can be added to the classpath for purposes of demoing or trying
> > out
> > > > geode (kicking the tires). I'd like the community to come up with
> > > > additional ideas on how to facilitate demoing and also make it easier
> > in
> > > > general to try out geode for the first time.
> > > >
> > > > -Kirk
> > > >
> > >
> > >
> > >
> > > --
> > > Cheers
> > >
> > > Jinmei
> > >
> >
>

Re: Where should geode example code live

[Kirk Lund <kl...@pivotal.io>]

Yep! Replace "gemfire" with "geode"

On Thu, Nov 10, 2016 at 11:07 AM, Kevin Duling <kd...@pivotal.io> wrote:

> +1
>
> Shouldn't that be org.apache.geode.security.examples?
>
> On Thu, Nov 10, 2016 at 11:03 AM, Jinmei Liao <ji...@pivotal.io> wrote:
>
> > +1 for both renaming it now and moving it to a separate module going
> > forward.
> >
> > On Thu, Nov 10, 2016 at 10:58 AM, Kirk Lund <kl...@apache.org> wrote:
> >
> > > We have some example code that's not in geode-examples.
> > > geode-core-1.0.0-incubating.jar currently contains this package with
> > > examples:
> > >
> > > org.geode.gemfire.security.templates
> > >
> > > Given that template means something a bit different from example, I'd
> > like
> > > to rename this package to examples. Is this acceptable?
> > >
> > > Going forward, this community needs to spend some considerable effort
> in
> > > improving modularity of geode. The geode-core module should contain
> only
> > > the bare essentials that are always necessary when using geode.
> Optional
> > > features and the like should move to their own modules. Along the same
> > line
> > > of thought, examples should move to geode-examples or some similar
> > > sub-module (or even a separate repo). That sub-module should generate a
> > jar
> > > that can be added to the classpath for purposes of demoing or trying
> out
> > > geode (kicking the tires). I'd like the community to come up with
> > > additional ideas on how to facilitate demoing and also make it easier
> in
> > > general to try out geode for the first time.
> > >
> > > -Kirk
> > >
> >
> >
> >
> > --
> > Cheers
> >
> > Jinmei
> >
>

Re: Where should geode example code live

[Kevin Duling <kd...@pivotal.io>]

+1

Shouldn't that be org.apache.geode.security.examples?

On Thu, Nov 10, 2016 at 11:03 AM, Jinmei Liao <ji...@pivotal.io> wrote:

> +1 for both renaming it now and moving it to a separate module going
> forward.
>
> On Thu, Nov 10, 2016 at 10:58 AM, Kirk Lund <kl...@apache.org> wrote:
>
> > We have some example code that's not in geode-examples.
> > geode-core-1.0.0-incubating.jar currently contains this package with
> > examples:
> >
> > org.geode.gemfire.security.templates
> >
> > Given that template means something a bit different from example, I'd
> like
> > to rename this package to examples. Is this acceptable?
> >
> > Going forward, this community needs to spend some considerable effort in
> > improving modularity of geode. The geode-core module should contain only
> > the bare essentials that are always necessary when using geode. Optional
> > features and the like should move to their own modules. Along the same
> line
> > of thought, examples should move to geode-examples or some similar
> > sub-module (or even a separate repo). That sub-module should generate a
> jar
> > that can be added to the classpath for purposes of demoing or trying out
> > geode (kicking the tires). I'd like the community to come up with
> > additional ideas on how to facilitate demoing and also make it easier in
> > general to try out geode for the first time.
> >
> > -Kirk
> >
>
>
>
> --
> Cheers
>
> Jinmei
>

Re: Where should geode example code live

[Jinmei Liao <ji...@pivotal.io>]

+1 for both renaming it now and moving it to a separate module going
forward.

On Thu, Nov 10, 2016 at 10:58 AM, Kirk Lund <kl...@apache.org> wrote:

> We have some example code that's not in geode-examples.
> geode-core-1.0.0-incubating.jar currently contains this package with
> examples:
>
> org.geode.gemfire.security.templates
>
> Given that template means something a bit different from example, I'd like
> to rename this package to examples. Is this acceptable?
>
> Going forward, this community needs to spend some considerable effort in
> improving modularity of geode. The geode-core module should contain only
> the bare essentials that are always necessary when using geode. Optional
> features and the like should move to their own modules. Along the same line
> of thought, examples should move to geode-examples or some similar
> sub-module (or even a separate repo). That sub-module should generate a jar
> that can be added to the classpath for purposes of demoing or trying out
> geode (kicking the tires). I'd like the community to come up with
> additional ideas on how to facilitate demoing and also make it easier in
> general to try out geode for the first time.
>
> -Kirk
>



-- 
Cheers

Jinmei