Re: [CONF] Geode > Release Steps

[Greg Chase]

Agree this is not part of "Apache Geode (incubating, or hatched)" release
process.

This is about propagating to known users, consumers, and adopters.

Maybe its time to put together a "powered by" page with direct links to
their latest releases.

This would also help serve as a propagation / communication check list.

-Greg

On Thu, Oct 27, 2016 at 12:19 PM, Swapnil Bawaskar 
wrote:

> Ok, I am going to replace steps 14 and 15 with:
> Work with the community to update the docker image, homebrew, macports,
> YCSB,
> Zeppelin, spring-data-geode.
>
> On Thu, Oct 27, 2016 at 12:00 PM, Anthony Baker  wrote:
>
> > Since homebrew and macports are external to ASF I don’t think we should
> > call them out in the release steps.  I do think it makes sense to inform
> > contributors in other communities (like homebrew, YCSB, Zeppelin, Spring,
> > etc) and help them upgrade to new releases.
> >
> > Anthony
> >
> >
> > > On Oct 27, 2016, at 11:43 AM, Swapnil Bawaskar (Confluence) <
> > conflue...@apache.org> wrote:
> > >
> > >  <
> https://cwiki.apache.org/
> > confluence/display/~swapnil.bawaskar?src=mail
> > timestamp=1477593839173=com.
> > atlassian.confluence.plugins.confluence-content-
> > notifications-plugin%3Apage-edited-notification=
> > 8aa980874e36a1eb014e36a2a5663b27> Swapnil Bawaskar edited a page
> > >
> > >   > Release+Steps?src=mail=1477593839173&
> > src.mail.notification=com.atlassian.confluence.plugins.
> confluence-content-
> > notifications-plugin%3Apage-edited-notification=
> > 8aa980874e36a1eb014e36a2a5663b27=view>Release
> > Steps  > Release+Steps?src=mail=1477593839173&
> > src.mail.notification=com.atlassian.confluence.plugins.
> confluence-content-
> > notifications-plugin%3Apage-edited-notification=
> > 8aa980874e36a1eb014e36a2a5663b27=view>
> > > ...
> > > Send a [DISCUSS] to dev@geode.incubator.apache.org  > dev@geode.incubator.apache.org>.
> > > Create a release candidate (see below).
> > > Send a [VOTE] to dev@geode.incubator.apache.org  > dev@geode.incubator.apache.org>.  See the template at Release vote
> > template .
> > Example  > dev/201601.mbox/%3cBY2PR10MB0615E804A4F4C0C9D4606339B6D90@BY2PR10MB0615.
> > namprd10.prod.outlook.com%3e>.
> > > Wait for the vote to complete and send a [RESULT][VOTE] to
> > dev@geode.incubator.apache.org .
> > Example  > dev/201602.mbox/%3cbac1def2-50fa-4037-b22d-3b7bfdca4...@pivotal.io%3e>:
> > > If the vote fails, fix the issues and goto 2.
> > > Send a [VOTE] to gene...@incubator.apache.org.  > gene...@incubator.apache.org.>Example  > org/mod_mbox/incubator-general/201602.mbox/%3c7AC725D7-ECEC-45FF-95AE-
> > bd77d1b18...@pivotal.io%3e>.
> > > Wait for the vote to complete (need 3 binding +1 votes) and send a
> > [RESULT][VOTE] to gene...@incubator.apache.org.  general@incubator.
> > apache.org.>Example  > general/201601.mbox/%3cCA+5xAo3fvEDU8BhjqXg9OwxDVT7c0c0R
> > cyj_vgpuicqoufg...@mail.gmail.com%3e>.
> > > If the vote fails, fix the issues and goto 2.
> > > Finalize the release (see below).
> > > Mark the JIRA version as released.
> > > Wait for the release to propagate to the mirrors (may take 1-2 days).
> > > Update the website source (geode-site/website/content/
> releases/index.html)
> > with the download links.
> > > Publish javadocs to the incubator website.
> > > Build website from sources as described in
> geode-site/website/README.md.
> > > In the generated site, create the directory
> geode-site/content/releases/
> > latest.
> > > Obtain a copy of the javadoc directory from the binary build and put it
> > in the geode-site/content/releases/latest directory (link from the
> > website's Docs landing page points to ../releases/latest/javadoc).
> > > Deploy the generated site by checking it into the asf-site branch of
> the
> > apache-geode repo.
> > > Build the docker image and upload.  TBD
> > > Update Homebrew and macports. TBD
> > > Send an [ANNOUNCE] to gene...@incubator.apache.org  > gene...@incubator.apache.org>, annou...@apache.org  > annou...@apache.org>, dev@geode.incubator.apache.org  > dev@geode.incubator.apache.org>, and u...@geode.incubator.apache.org.
> >   Example <
> > http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%
> > 3c9f324b22-c208-45e6-ad2c-cfd899a93...@hortonworks.com%3e>.
> > > ...
> > >  > resources:view-page-email-adg-footer-item:icon.png> <
> > https://cwiki.apache.org/confluence/display/GEODE/
> > Release+Steps?src=mail=1477593839173&
> > src.mail.notification=com.atlassian.confluence.plugins.
> confluence-content-
> > 

Re: [DISCUSS] Graduation

[Greg Chase]

+1

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Oct 25, 2016, at 5:25 PM, Roman Shaposhnik  wrote:
> 
> Hi!
> 
> with the 1.0.0-incubating release officially out (huge kudos
> to the team!) I think it is time we officially start our graduation
> discussion. Process-wise graduation consists of drafting
> a board resolution, getting it approved by the IPMC and finally
> submitting it to the ASF board's consideration. At the very minimum
> your resolution will contain:
>1. A name of the project (I assume that'll be Geode)
>2. A list of proposed PMC
>3. A proposed PMC chair
> A good example of a resolution can be found here:
>http://markmail.org/message/7ow2kdqa3rdx3x5k
> 
> On #2 my suggestion would be to have an opt-in system. Basically
> we will kick off the thread off on private@geode asking current PPMC
> members if they are willing to continue on the PMC.
> 
> On #3 I typically recommend podlings I mento to setup a rotating chair
> policy. This is, in no way, an ASF requirement so feel free to ignore it,
> but it worked well before. The chair will be expected up for rotation every
> year. It will be more that ok for the same person to self-nominate once
> the year is up -- but at the same time it'll be up to the same person to
> actually kick off a thread asking if anybody else is interested in serving
> as a chair for the next year. Of course, if there multiple candidates there
> will have to be a vote.
> 
> Speaking of self-nomination -- the same thread that we're going to kick
> off as part of solving for #2 will ask for folks to self-nominate as an 
> initial
> chair to be listed on the resolution.
> 
> Unless somebody objects strongly to my #2 and #3 proposals I'm going
> to kick of this thread on private@.
> 
> With that in mind, lets make the rest of the discussion on dev@ to be about
> collecting the datapoints to present to IPCM as part of us asking them to
> vote YES on our graduation. You can see my initial list of these data points
> below. Please, please add yours:
> 
> Project status:
> http://incubator.apache.org/projects/geode.html
> 
> Maturity assessment:
> https://cwiki.apache.org/confluence/display/GEODE/Geode+Podling+Maturity+Assessment
> 
> 4 releases
> 
> 2734 commits on develop
> 269 PR”s
> 92 contributors across all branches
> 
> dev list averaged ~650 msgs/month in 2016
> user list averaged ~90 msgs/month in 2016
> 267 unique posters
> 
> 1900 issues created
> 1230 issues resolved
> 
> 6 new committers / PPMC members added
> 
> Quick bump:  as far as committer diversity goes here’s the picture:
> 
> committer domains
> reasonably active
>  pivotal.io
>  kollective.com (Mark Bretl)
>  ampool.io
>  silverspringnet.com (Sai Boorlagadda)
> 
> inactive
>  snappydata.io
>  newrelic.com (Qihong)
>  google.com (Sourabh)
>  microsoft.com (Ashvin)
>  weave.works (Stuart)
>  elastic.co (Catherine)
>  dell.com (Lyndon, …)
>  vmware.com
>  brsg.io
>  cobaltdigital.marketing
>  cdkglobal.com
>  dev9.com
> 
> Thanks,
> Roman.

Re: From Incubation to TLP

[Greg Chase]

With the number of hats you have Roman, you can satisfy any diversity 
requirement...

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Sep 30, 2016, at 8:27 PM, Roman Shaposhnik  wrote:
> 
> On Thu, Sep 29, 2016 at 12:22 AM, Niall Pemberton
>  wrote:
>> On Thu, Sep 29, 2016 at 3:33 AM, Anthony Baker  wrote:
>> 
>>> Hi Niall!
>>> 
>>> Thanks for your really helpful input.  I agree that development of an
>>> active, stable, and diverse community that understands and practices the
>>> Apache Way is a primary indicator of readiness for graduation.  Do you (or
>>> any lurking mentors) have any thoughts on how similar projects have
>>> demonstrated community diversity?
>>> 
>> 
>> I found the last big debate on this on general@incubator (the Ignite
>> graduation) and looks like those diversity criteria are redundant:
>> 
>>- http://markmail.org/message/555sxkvkpbzrbvnd
>>- http://markmail.org/message/5l5hsygvntcx5fqb
> 
> Yup. Or may be its not that they are redundant, but rather the whole
> framing around diversity is a bit off. The way I look at it is this: the
> real goal is to make sure that the community is open, inclusive, collaborative
> and welcomes anybody regardless of their affiliation. Having a super
> diverse community is one way to qualify. But I think even less diverse
> communities can be seen to take "Apache Way" governance model to
> heart. And with my Geode's mentor hat on I can definitely say that Geode
> community has come a long way and is definitely ready from that
> standpoint.
> 
> Thanks,
> Roman.

Re: [ANNOUNCE] Donation of Geode documentation

[Greg Chase]

On Fri, Sep 30, 2016 at 10:28 AM, Karen Miller  wrote:

> I'd love to see the docs included in 1.0.


+1 - and although it might cause a delay in releasing, it will make for a
much more complete user experience.

Re: [VIDEO] Replay of Geode Clubhouse - Domain Driven Design & Reactive Programming w/ Apache Geode - Discussion Panel

[Greg Chase]

Thanks again to Vaughn Vernon and Wes Williams for talking with the Geode
Community.

Here is the replay of our discussion on Youtube
<https://youtu.be/lZf4O_XFXw0>, and a link to download the video for your
offline viewing pleasure
<https://www.dropbox.com/s/s1b8lkzkpxqotco/Geode_In_DDD_and_Reactive.m4v?dl=0>
.

And here is specific table of contents if you want to jump to a specific
part of the conversation on Youtube.

00:09 Introductions <https://youtu.be/lZf4O_XFXw0?t=9s>
03:15 How do in-memory data grids fit with DDD?
<https://youtu.be/lZf4O_XFXw0?t=3m15s>
09:00 What is CQRS, and when to use it?
<https://youtu.be/lZf4O_XFXw0?t=9m0s>
17:00 Using PDX to avoid jar file dependencies between bounded contexts
<https://youtu.be/lZf4O_XFXw0?t=17m0s>
22:56 Reactive programming and its fit with DDD
<https://youtu.be/lZf4O_XFXw0?t=22m56s>
28:25 How Geode fits with reactive programming
<https://youtu.be/lZf4O_XFXw0?t=28m25s>
32:08 How can Geode become more reactive?
<https://youtu.be/lZf4O_XFXw0?t=32m08s>

On Tue, Sep 20, 2016 at 10:49 AM, Gregory Chase <gch...@pivotal.io> wrote:

> Dear Geode Community,
> This is a reminder that tomorrow we have Vaughn Vernon and Wes Williams
> joining us for a further discussion of Domain Driven Design and reactive
> programming.
>
> This is a follow on of the Webinar recently run by Pivotal: Why
> Domain-Driven Design and Reactive Programming?
> <https://pivotal.io/agile/webinar/domain-driven-design-and-reactive-programming?mkt_tok=eyJpIjoiT0RFd1lXWmhNR1F4TlRkaiIsInQiOiJva2xJbDV0WXZIMGNRSEl0alRaNEh4c3RvWXRyNmVKcG1OMXA1eTJzbVB2eVJKUUMydmR5TjBqTXJqOHJQc3AyK3ZZMHRpXC9BOXY2b1U4eVwvWEVSVm53PT0ifQ%3D%3D>
>  This
> replay is now available and does not require registration.
>
> Also, please note that this Geode Clubhouse has been moved to one hour
> later than previously announced. (Now 10AM Pacific instead of 9AM Pacific).
>
> This meeting will kickoff on Weds, Sept 21 at 10AM Pacific
> <https://www.google.com/calendar/event?eid=ZnFpcTNrdTNkYWl2ZmE2MDcwdTNrdDc5a28gcGl2b3RhbC5pb191OGtndnVhaGprYm9oMWduZmh2NXRzMnY5Y0Bn=America/Los_Angeles>
>  <-
> add to your calendar.
>
> Note that we have a new meeting platform.  Here's how to join:
>
> This meeting is being run with Zoom.  If its your first time using it, you
> will be prompted to download their meeting client.
>
> Video & audio streaming: Join from PC, Mac, Linux, iOS or Android:
> https://pivotal.zoom.us/j/540483502
>
> Optional phone audio connection:
>
> Or iPhone one-tap (US Toll):  +14086380968,540483502# or +16465588656
> ,540483502#
>
> Or Telephone:
> Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
> Meeting ID: 540 483 502
> International numbers available: https://pivotal.
> zoom.us/zoomconference?m=Jnvh-1uWfqE95Tb4M9AwS9X7P9oPTlfH
>
>
> On Wed, Sep 14, 2016 at 10:44 AM, Gregory Chase <gch...@pivotal.io> wrote:
>
>> Dear Geode Community,
>> I'm super excited to have Vaughn Vernon and Wes Williams joining the next
>> Geode Clubhouse for a discussion about Domain Driven Design & Reactive
>> programming in context with Apache Geode.
>>
>> This meeting will kickoff on Weds, Sept 21 at 10AM Pacific
>> <https://www.google.com/calendar/event?eid=ZnFpcTNrdTNkYWl2ZmE2MDcwdTNrdDc5a28gcGl2b3RhbC5pb191OGtndnVhaGprYm9oMWduZmh2NXRzMnY5Y0Bn=America/Los_Angeles>
>>  <-
>> add to your calendar.
>>
>> This meeting is a follow on of the webinar running today at 11AM Pacific
>> <https://pivotal.io/agile/webinar/domain-driven-design-and-reactive-programming>.
>> I will reply with a replay link for this webinar when its available.
>>
>> Note that we have a new meeting platform.  Here's how to join:
>>
>> This meeting is being run with Zoom.  If its your first time using it,
>> you will be prompted to download their meeting client.
>>
>> Video & audio streaming: Join from PC, Mac, Linux, iOS or Android:
>> https://pivotal.zoom.us/j/540483502
>>
>> Optional phone audio connection:
>>
>> Or iPhone one-tap (US Toll):  +14086380968,540483502# or +16465588656
>> ,540483502#
>>
>> Or Telephone:
>> Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
>> Meeting ID: 540 483 502
>> International numbers available: https://pivotal.zoom.us/zoomco
>> nference?m=Jnvh-1uWfqE95Tb4M9AwS9X7P9oPTlfH
>>
>>
>>
>> --
>> Greg Chase
>>
>> Global Head, Big Data Communities
>> http://www.pivotal.io/big-data
>>
>> Pivotal Software
>> http://www.pivotal.io/
>>
>> 650-215-0477
>> @GregChase
>> Blog: http://geekmarketing.biz/
>>
>>
>
>
> --
> Greg Chase
>
> Global Head, Big Data Communities
> http://www.pivotal.io/big-data
>
> Pivotal Software
> http://www.pivotal.io/
>
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/
>
>

Re: Geode Community > Events List

[Greg Chase]

No, thank you Joey!

On Thu, Sep 15, 2016 at 4:27 PM, Joey McAllister <jmcallis...@pivotal.io>
wrote:

> Thanks, Greg!
>
> On Thu, Sep 15, 2016 at 4:24 PM Greg Chase <g...@gregchase.com> wrote:
>
> > Geode Clubhouse: DDD, Reactor Programming and Apache Geode Panel wth
> Vaughn
> > Vernon
> > Virtual | Calendar entry
> > <
> > https://www.google.com/calendar/event?eid=ZnFpcTNrdTNkYWl2ZmE2MDcwdTNrdD
> c5a28gcGl2b3RhbC5pb191OGtndnVhaGprYm9oMWduZmh2NXRzMnY5Y0Bn&
> ctz=America/Los_Angeles
> > >
> > 9/21 - 9AM Pacific
> >
> > Geode Clubhouse: Update on Geode's New Security Infrastructure with
> Jinmei
> > Liao
> > Virtual | Calendar entry
> > <
> > https://www.google.com/calendar/event?eid=bnM3ODdjYms2bm05aDJwYnJrYnBrb2
> Q2YnMgcGl2b3RhbC5pb191OGtndnVhaGprYm9oMWduZmh2NXRzMnY5Y0Bn&
> ctz=America/Los_Angeles
> > >
> > 10/19 - 9AM Pacific
> >
> > On Thu, Sep 15, 2016 at 4:15 PM, Joey McAllister <jmcallis...@pivotal.io
> >
> > wrote:
> >
> > > Hi all,
> > >
> > > Are there any upcoming Geode-related events that would be a good fit
> for
> > > the Community <http://geode.incubator.apache.org/community/> > Events
> > > section of the website? If so, I'd be happy to add them. (The three
> > > currently listed took place in January, February, and March of this
> > year.)
> > >
> > > It looks like the template is:
> > > - Event Name
> > > - Event City, Country
> > > - Event Date
> > > - If applicable, 1-2 Geode-related presentation titles and links to
> more
> > > info.
> > >
> > > Cheers,
> > > Joey
> > >
> >
>

Re: Fwd: Kafka Ingester

[Greg Chase]

On Wed, Jul 27, 2016 at 6:39 PM, Greg Chase <g...@gregchase.com> wrote:

> Hello everyone.  We have a community call tomorrow at 9AM Pacific.  Would
> you be interested in discussing this after your educational topic?
>

After *OUR* educational topic - Geode events & continuous query...

Re: Fwd: Kafka Ingester

[Greg Chase]

Hello everyone.  We have a community call tomorrow at 9AM Pacific.  Would
you be interested in discussing this after your educational topic?

-Greg

On Wed, Jul 27, 2016 at 5:46 PM, theseusyang  wrote:

>
> Olivier, it looks like good!
>
>
>
>
> --
> View this message in context:
> http://apache-geode-incubating-developers-forum.70738.x6.nabble.com/Fwd-Kafka-Ingester-tp6407p7469.html
> Sent from the Apache Geode (Incubating) Developers Forum mailing list
> archive at Nabble.com.
>

Re: Geode website tagged with minor Apache branding issue in audit

[Greg Chase]

On Fri, Jul 1, 2016 at 10:41 AM, William Markito 
wrote:

> We had a similar feedback from Niall during the first rollout of the
> website and then we increased the font-size of the disclaimer and the size
> of the incubator logo.
>
> I'd agree with Dave and we should definitely improve but with a more proper
> specifics to nail it.


The reviewer admits there is not a consensus on what a more specific
guideline should be.  Personally I think our rendering should be sufficient
in absence of that consensus.  To do more things would require pretty
significant changes to our web design concept.

Re: Geode website tagged with minor Apache branding issue in audit

[Greg Chase]

That is good feedback for their feedback.

On Fri, Jul 1, 2016 at 9:10 AM, Dave Barnes <dbar...@pivotal.io> wrote:

> My first question is what's the goal - is there another ASF site that would
> serve as an example to follow?
> Our current Apache info is a menu item at the bottom of the page. From the
> report, I gather that the auditor wants to see the logos and disclaimer
> "above the fold". More prominent logos can be easily done, once we agree on
> where they should be located.
> Can I safely assume that a [link to the disclaimer] is sufficient?
> The branding guide (http://incubator.apache.org/guides/branding.html)
> lacks
> specifics.
>
> On Thu, Jun 30, 2016 at 9:20 PM, Greg Chase <gregch...@apache.org> wrote:
>
> > Dear Geode community,
> > I see the Apache Geode website got tagged with a minor branding concern
> in
> > a recent audit of incubating projects.
> >
> > See the wiki entry here:
> > https://wiki.apache.org/incubator/BrandingAuditJune2016
> >
> > See start of the thread in gene...@incubator.apache.org here:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/201606.mbox/%3CCAOqetn-c49sfXSMck8hx%3DjGZQEw6paEmbdtMg32meLkHKcTPnQ%40mail.gmail.com%3E
> >
> > Basically the Apache & Apache incubator logos, and the incubator
> disclaimer
> > are not prominent enough, but at least they are present.
> >
> > Next time we look at a website update, we might see how we can make these
> > more obvious.
> >
> > Suggestions are welcome on this thread.
> >
> > -Greg
> >
>

Geode website tagged with minor Apache branding issue in audit

[Greg Chase]

Dear Geode community,
I see the Apache Geode website got tagged with a minor branding concern in
a recent audit of incubating projects.

See the wiki entry here:
https://wiki.apache.org/incubator/BrandingAuditJune2016

See start of the thread in gene...@incubator.apache.org here:
http://mail-archives.apache.org/mod_mbox/incubator-general/201606.mbox/%3CCAOqetn-c49sfXSMck8hx%3DjGZQEw6paEmbdtMg32meLkHKcTPnQ%40mail.gmail.com%3E

Basically the Apache & Apache incubator logos, and the incubator disclaimer
are not prominent enough, but at least they are present.

Next time we look at a website update, we might see how we can make these
more obvious.

Suggestions are welcome on this thread.

-Greg

Re: Apache Geode incubation

[Greg Chase]

The community is of course thinking about it. That is the point of the 
Incubator program.

However, I imagine we will be asking about graduation after the release of 
Geode 1.0 GA.

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Jun 21, 2016, at 6:49 AM, Dor Ben Dov  wrote:
> 
> Hi, 
> General speaking, what is the status of geode incubation in apache at the 
> moment, when will it be switched to Apache TLP  ? 
> 
> Dor
> 
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp

Support for Apache Geode in Apache Zest

[Greg Chase]

Dear Geode contributors,
I just got some detail about support for Apache Geode by Apache Zest in its
persistence abstraction.  It will be a while before they have a new
release, but this support is available in their github already.

Here is the implementation,
https://github.com/apache/zest-java/blob/develop/extensions/entitystore-geode/src/main/java/org/apache/zest/entitystore/geode/GeodeEntityStoreMixin.java

AND the configuration options that are supported initially can be seen in;
https://github.com/apache/zest-java/blob/develop/extensions/entitystore-geode/src/main/java/org/apache/zest/entitystore/geode/GeodeConfiguration.java


What does this mean? Well, Zest has a persistence abstraction for its
runtime model, and users can swap out any of the other Entity Stores
without code changes beyond the "assembly" (start up).

Entities are declared like this;

public interface Book
{
@Optional
Property isbn();

@Immutable
Property title();

@Immutable
Association author();

@UseDefaults
ManyAssociation reviews();

@UseDefaults
NamedAssociation distributors();
}

We can then do

@UnitOfWorkPropagation(MANDATORY)
public void createNewBook( String title, Author author )
{
UnitOfWork uow = unitOfWorkFactory.currentUnitOfWork() )
EntityBuilder builder = uow.newEntityBuilder(Book.class);
builder.instance().title().set( title );
builder.instance().author().set( author );
builder.newInstance();
}

No implementation class needed for the Book interface. But if we had
additional methods on the Book interface, we can assign one or more
"Mixins", and each mixin can handle one or more of those methods.

Regards,

-Greg

Do we want a "theme song" for Geode Cluhouse?

[Greg Chase]

Dear Geode Community,
In a hallway conversation with one of the committers, I got asked, "How
come Geode doesn't get a theme song".  They pointed to some work I do for
the Greenplum Community in running their virtual meetings:
https://www.youtube.com/watch?v=S9nHSKBSrlg

So, I'm very happy to bring in a theme song for the community.  We just
need to know what people would want to use.

The constraints are that these would need to be music tracks, probably on
Sound Cloud, released under a Creative Common's license permitting reuse
without royalty, and with modification.

I don't mind attributing the creator if I'm producing the video.

So my ask to the Geode community is - please nominate some sound tracks to
use as bumper music for Geode videos..

Here's one nomination by me.  I happen to know the composer, and although I
can't find the license he released for this track, I'm sure he'll publish a
version under CC for our usage if we ask:
https://soundcloud.com/choirshark/bongo1110

Re: Its been a year....

[Greg Chase]

Can someone cook up a birthday cake?

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Apr 27, 2016, at 12:27 PM, Roman Shaposhnik  wrote:
> 
> Hear! Hear! An amazing community journey!
> 
> Here's to the TLP and world domination! ;-)
> 
> Thanks,
> Roman.
> 
>> On Wed, Apr 27, 2016 at 11:31 AM, Anilkumar Gingade  
>> wrote:
>> Hi Geode,
>> 
>> Thought of sharing this milestone...
>> 
>> Wow...Its been a year...In last year ApacheCON (Apr 2015) we announced open
>> sourcing Geode, we made the Geode source available to the Apache
>> community...Its been a great journey from that point...
>> 
>> The geode community is growing and contributing to the Geode code
>> base...Thanks to all the developers and community, we have successfully
>> achieved two milestone releases and heading towards Graduations...
>> 
>> Great work team and contributors...
>> 
>> Thanks,
>> -Anil.
>> 
>> 
>> 
>> 

Re: Incubator status report on wiki?

[Greg Chase]

Yes please 

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Apr 8, 2016, at 1:05 PM, Michael Stolz  wrote:
> 
> Should the geode incubator status report be posted on the geode wiki under
> "Incubation Status Reports"?
> 
> --
> Mike Stolz
> Principal Engineer, GemFire Product Manager
> Mobile: 631-835-4771

Re: [GitHub] incubator-geode pull request: GEODE-1151 Add new committer to list...

[Greg Chase]

Please add Nitin Lamba too.

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Mar 30, 2016, at 4:15 PM, karensmolermiller  wrote:
> 
> GitHub user karensmolermiller opened a pull request:
> 
>https://github.com/apache/incubator-geode/pull/120
> 
>GEODE-1151 Add new committer to list on web page
> 
>Dave Barnes is a new committer to Geode. This PR adds his name
>to the list of committers on the Community web page.  To make
>the web page pretty, it also does a minor alteration to
>rebalance the number of names per column.
> 
> You can merge this pull request into a Git repository by running:
> 
>$ git pull https://github.com/karensmolermiller/incubator-geode 
> feature/GEODE-1151
> 
> Alternatively you can review and apply these changes as the patch at:
> 
>https://github.com/apache/incubator-geode/pull/120.patch
> 
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
> 
>This closes #120
> 
> 
> commit 3e295f98367de470b54a3c9008e10b094432a5be
> Author: Karen Miller 
> Date:   2016-03-30T23:02:22Z
> 
>GEODE-1151 Add new committer to list on web page
> 
>Dave Barnes is a new committer to Geode. This PR adds his name
>to the list of committers on the Community web page.  To make
>the web page pretty, it also does a minor alteration to
>rebalance the number of names per column.
> 
> 
> 
> 
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---

New Committer to Apache Geode: Nitin Lamba

[Greg Chase]

Please welcome *Nitin Lamba* as a new committer to the Apache Geode
project!

Nitin has already been an avid contributor to the enhancement of Apache
Geode, most notably serving as the release manager for the first offiical
release of Apache Geode.

Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should enable better
productivity.

Thanks to Nitin for his prior and future contributions to the amazing
Apache Geode technology!

-Greg

Re: Hello Brian - tangent off [VOTE] RC2: Apache Geode (Incubating) first Milestone release - v1.0.0-incubating.M1

[Greg Chase]

Brian,
You are not new to the Geode community - you were with us when we announced
Apache Geode (incubating) at ApacheCon in Austin.

However, we appreciate your helping us prove our first release candidate!

All your contributions are very welcome!

-Greg

On Mon, Feb 1, 2016 at 12:14 AM, Brian Dunlap  wrote:

> Hi everyone -
>
> I'm new to the Geode community - not sure if this impacts the M1 RC2
> decision.
>
> Today, while trying a clean build against rel/v1.0.0-incubating.M1.RC2, I'm
> getting this failure:
>
> :gemfire-core:test
>
>
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest
> > testMulticastTest FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
>
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest.testMulticastTest(JGroupsMessengerJUnitTest.java:818)
>
> 1850 tests completed, 1 failed, 35 skipped
>
> I was following the build instructions from github and running these
> targets:
> gradle build installDist
>
> Since the build fails, no worky-worky on kicking the tires.
>
> Any suggestions?
>
> I'm on the latest Java 8 JDK (71)  and running on El Capitan (10.11.3)
>
>
> Thanks!
> Brian -
>
>
> On Sun, Jan 31, 2016 at 10:44 AM, Niall Pemberton <
> niall.pember...@gmail.com
> > wrote:
>
> > +1 from me for this release.
> >
> >  * I checked the DISCLAIMER, LICENSE & NOTICE files
> >  * I check the sigs & checksums
> >  * I ran a build on the source distro
> >
> > Niall
> >
> > On Wed, Jan 27, 2016 at 8:21 PM, Nitin Lamba  wrote:
> >
> > > All,
> > >
> > > This is the second release candidate of the first release for Apache
> > > Geode, version 1.0.0-incubating.M1. Thanks to all the community members
> > to
> > > drive towards this milestone!
> > >
> > > It fixes the following issues:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420=12334248
> > >
> > > Compared to first release candidate (RC1), it fixes the following
> issues:
> > > [GEODE-610] - Review Geode's LICENSE & NOTICE File(s)
> > > [GEODE-769] - improve README.md file
> > > [GEODE-815] - RC Feedback: Fix LICENSE and NOTICE files
> > >
> > > *** Please download, test and vote by Monday, February 01, 0800 hrs US
> > > Pacific.
> > >
> > > Note that we are voting upon the source (tag):
> > >rel/1.0.0-incubating.M1.RC2
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.M1.RC2
> > > <
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.M1.RC1
> > > >
> > >
> > > Commit ID: c26334542fa9e90daff5f58467d6e174b3e0f3e2
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=commit;h=c26334542fa9e90daff5f58467d6e174b3e0f3e2
> > >
> > > Source and binary files:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M1.RC2/
> > >
> > > For the first release, the documentation on how to install and use
> Apache
> > > Geode are hosted on pivotal.io:
> > >http://geode.docs.pivotal.io
> > >
> > > Maven staging repo:
> > >
> > https://repository.apache.org/content/repositories/orgapachegeode-1001/
> > >
> > > Geode's KEYS file containing PGP keys we use to sign the release:
> > >
> > >
> >
> https://github.com/apache/incubator-geode/blob/release/1.0.0-incubating.M1/KEYS
> > >
> > > Release Key: pub  4096R/C72CFB64 2015-10-01
> > > Fingerprint: 948E 8234 14BE 693A 7F74  ABBE 19DB CAEE C72C FB64
> > >
> > > Thanks,
> > > Anthony & Nitin (on behalf of the Geode team)
> > >
> >
>

Re: Proposal: Move Events to a non-Repo website

[Greg Chase]

+1 for supporting Brazilian Holidays

+1 for a calendar service that makes it easier for the community to
contribute events.

On Tue, Jan 26, 2016 at 3:26 PM, Dave Barnes  wrote:

> First pass, using the calendar of Brazilian Holidays - look just below the
> Pivotal events:
>
> http://ec2-52-33-216-127.us-west-2.compute.amazonaws.com/community/
>
> On Tue, Jan 26, 2016 at 7:43 AM, Nitin Lamba  wrote:
>
> > +1 for data-driven event calendar! William's suggested solution is
> > available as a jQuery plugin [1].
> >
> > Nitin
> >
> > [1]
> >
> http://www.jqueryscript.net/social-media/jQuery-Plugin-To-Display-Google-Calendar-Feeds-On-Your-Website.html
> >
> > 
> > From: William Markito 
> > Sent: Tuesday, January 26, 2016 12:00 AM
> > To: dev@geode.incubator.apache.org
> > Subject: Re: Proposal: Move Events to a non-Repo website
> >
> > Hi Dave,  I think it's a great idea!  In fact, I'd rather have it some
> how
> > (javascript ?) pull that data from a Google Calendar feed or something
> like
> > that to automate the updates.
> >
> > +1
> >
> > On Mon, Jan 25, 2016 at 4:34 PM Dave Barnes  wrote:
> >
> > > RFF (Request for Feedback)
> > >
> > > Apache Geode website design suggestion: Replace the volatile Events
> > section
> > > of the Geode website with a link to a community events site that's not
> > part
> > > of the Apache Geode source code repo. That way, the events can be
> updated
> > > quickly by community members without the delay, overhead, and potential
> > > code corruption resulting from updating calendar items in the code
> repo.
> > >
> >
>

Re: [VOTE] Apache Geode (Incubating) first Milestone release - v1.0.0-incubating.M1

[Greg Chase]

On Wed, Jan 20, 2016 at 9:23 AM, Michael Stolz  wrote:

> What caused it to have such a short deadline? Did we do something to cause
> it to be so short or is that the default and we just didn't know to
> override it somehow?
>
>
Why we're still "incubating".

Its our first candidate for our first release.  We're learning to walk :)

Re: [ANNOUNCE] Donation of GemFire WAN and CQ code

[Greg Chase]

I believe I heard that GemFire has a .NET client that is not part of Apache
Geode.

On Tue, Jan 19, 2016 at 10:16 PM, Catherine Johnson <
catherine...@yahoo.com.invalid> wrote:

> Are there still bits that are only included with the commercial product
> GemFire? Or is everything open source now?
>
> Thanks!
> Catherine
>
> > On Jan 20, 2016, at 12:28 PM, Anthony Baker  wrote:
> >
> > I am pleased to announce the donation of additional GemFire code to the
> Geode community.  The code being donated adds significant capabilities used
> by many GemFire customers in production, namely WAN replication and
> Continuous Query.
> >
> > *WAN replication* provides event delivery and data synchronization for
> multi-site distributed clusters.  Asynchronous, persistent event delivery
> to remote systems enables patterns such Active/Active, Disaster Recovery,
> or Follow-the-Sun with support for configurable, eventually consistent data
> replication.  *Continuous Querying* allows clients to subscribe to server
> events by using SQL-like query filtering.  Events that match or modify the
> query results are queued and delivered to the client using the
> client/server subscription framework.
> >
> > The Software Grant Agreement for this code has been accepted by the ASF
> secretary.
> >
> > The donated code currently sits in a separate branch in the Geode
> repository named wan_cq_donation [1] and is awaiting community feedback.  I
> encourage everyone in the Geode community to review this donation and
> provide feedback.  Once the community has reached a consensus we can
> determine next steps and how this code might get merged into the develop
> branch so that all users can access these features.  Your suggestions are
> most welcome!
> >
> >
> > Thanks,
> > Anthony
> >
> > [1]
> https://git1-us-west.apache.org/repos/asf?p=incubator-geode.git;a=tree;h=refs/heads/wan_cq_donation;hb=refs/heads/wan_cq_donation
> <
> https://git1-us-west.apache.org/repos/asf?p=incubator-geode.git;a=tree;h=refs/heads/wan_cq_donation;hb=refs/heads/wan_cq_donation
> >
> >
>
>

Re: [DISCUSS] Generalized criteria for becoming an Apache Geode Committer

[Greg Chase]

Just for measure - what does it take to show up as a top contributor for
wiki changes in Apache Geode in the last 30 days?

http://projects.bitergia.com/apache-geode/browser/confluence.html

1 change.

It might sound like I'm asking for a lot, but its not.

Just needs to be more comprehensive, not "0" everywhere.

-Greg

On Wed, Jan 6, 2016 at 5:30 PM, Greg Chase <g...@gregchase.com> wrote:

> With the occasion of a request to vote in our first additional committer,
> its become clear that we don't have clear criteria for when someone should
> become a committer.
>
> The steps for becoming a committer are listed here in the wiki:
> https://cwiki.apache.org/confluence/display/GEODE/Becoming+a+committer
>
> And include these steps:
>
>
>>1. Once you become a contributor you *will probably be invited by*
>>another committer to be a new committer and *the community will vote*
>>
>>
>>1. *If the vote pass *and you get accepted...
>>
>>
> But there are no criteria by which someone should be nominated, or by
> which committers / PPMC should vote according to.
>
> In a discussion on private@geode, a number of good points have been
> raised which I will paraphrase.  The makers of these points can choose to
> weigh in directly to this thread if they want their statement refined or
> attributed to them.
>
> 1. "The Committers" are currently the same as "The PPMC".  So at this
> point, voting someone as a committer is voting them as the potential future
> PMC of Apache Geode.
>
> 2. Becoming a committer should be used to recognize a contributor as
> having further potential to contribute even more, and to encourage them to
> participate with and collaborate more with the community.
>
> In my personal opinion, contributors who show themselves as collaborative,
> community building, or supportive of users with a likelihood of
> contributing even more should be nominated and likely voted by the PPMC to
> be a contributor.
>
> While not the only source, many behaviors related to being collaborative,
> community building, or supportive of users is captured by our community
> dashboard: http://projects.bitergia.com/apache-geode/browser/
>
> Thus I'd expect high contributors in these areas to rank in top lists as
> follows:
>
> Collaborative:
> Jiras: open, comment, close
> Dev mail list: open threads, reply
> Git: commits
> Code reviews
>
> Someone who does not collaborate and only develops would likely only show
> up in pull requests, but not other collaborative infrastructure.
>
> Community building would include:
> Dev & user mail lists
> Wiki / confluent editing
>
> User supporting would incldue:
> User mail list responses
> Jiras opened and commented on
>
> I'm sure these lists can be better refined.
>
> While I wouldn't quantify this, I would argue that if someone shows up in
> multiple categories of contribution on top lists for more than one 30 day
> period, they are likely candidates to be nominated as a committer.
>
> I know of at least a couple of companies that pay their employees to be
> contributors to Apache Geode.  If their job changes, or they move to a
> different company, will they stay as a contributor if we make them a
> committer?  I'd argue this is much more likely if we see them contributing
> in multiple categories rather than just a single way.
>
> Finally, we need to create a model and standard of how we want our
> community to act.  By being more specific about asking for broader
> contribution to be recognized as a committer, this will help train new
> members of this community how to participate fully.
>
> I'll appreciate comments on these, and if I get enough agreement, I will
> add a proposed criteria to the wiki.
>
> Regards,
>
> -Greg
>

[DISCUSS] Generalized criteria for becoming an Apache Geode Committer

[Greg Chase]

With the occasion of a request to vote in our first additional committer,
its become clear that we don't have clear criteria for when someone should
become a committer.

The steps for becoming a committer are listed here in the wiki:
https://cwiki.apache.org/confluence/display/GEODE/Becoming+a+committer

And include these steps:


>1. Once you become a contributor you *will probably be invited by*
>another committer to be a new committer and *the community will vote*
>
>
>1. *If the vote pass *and you get accepted...
>
>
But there are no criteria by which someone should be nominated, or by which
committers / PPMC should vote according to.

In a discussion on private@geode, a number of good points have been raised
which I will paraphrase.  The makers of these points can choose to weigh in
directly to this thread if they want their statement refined or attributed
to them.

1. "The Committers" are currently the same as "The PPMC".  So at this
point, voting someone as a committer is voting them as the potential future
PMC of Apache Geode.

2. Becoming a committer should be used to recognize a contributor as having
further potential to contribute even more, and to encourage them to
participate with and collaborate more with the community.

In my personal opinion, contributors who show themselves as collaborative,
community building, or supportive of users with a likelihood of
contributing even more should be nominated and likely voted by the PPMC to
be a contributor.

While not the only source, many behaviors related to being collaborative,
community building, or supportive of users is captured by our community
dashboard: http://projects.bitergia.com/apache-geode/browser/

Thus I'd expect high contributors in these areas to rank in top lists as
follows:

Collaborative:
Jiras: open, comment, close
Dev mail list: open threads, reply
Git: commits
Code reviews

Someone who does not collaborate and only develops would likely only show
up in pull requests, but not other collaborative infrastructure.

Community building would include:
Dev & user mail lists
Wiki / confluent editing

User supporting would incldue:
User mail list responses
Jiras opened and commented on

I'm sure these lists can be better refined.

While I wouldn't quantify this, I would argue that if someone shows up in
multiple categories of contribution on top lists for more than one 30 day
period, they are likely candidates to be nominated as a committer.

I know of at least a couple of companies that pay their employees to be
contributors to Apache Geode.  If their job changes, or they move to a
different company, will they stay as a contributor if we make them a
committer?  I'd argue this is much more likely if we see them contributing
in multiple categories rather than just a single way.

Finally, we need to create a model and standard of how we want our
community to act.  By being more specific about asking for broader
contribution to be recognized as a committer, this will help train new
members of this community how to participate fully.

I'll appreciate comments on these, and if I get enough agreement, I will
add a proposed criteria to the wiki.

Regards,

-Greg

Re: Geode on OSv & Seastar?

[Greg Chase]

Not yet - know someone who wants to try? They can discuss results at a next 
virtual meeting.

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Nov 25, 2015, at 6:39 AM, James Thornton  wrote:
> 
> Hello -
> 
> Roman Shaposhnik gave a talk on OSv (http://osv.io/) at CF Summit 2014:
> 
> Pivotal - OSv: Probably the Best OS for Cloud Workloads You've Never Heard
> Of (CF Summit 2014)
> https://www.youtube.com/watch?v=OGmKVtvfOaQ
> 
> Here's a link to the OSv paper:
> 
>   -
>   https://www.usenix.org/system/files/conference/atc14/atc14-paper-kivity.pdf
>   -
>   
> https://www.usenix.org/conference/atc14/technical-sessions/presentation/kivity
> 
> OSv was developed by the team behind the KVM hypervisor. They also released an
> Apache 2 library called Seastar, a networking stack/fabric that uses
> Intel's DPDK.
> 
>   - http://www.seastar-project.org
>   - https://github.com/scylladb/seastar/wiki
> 
> Has Geode been tested on OSv, and has anyone looked into integrating
> Seastar with Geode?
> 
> - James
> 
> -- 
> James Thornton, *http://electricspeed.com *

Re: Final updates to Geode Website - Ready ?

[Greg Chase]

I may be screwed up as well. I recall expecting to see markdown but finding 
HTML.

This email encrypted by tiny buttons & fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

> On Nov 25, 2015, at 2:18 PM, Dave Barnes  wrote:
> 
> Greg - William's message explains the problem. I had the directories
> reversed - I thought .../website/content was the compiled version. You
> should see all of your PR #38 changes in the final result, modified only
> slightly by my proofreader's tweaks.
> Will review when I'm in the office again next week to make sure things
> happened as intended.
> -Dave
> 
> On Wed, Nov 25, 2015 at 11:26 AM, William Markito 
> wrote:
> 
>> Just updated including the latest changes from Greg and moved the
>> Incubation disclaimer to About the Project as Roman suggested.
>> 
>> Please try again: http://markito.github.io/geode-website/  and clean your
>> caches.
>> 
>> About the missing changes that Greg talked about,  he and Dave were
>> updating the "compiled" website and not the source so their changes were
>> being overridden. I'll update our instructions to avoid the problem in the
>> future.   In summary, *always* change something under
>> "gemfire-site/website/content" and *never *under "gemfire-site/content"
>> 
>> Thanks for the feedback and let's restart the voting please.
>> 
>> 
>>> On Wed, Nov 25, 2015 at 11:20 AM, Jianxia Chen  wrote:
>>> 
>>> +1
>>> 
>>> On Tue, Nov 24, 2015 at 10:30 PM, William Markito 
>>> wrote:
>>> 
 I've just pushed the latest fixes and added content to the community
>> page
 as well.
 
 Please check the result here ->
>> http://markito.github.io/geode-website/
 (clear your cache)
 
 From my point of view and based on the feedback I got so far, this is
 *ready* to be pushed to asf-site and update our current website.
 
 Please let me know if you think otherwise, have any comments or
>> feedback.
 
 Thanks,
 --
 
 William Markito Oliveira
 -- For questions about Apache Geode, please write to
 *dev@geode.incubator.apache.org
 *
>> 
>> 
>> 
>> --
>> 
>> William Markito Oliveira
>> -- For questions about Apache Geode, please write to
>> *dev@geode.incubator.apache.org
>> *
>> 

Re: Upcoming Apache Geode Roundtable on 11/17

[Greg Chase]

+ Nitin specifically :)

On Wed, Nov 11, 2015 at 3:59 PM, Amy Welch  wrote:

> Join us for next week's Apache Geode (incubating) Roundtable on November
> 17th.
>
> We plan a review of what's coming in Apache Geode 1.0 Alpha with
> William Markito, Anthony Baker and Swapnil Bawaskar.
>
> A shout out to Nitin Lamba for additional agenda items you'd like to add.
>
> Please join us next week, on Tuesday, November 17th
> at:https://pivotalcommunity.adobeconnect.com/clubhouse
>
> 11/17 Tuesday, 9:00am PST  UTC-8hours San Francisco, CA (USA)
> 11/17 Tuesday, 5:00pm GMT  UTC London, England (UK)
>
> We look forward to seeing you soon!
>
> Kind regards,
>
> Amy Welch
>

Re: Apache Geode is....

[Greg Chase]

On Wed, Sep 16, 2015 at 2:27 PM, Justin Erenkrantz 
wrote:

>
> Here's my $.02 of how I might describe it:
>
> Apache Geode is an in-memory strongly consistent highly distributed
> database built to support low-latency transactional applications.
>
> That comes in at 16 words.
>
> Cheers.  -- justin
>

I like it. Added some commas, but otherwise +1

Apache Geode is an in-memory, strongly consistent, highly distributed
database built to support low-latency transactional applications.

How can we get Geode docs viewable?

[Greg Chase]

Greetings team,
I know that moving docs to ASF infrastructure remains a to-do.

However we are actively maintaining and enhancing the docs in their current
github, which was created during Geode's pre-ASF phase:
https://github.com/project-geode/docs

What's not clear is how a user can actually access these docs in consumable
form. There's a link to a localhost in the github to view a current build,
but this link does not appear to function.

What, if any, is the correct procedure to have usable docs, and is there
anything short term we can do until we get the overall doc porting to ASF
issue solved?

-Greg

Can we add "website" component to Geode Jira?

[Greg Chase]

Hi team,
I could have sworn that we already had "website refresh" posted already as
a Jira issue, however searching for it is bringing up nothing.

Ideally website issues should be linked to a "website" component, but I
don't see a component for that either.

Can we get a "website" component defined in the Geode Jira.

Afterwards, I will try to search for the mythical "website refresh" Jira
issue, or create a new one for our pending website refresh.

Thanks!

-Greg

Re: Can we add "website" component to Geode Jira?

[Greg Chase]

On Thu, Sep 17, 2015 at 5:17 PM, Nitin Lamba  wrote:

> The component is called 'content'.
>
> The JIRA you may be looking for is GEODE-53?
> https://issues.apache.org/jira/browse/GEODE-53


Thanks for finding the relevant issue.

Could we change "content" to "website" as "content" seems rather generic to
me - unless we mean to also tag big projects on the wiki.

Re: Apache Geode is....

[Greg Chase]

On Thu, Sep 17, 2015 at 8:42 PM, Anthony Baker  wrote:

> What is more than a data grid but less than a database?
>

Positioning from both are valid. A lot of technologies position off
"database": "Object database", "document database", "in-memory database",
"NoSQL Database"

The question is whether IMDGs are taking on more and more "database like"
capabilities and thus can earn that position. Or are there things that
fundamentally IDMGs are unsuitable for, and this same use case would be
unsuitable for Geode.

I originally wrote IMDG for the short description of Geode since its a
great explanation to explain the highly distributed share-nothing
architecture. At Pivotal we market the technology as an "in-memory
database".


> I just had a conversation on the sidelines of a soccer game tonight
> explaining that no we don’t have database semantics but we do more than a
> basic IMDG.  They had done an exploration previously and had picked up
> hazelcast.
>

What exactly is meant by "database semantics"?  When I usually hear people
say that, they really mean RDBMS - tables, and SQL.

I know certain analysts who believe IMDGs are fundamentally NOT databases
because they don't do SQL.

-Greg

Re: Apache Geode is....

[Greg Chase]

Second frame is "About Apache Geode". 150 words or less for the body.  I'm
10 over at 160.

What we currently say right now needs a total rewrite:
http://geode.incubator.apache.org/about/


Proposed new About text (150 words or less for the body.  I'm 10 over at
160):

Processing low latency queries, transactions, and event messaging at high
concurrency

Apache Geode (incubating) was first developed to solve performance issues
at scale for commodities traders after the crash of Enron in 2002. It was
released to the market as the commercial product GemFire, a product of
Gemstone Systems. In April 2015, The code was granted to The ASF as Apache
Geode (incubating).

Apache Geode is a distributed in-memory database and integrated event
message queue built with three design principles:

   1.

   Elastic performance: Maintain low latency response through a
   self-balancing cluster architecture while keeping all data in-memory
   2.

   Distributed consistency: Guarantee consistency of data across
   distributed nodes of a cluster to support ACID transactions
   3.

   Resilient availability:  Without sacrificing consistency, ensure data
   remains available in a cluster through automated, redundancy, rebalancing,
   and self healing of the cluster

Geode nodes have an integrated message queue for delivering administrative
and cache events.  Events can match queries, be synchronous or
asynchronous, are ordered, persistent, and highly available. This
implements powerful capabilities such as guaranteed write-behind to RDBMS.


On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <g...@gregchase.com> wrote:

> Dear Geode contributors,
> I'm writing the website for the newly accepted Apache HAWQ incubating
> project.
>
> As part of this effort, I secured some web design resources to refresh the
> Apache Geode site as well.
>
> Talking to a number of contributors individually, they like the idea of
> changing the design somewhat to fit the CouchDB layout:
> http://couchdb.apache.org/, but keeping the 'Geode' graphics and look and
> feel.
>
> Its also a good time to refresh our general text which hasn't really been
> updated since before Geode joined Apache.
>
> First panel is a short description explaining what Geode is:
>
> "Apache Geode is a distributed, in-memory data grid and integrated
> messaging queue built to support low latency transactional applications at
> extreme scale."
>
> Should be 25 words or less. 20 words or less is even better. My score is
> "22".
>

Apache Geode is....

[Greg Chase]

Dear Geode contributors,
I'm writing the website for the newly accepted Apache HAWQ incubating
project.

As part of this effort, I secured some web design resources to refresh the
Apache Geode site as well.

Talking to a number of contributors individually, they like the idea of
changing the design somewhat to fit the CouchDB layout:
http://couchdb.apache.org/, but keeping the 'Geode' graphics and look and
feel.

Its also a good time to refresh our general text which hasn't really been
updated since before Geode joined Apache.

First panel is a short description explaining what Geode is:

"Apache Geode is a distributed, in-memory data grid and integrated
messaging queue built to support low latency transactional applications at
extreme scale."

Should be 25 words or less. 20 words or less is even better. My score is
"22".

Re: JSON implementation

[Greg Chase]

Let's discuss this in tomorrow's Apache geode Clubhouse meeting

This email encrypted by tiny buttons  fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

 On Aug 17, 2015, at 3:21 PM, Ignatyev, Konstantin ignat...@cobalt.com wrote:
 
 Done:
 https://issues.apache.org/jira/browse/GEODE-225
 
 https://issues.apache.org/jira/browse/GEODE-226
 
 Konstantin Ignatyev
 Enterprise Architect
 CDK Global
 
 t 206.219.8381  |  c 425.233.4536  |  f 206.269.6789
 konstantin.ignat...@cdk.commailto:konstantin.ignat...@cdk.com?subject=
 cdk.comhttp://www.cdkglobal.com
 
 
 
 On Aug 17, 2015, at 3:00 PM, William Markito 
 wmark...@pivotal.iomailto:wmark...@pivotal.io wrote:
 
 Thanks Konstantin!
 
 Would you mind opening a JIRA about those ?
 https://issues.apache.org/jira/browse/GEODE
 
 
 On Mon, Aug 17, 2015 at 2:51 PM, Ignatyev, Konstantin ignat...@cobalt.com
 wrote:
 
 Hi,
 
 I have been looking at Geode-s code and come across major performance
 killer for JSON handling in Geode, namely implementation of
 com.gemstone.gemfire.pdx.internal.PdxInstanceImpl#getObject
 
 as you can see in the snipped below the code creates ObjectMapper every
 time it needs to convert PDX instance into JSON. According to docs and
 examples on Jackson’s site instances of  ObjectMapper should be shared
 globally. Creating it for every transaction is quite expensive in terms of
 CPU and garbage collection.
 
 
 Another thing is date format, in the JSON land it is pretty much settled
 to be ISO 8661
 
 https://weblog.west-wind.com/posts/2014/Jan/06/JavaScript-JSON-Date-Parsing-and-real-Dates
 
 It would  be nice to be able to have Geode’s JSON standard compliant, or
 have this configurable.
 
 public Object getObject() {
 if (getPdxType().getNoDomainClass()) {
   //In case of Developer Rest APIs, All PdxInstances converted from Json
 will have a className =__GEMFIRE_JSON.
   //Following code added to convert Json/PdxInstance into the Java
 object.
   if(this.getClassName().equals(__GEMFIRE_JSON)){
 
 //introspect the JSON, does the @type meta-data exist.
 String className = extractTypeMetaData();
 
 if(StringUtils.hasText(className)) {
   try {
 ObjectMapper mapper = new ObjectMapper();
 mapper.setDateFormat(new SimpleDateFormat(MM/dd/));
 
 mapper.configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false);
 
 mapper.configure(com.fasterxml.jackson.core.JsonParser.Feature.ALLOW_UNQUOTED_FIELD_NAMES,
 true);
 String JSON = JSONFormatter.toJSON(this);
 Object classInstance = mapper.readValue(JSON,
 ClassPathLoader.getLatest().forName(className));
 return classInstance;
   }catch(Exception e){
 throw new PdxSerializationException(Could not deserialize as
 java class type could not resolved, e);
   }
 }
   }
   return this;
 }
 
 Regards,
 
 Konstantin Ignatyev
 
 
 
 
 --
 This message and any attachments are intended only for the use of the
 addressee and may contain information that is privileged and confidential.
 If the reader of the message is not the intended recipient or an authorized
 representative of the intended recipient, you are hereby notified that any
 dissemination of this communication is strictly prohibited. If you have
 received this communication in error, notify the sender immediately by
 return email and delete the message and any attachments from your system.
 
 
 
 
 --
 
 William Markito Oliveira
 Enterprise Architect
 -- For questions about Apache Geode, please write to
 *dev@geode.incubator.apache.org
 dev@geode.incubator.apache.org*
 
 
 --
 This message and any attachments are intended only for the use of the 
 addressee and may contain information that is privileged and confidential. If 
 the reader of the message is not the intended recipient or an authorized 
 representative of the intended recipient, you are hereby notified that any 
 dissemination of this communication is strictly prohibited. If you have 
 received this communication in error, notify the sender immediately by return 
 email and delete the message and any attachments from your system.

Lots of Texas-based participants in the Apache Geode Hackathon

[Greg Chase]

I know we have a few Texas area contributors for Apache Geode.

I thought you'd be interested to know that we seem to have a cluster of
Texas-based participants for the Apache Geode hackathon.

http://ambitious-apps.challengepost.com/participants

Maybe we should do a little spontaneous in-person get together in Dallas?

-Greg

Re: [VOTE] Grandfathering forgotten Geode contributors

[Greg Chase]

+1 again :)

On Thu, Jun 11, 2015 at 4:15 PM, Roman Shaposhnik r...@apache.org wrote:

 Hi!

 for various reasons we missed a few Pivotal folks
 when submitting a Geode proposal. There's nothing
 controversial about them -- just an honest mistake.
 They are all currently working on the project and
 contributed quite a bit in the past. In short, they have
 as much a claim in being a project committer as
 all the other folks who were on the proposal.

 I propose that we add them to the project as committers
 since they should've been on the proposal to begin with:
  * Chloe Jackson
  * Manuel David
  * Rajesh Kumar
  * Rishitesh Mishra
  * Shankar Hundekar
  * Michael Stolz
  * Mak Gokhale

 This majority vote is open for at least 72 hours.

 Here's my +1.

 Thanks,
 Roman.

Re: What should I do to correct documentation?

[Greg Chase]

Fabio - thanks for bringing these up.

Please consider posting one or more JIRA's with your findings:
https://issues.apache.org/jira/browse/GEODE/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
.

Docs are in transition from the interim repository still, so I'll have to
ask other contributors to weigh in on how to handle new contributions to
docs.

On Mon, Jun 8, 2015 at 8:30 AM, Fabio Mazanatti fabio.mazana...@pobox.com
wrote:

 Hi there,

 I was checking the Confluence docs and got a few points that can be easily
 improved, like these few lines:

 Geode in 5 minutes
 Obtain the source archive from Pivotal. Extract and build from source
 (note: currently Geode supports jdk1.7.75):
 $ cd geode
 $ ./gradlew build installDist

 1. The source files now must be obtained from GIT
 2. The text could mention that you don't need to have Gradle available in
 order to build Geode.
 When I saw the ./gradlew build line, I thought that you should list
 Gradle as a pre-req. Markito told me that it isn't necessary, the script
 takes care of it. It would be nice to make this clear.

 So, my point is: how can I help improving the docs? One can't edit it
 directly from Confluence, right? Just emailing the dev list is enough?


 Best,
 Fabio


 --
 Fabio Mazanatti
  --- http://mazanatti.info

[DISCUSS] Changes you want to the Geode website, please suggest here

[Greg Chase]

Team,
I'm planning a new blog about our huge progress we've made over the last
month since becoming an Apache incubating project.

Hopefully this will draw some new eyeballs.

I know the calendar page needs to be fixed up, and there's even a
suggestion for a calendar widget.

We have new community-developed artifacts like demos, videos, and talks to
post.

Anything else you would like to see or post?

Thanks!

-Greg

Apache Geode Arm-Waver

Re: Fabric Framework for distributed system management

[Greg Chase]

Well this is a really good subject. Pivotal Open-Source Hub is organizing our 
next virtual meet up. And we are looking for a couple of short deep dive 
technical topics. This one seems perfect. Would one of you be willing to throw 
together a couple of slides and maybe a demo Corey this can really help other 
Geode users.

This email encrypted by tiny buttons  fat thumbs, beta voice recognition, and 
autocorrect on my iPhone.

 On Jun 3, 2015, at 7:14 PM, Luke Shannon lshan...@pivotal.io wrote:
 
 NICE!
 
 On Wed, Jun 3, 2015 at 10:09 PM, Jens Deppe jde...@pivotal.io wrote:
 
 Luke, didn't I send you my fabric scripts from a while back?
 
 Attached is an example which was used for GemFireXD (now not available any
 more), but most of the structure remains the same.
 
 Another nice feature is that fabric lets you run jobs in parallel; I've
 been able to start up 100+ node clusters this way in under a minute.
 
 --Jens
 
 On Wed, Jun 3, 2015 at 6:01 PM, Abtin Afshar abtin.afs...@gmail.com
 wrote:
 
 Hi Randy,
 
 You can actually do a lot with Fabric. I hacked a quick script to
 download gemfire logs, stats, thread dumps and zip them up from any cluster
 I want (dev,sit, uat). Beauty of it is that you only need to install it in
 you local machine (in my case my Linux VM) and it uses ssh under the hood.
 You can also add any python goodness to your script and control your
 cluster with a simple command.
 
 Cheers!
 Abtin
 
 
 On Jun 3, 2015, at 3:41 PM, Randy May wrandy...@gmail.com wrote:
 
 Thats funny. I was just looking for something exactly like this to help
 me
 out with build automation at a client.  Thanks for sharing!
 
 On Wed, Jun 3, 2015 at 2:50 PM Luke Shannon lshan...@pivotal.io
 wrote:
 
 I was just working with a client who is using this framework to manage
 all
 their distributed geode processes (mainly capturing log and stats
 files for
 trouble shooting but also parallel starts to recover from persistence).
 
 http://www.fabfile.org/
 
 I have come across tons of custom shell script solutions to do this
 sort of
 thing, and have played with Ansible myself (which is great). This one
 look
 interesting. You can write Python, but you can also do a DSL that looks
 like this:
 
 from fabric.api import *
 
 
 
 env.hosts = ['cache_server1', 'cache_server2']
 
 env.user = 'my_user'
 
 env.password = 'my_pass'
 
 
 
 def download_log():
 
   with settings(warn_only=True):
 
   cd('/gemfire/cache/):
 
   get('mycache.log')
 
 
 
 
 --
 Luke Shannon | Sr. Field Engineer - Toronto | Pivotal
 -
 Join the Toronto Pivotal Usergroup:
 http://www.meetup.com/Toronto-Pivotal-User-Group/
 
 
 -- 
 Luke Shannon | Sr. Field Engineer - Toronto | Pivotal
 -
 Mobile:416-571-9495
 Join the Toronto Pivotal Usergroup:
 http://www.meetup.com/Toronto-Pivotal-User-Group/

Re: Our JIRA is fully functional now

[Greg Chase]

gregchase

On Tue, May 5, 2015 at 7:04 PM, Real Wes thereal...@outlook.com wrote:

 wes.williams


  On May 5, 2015, at 7:35 PM, Roman Shaposhnik r...@apache.org wrote:
 
  https://issues.apache.org/jira/browse/GEODE-1
 
  Please make sure to register accounts there
  and reply back to this thread with your IDs
  so that William and I can add you to the
  project developers on JIRA.
 
  Thanks,
  Roman.