Re: Proposal to restore Pulse logging in support/1.12

[Dale Emery]

Merged into support/1.12. Thanks all.

> On Apr 24, 2020, at 3:25 PM, Mark Bretl  wrote:
> 
> +1
> 
> On Fri, Apr 24, 2020 at 3:07 PM Owen Nichols  wrote:
> 
>> +1
>> 
>>> On Apr 24, 2020, at 3:06 PM, Jinmei Liao  wrote:
>>> 
>>> +1
>>> 
>>> On Fri, Apr 24, 2020 at 2:53 PM Anthony Baker  wrote:
>>> 
 +1
 
> On Apr 24, 2020, at 2:46 PM, Dale Emery  wrote:
> 
> During the cleanup of the gradle build and logging, the Pulse webapp
 lost its slf4j implementation. As a result, Pulse stopped writing log
>> files.
> 
> I’ve restored Pulse logging in the develop branch.
> 
> I would like to restore it in support/1.12. I’ve created a PR:
 https://github.com/apache/geode/pull/4992 <
 https://github.com/apache/geode/pull/4992>
> 
> Cheers,
> Dale
> 
> —
> Dale Emery
> dem...@pivotal.io
> dem...@vmware.com
> 
 
 
>>> 
>>> --
>>> Cheers
>>> 
>>> Jinmei
>> 
>> 

—
Dale Emery
dem...@pivotal.io
dem...@vmware.com

[DISCUSS] Geode 1.13 support branch planning

[Dave Barnes]

It's time to prepare for cutting the Geode 1.13 support branch.
Think about what you'd like to contribute, whip it into shape, and check it
into develop. We'll assess our position on Thursday, April 30, 2020, and
see if cutting the branch is feasible at that time.
Please raise any concerns to the community on this [DISCUSS] thread.
Thanks,
Dave Barnes
Geode 1.13 Release Manager

Re: [VOTE] Using Github issues and wiki for geode-kafka-connector project

[Jacob Barrett]

I would like to circle this around to an older conversation around the RFC 
process. We chose to use the ASF wiki and email over using repo and PR process. 
If we move more things over to GitHub I think that warrants a rethink. RFC 
conversations have been split between email and wiki comments. Using the PR 
process integrates inline commenting and email into a single interface. We 
don’t need to discuss this now, just tossing it out as food for thought as we 
look to embrace more GitHub features over ASF services.

-Jake

> On Apr 24, 2020, at 9:12 AM, Robert Houghton  wrote:
> 
> Looks like we can use the `.asf.yml` file in our repositories to enable
> `issues` and `wiki` behavior ourselves if we decide we like the feature :)
> 
> On Fri, Apr 24, 2020 at 7:46 AM Dave Barnes  wrote:
> 
>> +1
>> I like the look of the samples.
>> I also want to echo Anthony and Blake: Accessibility is huge, not only
>> because it smooths the way for adding content, but for pruning outdated
>> material.
>> 
>> On 4/24/20, 7:18 AM, "Blake Bender"  wrote:
>> 
>>+1 - Wow, research - nice work, Naba, this is great!
>> 
>>Just want to emphasize a larger point I failed to make in my response
>> re:
>>Markdown.  My experience with Wikis has been that it's very difficult
>> to
>>convince people to contribute entries/edits, and an active community of
>>contributors makes a big difference between a good and less-good Wiki.
>>Better content on the Wiki naturally leads to more people reading, so
>>anything we can do to eliminate barriers to entry for contributing to
>> our
>>wiki is a good thing.  Having the wiki right there on GitHub removes a
>> big
>>impediment, we should def do this.
>> 
>>Thanks,
>> 
>>Blake
>> 
>> 
>>On Thu, Apr 23, 2020 at 8:14 PM Nabarun Nag  wrote:
>> 
>>> Hi Anthony!
>>> 
>>> Sorry for the late reply but I was doing some research. The issues
>> and wiki
>>> section as of now has been used by few engineers only and Confluent
>> has not
>>> yet entered any issues as they are still reviewing the project. I
>> went
>>> ahead and looked into all projects in the Apache domain using issues
>> and
>>> the extra features they enable.
>>> *JIRA vs Issues:*
>>> 
>>>   - There are a sizable number of Apache projects who are using
>> GitHub
>>>   issues
>>>   - One clear advantage is the automatic linking of PRs and Issues.
>> Issues
>>>   can be closed automatically once the PR is merged.
>>>   - It can also enable a feature to delete the feature branch
>>>   automatically once the PRs is merged (we have lot unused
>>> feature/GEODE-
>>>   branches in origin which were not deleted after merging PRs)
>>>   - It enables us to use Github Project management(Github version of
>>>   PivotalTracker)  which is integrated with Github issues and PRs
>> and all
>>> the
>>>   movement from "To-do", "In-progress", "resolved" and "closed" are
>>> automated
>>>   depending on if a PR is opened, requires reviews, reviewed and
>> merged
>>> state.
>>> 
>>> *Github Wiki vs Confluence Wiki:*
>>> 
>>>   - As you have mentioned that visibility is more important, we can
>> follow
>>>   other open-source products like Greenplum, Hystrix and we can use
>> the
>>> wiki
>>>   page to explain stuff like how to contribute, basic architecture,
>>> internal
>>>   knowledge, i.e information that is needed to contribute to Geode.
>>>   - A signification advantage is the colocation of code and wiki.
>> Any
>>>   developer can find Geode GitHub repo and that person now has all
>> the
>>> tools
>>>   needed to start contributing.
>>> 
>>> 
>>> A few examples of well-written wikis on GitHub:
>>> 
>>>   -
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fd3%2Fd3%2Fwikidata=02%7C01%7Cdaveba%40vmware.com%7Cb17baa964f014fcecc5108d7e85a6b55%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637233347359128192sdata=Yq%2Bi%2FuU2%2B5JiQ1jd%2BasQ0%2F%2BTPrK4vdxm%2FK6Faw4UW3M%3Dreserved=0
>>>   -
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNetflix%2FHystrix%2Fwikidata=02%7C01%7Cdaveba%40vmware.com%7Cb17baa964f014fcecc5108d7e85a6b55%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637233347359128192sdata=1c5DQgA%2BWzGFZW5v%2FJdJeeyyELsNyWuFD3JNC2C5VhI%3Dreserved=0
>>>   -
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fhelix%2Fwikidata=02%7C01%7Cdaveba%40vmware.com%7Cb17baa964f014fcecc5108d7e85a6b55%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637233347359128192sdata=89fieZFbngwXwD2uXCkEg0PTWtw1nbtU2xVn%2BpPm%2FFU%3Dreserved=0
>>> 
>>> 
>>> ASF: word on the street is that it was mentioned in ApacheCon, that
>> they
>>> support the use of Github wiki and issues in ASF projects, and this
>> can
>>> also be seen in multiple INFRA tickets mentioning enabling wiki.
>>> 
>>> I am also looking into ZenHub to improve our workflow. ZenHub is a
>> very
>>> robust project management tools used by Apache Contributors and
>>> 

Re: Switching default branch in .net core repo

[Mark Bretl]

+1

--Mark

On Thu, Apr 23, 2020 at 9:47 AM Dave Barnes  wrote:

> +1
> Dave
>
> On 4/23/20, 8:29 AM, "Karen Miller"  wrote:
>
> +1
> Karen
>
>
> On Thu, Apr 23, 2020 at 8:14 AM Dan Smith  wrote:
>
> > +1
> >
> > -Dan
> >
> > On Thu, Apr 23, 2020, 8:05 AM Anthony Baker 
> wrote:
> >
> > > Please do, this will match our default approach to development
> > > (gitflow-ish).
> > >
> > > +1
> > >
> > > Anthony
> > >
> > >
> > > > On Apr 23, 2020, at 7:35 AM, Blake Bender 
> wrote:
> > > >
> > > > Good morning,
> > > >
> > > > We created a repo yesterday for the .net core client work, and
> the
> > > default
> > > > branch out of the gate is set to master.  I'd like to switch it
> to
> > > develop,
> > > > like the rest of the Geode repos, which apparently requires a
> quick
> > > > heads-up and a couple of +1s to go ahead with.  So... is
> everyone okay
> > > with
> > > > this change?
> > > >
> > > > Thanks,
> > > >
> > > > Blake
> > >
> > >
> >
>
>

Re: [DISCUSS] preparing for Geode 1.13.0 release

[Mark Bretl]

Thanks Dave!

--Mark

On Thu, Apr 23, 2020 at 2:55 PM Owen Nichols  wrote:

> Awesome, thanks for stepping up, Dave!
>
> Please familiarize yourself with the instructions at
> https://cwiki.apache.org/confluence/display/GEODE/Releasing+Apache+Geode.
> If you have any questions along the way, there are quite a few past release
> managers on the dev list you can reach out to.
>
> > On Apr 23, 2020, at 2:40 PM, Dave Barnes  wrote:
> >
> > I'm willing.
> >
> > On 4/22/20, 11:43 AM, "Owen Nichols"  wrote:
> >
> >Geode is scheduled to cut support/1.13 on May 4, as per the quarterly
> release schedule approved [1] in 2018 and affirmed in last month’s
> “Shipping patch releases” RFC [2].
> >
> >Please volunteer if you are interested in serving as Release Manager
> for Geode 1.13.0.
> >
> >[1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F8626f7cc73b49cc90129ec5f6021adab3815469048787032935bfc1e%2540%253Cdev.geode.apache.org%253Edata=02%7C01%7Cdaveba%40vmware.com%7Ccee476d475d84a2a3ceb08d7e6ed0867%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637231778047185914sdata=%2BC7sDyrQloYd%2F4UxmBPEXvDKmeKHXzKV6rxPdghbZIE%3Dreserved=0
> >[2]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FGEODE%2FShipping%2Bpatch%2Breleasesdata=02%7C01%7Cdaveba%40vmware.com%7Ccee476d475d84a2a3ceb08d7e6ed0867%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637231778047190906sdata=CAMNC6g7u9GconPgjQF1Qvk90EIFvPvQ449jHjitRIY%3Dreserved=0
> >
>
>

Re: Proposal to restore Pulse logging in support/1.12

[Mark Bretl]

+1

On Fri, Apr 24, 2020 at 3:07 PM Owen Nichols  wrote:

> +1
>
> > On Apr 24, 2020, at 3:06 PM, Jinmei Liao  wrote:
> >
> > +1
> >
> > On Fri, Apr 24, 2020 at 2:53 PM Anthony Baker  wrote:
> >
> >> +1
> >>
> >>> On Apr 24, 2020, at 2:46 PM, Dale Emery  wrote:
> >>>
> >>> During the cleanup of the gradle build and logging, the Pulse webapp
> >> lost its slf4j implementation. As a result, Pulse stopped writing log
> files.
> >>>
> >>> I’ve restored Pulse logging in the develop branch.
> >>>
> >>> I would like to restore it in support/1.12. I’ve created a PR:
> >> https://github.com/apache/geode/pull/4992 <
> >> https://github.com/apache/geode/pull/4992>
> >>>
> >>> Cheers,
> >>> Dale
> >>>
> >>> —
> >>> Dale Emery
> >>> dem...@pivotal.io
> >>> dem...@vmware.com
> >>>
> >>
> >>
> >
> > --
> > Cheers
> >
> > Jinmei
>
>

Re: Proposal to restore Pulse logging in support/1.12

[Owen Nichols]

+1

> On Apr 24, 2020, at 3:06 PM, Jinmei Liao  wrote:
> 
> +1
> 
> On Fri, Apr 24, 2020 at 2:53 PM Anthony Baker  wrote:
> 
>> +1
>> 
>>> On Apr 24, 2020, at 2:46 PM, Dale Emery  wrote:
>>> 
>>> During the cleanup of the gradle build and logging, the Pulse webapp
>> lost its slf4j implementation. As a result, Pulse stopped writing log files.
>>> 
>>> I’ve restored Pulse logging in the develop branch.
>>> 
>>> I would like to restore it in support/1.12. I’ve created a PR:
>> https://github.com/apache/geode/pull/4992 <
>> https://github.com/apache/geode/pull/4992>
>>> 
>>> Cheers,
>>> Dale
>>> 
>>> —
>>> Dale Emery
>>> dem...@pivotal.io
>>> dem...@vmware.com
>>> 
>> 
>> 
> 
> -- 
> Cheers
> 
> Jinmei

Re: Proposal to restore Pulse logging in support/1.12

[Jinmei Liao]

+1

On Fri, Apr 24, 2020 at 2:53 PM Anthony Baker  wrote:

> +1
>
> > On Apr 24, 2020, at 2:46 PM, Dale Emery  wrote:
> >
> > During the cleanup of the gradle build and logging, the Pulse webapp
> lost its slf4j implementation. As a result, Pulse stopped writing log files.
> >
> > I’ve restored Pulse logging in the develop branch.
> >
> > I would like to restore it in support/1.12. I’ve created a PR:
> https://github.com/apache/geode/pull/4992 <
> https://github.com/apache/geode/pull/4992>
> >
> > Cheers,
> > Dale
> >
> > —
> > Dale Emery
> > dem...@pivotal.io
> > dem...@vmware.com
> >
>
>

-- 
Cheers

Jinmei

Re: Proposal to restore Pulse logging in support/1.12

[Anthony Baker]

+1

> On Apr 24, 2020, at 2:46 PM, Dale Emery  wrote:
> 
> During the cleanup of the gradle build and logging, the Pulse webapp lost its 
> slf4j implementation. As a result, Pulse stopped writing log files.
> 
> I’ve restored Pulse logging in the develop branch.
> 
> I would like to restore it in support/1.12. I’ve created a PR: 
> https://github.com/apache/geode/pull/4992 
> 
> 
> Cheers,
> Dale
> 
> —
> Dale Emery
> dem...@pivotal.io
> dem...@vmware.com
> 

Proposal to restore Pulse logging in support/1.12

[Dale Emery]

During the cleanup of the gradle build and logging, the Pulse webapp lost its 
slf4j implementation. As a result, Pulse stopped writing log files.

I’ve restored Pulse logging in the develop branch.

I would like to restore it in support/1.12. I’ve created a PR: 
https://github.com/apache/geode/pull/4992 


Cheers,
Dale

—
Dale Emery
dem...@pivotal.io
dem...@vmware.com

Re: [VOTE] Using Github issues and wiki for geode-kafka-connector project

[Robert Houghton]

Looks like we can use the `.asf.yml` file in our repositories to enable
`issues` and `wiki` behavior ourselves if we decide we like the feature :)

On Fri, Apr 24, 2020 at 7:46 AM Dave Barnes  wrote:

> +1
> I like the look of the samples.
> I also want to echo Anthony and Blake: Accessibility is huge, not only
> because it smooths the way for adding content, but for pruning outdated
> material.
>
> On 4/24/20, 7:18 AM, "Blake Bender"  wrote:
>
> +1 - Wow, research - nice work, Naba, this is great!
>
> Just want to emphasize a larger point I failed to make in my response
> re:
> Markdown.  My experience with Wikis has been that it's very difficult
> to
> convince people to contribute entries/edits, and an active community of
> contributors makes a big difference between a good and less-good Wiki.
> Better content on the Wiki naturally leads to more people reading, so
> anything we can do to eliminate barriers to entry for contributing to
> our
> wiki is a good thing.  Having the wiki right there on GitHub removes a
> big
> impediment, we should def do this.
>
> Thanks,
>
> Blake
>
>
> On Thu, Apr 23, 2020 at 8:14 PM Nabarun Nag  wrote:
>
> > Hi Anthony!
> >
> > Sorry for the late reply but I was doing some research. The issues
> and wiki
> > section as of now has been used by few engineers only and Confluent
> has not
> > yet entered any issues as they are still reviewing the project. I
> went
> > ahead and looked into all projects in the Apache domain using issues
> and
> > the extra features they enable.
> > *JIRA vs Issues:*
> >
> >- There are a sizable number of Apache projects who are using
> GitHub
> >issues
> >- One clear advantage is the automatic linking of PRs and Issues.
> Issues
> >can be closed automatically once the PR is merged.
> >- It can also enable a feature to delete the feature branch
> >automatically once the PRs is merged (we have lot unused
> > feature/GEODE-
> >branches in origin which were not deleted after merging PRs)
> >- It enables us to use Github Project management(Github version of
> >PivotalTracker)  which is integrated with Github issues and PRs
> and all
> > the
> >movement from "To-do", "In-progress", "resolved" and "closed" are
> > automated
> >depending on if a PR is opened, requires reviews, reviewed and
> merged
> > state.
> >
> > *Github Wiki vs Confluence Wiki:*
> >
> >- As you have mentioned that visibility is more important, we can
> follow
> >other open-source products like Greenplum, Hystrix and we can use
> the
> > wiki
> >page to explain stuff like how to contribute, basic architecture,
> > internal
> >knowledge, i.e information that is needed to contribute to Geode.
> >- A signification advantage is the colocation of code and wiki.
> Any
> >developer can find Geode GitHub repo and that person now has all
> the
> > tools
> >needed to start contributing.
> >
> >
> > A few examples of well-written wikis on GitHub:
> >
> >-
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fd3%2Fd3%2Fwikidata=02%7C01%7Cdaveba%40vmware.com%7Cb17baa964f014fcecc5108d7e85a6b55%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637233347359128192sdata=Yq%2Bi%2FuU2%2B5JiQ1jd%2BasQ0%2F%2BTPrK4vdxm%2FK6Faw4UW3M%3Dreserved=0
> >-
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNetflix%2FHystrix%2Fwikidata=02%7C01%7Cdaveba%40vmware.com%7Cb17baa964f014fcecc5108d7e85a6b55%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637233347359128192sdata=1c5DQgA%2BWzGFZW5v%2FJdJeeyyELsNyWuFD3JNC2C5VhI%3Dreserved=0
> >-
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fhelix%2Fwikidata=02%7C01%7Cdaveba%40vmware.com%7Cb17baa964f014fcecc5108d7e85a6b55%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637233347359128192sdata=89fieZFbngwXwD2uXCkEg0PTWtw1nbtU2xVn%2BpPm%2FFU%3Dreserved=0
> >
> >
> > ASF: word on the street is that it was mentioned in ApacheCon, that
> they
> > support the use of Github wiki and issues in ASF projects, and this
> can
> > also be seen in multiple INFRA tickets mentioning enabling wiki.
> >
> > I am also looking into ZenHub to improve our workflow. ZenHub is a
> very
> > robust project management tools used by Apache Contributors and
> > corporations like VMware.
> >
> > Regards
> > Nabarun Nag
> >
> >
> > On Thu, Apr 23, 2020 at 2:40 PM Anthony Baker 
> wrote:
> >
> > > Having used pretty every style of wiki, I care less about the wiki
> tech
> > > and more about making the content easily accessible and
> discoverable for
> > > our users and contributors.  Our current wiki has a lot of useful
> > >