Re: Kafka Summit:- Geode Kafka Connector

[Greg Chase]

Go for it!  You'll also want a strong positioning of when to use Geode, and
when to use Kafka.  Showing multiple use cases (if this makes sense) of
Geode broadcasting messages to Kafka as well as consuming messages from
Kafka would be awesome.  In the positioning, and explanation of use cases,
you'll want to show how Geode's own event detection capabilities like
continuous query come into play.  When do you want detection parameters
defined in Geode and its application vs. configured in the Kafka
infrastructure with KSQL, for example.

On Thu, Jan 7, 2021 at 12:08 PM Jason Huynh  wrote:

> Hi Ashish,
>
> Are you asking for someone to present, or are you asking if it is ok for
> you to present?  I don't think there are any restrictions on presenting,
> hopefully someone will correct me if I am wrong.
>
> I think the call for papers is still open but closing relatively soon?  So
> if you plan on presenting, you'd have to submit a paper and get it accepted.
>
> -Jason
>
> On 1/7/21, 10:00 AM, "aashish choudhary" 
> wrote:
>
> Hi,
>
> I was thinking if we can do a demo of geode Kafka connector in Europe
> Kafka
> Summit.
>
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsessionize.com%2Fkafka-summit-eu-2021%2F&data=04%7C01%7Cjhuynh%40vmware.com%7Cb077adc7e8754fc15f4008d8b33611a9%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637456392138304458%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZjW%2BQ08pnXAalcpyn9AmIfL7x6YSP3afWGuIHrJ27EA%3D&reserved=0
>
> Thoughts?
>
> With best regards,
> Ashish
>
>

Do you want to Tweet for @ApacheGeode?

[Greg Chase]

Greetings Apache Geode community,
Tweeting for the Apache Geode project in the past has been a community
effort.

However, our most prolific tweeters are currently not spending much time
with the project.

As a result @ApacheGeode has fallen silent.

Per ASF recommendations, we manage access to the @ApacheGeode Twitter
handle through Tweet Deck. Any contributor is welcome to Tweet on behalf of
the project.  You simply need to ask for access, such as replying to this
thread.

Presuming no concerns raised by the PMC, access is granted to your personal
Twitter credentials to access @ApacheGeode using Tweet Deck.

Administrative rights to @ApacheGeode are maintained by several PMC members.

The guideline for Tweeting for @ApacheGeode is to promote the project,
announce any important releases, events or topics, and to help answer
questions or direct askers to u...@geode.apache.org.

You are also welcome to engage in technical topics of interest to Apache
Geode users, such as event driven architectures, caching patterns,
in-memory computing, etc.

We recommend not engaging in bashing other projects or products, or
engaging in off-topic discussions.

If you are interested in helping Tweet for @ApacheGeode, I invite you to
volunteer by replying to this thread.

Regards,

-Greg

Re: Do you want to Tweet for @ApacheGeode?

[Greg Chase]

Thanks both Michael and Swapnil.  If you could please send me a private
response with your Twitter handle, I will authorize you to Tweet from
@ApacheGeode.

If anyone else would also like to help, please respond publicly to the dev
group first about your interest.

Thanks!

-Greg

On Wed, Jun 7, 2017 at 10:14 AM, Swapnil Bawaskar 
wrote:

> So can I.
>
> On Tue, Jun 6, 2017 at 4:40 PM Michael Stolz  wrote:
>
> > Hey Greg,
> >
> > I could tweet now and then.
> >
> > --
> > Mike Stolz
> > Principal Engineer, GemFire Product Manager
> > Mobile: +1-631-835-4771 <(631)%20835-4771>
> >
> > On Tue, Jun 6, 2017 at 12:28 PM, Greg Chase 
> wrote:
> >
> > > Greetings Apache Geode community,
> > > Tweeting for the Apache Geode project in the past has been a community
> > > effort.
> > >
> > > However, our most prolific tweeters are currently not spending much
> time
> > > with the project.
> > >
> > > As a result @ApacheGeode has fallen silent.
> > >
> > > Per ASF recommendations, we manage access to the @ApacheGeode Twitter
> > > handle through Tweet Deck. Any contributor is welcome to Tweet on
> behalf
> > of
> > > the project.  You simply need to ask for access, such as replying to
> this
> > > thread.
> > >
> > > Presuming no concerns raised by the PMC, access is granted to your
> > personal
> > > Twitter credentials to access @ApacheGeode using Tweet Deck.
> > >
> > > Administrative rights to @ApacheGeode are maintained by several PMC
> > > members.
> > >
> > > The guideline for Tweeting for @ApacheGeode is to promote the project,
> > > announce any important releases, events or topics, and to help answer
> > > questions or direct askers to u...@geode.apache.org.
> > >
> > > You are also welcome to engage in technical topics of interest to
> Apache
> > > Geode users, such as event driven architectures, caching patterns,
> > > in-memory computing, etc.
> > >
> > > We recommend not engaging in bashing other projects or products, or
> > > engaging in off-topic discussions.
> > >
> > > If you are interested in helping Tweet for @ApacheGeode, I invite you
> to
> > > volunteer by replying to this thread.
> > >
> > > Regards,
> > >
> > > -Greg
> > >
> >
>

Re: Need authorization to tweet for Apache Geode

[Greg Chase]

Added you Mike.

On Wed, Jun 7, 2017 at 1:41 PM, Michael Stolz  wrote:

> Hi Greg,
>
> I didn't give you my Twitter handle: @MikeStolz1
>
>
> --
> Mike Stolz
> Principal Engineer, GemFire Product Manager
> Mobile: +1-631-835-4771
>
> On Wed, Jun 7, 2017 at 1:23 PM, Gregory Chase  wrote:
>
> > Hi Jag,
> > Thanks for volunteering to help communicate the goodness of @ApacheGeode!
> >
> > I'll add you to the authorized Twitter team in TweetDeck!
> >
> > -Greg
> >
> > On Wed, Jun 7, 2017 at 1:19 PM, Jagdish Mirani 
> wrote:
> >
> > > Hello:
> > > I would like to be authorized to tweet for Apache Geode - I would like
> to
> > > Tweet from the project handle on behalf of the project.
> > >
> > > About me.
> > >
> > > *Twitter handle: *@jagmirani
> > > *Role: *I am the Product Marketing Manager for Pivotal GemFire (which
> is
> > > based on Apache Geode). Also, I work closely with our engineering and
> > > Product Management teams on our contributions to the Geode project.
> > >
> > > Please authorize tweeting privileges for me.
> > >
> > > Regards
> > > Jagdish Mirani
> > >
> >
> >
> >
> > --
> > Greg Chase
> >
> > Product team
> > http://www.pivotal.io/big-data
> >
> > Pivotal Software
> > http://www.pivotal.io/
> >
> > 650-215-0477
> > @GregChase
> > Blog: http://geekmarketing.biz/
> >
>

Re: Need authorization to tweet for Apache Geode

[Greg Chase]

Never too many.  I've added you to the TweetDeck team.



On Wed, Jun 7, 2017 at 2:08 PM, Kirk Lund  wrote:

> I'll volunteer to help too unless that's too many folks. My twitter is
> @kirk_lund
>
> On Wed, Jun 7, 2017 at 1:51 PM, Greg Chase  wrote:
>
> > Added you Mike.
> >
> > On Wed, Jun 7, 2017 at 1:41 PM, Michael Stolz  wrote:
> >
> > > Hi Greg,
> > >
> > > I didn't give you my Twitter handle: @MikeStolz1
> > >
> > >
> > > --
> > > Mike Stolz
> > > Principal Engineer, GemFire Product Manager
> > > Mobile: +1-631-835-4771
> > >
> > > On Wed, Jun 7, 2017 at 1:23 PM, Gregory Chase 
> wrote:
> > >
> > > > Hi Jag,
> > > > Thanks for volunteering to help communicate the goodness of
> > @ApacheGeode!
> > > >
> > > > I'll add you to the authorized Twitter team in TweetDeck!
> > > >
> > > > -Greg
> > > >
> > > > On Wed, Jun 7, 2017 at 1:19 PM, Jagdish Mirani 
> > > wrote:
> > > >
> > > > > Hello:
> > > > > I would like to be authorized to tweet for Apache Geode - I would
> > like
> > > to
> > > > > Tweet from the project handle on behalf of the project.
> > > > >
> > > > > About me.
> > > > >
> > > > > *Twitter handle: *@jagmirani
> > > > > *Role: *I am the Product Marketing Manager for Pivotal GemFire
> (which
> > > is
> > > > > based on Apache Geode). Also, I work closely with our engineering
> and
> > > > > Product Management teams on our contributions to the Geode project.
> > > > >
> > > > > Please authorize tweeting privileges for me.
> > > > >
> > > > > Regards
> > > > > Jagdish Mirani
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Greg Chase
> > > >
> > > > Product team
> > > > http://www.pivotal.io/big-data
> > > >
> > > > Pivotal Software
> > > > http://www.pivotal.io/
> > > >
> > > > 650-215-0477
> > > > @GregChase
> > > > Blog: http://geekmarketing.biz/
> > > >
> > >
> >
>

Re: Concourse pipeline

[Greg Chase]

I wonder - do we want a separate email alias for these messages if they are
going to be even more frequent than Travis?

On Fri, Dec 1, 2017 at 3:24 PM, Sean Goller  wrote:

> Hi everyone,
>   If you haven't already heard, we have a new concourse pipeline
> infrastructure up and running at https://concourse.apachegeode-ci.info/ .
> When these jobs fail, email will be sent to the dev list, so be aware! :)
>
> -Sean.
>

Re: geode.apache.org and GDPR

[Greg Chase]

Part of GDPR: Don’t collect or store data you don’t intend to use.

+1 to remove it.

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

> On May 21, 2018, at 8:29 AM, Anthony Baker  wrote:
> 
> The geode website uses Google Analytics [1].  IANAL but there are some 
> constraints that will apply when GPDR takes effect [2].  Specifically, users 
> can opt-out of data collection.  Given how little use we’ve made of this 
> data, I think it would be simpler to just remove the GA tracker from our 
> website.
> 
> Thoughts?
> 
> 
> Anthony
> 
> [1] 
> https://github.com/apache/geode-site/blob/master/website/layouts/header.html#L40
>  
> 
> [2] https://issues.apache.org/jira/browse/MSKINS-143 
> 
> 

Re: [ANNOUNCE] Apache Geode release 1.1.0

[Greg Chase]

Awesome and congratulations!

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

> On Feb 15, 2017, at 5:34 PM, Hitesh Khamesra  
> wrote:
> 
> The Apache Geode team is proud to announce Apache Geode release version 1.1.0
> 
> Apache *Geode* is a data management platform that provides a
> database-like consistency model, reliable transaction processing and a
> shared-nothing architecture to maintain very low latency performance with
> high concurrency processing.
> 
> The release artifacts are available at:
>  http://geode.apache.org/releases/
> 
> To use the artifacts, please use the following documentation:
>  http://geode.apache.org/docs/guide/11/about_geode.html
> 
> Git source:
>  
> https://git-wip-us.apache.org/repos/asf?p=geode.git;a=tag;h=1d7a03bbab47a154b59dc6a4e811f7fc4a74c941
> 
> Git commit SHA1: 2286fd064a52173eab8fdcfadfb89a01e81ef728
> 
> Release Notes:
>  
> https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1.1.0
> 
> We would like to thank all the contributors that made the release possible.
> 
> Regards,
> Hitesh & Karen on behalf of the Apache Geode team

Re: for discussion: separate website into its own repo

[Greg Chase]

The single repository is from our time as an incubating project.

Now we can act like a grown up project 😜

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

> On Feb 16, 2017, at 4:57 PM, Anilkumar Gingade  wrote:
> 
> +1
> 
> On Thu, Feb 16, 2017 at 4:45 PM, Joey McAllister 
> wrote:
> 
>> +1 to Karen's suggestion of moving the website to its own repo.
>> 
>> +1 to Dan's suggestion scripting the website build/publishing with a CI
>> system based on commits.
>> 
>>> On Thu, Feb 16, 2017 at 4:38 PM Dan Smith  wrote:
>>> 
>>> +1
>>> 
>>> I think the current setup is confusing, because the website is supposed
>> to
>>> include docs that are generated from the last release, but the site
>>> instructions say the site should be generated from develop. A separate
>> repo
>>> with a single branch will probably reduce confusion.
>>> 
>>> We also need to script the website building and publishing, and ideally
>>> have the publishing done by a CI system based on commits. It looks like
>>> some other projects are talking about doing this with jenkins jenkins -
>> see
>>> INFRA-10722 for example.
>>> 
>>> -Dan
>>> 
>>> On Thu, Feb 16, 2017 at 4:10 PM, Karen Miller 
>> wrote:
>>> 
 I think that the website content that is currently in geode/geode-site
 ought to be moved to its own repository.  The driving reason for this
>> is
 that changes to the website occur on a different schedule than code
 releases.  We often want to add a new committer's name or a new
 event, and these items are not associated with sw releases. A new
>> website
 release that comes from the develop branch may have commits that
 should not yet be made public.
 
 Are there downsides to separating the website content into its own
>> repo?
 
>>> 
>> 

Re: please add me to community

[Greg Chase]

Hi Lior,
We see you in the community already

Is there a particular kind of access you are seeking?

-Greg

On Tue, Mar 7, 2017 at 4:48 AM, Lior Lew  wrote:

> Hello,
>
>
>
> My name is Lior Lew and I work in Amdocs on Geode implementation. Please
> add me to the community
>
>
>
> --
>
> Sincerely,
>
> Lior Lew
>
> Software Architect |  lior...@amdocs.com |  ( +(972) 52-8-351-788
>
> [image: amdocs-a]
>
>
> 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
>

Re: [VOTE] Resolution to Terminate Apache Geode

[Greg Chase]

+1 to terminate

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

> On Jul 28, 2024, at 8:09 PM, rup...@webstersystems.co.uk wrote:
> 
> Hi Mark,
> 
> Thanks for the mail & discussion. Maybe we need a Geode discord?
> I vote against but can't contribute resources to keep it going.
> I think it was a generous decision of Gemfire / VM to open source Gemfire / 
> Geode in the first place.
> They've closed sourced it again because of the $ from commercial support & 
> clients still using it.
> There was definitely uptake because of open source that wouldn't have 
> happened commercially.
> A pity that the open source model isn't commercially making $ for the owning 
> corporation.
> 
> Thanks, kind regards,
> Rupert
> 
> Rupert St John Webster
> 
> Webster Systems Ltd
> Tel: 07740 289100
> http://www.webstersystems.co.uk
> UK Registered No: 6517977
> 
> -Original Message-
> From: Mark Bretl 
> Sent: 27 July 2024 01:02
> To: geode 
> Subject: [VOTE] Resolution to Terminate Apache Geode
> 
> Hello Geode PMC and Dev Community,
> 
> Based on the minimal responses we have had with requests for new volunteers 
> and various discussions on the overall project health, the time has come to 
> have a vote for moving the Geode project to the Apache Attic.
> 
> Please cast your vote on the following resolution.
> 
> Voting deadline:
> 3PM Pacific Tuesday, August 6, 2024
> 
> """
> WHEREAS, the Project Management Committee of the Apache Geode project has 
> arrived at a consensus to recommend moving the project to the Attic; and
> 
> WHEREAS, the Board of Directors deems it no longer in the best interest of 
> the Foundation to continue the Apache Geode project due to inactivity;
> 
> NOW, THEREFORE, BE IT RESOLVED, that the Apache Geode project is hereby 
> terminated; and be it further
> 
> RESOLVED, that the Attic PMC be and hereby is tasked with oversight over the 
> software developed by the Apache Geode Project; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Geode" is hereby 
> terminated; and be it further
> 
> RESOLVED, that the Apache Geode PMC is hereby terminated.
> """
> 
> 
> Best regards,
> 
> Mark Bretl
> VP, Apache Geode
> 

Re: [VOTE] Resolution to Terminate Apache Geode

[Greg Chase]

+1 😥

On Fri, Aug 2, 2024 at 12:39 PM Roger Whitcomb 
wrote:

> Sadly my vote is +1 to terminate the project.
>
> Thanks,
> ~Roger Whitcomb
>
>
> > On Jul 26, 2024, at 6:05 PM, Mark Bretl  wrote:
> >
> > Hello Geode PMC and Dev Community,
> >
> > Based on the minimal responses we have had with requests for new
> volunteers
> > and various discussions on the overall project health, the time has come
> to
> > have a vote for moving the Geode project to the Apache Attic.
> >
> > Please cast your vote on the following resolution.
> >
> > Voting deadline:
> > 3PM Pacific Tuesday, August 6, 2024
> >
> > """
> > WHEREAS, the Project Management Committee of the Apache Geode project
> > has arrived at a consensus to recommend moving the project to the
> > Attic; and
> >
> > WHEREAS, the Board of Directors deems it no longer in the best interest
> > of the Foundation to continue the Apache Geode project due to
> > inactivity;
> >
> > NOW, THEREFORE, BE IT RESOLVED, that the Apache Geode project is hereby
> > terminated; and be it further
> >
> > RESOLVED, that the Attic PMC be and hereby is tasked with oversight
> > over the software developed by the Apache Geode Project; and be it
> > further
> >
> > RESOLVED, that the office of "Vice President, Apache Geode" is hereby
> > terminated; and be it further
> >
> > RESOLVED, that the Apache Geode PMC is hereby terminated.
> > """
> >
> >
> > Best regards,
> >
> > Mark Bretl
> > VP, Apache Geode
>

Re: GemFireConfigException

[Greg Chase]

Looks like a great Jira Issue! Please file!

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

> On Dec 19, 2016, at 5:07 AM, Dor Ben Dov  wrote:
> 
> Hi 
> 
> Any plans to refactor rename GemFireConfigException and GemFireException to 
> Geode? 
> 
> Regards,
> 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