Re: [VOTE] Release Apache DevLake (Incubating) v0.21.0-rc1

[Felix Cheung]

+1 (binding)

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers

did not compile from source


On Mon, Apr 15, 2024 at 5:02 AM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> I checked:
> - incubating is in the name
> - LICENSE and NOTICE look good
> - DISCLAIMER is present
> - ASF header is there
> - No binary file found in source distribution
> - Build worked on my machine
>
> Thanks
> Regards
> JB
>
> On Thu, Apr 11, 2024 at 2:23 PM Zikuan An  wrote:
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache DevLake (Incubating)
> > v0.21.0-rc1.
> > The Apache DevLake community has voted on and approved a proposal
> > to release Apache DevLake (Incubating) version v0.21.0-rc1.
> >
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Community vote thread:
> >
> > https://lists.apache.org/thread/j8qowrhfdoqgyghg904bjs8ds639dl90
> >
> >
> > Community vote result thread:
> >
> > https://lists.apache.org/thread/x32ln363j3rntglrbb1hsqj5bd8ns6y2
> >
> >
> > The release candidates:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.21.0-incubating-rc1
> >
> >
> > Git tag for the release:
> >
> > https://github.com/apache/incubator-devlake/releases/tag/v0.21.0-rc1
> >
> >
> > Keys to verify the Release Candidate:
> >
> > https://downloads.apache.org/incubator/devlake/KEYS
> >
> >
> > How to build:
> >
> > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> >
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes is reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> >
> > Thanks
> >
> > Zikuan An
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] SPIP: Pure Python Package in PyPI (Spark Connect)

[Felix Cheung]

+1

From: Denny Lee 
Sent: Monday, April 1, 2024 10:06:14 AM
To: Hussein Awala 
Cc: Chao Sun ; Hyukjin Kwon ; Mridul 
Muralidharan ; dev 
Subject: Re: [VOTE] SPIP: Pure Python Package in PyPI (Spark Connect)

+1 (non-binding)


On Mon, Apr 1, 2024 at 9:24 AM Hussein Awala 
mailto:huss...@awala.fr>> wrote:
+1(non-binding) I add to the difference will it make that it will also simplify 
package maintenance and easily release a bug fix/new feature without needing to 
wait for Pyspark to release.

On Mon, Apr 1, 2024 at 4:56 PM Chao Sun 
mailto:sunc...@apache.org>> wrote:
+1

On Sun, Mar 31, 2024 at 10:31 PM Hyukjin Kwon 
mailto:gurwls...@apache.org>> wrote:
Oh I didn't send the discussion thread out as it's pretty simple, non-invasive 
and the discussion was sort of done as part of the Spark Connect initial 
discussion ..

On Mon, Apr 1, 2024 at 1:59 PM Mridul Muralidharan 
mailto:mri...@gmail.com>> wrote:

Can you point me to the SPIP’s discussion thread please ?
I was not able to find it, but I was on vacation, and so might have missed this 
…


Regards,
Mridul

On Sun, Mar 31, 2024 at 9:08 PM Haejoon Lee 
 wrote:
+1

On Mon, Apr 1, 2024 at 10:15 AM Hyukjin Kwon 
mailto:gurwls...@apache.org>> wrote:
Hi all,

I'd like to start the vote for SPIP: Pure Python Package in PyPI (Spark Connect)

JIRA
Prototype
SPIP 
doc

Please vote on the SPIP for the next 72 hours:

[ ] +1: Accept the proposal as an official SPIP
[ ] +0
[ ] -1: I don’t think this is a good idea because …

Thanks.

Re: Gluten has been transferred to Apache repository(https://github.com/apache/incubator-gluten.git)

[Felix Cheung]

Great!

On Mon, Mar 11, 2024 at 3:35 AM Keyong Zhou  wrote:

> Great! Thanks for the effort!
>
> Regards,
> Keyong Zhou
>
> Jacky Lee  于2024年3月11日周一 16:40写道：
>
> > Great. Thanks for your efforts, Weiting!
> >
> > Yu Li  于2024年3月11日周一 16:37写道：
> > >
> > > Great to know! Thanks for the update and efforts, Weiting!
> > >
> > > Best Regards,
> > > Yu
> > >
> > > On Sat, 9 Mar 2024 at 11:05, ShaoFeng Shi 
> > wrote:
> > > >
> > > > Weiting, that's great! Thanks for the progress update.
> > > >
> > > > Best regards,
> > > >
> > > > Shaofeng Shi 史少锋
> > > > Apache Kylin PMC member,
> > > > Apache Incubator PMC member,
> > > > Email: shaofeng...@apache.org
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > XiDuo You  于2024年3月8日周五 09:04写道：
> > > >>
> > > >> Thank you Weiting !
> > > >>
> > > >> WeitingChen  于2024年3月8日周五 00:33写道：
> > > >> >
> > > >> > FYI.
> > > >> > Gluten has been transferred to the Apache repository:
> > https://github.com/apache/incubator-gluten.git.
> > > >> > The original git address will be redirected to the new one.
> > > >> > We may be required to use the following couple of days to test the
> > code with CI servers in Apache.
> > > >> > Please allow a slow response for code review or CI/CD test failure
> > during the time frame.
> > > >> >
> > > >> > Thanks,
> > > >> > Weiting
> > > >>
> > > >>
> -
> > > >> To unsubscribe, e-mail: dev-unsubscr...@gluten.apache.org
> > > >> For additional commands, e-mail: dev-h...@gluten.apache.org
> > > >>
> >
>

Re: [VOTE] Have Amoro join the Incubator

[Felix Cheung]

+1 binding

On Sun, Mar 3, 2024 at 3:56 AM PJ Fanning  wrote:

> +1 (binding)
>
> On 2024/03/03 07:08:53 Imba Jin wrote:
> > +1 (non-binding)
> >
> > Good luck~
> >
> > On 2024/03/03 01:44:24 Justin Mclean wrote:
> > > Hi,
> > >
> > > Following on from the discussion of the Amoro proposal [1][2], let's
> vote on having it join the Incubator.
> > >
> > > Please cast your vote:
> > >
> > > [ ] +1, have it join the Incubator as an incubating project
> > > [ ] +0, I have no strong opinion either way
> > > [ ] -1, do not have it join the Incubator because...
> > >
> > > Kind Regards,
> > > Justin
> > >
> > > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal
> > > 2. https://lists.apache.org/thread/7t2bm6x19zq2d79cn8jj2wqd3f2t3k00
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Gluten Into the ASF Incubator

[Felix Cheung]

+1 binding

On Wed, Jan 3, 2024 at 10:26 PM vin jake  wrote:

> +1(non-binding).
>
> Good luck.
>
> Best,
> kabikabi.
>
> On Thu, Jan 4, 2024 at 10:48 AM ShaoFeng Shi 
> wrote:
>
> > Hi Incubator,
> >
> > Following the discussion [DISCUSS] Gluten proposal[1],
> > I am starting this official vote for the Gluten project.
> >
> > Here is their proposal:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/GlutenProposal
> >
> > Please cast your vote:
> >
> > [ ] +1, bring into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring Gluten into the Incubator, because...
> >
> > The vote will open for one week from today.
> >
> > [1] https://lists.apache.org/thread/xgsm75t721vgnlthgy84909ggqok77j4
> >
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> > Apache Kylin PMC member,
> > Apache Incubator PMC member,
> > Email: shaofeng...@apache.org
> >
>

Re: [DISCUSS] Gluten proposal

[Felix Cheung]

Very interesting. Let me know if I can help as mentor



On Sat, Dec 23, 2023 at 7:30 AM tison  wrote:

> Thanks for driving this proposal Shaofeng :D
>
> +1 to support this project entering the Incuabtor. It's in good shape
> to develop an OSS project with a diverse group. Hopefully, the
> Incubator can help it evaluate whether The Apache Way fits in its
> community and growth.
>
> One thing to be noticed is that you're not listed on the mentor list.
> By definition the champion helps the candidate go through the
> proposing stage and is not always a mentor. If you're going to be the
> mentor, you should add yourself to the mentor list also. But it's OK
> that you can serve as a mentor.
>
> Best,
> tison.
>
> ShaoFeng Shi  于2023年12月23日周六 20:43写道：
> >
> > Hi Enrico,
> >
> > This is a good question. Actually I asked the same to the team when they
> > find me for coaching.
> >
> > As the proposal mentioned, Gluten is a middle layer between the JVM-based
> > SQL engine and native libraries. It connects the two sides, and build
> > common services like unified plan transformation, seamless native
> > integration, clear JNI interfaces, etc. Spark is the first engine it
> > supports now, but the framework and mechanism can also work for other
> > engines like Trino, Flink SQL in the future (the proposal also mentioned
> > this). Underlying Gluten, it can integrate with different libararies,
> like
> > Velox, Clickhouse and Arrow (not ready yet). So, its mission and scope is
> > different, that's why we put it as a new project.
> >
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> > Apache Kylin PMC,
> > Apache Incubator PMC,
> > Email: shaofeng...@apache.org
> >
> > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> > Join Kylin user mail group: user-subscr...@kylin.apache.org
> > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> >
> >
> >
> >
> > Enrico Olivelli  于2023年12月22日周五 22:43写道：
> >
> > > Shaofeng,
> > >
> > > Il giorno ven 22 dic 2023 alle ore 13:59 ShaoFeng Shi
> > >  ha scritto:
> > > >
> > > > Hi IPMC members,
> > > >
> > > > I would like to propose a new project to the ASF incubator - Gluten.
> > > >
> > > > Gluten[1] is a middle layer responsible for offloading Apache Spark
> SQL
> > > > queries to native engines. This project aims to address the CPU
> > > > computational bottleneck to offload SparkSQL operators to native
> engines
> > > in
> > > > data loading scenarios based on Apache Spark.
> > >
> > > Have you considered making this project a subproject of Apache Spark ?
> > >
> > > Enrico
> > >
> > > >
> > > > Here is the proposal -
> > > > https://cwiki.apache.org/confluence/display/INCUBATOR/GlutenProposal
> > > >
> > > > I would be the Champion of the project. I will mentor and help the
> > > project
> > > > through the incubator with Yu Li [l...@apache.org], Kent Yao [
> > > y...@apache.org]
> > > > and Wenli Zhang [ovi...@apache.org] .
> > > >
> > > > We are open to hearing the feedback from the incubator.
> > > >
> > > > Best,
> > > > Shaofeng Shi.
> > > >
> > > > [1] https://oap-project.github.io/gluten/
> > > >
> > > > Best regards,
> > > >
> > > > Shaofeng Shi 史少锋
> > > > Apache Kylin PMC,
> > > > Apache Incubator PMC,
> > > > Email: shaofeng...@apache.org
> > > >
> > > > Apache Kylin FAQ:
> https://kylin.apache.org/docs/gettingstarted/faq.html
> > > > Join Kylin user mail group: user-subscr...@kylin.apache.org
> > > > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc3

[Felix Cheung]

To be clear this section of the license file is about
config-ui/.yarn/releases/yarn-3.4.1.cjs ?

The following libraries are distributed under the MIT License: fill-range -
Copyright (c) 2014-present, Jon Schlinkert. is-extglob - Copyright (c)
2014-2016, Jon Schlinkert. is-glob - Copyright (c) 2014-2017, Jon
Schlinkert. is-number - Copyright (c) 2014-present, Jon Schlinkert.
is-windows - Copyright © 2015-2018, Jon Schlinkert. to-regex-range -
Copyright (c) 2015-present, Jon Schlinkert. Yarn software - Copyright (c)
2015, Rebecca Turner Yarn software - Copyright Joyent, Inc. and other Node
contributors. Yarn software - Copyright Node.js contributors. All rights
reserved. Yarn software - Copyright (c) 2014 Blake Embrey (
he...@blakeembrey.com)


On Sun, Dec 10, 2023 at 6:10 PM Zikuan An  wrote:

> The file is already listed, it is
> ./config-ui/.yarn/releases/yarn-3.4.1.cjs. It is a generated binary file
> and includes multiple third-party codes, each under its respective license.
> [image: image.png]
>
> Felix Cheung  于2023年12月11日周一 05:46写道：
>
>> Is it possible to list files?
>> > point to the relative file path
>>
>>
>> On Fri, Dec 8, 2023 at 7:45 PM Zikuan An  wrote:
>>
>> > Hi Felix,
>> >
>> > Thank you very much for your reply.
>> >
>> > I think we have listed them all,
>> > You can find the code and license on
>> > https://github.com/apache/incubator-devlake/pull/6483 or
>> > https://github.com/apache/incubator-devlake/blob/v0.19.0-rc3/LICENSE
>> > <https://github.com/apache/incubator-devlake/blob/v0.19.0-rc3/LICENSE)>
>> > It's just that it's aggregated instead of listing each one individually.
>> >
>> > Best,
>> > Zikuan An
>> >
>> > Felix Cheung  于2023年12月9日周六 06:39写道：
>> >
>> > > I see the main comments from rc2 have been addressed. To add though,
>> if
>> > > possible please add text in LICENSE to point to the relative file
>> path to
>> > > files under these licenses (remaining comment from the last vote)
>> > >
>> > > - You still need to, as required by the license, include the full
>> text of
>> > > the MIT licenses, which include the copyright line. - What code is
>> > > "Copyright (c) 2015, Rebecca Turner”, and what license is it under? -
>> > What
>> > > code is "Copyright Joyent, Inc. and other Node contributors.”, and
>> what
>> > > license is it under? - What code is "Copyright Node.js contributors.
>> All
>> > > rights reserved.", and what license is it under? - What code is
>> > "Copyright
>> > > (c) 2014 Blake Embrey (he...@blakeembrey.com)”, and what license is
>> it
>> > > under?
>> > >
>> > >
>> > > On Mon, Nov 27, 2023 at 7:26 PM Zikuan An  wrote:
>> > >
>> > > > Hello everyone,
>> > > >
>> > > > This is a call for the vote to release Apache DevLake (Incubating)
>> > > > v0.19.0-rc3.
>> > > > The Apache DevLake community has voted on and approved a proposal to
>> > > > release
>> > > >  Apache DevLake (Incubating) version v0.19.0-rc3.
>> > > >
>> > > >
>> > > > We now kindly request the Incubator PMC members review and vote on
>> this
>> > > > incubator release.
>> > > >
>> > > > Community vote thread:
>> > > >
>> > > > https://lists.apache.org/thread/g9jm19jyo3vkzq3ngvg2tx66wkdjbkb2
>> > > >
>> > > >
>> > > > Community vote result thread:
>> > > >
>> > > > https://lists.apache.org/thread/v735p87z7rl4pcdow521rcnq9r3n2jvx
>> > > >
>> > > >
>> > > > The release candidates:
>> > > >
>> > > >
>> > > >
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc3
>> > > >
>> > > >
>> > > > Git tag for the release:
>> > > >
>> > > >
>> https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc3
>> > > >
>> > > >
>> > > > Keys to verify the Release Candidate:
>> > > >
>> > > > https://downloads.apache.org/incubator/devlake/KEYS
>> > > >
>> > > >
>> > > > How to build:
>> > > >
>> > > > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>> > > >
>> > > >
>> > > > The vote will be open for at least 72 hours or until the necessary
>> > number
>> > > > of votes is reached.
>> > > >
>> > > > Please vote accordingly:
>> > > > [ ] +1 approve
>> > > > [ ] +0 no opinion
>> > > > [ ] -1 disapprove with the reason
>> > > >
>> > > >
>> > > > Thanks
>> > > >
>> > > > Zikuan An
>> > > >
>> > >
>> >
>>
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc3

[Felix Cheung]

Is it possible to list files?
> point to the relative file path


On Fri, Dec 8, 2023 at 7:45 PM Zikuan An  wrote:

> Hi Felix,
>
> Thank you very much for your reply.
>
> I think we have listed them all,
> You can find the code and license on
> https://github.com/apache/incubator-devlake/pull/6483 or
> https://github.com/apache/incubator-devlake/blob/v0.19.0-rc3/LICENSE
> <https://github.com/apache/incubator-devlake/blob/v0.19.0-rc3/LICENSE)>
> It's just that it's aggregated instead of listing each one individually.
>
> Best,
> Zikuan An
>
> Felix Cheung  于2023年12月9日周六 06:39写道：
>
> > I see the main comments from rc2 have been addressed. To add though, if
> > possible please add text in LICENSE to point to the relative file path to
> > files under these licenses (remaining comment from the last vote)
> >
> > - You still need to, as required by the license, include the full text of
> > the MIT licenses, which include the copyright line. - What code is
> > "Copyright (c) 2015, Rebecca Turner”, and what license is it under? -
> What
> > code is "Copyright Joyent, Inc. and other Node contributors.”, and what
> > license is it under? - What code is "Copyright Node.js contributors. All
> > rights reserved.", and what license is it under? - What code is
> "Copyright
> > (c) 2014 Blake Embrey (he...@blakeembrey.com)”, and what license is it
> > under?
> >
> >
> > On Mon, Nov 27, 2023 at 7:26 PM Zikuan An  wrote:
> >
> > > Hello everyone,
> > >
> > > This is a call for the vote to release Apache DevLake (Incubating)
> > > v0.19.0-rc3.
> > > The Apache DevLake community has voted on and approved a proposal to
> > > release
> > >  Apache DevLake (Incubating) version v0.19.0-rc3.
> > >
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > Community vote thread:
> > >
> > > https://lists.apache.org/thread/g9jm19jyo3vkzq3ngvg2tx66wkdjbkb2
> > >
> > >
> > > Community vote result thread:
> > >
> > > https://lists.apache.org/thread/v735p87z7rl4pcdow521rcnq9r3n2jvx
> > >
> > >
> > > The release candidates:
> > >
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc3
> > >
> > >
> > > Git tag for the release:
> > >
> > > https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc3
> > >
> > >
> > > Keys to verify the Release Candidate:
> > >
> > > https://downloads.apache.org/incubator/devlake/KEYS
> > >
> > >
> > > How to build:
> > >
> > > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> > >
> > >
> > > The vote will be open for at least 72 hours or until the necessary
> number
> > > of votes is reached.
> > >
> > > Please vote accordingly:
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > >
> > > Thanks
> > >
> > > Zikuan An
> > >
> >
>

Re: [VOTE] Accept Fury Into the ASF Incubator

[Felix Cheung]

+1 binding

On Sat, Dec 9, 2023 at 11:05 PM Ayush Saxena  wrote:

> +1(Binding)
>
> -Ayush
>
> > On 10-Dec-2023, at 12:10 PM, zhongyi tan  wrote:
> >
> > +1 （binding）
> >
> >> On Fri, Dec 8, 2023 at 7:05 PM tison  wrote:
> >>
> >> Hi Incubator
> >>
> >> Following the discussion [DISCUSS] Incubating Proposal of Fury [1], I
> >> am starting this official vote for the Fury project.
> >>
> >> Here is their proposal:
> >> https://cwiki.apache.org/confluence/display/INCUBATOR/Fury+Proposal
> >>
> >> Please cast your vote:
> >>
> >> [ ] +1, bring into the Incubator
> >> [ ] +0, I don't care either way
> >> [ ] -1, do not bring Fury into the Incubator, because...
> >>
> >> The vote will open for one week from today, Dec. 8th, 2023
> >>
> >> Best,
> >> tison.
> >>
> >> [1] https://lists.apache.org/thread/jr3qwzxg2m6507zsll5fs8mopcco3ny3
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Uniffle (Incubating) V0.8.0 RC3

[Felix Cheung]

+1

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers


On Thu, Dec 7, 2023 at 6:36 AM Xianjing Feng 
wrote:

> Hello Incubator Community,
>
> This is a call for a vote to release Apache Uniffle(Incubating) version
> V0.8.0 RC3
>
> The Apache Uniffle community has voted on and approved a proposal to
> release
> Apache Uniffle(Incubating) version V0.8.0 RC3
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Uniffle community vote thread:
> • https://lists.apache.org/thread/9psgtxkdynqrcsjcgotfzmx4jl33t0d2
>
> Vote result thread:
> • https://lists.apache.org/thread/j8nhy5o4k5j3c1jd5vrmqg9zmxfz7y92
>
> The release candidate:
> • https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.8.0-rc3/
>
> Git tag for the release:
> • https://github.com/apache/incubator-uniffle/tree/v0.8.0-rc3
>
> Release notes:
> • https://uniffle.apache.org/download/release-notes-0.8.0
>
> The artifacts signed with PGP key [3E6F20AC33D1F201],
> corresponding to [xianjingf...@apache.org], that can be found in keys
> file:
> • https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS
>
> As the DISCLAIMER-WIP shows, this release still left some license
> problems, which will be gradually resolved during incubation.
>
> The vote will be open for at least 72 hours or until necessary
> number of votes are reached.
>
> Please vote accordingly:
>
> [] +1 approve
> [] +0 no opinion
> [] -1 disapprove with the reason
>
> Thanks,
> On behalf of Apache Uniffle (Incubating) community
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc3

[Felix Cheung]

I see the main comments from rc2 have been addressed. To add though, if
possible please add text in LICENSE to point to the relative file path to
files under these licenses (remaining comment from the last vote)

- You still need to, as required by the license, include the full text of
the MIT licenses, which include the copyright line. - What code is
"Copyright (c) 2015, Rebecca Turner”, and what license is it under? - What
code is "Copyright Joyent, Inc. and other Node contributors.”, and what
license is it under? - What code is "Copyright Node.js contributors. All
rights reserved.", and what license is it under? - What code is "Copyright
(c) 2014 Blake Embrey (he...@blakeembrey.com)”, and what license is it
under?


On Mon, Nov 27, 2023 at 7:26 PM Zikuan An  wrote:

> Hello everyone,
>
> This is a call for the vote to release Apache DevLake (Incubating)
> v0.19.0-rc3.
> The Apache DevLake community has voted on and approved a proposal to
> release
>  Apache DevLake (Incubating) version v0.19.0-rc3.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/g9jm19jyo3vkzq3ngvg2tx66wkdjbkb2
>
>
> Community vote result thread:
>
> https://lists.apache.org/thread/v735p87z7rl4pcdow521rcnq9r3n2jvx
>
>
> The release candidates:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc3
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc3
>
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Thanks
>
> Zikuan An
>

Re: [DISCUSS] OneTable proposal

[Felix Cheung]

Interesting. Let me know if I can be of help as mentor


On Mon, Dec 4, 2023 at 1:35 PM Austin Bennett  wrote:

> Awesome -- OneTable has a great purpose/mission, and can be really
> useful!  I look forward to helping where I am able.
>
>
> On 2023/12/04 21:23:17 Jesus Camacho Rodriguez wrote:
> > Hi All,
> >
> > I would like to propose a new project to the ASF incubator - OneTable.
> >
> > OneTable[1] is an omni-directional converter for table formats that
> > facilitates interoperability across data processing systems and query
> > engines. Currently, OneTable supports widely adopted open-source table
> > formats such as Apache Hudi, Apache Iceberg, and Delta Lake.
> >
> > Here is the proposal -
> > https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal
> >
> > I would be the Champion of the project. I will mentor and help the
> project
> > through the incubator with Hitesh Shah [hit...@apache.org], Stamatis
> > Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré [
> > jbono...@apache.org].
> >
> > We are looking forward to your feedback!
> >
> > Thanks,
> > Jesús
> >
> > [1] https://github.com/onetable-io/onetable
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc2

[Felix Cheung]

+1 binding

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers

what is this file config-ui/.yarn/releases/yarn-3.4.1.cjs - seems to have
code in it (and it does not have a license header)


On Wed, Nov 15, 2023 at 6:17 AM Willem Jiang  wrote:

> +1(binding).
>
> Here is what I checked:
> - The checksums and signatures are validated.
> - The LICENSE and NOTICE files look good to me.
> - There is a DISCLAIMER file about incubating.
> - No binary files in the source release.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Nov 10, 2023 at 10:28 PM Zikuan An  wrote:
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache DevLake (Incubating)
> > v0.19.0-rc2.
> > The Apache DevLake community has voted on and approved a proposal to
> > release Apache DevLake (Incubating) version v0.19.0-rc2.
> >
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Community vote thread:
> >
> > https://lists.apache.org/thread/zqhrctqz39xyslfjsd0zz30gtdbv4t20
> >
> >
> > Community vote result thread:
> >
> > https://lists.apache.org/thread/g06ns1vbqopyw6r460m25pvcvwh932s6
> >
> >
> > The release candidates:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc2
> >
> >
> > Git tag for the release:
> >
> > https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc2
> >
> >
> > Keys to verify the Release Candidate:
> >
> > https://downloads.apache.org/incubator/devlake/KEYS
> >
> >
> > How to build:
> >
> > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> >
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes is reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> >
> > Thanks
> >
> > Zikuan An
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Answer into the Apache Incubator

[Felix Cheung]

+1 binding

On Tue, Oct 3, 2023 at 10:24 AM Craig Russell  wrote:

> +1 binding.
>
> Good luck!
> Craig
>
> > On Oct 2, 2023, at 17:17, Willem Jiang  wrote:
> >
> > Following up the [DISCUSS] thread on Answer [1] I would like to call a
> > VOTE to accept into the Apache Incubator.
> >
> > Answer is a question-and-answer (Q) platform software for teams at
> > any scale to build a help center, knowledge base, community forum,
> > etc.
> >
> > Please cast your vote:
> >
> >  [ ] +1, bring into the Incubator
> >  [ ] +0, I don't care either way
> >  [ ] -1, do not bring Answer into the Incubator, because...
> >
> > The vote will open at least for 72 hours and only votes from the
> > Incubator PMC are binding, but votes from everyone are welcome.
> >
> > Please check out the Answer Proposal from the incubator wiki[2].
> >
> > [1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn
> > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal
> >
> > Best Regards,
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> Craig L Russell
> c...@apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Teaclave (incubating) v0.5.1-rc.2

[Felix Cheung]

+1

- incubating in name
- signature and hash are fine

it looks like there is a conflict between KEYS (file) and keys (directory):
$ tar xzf apache-teaclave-0.5.1-rc.2-incubating.tar.gz
apache-teaclave-0.5.1-rc.2-incubating/KEYS: Can't replace existing
directory with non-directory
tar: Error exit delayed from previous errors.

- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- source files have ASF headers?

it looks like a lot of files are "external"? they do not have ASF header
/common/rusty_leveldb_sgx/*
/third_party/wasm-micro-runtime/*
/third_party/rust-sgx-sdk/*

what is the plan for those? do they have to be included in the source
release?

did not compile from source



On Fri, May 26, 2023 at 10:26 PM Gordon  wrote:

> +1, thanks.
>
> On Wed, May 24, 2023 at 11:00 PM He Sun  wrote:
>
> > Hi all,
> >
> > I am pleased to be calling this vote for the release of
> > Apache Teaclave (incubating) 0.5.1 (release candidate 2).
> >
> > The Apache Teaclave (incubating) community has voted and approved the
> > release. The result thread is
> > https://lists.apache.org/thread/qt3z2m4yvghxtvw3gwyorj67px8okjqy
> >
> > The release candidate to be voted over is available at:
> > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.5.1-rc.2/
> >
> > The artifacts signed with PGP key
> > [777A1FBA5762313CD86EC2727144C76533763CD9] in the keys file:
> > - https://dist.apache.org/repos/dist/dev/incubator/teaclave/KEYS
> >
> > The Git commit for this release is:
> > -
> >
> https://github.com/apache/incubator-teaclave/commit/39d575adf291431f2f9656057676cdc55d89f96f
> >
> > The release note is available in:
> > - https://github.com/apache/incubator-teaclave/releases/tag/v0.5.1-rc.2
> >
> > Build guide and get started instructions can be found at:
> > -
> >
> https://github.com/apache/incubator-teaclave/blob/v0.5.1-rc.2/docs/my-first-function.md
> >
> > The short version of building Teaclave from the source tarball:
> >
> > ```
> > $ wget
> >
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/0.5.1-rc.2/apache-teaclave-0.5.1-rc.2-incubating.tar.gz
> > $ tar zxvf apache-teaclave-0.5.1-rc.2-incubating.tar.gz && cd \
> > apache-teaclave-0.5.1-rc.2-incubating
> > $ # Instructions to verify the source tar:
> > https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> >
> > $ docker run --rm -v $(pwd):/teaclave -w /teaclave \
> > -it teaclave/teaclave-build-ubuntu-2004-sgx-2.17.1:0.2.0 \
> > bash -c ". /root/.cargo/env && \
> > . /opt/sgxsdk/environment && \
> > mkdir -p build && cd build && \
> > cmake -DTEST_MODE=ON -DSGX_SIM_MODE=ON -DGIT_SUBMODULE=OFF .. && \
> > make -j"
> > ```
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes are reached.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> >
> > Best,
> >
> > He Sun
> > Apache Teaclave (incubating)
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache Uniffle(Incubating) 0.7.0

[Felix Cheung]

+1 binding

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers


On Sun, Apr 2, 2023 at 9:24 PM Liu Xun  wrote:

> +1 (binding) from me,
>
> I have checked the following items:
> - Incubating in name
> - LICENSE and NOTICE are fine
> - DISCLAIMER-WIP exists
> - All links are valid
> - No unexpected binary files
> - All ASF files have ASF headers
> - Can compile from source
>   `mvn clean install`
>
> Best regards
> Xun Liu
>
> On 2023/03/30 02:59:51 Junfan Zhang wrote:
> > Hello IPMC, This is an official vote for the Apache
> > Uniffle(Incubating) 0.7.0 that we have been working toward.
> >
> > To learn more about Apache Uniffle(Incubating), please see:
> >
> > https://uniffle.apache.org
> >
> > The Apache Uniffle (incubating) community has voted and approved the
> release.
> >
> > Vote thread:
> >
> > https://lists.apache.org/thread/f9yko759l24y30l7n098tgk56sdt1d33
> >
> > Result thread:
> >
> > https://lists.apache.org/thread/yrnql56fnkl453jhvo0wsbvfn98y2zg8
> >
> > Release changes:
> > Compared to 0.6.1, the most important features are as follows
> > 1. Better support for spark AQE
> > 2. Optimization of a huge partition to improve stability of shuffle
> servers
> > 3. More bug fixes and usability improvements of K8S operator
> > 4. Add support of user quota management and more compression algorithms
> > 5. Add support for the spark data eviction mechanism of stage level
> > 6. Some improvement of stability and performance
> >
> > And the detailed changelog could be found in
> > https://github.com/apache/incubator-uniffle/compare/v0.6.1..v0.7.0-rc4
> >
> >
> > The release candidates:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.7.0-rc4/
> >
> > Git tag for the release:
> >
> > https://github.com/apache/incubator-uniffle/tree/v0.7.0-rc4
> >
> > Release Commit ID:
> >
> > 4ffee9eb1efa17e2faa66b72472dcd1613886cc1
> >
> > Keys to verify the Release Candidate:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS
> >
> > GPG user ID:
> >
> > Junfan Zhang
> >
> > The vote will be open for at least 72 hours or until necessary numbers
> > of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Checklist for reference:
> >
> > * Download links, checksums and PGP signatures are valid.
> > * Source code distributions have correct names matching the current
> release.
> > * Release files have the word incubating in their name.
> > * DISCLAIMER, LICENSE and NOTICE files are correct.
> > * All files have license headers if necessary.
> > * No unlicensed compiled archives bundled in source archive.
> > * The source tarball matches the git tag.
> >
> > More detail checklist please refer:
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > The following votes are carried over from the Uniffle dev mailing list:
> >
> > +1(binding)
> > roryqi,
> > Meng Duan,
> > Xianjin Ye
> >
> > Best Regards,
> > Junfan Zhang
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.15.0-rc4

[Felix Cheung]

As I understand you can release under the WIP disclaimer


On Mon, Jan 30, 2023 at 12:31 AM Zikuan An  wrote:

> Thanks for your valuable suggestion.
>
> I will revisit the whole process and re-open the vote after fixing the
> issues you mentioned.
>
>
> Best,
>
> Zikuan An
>
> Justin Mclean  于2023年1月19日周四 16:25写道：
>
> > Hi,
> >
> > Because it contains a restriction of use clause e.g. "This license does
> > not include the right to compile assets, vectors or images from
> ManyPixels
> > to replicate a similar or competing service, in any form or distribute
> the
> > assets in packs or otherwise. This extends to automated and non-automated
> > ways to link, embed.” It would be best to ask on legal discuss about
> this.
> >
> > For instance this license has been considered Category X. [1]
> >
> > Kind Regards,
> > Justin
> >
> > 1. https://www.pexels.com/license/
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.15.0-rc2

[Felix Cheung]

- incubating in name
- signature and hash fine
- No unexpected binary files
- All source files have ASF headers

- LICENSE, NOTICE and DISCLAIMER

1) is tap-pagerduty required to operate/run? it is in requirements.txt and
it has a GPL-v3 license
https://github.com/goodeggs/tap-pagerduty/blob/goodeggs/prod/LICENSE
https://www.apache.org/legal/resolved.html#category-x

2) BSD-2 or 3 licensed dependencies have a condition for notice - there are
a fair number of them
when dependencies are only for built they are still built into the binary
distribution, generally, projects might use a NOTICE-binary file that gets
included in binary distribution

3) these are "indirect" dependencies that have MPL, ISL, or non-standard
license, require notice etc
https://github.com/hashicorp/hcl/blob/main/LICENSE
https://github.com/davecgh/go-spew/blob/master/LICENSE
https://github.com/russross/blackfriday/blob/master/LICENSE.txt
https://github.com/gogo/protobuf/blob/master/LICENSE
https://github.com/emirpasic/gods/blob/master/LICENSE
https://github.com/go-git/gcfg/blob/v1/LICENSE
https://github.com/kevinburke/ssh_config/blob/master/LICENSE
https://github.com/pmezard/go-difflib/blob/master/LICENSE

My suggestion would be to change to WIP DISCLAIMER until these can be fully
resolved.
https://incubator.apache.org/policy/incubation.html#disclaimers



On Thu, Jan 12, 2023 at 8:24 PM david zollo  wrote:

> +1 (binding)
> I checked the following list,
> - incubating in name - signature and checksum are OK - DISCLAIMER exists,
> all go files has license headers
> - No unexpected binary files
>
>
>
> Best Regards
>
> ---
> Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> David
> Linkedin: https://www.linkedin.com/in/davidzollo
> Twitter: @WorkflowEasy 
> ---
>
>
> On Fri, Jan 13, 2023 at 10:51 AM Zikuan An  wrote:
>
> > Hello everyone,
> >
> > This is a call for vote to release Apache DevLake (Incubating)
> v0.15.0-rc2
> >
> > The Apache DevLake community has voted on and approved a proposal to
> > release
> >
> > Apache DevLake (Incubating) version v0.15.0-rc2
> >
> >
> >
> > We now kindly request the Incubator PMC members review and vote on this
> >
> > incubator release.
> >
> >
> > Linkis community vote thread:
> >
> > *https://lists.apache.org/thread/sd9qfp7vl7pn12xg4hwdfcn0fhboytqm
> > *
> >
> >
> >
> > Vote result thread:
> >
> > https://lists.apache.org/thread/35h6yzj3vl9zxo21wl6dlzj29o23j0nl
> >
> > The release candidates:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.15.0-incubating-rc2
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-devlake/releases/tag/v0.15.0-rc2
> >
> > Keys to verify the Release Candidate:
> > https://downloads.apache.org/incubator/devlake/KEYS
> >
> > How to build:
> > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes are reached.
> >
> >
> > Please vote accordingly:
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove with the reason
> >
>

Re: [VOTE] Release Apache Sedona 1.3.1-incubating-rc1

[Felix Cheung]

+1 binding

On Sat, Dec 17, 2022 at 1:00 AM Jia Yu  wrote:

> Hi all,
>
> This is a call for vote on Apache Sedona 1.3.1-incubating-rc1. Due to two
> critical bugs [1] and [2] , the users who use 1.3.0 have trouble running
> Sedona on Java 8 or Scala 2.12. We have to make this new release in a short
> period of time.
>
> Thanks,
> Jia
>
> Sedona Community vote thread (Permalink from
> https://lists.apache.org/list.html):
> https://lists.apache.org/thread/wj0bsgyy48f9dw8n896tc0rt22dy7ww7
>
> Sedona community vote result thread (Permalink from
> https://lists.apache.org/list.html):
> https://lists.apache.org/thread/4l8yl3bd7yqbxzgmzc2odnxgsgs33vjc
>
> Release notes:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.3.1-incubating-rc1/docs/setup/release-notes.md
>
> Build instructions:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.3.1-incubating-rc1/docs/setup/compile.md
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.3.1-incubating-rc1
>
> GPG public key to verify the Release:
> https://downloads.apache.org/incubator/sedona/KEYS
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.3.1-incubating-rc1/
>
> The vote will be open for at least 72 hours or until at least 3 "+1" PMC
> votes are cast
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> [ ] LICENSE is there
>
> [ ] No unexpected binary files
>
> For a detailed checklist  please refer to:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> [1] https://issues.apache.org/jira/browse/SEDONA-210
> [2] https://issues.apache.org/jira/browse/SEDONA-211
>

Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.1-rc3

[Felix Cheung]

What is the plan? Seem strange to require a patched Apache project to work.


On Wed, Dec 7, 2022 at 6:22 PM Kaijie Chen  wrote:

> > What are the reason for these? btw, if this is from the Apache Spark
> > project you might need to attribute it in LICENSE.
> >
> >
> apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.1.2_dynamic_allocation_support.patch
> >
> apache-uniffle-0.6.1-incubating-src/spark-patches/spark-2.4.6_dynamic_allocation_support.patch
> >
> apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.2.1_dynamic_allocation_support.patch
>
> Thanks Felix for checking. These patches are not from Apache Spark.
> Instead, it is for our users to patch Apache Spark to enable more
> features of Uniffle.
>
> Kaijie
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.1-rc3

[Felix Cheung]

+1 (binding)

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers

What are the reason for these? btw, if this is from the Apache Spark
project you might need to attribute it in LICENSE.

apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.1.2_dynamic_allocation_support.patch
apache-uniffle-0.6.1-incubating-src/spark-patches/spark-2.4.6_dynamic_allocation_support.patch
apache-uniffle-0.6.1-incubating-src/spark-patches/spark-3.2.1_dynamic_allocation_support.patch


On Wed, Dec 7, 2022 at 7:47 AM Xianjin YE  wrote:

> +1 from my side.
> - Download links are valid
> - Building and unit tests are ok.
>
> > On Dec 7, 2022, at 18:53, Charles Zhang  wrote:
> >
> > +1(non-binding)  from me, and I checked the following items:
> >
> > - [X] Download links are valid.
> > - [X] Checksums and PGP signatures are valid.
> > - [X] All files have license headers if necessary.
> > - [X] No compiled archives bundled in the source archive.
> > - [X] Building is OK.
> >
> > Best wishes,
> > Charles Zhang
> > from Apache InLong
> >
> >
> > Kent Yao  于2022年12月7日周三 17:26写道：
> >
> >> +1(non-binding)
> >>
> >> - Download links are valid
> >> - Signatures are OK
> >> - Checksums are OK
> >> -  LICENSE, NOTICE, and DISCLAIMER  are OK
> >> - Successfully passes UT
> >>
> >> Kent Yao
> >>
> >> On 2022/12/07 02:19:36 He Qi wrote:
> >>> From my side
> >>> +1
> >>>
> >>> I have checked
> >>> * Download links, checksums and PGP signatures are valid
> >>> * LICENSE, NOTICE and DISCLAIMER-WIP files are correct
> >>> * No unlicensed compiled archives bundled in source archive.
> >>> * UT passed. I use the command `mvn package -Pspark3
> >>>
> >>> On 2022/12/06 05:56:13 Kaijie Chen wrote:
>  Hello Incubator Community,
> 
>  This is a call for a vote to release Apache Uniffle (Incubating)
>  version 0.6.1-rc3.
> 
>  The Apache Uniffle community has voted on and approved a proposal to
>  release Apache Uniffle (Incubating) version 0.6.1-rc3.
> 
>  We now kindly request the Incubator PMC members review and vote on
> this
>  incubator release.
> 
>  Uniffle community vote thread:
>  https://lists.apache.org/thread/sorpwljxl2nssowhloswo662jng5qwr7
> 
>  Vote result thread:
>  https://lists.apache.org/thread/4k9v3n6fvtmd3y37jhof2t6kb90qjg36
> 
>  The release candidate:
>  https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.6.1-rc3/
> 
>  Git tag for the release:
>  https://github.com/apache/incubator-uniffle/tree/v0.6.1-rc3
> 
>  Release notes:
>  https://uniffle.apache.org/download/release-notes-0.6.1/
> 
>  The artifacts signed with PGP key
>  3B8167D035D33A4C2D725FAA39A39E985C5EFBA4
>  corresponding to c...@apache.org, that can be found in keys file:
>  https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS
> 
>  The vote will be open for at least 72 hours or until the necessary
>  number of votes are reached.
> 
>  Please vote accordingly:
> 
>  [ ] +1 approve
>  [ ] +0 no opinion
>  [ ] -1 disapprove with the reason
> 
>  Thanks,
>  Kaijie Chen
>  On behalf of Apache Uniffle (Incubating) community
> 
>  -
>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>  For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache Sedona as an Apache Top Level Project

[Felix Cheung]

Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Sedona Project be and hereby is responsible
> for the creation and maintenance of software related to a big geospatial
> data processing engine. It provides an easy to use APIs for spatial data
> scientists to manage, wrangle, and process geospatial data; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache Sedona" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Sedona
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Sedona
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Sedona Project:
>
>  * Adam Binford 
>  * Felix Cheung 
>  * George Percivall 
>  * Jean-Baptiste Onofré 
>  * Jia Yu   
>  * Jinxuan Wu   
>  * Kanchan Chowdhury
>  * Kengo Seki   
>  * Mo Sarwat
>  * Netanel Malka
>  * Paweł Kociński   
>  * Sachio Wakai 
>  * Sunil G  
>  * Von Gosling  
>  * Yitao Li 
>  * Zongsi Zhang 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jia Yu be appointed to the
> office of Vice President, Apache Sedona, to serve in accordance with and
> subject to the direction of the Board of Directors and the Bylaws of the
> Foundation until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be it further
>
> RESOLVED, that the Apache Sedona Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Sedona
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Sedona podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> [1] Sedona incubation status:
> https://incubator.apache.org/projects/sedona.html
>
> [2] Sedona community graduation discussion:
> https://lists.apache.org/thread/fspvqmp0lwqrq0j8kb63jxwh1c00o0wf
>
> [3] Sedona community graduation vote:
> https://lists.apache.org/thread/xwvx1txhstsbxojoqfthm609yt6ncyjp
>
> [4] Sedona community graduation vote result:
> https://lists.apache.org/thread/6ggb9pkhcb5h8k4bsgx754kt2jlnns1z
>
> [5] Sedona community PMC confirmation and chair nomination vote:
> https://lists.apache.org/thread/qp8y7drhqq7dy91dc90lrw3cxd95nk66
>
> [6] Sedona community PMC confirmation and chair nomination vote result:
> https://lists.apache.org/thread/blwgor0yp73ozgkbgzlk1959o599sxff
>
> [7] Sedona community self assessment in terms of Apache Project Maturity
> Model: https://issues.apache.org/jira/browse/SEDONA-81
>
> [8] Sedona project website check:
> https://whimsy.apache.org/pods/project/sedona
>
> [9] Apache Software Foundation privacy policy:
> https://privacy.apache.org/policies/privacy-policy-public.html
>
> [10] Establish Whether "Apache Sedona" is a suitable name:
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-200
>
> [11] Sedona license:
> https://github.com/apache/incubator-sedona/blob/master/LICENSE
>
> [12] Sedona Graduation discussion in the incubator mailing list Sept 2022:
> https://lists.apache.org/thread/4s7cmt9b2ld0z62ghr8ykrr1conwlvk1
>
> [13] Sedona Graduation discussion in the incubator mailing list Dec 2022:
> https://lists.apache.org/thread/lj4n6nmqz5qowv6oqlzz06d6h87l7592
>

Re: [VOTE] Release Apache Sedona 1.3.0-incubating-rc2

[Felix Cheung]

+1 (binding)

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers
- compile from source


On Mon, Nov 21, 2022 at 8:36 PM Jia Yu  wrote:

> Hi all,
>
> This is a call for vote on Apache Sedona 1.3.0-incubating-rc2. Please refer
> to the changes listed at the bottom of this email.
>
> Sedona Community vote thread (Permalink from
> https://lists.apache.org/list.html):
> https://lists.apache.org/thread/f7vnm6pchltjco686dsqfc8ntrhbwto2
>
> Sedona community vote result thread (Permalink from
> https://lists.apache.org/list.html):
> https://lists.apache.org/thread/4098nf7rl8byl8pkcyyj8z62qt3l9rkh
>
> Release notes:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.3.0-incubating-rc2/docs/setup/release-notes.md
>
> Build instructions:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.3.0-incubating-rc2/docs/setup/compile.md
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.3.0-incubating-rc2
>
> GPG public key to verify the Release:
> https://downloads.apache.org/incubator/sedona/KEYS
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.3.0-incubating-rc2/
>
> The vote will be open for at least 72 hours or until at least 3 "+1" PMC
> votes are cast
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> For a detailed checklist  please refer to:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Thanks,
> Jia
>

Re: [VOTE] Release Apache Sedona 1.3.0-incubating-rc1

[Felix Cheung]

What’s the thought on R dbplyr dependency?

From: Jia Yu 
Sent: Saturday, November 12, 2022 12:40:27 PM
To: dev@sedona.apache.org 
Subject: Re: [VOTE] Release Apache Sedona 1.3.0-incubating-rc1

Dear all,

This release is supposed to be the last release before graduation. Please
make sure you vote +1 with a checklist (see my vote below). The incubator
PMCs rejected our graduation proposal last time because we didn't provide
the checklist for each vote.

Again, checking this release is extremely easy if you use the MyBinder
notebook provided in Mo's email. All you need to do is click a few buttons
and wait a few minutes.

We really appreciate your help!

Thanks,
Jia

+1

I checked:
* Download links are valid
* Checksums and PGP signatures are valid
* DISCLAIMER and NOTICE are included
* Source code artifacts have correct names matching the current release
* The project can compile from the source code


On Sat, Nov 12, 2022 at 8:48 AM Mo Sarwat  wrote:

> Hi all,
>
> This is a call for vote on Apache Sedona 1.3.0-incubating-rc1. Please refer
> to the changes listed at the bottom of this email.
>
> Release notes:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.3.0-incubating-rc1/docs/setup/release-notes.md
>
> Build instructions:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.3.0-incubating-rc1/docs/setup/compile.md
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.3.0-incubating-rc1
>
> GPG public key to verify the Release:
> https://downloads.apache.org/incubator/sedona/KEYS
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.3.0-incubating-rc1/
>
> The vote will be open for at least 72 hours or until at least 3 "+1" PMC
> votes are cast
>
> Instruction for checking items on the checklist:
> https://sedona.apache.org/community/vote/
>
> We recommend you use this Jupyter notebook on MyBinder to perform this
> task:
>
> https://mybinder.org/v2/gh/jiayuasu/sedona-tools/HEAD?labpath=binder%2Fverify-release.ipynb
>
> **Please vote accordingly and you must provide your checklist for your
> vote**.
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> For a detailed checklist  please refer to:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Regards,
> Mo Sarwat
>

Fwd: Podling Sedona Report Reminder - November 2022

[Felix Cheung]

-- Forwarded message -
From: 
Date: Sat, Oct 22, 2022 at 9:08 PM
Subject: Podling Sedona Report Reminder - November 2022
To: 


Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 16 November 2022.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, November 02).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/November2022

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: [VOTE] Accept Celeborn into the Apache Incubator

[Felix Cheung]

+1 (binding)



On Wed, Oct 12, 2022 at 7:26 AM Ashish  wrote:

> +1 (non-binding)
>
> On Tue, Oct 11, 2022 at 8:49 PM Yu Li  wrote:
>
> > Hi all,
> >
> > Following up on the [DISCUSS] thread on Celeborn [1] [2], I would like to
> > call a VOTE to accept Celeborn into the Apache Incubator, please check
> out
> > the Celeborn Proposal from the incubator wiki [3].
> >
> > Please cast your vote:
> >
> > [ ] +1, bring Celeborn into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring Celeborn into the Incubator, because...
> >
> > The vote will open at least for 72 hours, and only votes from the
> Incubator
> > PMC are binding, but votes from everyone are welcome.
> >
> > Best Regards,
> > Yu
> >
> > [1] https://lists.apache.org/thread/rlkzg8m5923vngyon0bwcv97x3m68x4c
> > [2] https://lists.apache.org/thread/hjy3gpvocjtls5vp9h1llcvmwkgz3lcy
> > [3]
> https://cwiki.apache.org/confluence/display/INCUBATOR/CelebornProposal
> >
>
>
> --
> thanks
> ashish
>

Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.0 rc1

[Felix Cheung]

Also, strongly recommend the first release is with the WIP DISCLAIMER 
https://incubator.apache.org/policy/incubation.html#disclaimers

From: Kaijie Chen 
Sent: Sunday, October 9, 2022 3:58:21 AM
To: dev@uniffle.apache.org 
Subject: Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.0 rc1

Looks like the non-ascii charactor in some files is caused by misuse of Chinese 
colon.

I have submitted a PR to fix this. Please cherry-pick if you feel it's 
necessary.
https://github.com/apache/incubator-uniffle/pull/255

Kaijie

On 2022/10/09 10:38:07 Kaijie Chen wrote:
> +1 (non-binding)
>
>  [x] Download links are valid.
>  [x] Checksums and PGP signatures are valid.
>  [x] Source code distributions have correct names matching the current 
> release.
>  [x] LICENSE and NOTICE files are correct for each Uniffle repo.
>  [x] All files have license headers if necessary.
>  [x] No unlicensed compiled archives bundled in source archive.
>
> ---
>
> $ find . -exec file {} \; | awk -F : '{print $2}' | sort | uniq -c
>  123  ASCII text
>   16  Bourne-Again shell script text executable, ASCII text
>1  C++ source text, ASCII text
>4  Java source text, ASCII text
>  332  Java source, ASCII text
>1  Java source, Unicode text, UTF-8 text
>1  PNG image data, 1645 x 802, 8-bit/color RGBA, non-interlaced
>1  PNG image data, 439 x 447, 8-bit/color RGBA, non-interlaced
>1  PNG image data, 997 x 499, 8-bit/color RGBA, non-interlaced
>1  Python script text executable, ASCII text
>   21  XML 1.0 document text, ASCII text
>1  c program text, ASCII text
>  299  directory
>1  empty
>2  exported SGML document text, ASCII text
>1  exported SGML document text, Unicode text, UTF-8 text
>1  makefile script text, ASCII text
>3  unified diff output text, ASCII text
>
> Best,
> Kaijie Chen
>
> On 2022/10/09 09:41:16 roryqi wrote:
> > Hello Uniffle community
> >
> >This is a call for vote to release Apache Uniffle (Incubating)
> > version 0.6.0-rc1.
> >
> >The release candidates:
> >https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.6.0-rc1/
> >
> >Git tag for the release:
> >https://github.com/apache/incubator-uniffle/commits/v0.6.0-rc1
> >
> >Keys to verify the Release Candidate:
> >https://downloads.apache.org/incubator/uniffle/KEYS
> >
> >GPG user ID:
> >roryqi
> >
> >The vote will be open for at least 72 hours or until necessary
> > number of votes are reached.
> >
> >Please vote accordingly:
> >
> >[ ] +1 approve
> >[ ] +0 no opinion
> >[ ] -1 disapprove with the reason
> >
> >Checklist for reference:
> >
> >[ ] Download links are valid.
> >[ ] Checksums and PGP signatures are valid.
> >[ ] Source code distributions have correct names matching the
> > current release.
> >[ ] LICENSE and NOTICE files are correct for each Uniffle repo.
> >[ ] All files have license headers if necessary.
> >[ ] No unlicensed compiled archives bundled in source archive.
> >
> >More detail checklist  please refer:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Thanks
> >   roryqi
> >
>

Re: [RESULT][VOTE] Release Apache DevLake (Incubating) v0.14.0-rc1

[Felix Cheung]

Correction: my vote is binding


On Fri, Oct 7, 2022 at 8:00 PM Liang Zhang 
wrote:

> Hi all,
>
> The vote to Apache DevLake(Incubating) v0.14.0-rc1 is now closed. Thanks
> for reviewing and voting.
>
> The release voting has passed with 4 binding votes and 2 non-binding
> votes, no +0 or -1 votes.
>
> Binding:
>
> - Jean-Baptiste Onofré
> - Madhawa Gunasekara
> - David Zollo
> - Willem Jiang
>
>
> Non-binding:
> - Felix Cheung
> - Li Gang
>
> The voting thread is:
> https://lists.apache.org/thread/lgfrsv0ymfk1c19ngnkkn46cspkf76lg
>
> Thank you to all those who have provided us with help, advice and
> guidance. We will continue to finish the rest of the work.
>
>
> Thanks
> Liang Zhang
>
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.14.0-rc1

[Felix Cheung]

+1

- LICENSE and NOTICE
No binary distribution on
https://dist.apache.org/repos/dist/dev/incubator/devlake/0.14.0-incubating-rc1/
(note: some binary dependency has NOTICE).

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- No unexpected binary files
- All source files have ASF headers


On Tue, Oct 4, 2022 at 5:55 AM Liang Zhang 
wrote:

> Hello all,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.14.0-rc1
>
> The Apache DevLake community has voted on and approved a proposal to
> release
> Apache DevLake (Incubating) version v0.14.0-rc1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Linkis community vote thread:
> https://lists.apache.org/thread/s6jj2tl5mlyb8jpdd88jmo5woydzhp54
>
> Vote result thread:
> https://lists.apache.org/thread/mb5sxdopprqksf1ppfggkvkwxs6110zk
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.14.0-incubating-rc1/
>
> Git tag for the release:
> https://github.com/apache/incubator-devlake/tree/v0.14.0-rc1
>
> Keys to verify the Release Candidate:
> https://downloads.apache.org/incubator/devlake/KEYS
>
> How to build:
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Why are hash functions seeded with 42?

[Felix Cheung]

+1 to doc, seed argument would be great if possible

From: Sean Owen 
Sent: Monday, September 26, 2022 5:26:26 PM
To: Nicholas Gustafson 
Cc: dev 
Subject: Re: Why are hash functions seeded with 42?

Oh yeah I get why we love to pick 42 for random things. I'm guessing it was a 
bit of an oversight here as the 'seed' is directly initial state and 0 makes 
much more sense.

On Mon, Sep 26, 2022, 7:24 PM Nicholas Gustafson 
mailto:njgustaf...@gmail.com>> wrote:
I don’t know the reason, however would offer a hunch that perhaps it’s a nod to 
Douglas Adams (author of The Hitchhiker’s Guide to the Galaxy).

https://news.mit.edu/2019/answer-life-universe-and-everything-sum-three-cubes-mathematics-0910

On Sep 26, 2022, at 16:59, Sean Owen 
mailto:sro...@gmail.com>> wrote:


OK, it came to my attention today that hash functions in spark, like xxhash64, 
actually always seed with 42: 
https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/hash.scala#L655

This is an issue if you want the hash of some value in Spark to match the hash 
you compute with xxhash64 somewhere else, and, AFAICT most any other impl will 
start with seed=0.

I'm guessing there wasn't a great reason for this, just seemed like 42 was a 
nice default seed. And we can't change it now without maybe subtly changing 
program behaviors. And, I am guessing it's messy to let the function now take a 
seed argument, esp. in SQL.

So I'm left with, I guess we should doc that? I can do it if so.
And just a cautionary tale I guess, for hash function users.

Re: DBI dependency in Sedona R

[Felix Cheung]

>From what I can see, it’s only directly used in two places

- tests
- sql variant
https://github.com/apache/incubator-sedona/blob/65080422b6256a0f12cc74347ac2ed531d26a4f6/R/R/dependencies.R#L135

Don’t know enough about dbplyr to tell if that functionality can be turned
off (say if sql is not used)


On Wed, Sep 14, 2022 at 12:05 AM Jia Yu  wrote:

> This is a question raised by the incubator community regarding graduating
> Sedona to a TLP.
>
> On Tue, Sep 13, 2022 at 11:57 PM Jia Yu  wrote:
>
> > Hi Yitao,
> >
> > The DBI dependency in Sedona R (
> > https://github.com/apache/incubator-sedona/blob/master/R/DESCRIPTION) is
> > under LGPL 2.1 license, which may have compatibility issues with ASF. Is
> it
> > mandatory? If not, can we remove it?
> >
> > Thanks,
> > Jia
> >
>

Website

[Felix Cheung]

Please take a look at the bottom of this report
https://incubator.apache.org/clutch/sedona.html

And esp at
https://whimsy.apache.org/pods/project/sedona

Re: [VOTE] Release Apache DevLake (Incubating) v0.13.0-rc1

[Felix Cheung]

+1 (binding)

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files

these file should have ASF header:
./plugins/azure/impl/impl.go
./plugins/azure/models/build.go
./plugins/azure/models/migrationscripts/archived/build.go
./plugins/azure/models/migrationscripts/archived/build_definition.go
./plugins/azure/models/build_definition.go
./plugins/jira/models/migrationscripts/20220407_add_source_table.go
./plugins/jenkins/models/task.go
./plugins/jenkins/models/job_dag.go
./plugins/jenkins/models/pipeline.go
./plugins/jenkins/models/build_repo.go
./models/migrationscripts/20220711_add_subtasks_table.go
./models/domainlayer/devops/cicd_pipeline.go
./models/domainlayer/devops/cicd_pipeline_repo.go
./models/domainlayer/devops/cicd_task.go


On Wed, Sep 7, 2022 at 8:37 AM Willem Jiang  wrote:

> +1 (binding)
>
> I checked
> - The checksums and signatures are validated.
> - The LICENSE and NOTICE files look good to me.
> - There is DISCLAIMER-WIP
> - No binary files in the source release
> - All source files have ASF headers (**.go and **.js)
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
> On Thu, Sep 1, 2022 at 9:32 AM Liang Zhang
>  wrote:
> >
> > Hello all,
> >
> > This is a call for vote to release Apache DevLake (Incubating)
> v0.13.0-rc1
> >
> > The Apache DevLake community has voted on and approved a proposal to
> release
> > Apache DevLake (Incubating) version v0.13.0-rc1
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Linkis community vote thread:
> > https://lists.apache.org/thread/1ym0yng90fb89cs1br0jsd0tp2ycv81c
> >
> > Vote result thread:
> > https://lists.apache.org/thread/8qd5d3zt5qw88pr9l79d2zl5ndjpjygk
> >
> > The release candidates:
> >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.13.0-incubating-rc1/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-devlake/tree/v0.13.0-rc1
> >
> > Keys to verify the Release Candidate:
> > https://downloads.apache.org/incubator/devlake/KEYS
> >
> >
> > The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > Apache DevLake(Incubating) community
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Release Apache DevLake (Incubating) v0.13.0-rc1

[Felix Cheung]

Remember to put [VOTE] at the beginning of the email subject.


On Wed, Aug 31, 2022 at 5:47 AM Liang Zhang 
wrote:

> Hello all,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.13.0-rc1
>
> The Apache DevLake community has voted on and approved a proposal to
> release
> Apache DevLake (Incubating) version v0.13.0-rc1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Linkis community vote thread:
> https://lists.apache.org/thread/1ym0yng90fb89cs1br0jsd0tp2ycv81c
>
> Vote result thread:
> https://lists.apache.org/thread/8qd5d3zt5qw88pr9l79d2zl5ndjpjygk
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.13.0-incubating-rc1/
>
> Git tag for the release:
> https://github.com/apache/incubator-devlake/tree/v0.13.0-rc1
>
> Keys to verify the Release Candidate:
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> Apache DevLake(Incubating) community
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire Hivemall from Incubator

[Felix Cheung]

+1 (binding)


On Sun, Aug 28, 2022 at 7:06 PM Dave Fisher  wrote:

> +1 (binding)
>
> Sent from my iPhone
>
> > On Aug 27, 2022, at 11:57 PM, Calvin Kirs  wrote:
> >
> > Hi IPMC,
> >
> > Hivemall has been incubating since 2016-09-13.
> >
> > From last year, activity has been low and the chances of attracting new
> > committers and building a vibrant community seem very slim at this point.
> >
> > The dev community vote was started by the PPMC for over a month and
> > can be found here[1],[2]
> >
> > I therefore propose to retire Hivemall from the Incubator.
> >
> > I want to start this official vote.
> >
> > Voting will start now and will remain open for at least 72 hours.
> >
> > Notice: Because the dev vote didn't get enough +1's, this vote is not
> > the same as usual, it's not a laze vote.
> >
> > [ ] +1 Retire the project
> > [ ] +0 No opinion.
> > [ ] -1 Do not retire the project because...
> >
> > [1]https://lists.apache.org/thread/3s7bjgqm7864qbwnf1ny3lszklm65sgn
> > [2]https://lists.apache.org/thread/cv267tds166z7vtbzjt46nrz26xhzgvb
> >
> > --
> > Best wishes！
> > CalvinKirs
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Sedona 1.2.1-incubating-rc1

[Felix Cheung]

Source code and binaries:
https://dist.apache.org/repos/dist/dev/incubator/sedona/1.2.1-incubating-rc1/

On Sat, Aug 13, 2022 at 9:22 PM Jean-Baptiste Onofré 
wrote:

> Hi,
>
> Can you please include the link to dist source package ? That's the
> most important thing to check.
>
> Thanks,
> Regards
> JB
>
> On Wed, Aug 10, 2022 at 4:55 AM Kanchan Chowdhury 
> wrote:
> >
> > Hi all,
> >
> > This is a call for vote on Apache Sedona 1.2.1-incubating-rc1. Please
> refer
> > to the changes listed at the bottom of this email.
> >
> > Sedona Community vote thread:
> > https://lists.apache.org/thread/511gjndxmdxh4g2rzwyxppjc00orz3s3
> >
> > Sedona community vote result thread:
> > https://lists.apache.org/thread/jyb3yp2wpnhp8kx7t8dnls8xljwqflxr
> >
> > Release notes:
> >
> https://github.com/apache/incubator-sedona/blob/bcb1803c24dc9decfb113a31db8fc14433be025b/docs/setup/release-notes.md
> >
> > Build instructions:
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.1-incubating-rc1/docs/setup/compile.md
> >
> > GitHub tag:
> >
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.2.1-incubating-rc1
> >
> > GPG public key to verify the Release:
> > https://downloads.apache.org/incubator/sedona/KEYS
> >
> > Source code and binaries:
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.2.1-incubating-rc1/
> >
> > The vote will be open for at least 72 hours or until at least 3 "+1" PMC
> > votes are cast
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove with the reason
> >
> > Checklist for reference (because of DISCLAIMER-WIP, other checklist items
> > are not blockers):
> >
> > [ ] Download links are valid.
> >
> > [ ] Checksums and PGP signatures are valid.
> >
> > [ ] DISCLAIMER is included.
> >
> > [ ] Source code artifacts have correct names matching the current
> release.
> >
> > For a detailed checklist  please refer to:
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Sedona 1.2.1-incubating-rc1

[Felix Cheung]

+1

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
Note: is the community ready for the full DISCLAIMER (not -DISCLAIMER-WIP)
in the next release?

- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers
Note: /binder/*.ipynb should probably have the ASF headers in md block?



On Tue, Aug 9, 2022 at 7:56 PM Kanchan Chowdhury 
wrote:

> Hi all,
>
> This is a call for vote on Apache Sedona 1.2.1-incubating-rc1. Please refer
> to the changes listed at the bottom of this email.
>
> Sedona Community vote thread:
> https://lists.apache.org/thread/511gjndxmdxh4g2rzwyxppjc00orz3s3
>
> Sedona community vote result thread:
> https://lists.apache.org/thread/jyb3yp2wpnhp8kx7t8dnls8xljwqflxr
>
> Release notes:
>
> https://github.com/apache/incubator-sedona/blob/bcb1803c24dc9decfb113a31db8fc14433be025b/docs/setup/release-notes.md
>
> Build instructions:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.1-incubating-rc1/docs/setup/compile.md
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.2.1-incubating-rc1
>
> GPG public key to verify the Release:
> https://downloads.apache.org/incubator/sedona/KEYS
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.2.1-incubating-rc1/
>
> The vote will be open for at least 72 hours or until at least 3 "+1" PMC
> votes are cast
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference (because of DISCLAIMER-WIP, other checklist items
> are not blockers):
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> For a detailed checklist  please refer to:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.12.0-rc2

[Felix Cheung]

I believe I did but will double check.


On Mon, Aug 8, 2022 at 12:43 AM Klesh Wong  wrote:

> Hi, Felix
>
>   Thanks for your support.
>   Did you import the "KEYS" before the verification?
>
> > > > > > Keys to verify the Release Candidate:
> > > > > > https://downloads.apache.org/incubator/devlake/KEYS
>
>   Thanks
>
> Klesh Wong
>
>
> On 22/08/07 11:26PM, Felix Cheung wrote:
> > Is the signing key in the KEYS file? It seems I’m getting an error.
> >
> > - incubating in name
> > - signature and hash fine
> > gpg: Can't check signature: No public key
> > - DISCLAIMER is fine
> > - LICENSE is fine
> > NOTICE should say Apache DevLake (incubating)
> > - No unexpected binary files
> > - All source files have ASF headers
> >
> >
> > On Sun, Aug 7, 2022 at 8:23 PM david zollo 
> wrote:
> >
> > > +1 binding
> > >
> > > I checked,
> > > -  DISCLAIMER-WIP exists.
> > > - The checksums and signatures.
> > > - LICENSE and NOTICE files.
> > >
> > >
> > > Best Regards
> > >
> > > ---
> > > Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> > > David Zollo
> > > Linkedin: https://www.linkedin.com/in/davidzollo
> > > Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy>
> > > ---
> > >
> > >
> > > On Fri, Aug 5, 2022 at 2:39 PM zhangli...@apache.org <
> > > zhangli...@apache.org>
> > > wrote:
> > >
> > > > +1 binding
> > > >
> > > > I checked:
> > > >
> > > > - The checksums and signatures.
> > > > - LICENSE and NOTICE files.
> > > > - All source files have ASF headers.
> > > > - No binary files in the source release.
> > > >
> > > > --
> > > >
> > > > Sincerely,
> > > > Liang Zhang (John)
> > > > Apache ShardingSphere
> > > >
> > > >
> > > > Willem Jiang  于2022年8月4日周四 10:17写道：
> > > >
> > > > > +1 binding
> > > > > I checked
> > > > > - The checksums and signatures are vailidate.
> > > > > - LICENSE and NOTICE file look good to me.
> > > > > - There is DISCLAIMER-WIP
> > > > > - No binary files in the source release
> > > > > - All source files have ASF headers (**.go and **.js)
> > > > >
> > > > > Willem Jiang
> > > > >
> > > > > Twitter: willemjiang
> > > > > Weibo: 姜宁willem
> > > > >
> > > > > On Mon, Aug 1, 2022 at 10:16 PM Liang Zhang
> > > > >  wrote:
> > > > > >
> > > > > > Hello all,
> > > > > >
> > > > > > This is a call for vote to release Apache DevLake (Incubating)
> > > > > v0.12.0-rc2
> > > > > >
> > > > > > The Apache DevLake community has voted on and approved a
> proposal to
> > > > > release
> > > > > > Apache DevLake (Incubating) version v0.12.0-rc2
> > > > > >
> > > > > > We now kindly request the Incubator PMC members review and vote
> on
> > > this
> > > > > > incubator release.
> > > > > >
> > > > > > Linkis community vote thread:
> > > > > > https://lists.apache.org/thread/yxy3kokhhhxlkxcr4op0pwslts7d8tcy
> > > > > >
> > > > > > Vote result thread:
> > > > > > https://lists.apache.org/thread/qr3fj42tmryztt919jsy5q8hbpmcztky
> > > > > >
> > > > > > The release candidates:
> > > > > >
> > > > >
> > > >
> > >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.12.0-incubating-rc2/
> > > > > >
> > > > > > Git tag for the release:
> > > > > > https://github.com/apache/incubator-devlake/tree/v0.12.0-rc2
> > > > > >
> > > > > > Keys to verify the Release Candidate:
> > > > > > https://downloads.apache.org/incubator/devlake/KEYS
> > > > > >
> > > > > > some issues raised from the last voting[1].
> > > > > > - Several files don't have have ASF headers -- Fixed in this
> release
> > > > > >
> > > > 

Re: [VOTE] Release Apache DevLake (Incubating) v0.12.0-rc2

[Felix Cheung]

Is the signing key in the KEYS file? It seems I’m getting an error.

- incubating in name
- signature and hash fine
gpg: Can't check signature: No public key
- DISCLAIMER is fine
- LICENSE is fine
NOTICE should say Apache DevLake (incubating)
- No unexpected binary files
- All source files have ASF headers


On Sun, Aug 7, 2022 at 8:23 PM david zollo  wrote:

> +1 binding
>
> I checked,
> -  DISCLAIMER-WIP exists.
> - The checksums and signatures.
> - LICENSE and NOTICE files.
>
>
> Best Regards
>
> ---
> Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> David Zollo
> Linkedin: https://www.linkedin.com/in/davidzollo
> Twitter: @WorkflowEasy 
> ---
>
>
> On Fri, Aug 5, 2022 at 2:39 PM zhangli...@apache.org <
> zhangli...@apache.org>
> wrote:
>
> > +1 binding
> >
> > I checked:
> >
> > - The checksums and signatures.
> > - LICENSE and NOTICE files.
> > - All source files have ASF headers.
> > - No binary files in the source release.
> >
> > --
> >
> > Sincerely,
> > Liang Zhang (John)
> > Apache ShardingSphere
> >
> >
> > Willem Jiang  于2022年8月4日周四 10:17写道：
> >
> > > +1 binding
> > > I checked
> > > - The checksums and signatures are vailidate.
> > > - LICENSE and NOTICE file look good to me.
> > > - There is DISCLAIMER-WIP
> > > - No binary files in the source release
> > > - All source files have ASF headers (**.go and **.js)
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Mon, Aug 1, 2022 at 10:16 PM Liang Zhang
> > >  wrote:
> > > >
> > > > Hello all,
> > > >
> > > > This is a call for vote to release Apache DevLake (Incubating)
> > > v0.12.0-rc2
> > > >
> > > > The Apache DevLake community has voted on and approved a proposal to
> > > release
> > > > Apache DevLake (Incubating) version v0.12.0-rc2
> > > >
> > > > We now kindly request the Incubator PMC members review and vote on
> this
> > > > incubator release.
> > > >
> > > > Linkis community vote thread:
> > > > https://lists.apache.org/thread/yxy3kokhhhxlkxcr4op0pwslts7d8tcy
> > > >
> > > > Vote result thread:
> > > > https://lists.apache.org/thread/qr3fj42tmryztt919jsy5q8hbpmcztky
> > > >
> > > > The release candidates:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.12.0-incubating-rc2/
> > > >
> > > > Git tag for the release:
> > > > https://github.com/apache/incubator-devlake/tree/v0.12.0-rc2
> > > >
> > > > Keys to verify the Release Candidate:
> > > > https://downloads.apache.org/incubator/devlake/KEYS
> > > >
> > > > some issues raised from the last voting[1].
> > > > - Several files don't have have ASF headers -- Fixed in this release
> > > >
> > > > - NOTICE is there but need to be extended (it's almost empty) -- No
> new
> > > entries for now, we will append them at the first time when needed
> > > >
> > > > - Use CI to help check license header -- We followed this advice and
> > > have set up a GitHub Action workflow to do the job
> > > >
> > > > - Use https://downloads.apache.org/incubator/devlake/KEYS as the
> link
> > > of KEYS -- As shown above, we are using the correct link
> > > >
> > > > The vote will be open for at least 72 hours or until necessary number
> > of
> > > votes are reached.
> > > >
> > > > Please vote accordingly:
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > [1]https://lists.apache.org/thread/hbwf24xmfl5xkn3mocvn55hpzodcf010
> > > > Thanks,
> > > > Apache DevLake(Incubating) community
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc1

[Felix Cheung]

I’d recommend it for the very first release.

It might work without, or it might take quite a bit of effort.

On Fri, Jun 24, 2022 at 12:27 PM Hezheng Yin 
wrote:

> Hi Felix, thanks for the suggestion. If we were able to resolve the
> licensing issues Justin raised, would you still recommend us switching to
> WIP DISCLAIMER?
>
> Hi Justin, thanks for the clarification. We have gone through all the
> image files in the release:
>
> 1. All flaticon icons [1] are replaced with blueprintjs icons [2] that have
> Apache 2.0 license.
> 2. For images created by ourselves, do we need to formally license them? If
> so, is there a guideline that we can follow?
> 3. In DevLake UI, we also make use of GitHub/GitLab/Jenkins/Jira logos on
> the integration page. We found their logo usage guidelines [3][4][5][6]
> online but couldn't find a formal license for these logos. For example, the
> GitHub Logos and Usage page [3] states it's ok to "Use the Octocat or
> GitHub logo to advertise that your product has built-in GitHub
> integration". Is it compliant with Apache policy to include such logos in
> the release?
>
> We'll restart the voting process on the DevLake mailing list once we
> address the issues above.
>
> [1] https://www.flaticon.com/pricing
> [2] https://blueprintjs.com/
> [3] https://github.com/logos
> [4]
>
> https://about.gitlab.com/handbook/marketing/corporate-marketing/brand-activation/trademark-guidelines/
> [5] https://www.jenkins.io/press/
> [6] https://www.atlassian.com/company/news/press-kit
>
> Best,
> Hezheng
>
>
>
> On Wed, Jun 22, 2022 at 8:52 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > And to be sure, we should go through the community vote step again
> before
> > > making another voting thread in general@incubator.apache.org. Is this
> > > correct? Thanks in advance!
> >
> > Yes your PPMC will ned to vote on the new release candidate before
> > bringing it for a vote by the incubator PMC.
> >
> > Kind Regards,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc1

[Felix Cheung]

I would strongly suggest having the WIP DISCLAIMER also


On Wed, Jun 22, 2022 at 8:08 AM Hezheng Yin 
wrote:

> Hi,
>
> Thank you all for your guidance. This is extremely helpful as DevLake works
> towards its first ASF release. We'll address all the feedback and re-start
> the voting process.
>
> And to be sure, we should go through the community vote step again before
> making another voting thread in general@incubator.apache.org. Is this
> correct? Thanks in advance!
>
> Best,
> Hezheng
>
> On Wed, Jun 22, 2022 at 6:42 AM Liang Zhang 
> wrote:
>
> > Thank you very much for your kindly reminder and helpful suggestion,
> > especially  Willem Jiang, Calvin Kirs, and Justin Mclean. We will take
> the
> > issues you mentioned seriously and relaunch a new round of voting after
> the
> > fix is ready.
> >
> > Best Wishes
> > Liang Zhang
> >
> > On 2022/06/22 06:57:15 Justin Mclean wrote:
> > > Hi,
> > >
> > > Sorry but t’s -1 (binding) from me. There are a number of icons and
> > other PNG files in the release and their license is not included in the
> > LICENSE file. I’ve not checked them all but some seem to come from [1],
> not
> > that attribution is required and that the license may not be compatible
> > with the Apache license.
> > >
> > > I checked:
> > > - incubating in name
> > > - LICENSE is missing information and it’s unknown if include 3rd party
> > respires are compatible with the Apache license.
> > > - NOTICE is fine
> > > - signatures and hashes are correct
> > > - all ASF files have ASF headers
> > > - no unexpected binary files
> > > - I didn’t compile the source
> > >
> > > Kind Regards,
> > > Justin
> > >
> > > 1. https://www.flaticon.com/pricing
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Retire Crail

[Felix Cheung]

+1

(As mentor)


On Mon, Jun 6, 2022 at 12:48 PM Julian Hyde  wrote:

> After years of declining activity[1][2], and following discussions on
> dev@ [3][4] the Crail podling has voted to retire from incubation
> [5][6]. Per policy [7] I am proposing an IPMC vote to retire Crail.
>
> The vote is by lazy consensus and runs for 72 hours.
>
> +1 [ ] Retire Crail from the Incubator
> -1 [ ] Do not retire Crail from the Incubator
>
> Here is my vote:
> +1 [x] Retire Crail from the Incubator
>
> Julian Hyde
> (Member IPMC, Crail mentor)
>
> [1] https://incubator.apache.org/projects/crail.html
> [2] https://lists.apache.org/list?d...@crail.apache.org
> [3] https://lists.apache.org/thread/6hxkph98gobb5y7lrvx62rgr6ob9o91h
> [4] https://lists.apache.org/thread/9n08m29xgpshs4f2wxgspm4tlt44r98g
> [5] https://lists.apache.org/thread/xzss2o1oj2k85bbhvx883ojlrlozg3zm
> [6] https://lists.apache.org/thread/7165g55mrchzrlmhczfgybgzlnl2hxpj
> [7] https://incubator.apache.org/guides/retirement.html#deciding_to_retire
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Sedona to Top Level Project

[Felix Cheung]

Are there decision-making guidelines published?


On Sun, May 29, 2022 at 10:49 PM Jia Yu  wrote:

> Dear Sedona PMC members and users,
>
> We are getting ready for the graduation process.
>
> 1. I have summarized the community statistics and Sedona maturity model.
> See https://issues.apache.org/jira/browse/SEDONA-81
> 2. I have created a suitable name search JIRA ticket (may take some time to
> get approved):
>
> https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-200?filter=reportedbyme
> 3. I have updated the podling report (may need a few hours to by synced):
> https://incubator.apache.org/projects/sedona.html
>
> PMC members, please double check these questions from the podling report
> and see if you have any concerns. Otherwise, I will mark them as "NO" after
> June 5th. Then I will call for a vote for graduation and sign off
> the report.
>
> Collaborative Development
>
>- Have all of the active long-term volunteers been identified and
>acknowledged as committers on the project?
>- Are there three or more independent committers? (The legal definition
>of independence is long and boring, but basically it means that there
> is no
>binding relationship between the individuals, such as a shared employer,
>that is capable of overriding their free will as individuals, directly
> or
>indirectly.)
>- Are project decisions being made in public by the committers?
>- Are the decision-making guidelines published and agreed to by all of
>the committers?
>
> Licensing awareness
>
>- Are all licensing, trademark, credit issues being taken care of and
>acknowledged by all committers?
>
> Thanks,
> Jia
>
> On Fri, Dec 10, 2021 at 7:51 AM Felix Cheung 
> wrote:
>
> > Hi!
> >
> > Highly recommend the community look at and complete the Maturity mode
> >
> >
> https://community.apache.org/apache-way/apache-project-maturity-model.html
> >
> > Also it is a good idea to compute some community stats: number of
> > contributions (commits), number of contributors (and growth since
> > incubation), email discussions, releases,  number of release managers,
> > affiliations of committers / PPMC members, new committers or PPMC members
> > since incubation etc
> >
> > 
> > From: Paweł Kociński 
> > Sent: Friday, December 10, 2021 2:12:57 AM
> > To: Jia Yu 
> > Cc: Jinxuan Wu ; Mohamed Sarwat ;
> > Netanel Malka ; Zongsi Zhang <
> > zongsi.zh...@grabtaxi.com>; dev@sedona.apache.org  >
> > Subject: Re: [DISCUSS] Graduate Sedona to Top Level Project
> >
> > That sounds awesome. Can I help you somehow with the process ?
> >
> >
> > W dniu pt., 10.12.2021 o 01:56 Jia Yu  napisał(a):
> >
> > > Dear all,
> > >
> > > It has been 16 months since Apache Sedona joined the Apache Incubator
> in
> > > July 2020. We have made 4 Apache releases so far. I think it is a good
> > time
> > > to start the discussion of  graduating Apache Sedona from the incubator
> > to
> > > become a Top Level Project.
> > >
> > > For graduation, to the best of my knowledge, we need to follow the
> > > graduation guideline [1] and podling status report [2]. After a brief
> > > evaluation, I think most of the remaining steps are to clear up the
> > > copyright issues.
> > >
> > > Please feel free to chime in if you think there are any blockers.
> > > Meanwhile, I will start to fix the issues on our way to graduation.
> > >
> > > [1] https://incubator.apache.org/guides/graduation.html
> > > [2] https://incubator.apache.org/projects/sedona.html
> > >
> > > Thanks,
> > > Jia
> > >
> >
>

Re: [VOTE] Accept Uniffle into the Apache Incubator

[Felix Cheung]

+1 binding

On Wed, Jun 1, 2022 at 10:47 AM Brahma Reddy Battula 
wrote:

> +1 (non binding)
>
> On Wed, 1 Jun 2022 at 9:50 AM, Young Seung Andrew Ko <
> youngseung.and...@gmail.com> wrote:
>
> > +1 (non binding)
> >
> > Thank you :)
> >
> > 2022년 6월 1일 (수) 오후 12:25, Sammi Chen 님이 작성:
> >
> > > +1 (non-binding)
> > >
> > > Good luck to Uniffle!
> > >
> > > Regards,
> > > Sammi
> > >
> > > On Tue, 31 May 2022 at 09:37, Jerry Shao  wrote:
> > >
> > > > Hi all,
> > > >
> > > > Following up the [DISCUSS] thread on Uniffle[1] and Firestorm[2], I
> > would
> > > > like to
> > > > call a VOTE to accept Uniffle into the Apache Incubator, please check
> > out
> > > > the Uniffle Proposal from the incubator wiki[3].
> > > >
> > > > Please cast your vote:
> > > >
> > > > [ ] +1, bring Uniffle into the Incubator
> > > > [ ] +0, I don't care either way
> > > > [ ] -1, do not bring Uniffle into the Incubator, because...
> > > >
> > > > The vote will open at least for 72 hours, and only votes from the
> > > > Incubator PMC are binding, but votes from everyone are welcome.
> > > >
> > > > [1] https://lists.apache.org/thread/fyyhkjvhzl4hpzr52hd64csh5lt2wm6h
> > > > [2] https://lists.apache.org/thread/y07xjkqzvpchncym9zr1hgm3c4l4ql0f
> > > > [3]
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/UniffleProposal
> > > >
> > > > Best regards,
> > > > Jerry
> > > >
> > >
> >
> --
>
>
>
> --Brahma Reddy Battula
>

Re: [VOTE] Graduate Apache InLong(Incubating) as a TLP

[Felix Cheung]

+1 binding

On Thu, May 26, 2022 at 6:14 PM li gang  wrote:

> +1 (non-binding)
>
> Charles Zhang  于2022年5月25日周三 14:34写道：
>
> > Dear Apache Incubator Community,
> >
> >
> > The InLong community has a discussion thread [1], passed the community
> vote
> > [2], and the vote result is published [3]. We have discussed the
> graduation
> > for InLong in the Incubator Community [4], where no issues were raised
> and
> > lots of positive responses were received.
> >
> >
> > I would like to start this voting thread to request graduating Apache
> > InLong (incubating) from the incubator as a TLP. Please provide your vote
> > as one of the following options:
> >
> > [ ] +1 Yes, I support InLong to graduate from the Apache incubator.
> >
> > [ ] +0 No opinion.
> >
> > [ ] -1 No, the InLong project is not ready to graduate, because ...
> >
> >
> > The VOTE will remain open for at least 72 hours.
> >
> >
> > Since incubating in ASF, the project itself has become more mature and
> >
> > stable. The following is a brief summary of the project and community
> >
> > during the incubation:
> >
> >
> > - 11 versions were released by 6 different release managers, of which 5
> >
> > versions are the original TubeMQ, and 6 versions are after the name was
> >
> > changed to InLong. The release cadence is about 2 months [5].
> >
> >
> > - 10 new Committers and 3 PPMCs were added during incubating, they are
> from
> >
> > 4 different organizations. All PPMCs and Committers are spread across 8
> >
> > different organizations [6].
> >
> >
> > - 101 unique code developers [7].
> >
> >
> > - Closed more than 2200 issues, with an average of 200 issues per version
> >
> > [8].
> >
> >
> > - All the dependencies were reviewed and ensured they do not bring any
> >
> > license issues [9].
> >
> >
> > - Evaluated the InLong project and self-checked the InLong maturity model
> >
> > [10] and the pre-graduation Check [11].
> >
> >
> > - Well and Complete documentation for contributors and users [12].
> >
> >
> > - Created channels like Email, Slack, Twitter, WeChat, and GitHub
> >
> > Discussions to communicate, with more than 650 subscribers.
> >
> >
> > - Actively participated in or held more than 15 meetups to increase
> >
> > community influence.
> >
> >
> > Please see the proposed board resolution below and let us know what you
> >
> > think. The initial PMC members were passed by the discussion and
> invitation
> >
> > [13].
> >
> >
> > [1] https://lists.apache.org/thread/pzqk3z4pbbh3qx0cl1hmpzo1305p2lro
> >
> > [2] https://lists.apache.org/thread/03topv74zgp4j22cg805l50sqzcr3y20
> >
> > [3] https://lists.apache.org/thread/n1mkcplz53ytlmhk7r506toxgsv6rfw9
> >
> > [4] https://lists.apache.org/thread/4zyt242opdhxclt9qqs9q34k7mlc0v5t
> >
> > [5] https://inlong.apache.org/download/main/
> >
> > [6] https://whimsy.apache.org/roster/ppmc/inlong
> >
> > [7] https://github.com/apache/incubator-inlong/graphs/contributors
> >
> > [8]
> >
> >
> https://github.com/apache/incubator-inlong/issues?q=is%3Aissue+is%3Aclosed
> >
> > [9] https://github.com/apache/incubator-inlong/tree/master/licenses
> >
> > [10]
> >
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INLONG=Maturity+Assessment+for+InLong
> >
> > [11]
> >
> > https://cwiki.apache.org/confluence/display/INLONG/Graduation+Check+List
> >
> > [12] https://inlong.apache.org/docs/next/introduction
> >
> > [13] https://lists.apache.org/thread/mgl2jgpdojb6dzdhnhoq7dfqs26hj2xc
> >
> >
> >
> >
> --
> >
> > Establish the Apache InLong Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> >
> > the Foundation and consistent with the Foundation's purpose to establish
> >
> > a Project Management Committee charged with the creation and maintenance
> >
> > of open-source software, for distribution at no charge to the public,
> >
> > related to a one-stop data integration framework that provides
> >
> > automatic, secure, and reliable data transmission capabilities. InLong
> >
> > supports both batch and stream data processing at the same time, which
> >
> > offers great power to build data analysis, modeling, and other real-time
> >
> > applications based on streaming data.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >
> > (PMC), to be known as the "Apache InLong Project", be and hereby is
> >
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache InLong Project be and hereby is responsible
> >
> > for the creation and maintenance of software related to a one-stop data
> >
> > integration framework that provides automatic, secure, and reliable data
> >
> > transmission capabilities. InLong supports both batch and stream data
> >
> > processing at the same time, which offers great power to build data
> >
> > analysis, modeling, and other 

Re: [DISCUSSION] Incubating Proposal of Firestorm

[Felix Cheung]

Same here, would love to see if I can help, Jerry.


On Mon, May 16, 2022 at 10:31 PM Saisai Shao  wrote:

> Thanks Weiwei, let me add you to the mentor list.
>
> Best regards,
> Jerry
>
> Weiwei Yang  于2022年5月17日周二 12:18写道：
>
> > +1
> > This is an interesting project, I'd be happy to help the project's
> > incubation process.
> > Let me know if you need my help, Thanks
> >
> > On Mon, May 16, 2022 at 8:09 PM Saisai Shao 
> > wrote:
> >
> > > Got it, thanks a lot Justin.
> > >
> > > Best regards,
> > > Jerry
> > >
> > > Justin Mclean  于2022年5月17日周二 10:59写道：
> > >
> > > > Hi,
> > > >
> > > > The new project name doesn’t need to be a registered trademark, but
> you
> > > > would still need to pick a name that is now likely to have any
> > trademark
> > > > issues.
> > > >
> > > > The project may want to get the ASF to register the mark at a later
> > date,
> > > > but it wold be best to talk abut that on the trademarks@ list.
> > > >
> > > > Kind Regards,
> > > > Justin
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

Re: [VOTE] Graduate Apache AGE (Incubating) as a TLP

[Felix Cheung]

+1 (binding)

The community has really taken an effort since the last discussion thread.
Good luck!


On Tue, May 10, 2022 at 9:32 AM Jean-Baptiste Onofré 
wrote:

> +1 (binding)
>
> Good luck as TLP.
>
> Regards
> JB
>
> On Mon, May 9, 2022 at 1:34 AM Eya Badal  wrote:
> >
> > Dear Apache Incubator Community,
> >
> > Having passed the Community Graduation Vote [1] by the AGE community
> with a
> > vote result to graduate the incubation [2], we have discussed Apache
> AGE's
> > graduation in the general@incubator [DISCUSS] thread [3], where no
> issues
> > were raised and lots of positive responses were received.
> >
> > I would like to start this voting thread to request graduating Apache AGE
> > (incubating) from the incubator as a TLP.
> >
> > Please provide your vote as one of the following options:
> >
> > [ ] +1 - Recommend graduation of Apache AGE as a Top Level
> >
> > [ ] 0   - I don't feel strongly about it, but don't object
> >
> > [ ] -1  - Do not recommend the graduation of Apache AGE because …
> >
> > The VOTE will remain open for at least 72 hours.
> >
> >
> >
> > In addition to building and releasing the AGE software the Apache Way,
> the
> > Apache AGE (Incubating) project community has grown in the following
> areas:
> >
> >
> >-
> >
> >Close to 1000 commits
> >-
> >
> >Added 9 new committers (from 7 different companies/institutions in 7
> >different countries) and elevated 4 committers to PPMC
> >-
> >
> >7 Apache releases (AGE 0.3, 0.4, 0.5, 0.6, 0.7 and 1.0 and sub-project
> >AGE Viewer 1.0) from different release managers [4]
> >-
> >
> >4 mentors, 13 PPMC members / committers (mentors excluded)
> >-
> >
> >50+ unique contributors - Contributions span more than 20 countries
> >across the globe
> >
> >
> >-
> >
> >Developed and maintained the Apache AGE website [5]
> >-
> >
> >Created an online user guide updated automatically to support new
> >version of AGE. [6]
> >-
> >
> >Assessed ourselves against the Apache Project maturity matrix [7] and
> >didn't find any issues
> >
> >
> >
> >
> > [1] https://lists.apache.org/thread/q2cgbnhvpzk2k0m8yfh89lzc75qym9k9
> >
> > [2] https://lists.apache.org/thread/lr3x9bm8jyv6o5kvyh7cf3tyxrpp2kwm
> >
> > [3] https://lists.apache.org/thread/fhdc27bp8lp7nsklq0ttc3cvyx7543ky
> >
> > [4] Apache AGE website release page <https://age.apache.org/?l=versions>
> >
> > [5] https://age.apache.org/
> >
> > [6] Online user guide at Apache AGE website <https://age.apache.org/#>
> > under the Documentation menu
> >
> > [7] Apache AGE maturity assessment <https://age.apache.org/?l=maturity>
> >
> >
> >
> >
> 
> >
> > Establish the Apache AGE Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> >
> > the Foundation and consistent with the Foundation's purpose to establish
> >
> > a Project Management Committee charged with the creation and maintenance
> >
> > of open-source software, for distribution at no charge to the public,
> >
> > related to a multi-model database that enables graph and relational
> >
> > models built on PostgreSQL.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >
> > (PMC), to be known as the "Apache AGE Project", be and hereby is
> >
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache AGE Project be and hereby is responsible for
> >
> > the creation and maintenance of software related to a multi-model
> >
> > database that enables graph and relational models built on PostgreSQL;
> >
> > and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache AGE" be and hereby
> >
> > is created, the person holding such office to serve at the direction of
> >
> > the Board of Directors as the chair of the Apache AGE Project, and to
> >
> > have primary responsibility for management of the projects within the
> >
> > scope of responsibility of the Apache AGE Project; and be it further
> >
> > RESOLVED, that the persons listed imm

Re: Podling Sedona Report Reminder - May 2022

[Felix Cheung]

Reminder

From: johndam...@apache.org 
Sent: Wednesday, April 27, 2022 5:50:12 PM
To: d...@sedona.incubator.apache.org 
Subject: Podling Sedona Report Reminder - May 2022

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 May 2022.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, May 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/May2022

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

Re: Podling Teaclave Report Reminder - May 2022

[Felix Cheung]

Reminder

From: johndam...@apache.org 
Sent: Wednesday, April 27, 2022 5:50:12 PM
To: d...@teaclave.incubator.apache.org 
Subject: Podling Teaclave Report Reminder - May 2022

Dear podling,

This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.

The board meeting is scheduled for Wed, 18 May 2022.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, May 04).

Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.

Candidate names should not be made public before people are actually
elected, so please do not include the names of potential committers or
PPMC members in your report.

Thanks,

The Apache Incubator PMC

Submitting your Report

--

Your report should contain the following:

*   Your project name
*   A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
*   A list of the three most important issues to address in the move
towards graduation.
*   Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
*   How has the community developed since the last report
*   How has the project developed since the last report.
*   How does the podling rate their own maturity.

This should be appended to the Incubator Wiki page at:

https://cwiki.apache.org/confluence/display/INCUBATOR/May2022

Note: This is manually populated. You may need to wait a little before
this page is created from a template.

Note: The format of the report has changed to use markdown.

Mentors
---

Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.

Incubator PMC

-
To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org
For additional commands, e-mail: dev-h...@teaclave.apache.org

Re: [VOTE] Accept into the Apache Incubator

[Felix Cheung]

+1

On Fri, Apr 22, 2022 at 10:04 AM Xiaorui Wang 
wrote:

> +1
>
> Best regards,
>
> Xiaorui Wang 王小瑞
> Apache RocketMQ PMC chair
>
>
> Kevin Ratnasekera  于2022年4月23日周六 00:24写道：
>
> > +1 ( binding )
> >
> > On Fri, Apr 22, 2022 at 6:14 PM Madhawa Gunasekara 
> > wrote:
> >
> > > Hi
> > >
> > > +1 (binding)
> > >
> > > On Fri, Apr 22, 2022 at 6:01 PM Furkan KAMACI 
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > +1 (binding).
> > > >
> > > > Kind Regards,
> > > > Furkan KAMACI
> > > >
> > > > On Fri, Apr 22, 2022 at 5:05 PM XiaoYu  wrote:
> > > >
> > > > > + 1 （non-binding）
> > > > >
> > > > > good luck！
> > > > >
> > > > > Willem Jiang  于2022年4月22日周五 22:00写道：
> > > > > >
> > > > > > Sorry, my bad,  I forgot to add the DevLake into the title.
> > > > > >
> > > > > > The title should be  [VOTE] Accept DevLake into the Apache
> > Incubator.
> > > > > >
> > > > > > Willem Jiang
> > > > > >
> > > > > > Twitter: willemjiang
> > > > > > Weibo: 姜宁willem
> > > > > >
> > > > > > On Fri, Apr 22, 2022 at 9:46 PM Kent Yao  wrote:
> > > > > > >
> > > > > > > +1, good luck!
> > > > > > >
> > > > > > > Seems the title should be [VOTE] Accept DevLake into the Apache
> > > > > Incubator
> > > > > > >
> > > > > > > BR,
> > > > > > >
> > > > > > > Kent Yao
> > > > > > >
> > > > > > > Willem Jiang  于2022年4月22日周五 21:39写道：
> > > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Following up the [DISCUSS] thread on DevLake [1], I would
> like
> > to
> > > > > call a
> > > > > > > > VOTE to accept DevLake into the Apache Incubator.
> > > > > > > >
> > > > > > > > Please cast your vote:
> > > > > > > >
> > > > > > > >   [ ] +1, bring DevLake into the Incubator
> > > > > > > >   [ ] +0, I don't care either way
> > > > > > > >   [ ] -1, do not bring DevLake into the Incubator, because...
> > > > > > > >
> > > > > > > > The vote will open at least for 72 hours, and only votes from
> > the
> > > > > > > > Incubator PMC are binding, but votes from everyone are
> welcome.
> > > > > > > >
> > > > > > > > Please check out the DevLake Proposal from the incubator
> > wiki[2].
> > > > > > > >
> > > > > > > > [1]
> > > > https://lists.apache.org/thread/b4jj51v7o9db193skfhzkn0nz2w8361l
> > > > > > > > [2]
> > > > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/DevLakeProposal
> > > > > > > >
> > > > > > > > Willem Jiang
> > > > > > > >
> > > > > > > > Twitter: willemjiang
> > > > > > > > Weibo: 姜宁willem
> > > > > > > >
> > > > > > > >
> > > > -
> > > > > > > > To unsubscribe, e-mail:
> > general-unsubscr...@incubator.apache.org
> > > > > > > > For additional commands, e-mail:
> > > general-h...@incubator.apache.org
> > > > > > > >
> > > > > > >
> > > > > > >
> > > -
> > > > > > > To unsubscribe, e-mail:
> general-unsubscr...@incubator.apache.org
> > > > > > > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> > > > > > >
> > > > > >
> > > > > >
> > -
> > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > > For additional commands, e-mail:
> general-h...@incubator.apache.org
> > > > > >
> > > > >
> > > > >
> -
> > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Accept Kvrocks into the Apache Incubator

[Felix Cheung]

+1

On Thu, Apr 21, 2022 at 7:28 PM Sheng Wu  wrote:

> +1 binding
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
> Liang Chen  于2022年4月22日周五 09:19写道：
> >
> > +1(binding)
> >
> > Regards
> > Liang
> >
> > 在 2022年4月20日星期三，Furkan KAMACI  写道：
> >
> > > Hi,
> > >
> > > +1 (binding)
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > On 20 Apr 2022 Wed at 13:49 Calvin Kirs  wrote:
> > >
> > > > +1 (binding)
> > > > Good luck.
> > > >
> > > > 张铎(Duo Zhang)  于2022年4月20日周三 18:29写道：
> > > > >
> > > > > +1(binding)
> > > > >
> > > > > Goson zhang  于2022年4月20日周三 18:27写道：
> > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > Good luck!
> > > > > >
> > > > > > Willem Jiang  于2022年4月20日周三 14:38写道：
> > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > Willem Jiang
> > > > > > >
> > > > > > > Twitter: willemjiang
> > > > > > > Weibo: 姜宁willem
> > > > > > >
> > > > > > > On Wed, Apr 20, 2022 at 7:25 AM Liang Chen <
> > > chenliang...@apache.org>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Following up the [DISCUSS] thread on Kvrocks[1], I would
> like to
> > > > > > > > call a VOTE to accept Kvrocks into the Apache Incubator,
> please
> > > > check
> > > > > > out
> > > > > > > > the Kvrocks Proposal from the incubator wiki[2].
> > > > > > > >
> > > > > > > > Please cast your vote:
> > > > > > > >
> > > > > > > > [ ] +1, bring Kvrocks into the Incubator
> > > > > > > > [ ] +0, I don't care either way
> > > > > > > > [ ] -1, do not bring Kvrocks into the Incubator, because...
> > > > > > > >
> > > > > > > > The vote will open at least for 72 hours, and only votes
> from the
> > > > > > > > Incubator PMC are binding, but votes from everyone are
> welcome.
> > > > > > > >
> > > > > > > > [1]
> > > > https://lists.apache.org/thread/bdtmvbmvzrgjd1kj7mdrp9tkqrhg3d31
> > > > > > > > [2]
> > > > > > >
> > > >
> https://cwiki.apache.org/confluence/display/INCUBATOR/KvrocksProposal
> > > > > > > >
> > > > > > > > Regards
> > > > > > > > Liang
> > > > > > >
> > > > > > > 
> > > -
> > > > > > > To unsubscribe, e-mail:
> general-unsubscr...@incubator.apache.org
> > > > > > > For additional commands, e-mail:
> general-h...@incubator.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best wishes！
> > > > CalvinKirs
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Teaclave TrustZone SDK (incubating) v0.2.0-rc.2

[Felix Cheung]

+1

Note: the KEYS file does not need to be packaged into the release.

- incubating in name
- signature and hash fine
- DISCLAIMER-WIP is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers

On Tue, Apr 12, 2022 at 11:24 AM Mingshen Sun  wrote:

> Dear Community,
>
> Sorry for the multiple follow ups. Please help to review this release
> (we need more IPMC votes). Thanks!
>
> Mingshen
>
> On Tue, Apr 5, 2022 at 4:10 PM Mingshen Sun  wrote:
> >
> > Thanks!
> >
> > We still need one more IPMC vote for the final release.
> >
> > Mingshen
> >
> > On Mon, Apr 4, 2022 at 2:37 PM Furkan KAMACI 
> wrote:
> > >
> > > Hi,
> > >
> > > +1 (binding)
> > >
> > > Kind Regards,
> > > Furkan KAMACI
> > >
> > > On 4 Apr 2022 Mon at 23:29 Mingshen Sun  wrote:
> > >
> > > > Hi all,
> > > >
> > > > We still need TWO more IPMC binding votes for this release [1].
> Please
> > > > let me know if there's anything I can help with. Thanks.
> > > >
> > > > Mingshen
> > > >
> > > > [1] https://incubator.apache.org/policy/incubation.html#releases
> > > >
> > > > On Thu, Mar 31, 2022 at 6:58 PM Gordon  wrote:
> > > > >
> > > > > LGTM, +1 (binding), thanks.
> > > > >
> > > > > On Thu, Mar 31, 2022 at 6:27 PM Mingshen Sun 
> wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > We need more votes from IPMC for this release. Please kindly
> help to
> > > > > > review this new release. Thanks!
> > > > > >
> > > > > > Mingshen
> > > > > >
> > > > > > On Wed, Mar 30, 2022 at 6:10 PM Zhaofeng Chen 
> wrote:
> > > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > I checked
> > > > > > > - LICENSE and NOTICE files exist
> > > > > > > - DISCLAIMER file exist
> > > > > > > - Include the word incubating in the release filename
> > > > > > > - No unexpected binary files
> > > > > > > - Build successfully by following the instruction
> > > > > > >
> > > > > > > Best,
> > > > > > > Zhaofeng
> > > > > > >
> > > > > > > On Sun, Mar 27, 2022 at 7:58 PM Yuan Zhuang 
> > > > wrote:
> > > > > > >
> > > > > > > > Dear community,
> > > > > > > >
> > > > > > > > I am pleased to be calling this vote for the second release
> of
> > > > Apache
> > > > > > > > Teaclave TrustZone SDK (incubating) 0.2.0 (release candidate
> 2).
> > > > > > > >
> > > > > > > > The Apache Teaclave (incubating) community has voted and
> approved
> > > > the
> > > > > > > > release, with seven +1 votes from IPMC members (Mingshen Sun,
> > > > Yulong
> > > > > > Zhang,
> > > > > > > > Yu Ding, Tongxin Li, Rundong Zhou, Duan Ran, Rong Fan).
> > > > > > > >
> > > > > > > > Vote thread:
> > > > > > > >
> > > > > > > > -
> https://lists.apache.org/thread/f1qqf8qrc1wvf6zznzbl7y6rkk0thb9n
> > > > > > > >
> > > > > > > > Result thread:
> > > > > > > >
> > > > > > > > -
> https://lists.apache.org/thread/2m55lk5m6nskdn8rmq4ccgo1vrmklb13
> > > > > > > >
> > > > > > > >
> > > > > > > > The release candidate to be voted over is available at:
> > > > > > > >
> > > > > > > > -
> > > > > > > >
> > > > > >
> > > >
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/
> > > > > > > >
> > > > > > > > The release candidate is signed with a GPG key available at:
> > > > > > > >
> > > > > > > > - https://downloads.apache.org/incubator/teaclave/KEYS
> > > > > > > >
> > > > > > > > The Git commit for this release is:
> > > > > > > >
> > > > > > > > -
> > > > > > > >
> > > > > >
> > > >
> https://gitbox.apache.org/repos/asf?p=incubator-teaclave-trustzone-sdk.git;a=commit;h=9250da957b4c9dd9c916d582439cca28a359ec02
> > > > > > > >
> > > > > > > > The release note is available in:
> > > > > > > >
> > > > > > > > -
> > > > > > > >
> > > > > >
> > > >
> https://github.com/apache/incubator-teaclave-trustzone-sdk/releases/tag/v0.2.0-rc.2
> > > > > > > >
> > > > > > > > Build guide and get started instructions can be found at:
> > > > > > > >
> > > > > > > > -
> > > > https://github.com/apache/incubator-teaclave-trustzone-sdk#readme
> > > > > > > >
> > > > > > > >
> > > > > > > > The short version of building Teaclave TrustZone SDK from the
> > > > source
> > > > > > > > tarball:
> > > > > > > >
> > > > > > > > ```
> > > > > > > > $ wget
> > > > > > > >
> > > > > >
> > > >
> https://dist.apache.org/repos/dist/dev/incubator/teaclave/trustzone-sdk-0.2.0-rc.2/apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating.tar.gz
> > > > > > > >
> > > > > > > > # Instructions to verify the source tar:
> > > > > > > > #
> > > > > >
> > > >
> https://teaclave.apache.org/download/#verify-the-integrity-of-the-files
> > > > > > > >
> > > > > > > > $ tar zxvf
> > > > apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating.tar.gz
> > > > > > &&
> > > > > > > > cd apache-teaclave-trustzone-sdk-0.2.0-rc.2-incubating
> > > > > > > >
> > > > > > > > # Build the SDK and TAs
> > > > > > > > $ docker run -v$(pwd):/teaclave -w /teaclave -it
> > > > > > > > teaclave/teaclave-trustzone-sdk-build:0.3.0 bash -c
> "./setup.sh &&
> > > > > > source
> > > > > 

Re: [VOTE] Apache AGE 1.0.0-rc1 Release

[Felix Cheung]

+1

-incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers


On Tue, Apr 5, 2022 at 5:22 PM Nicholas Sorrell  wrote:

> Dear Apache Community,
>
> This is an official vote for the Apache AGE 1.0.0-rc1 release.
>
> The Apache AGE community vote thread can be found here:
> https://lists.apache.org/thread/wfqjhhz2pv5c3w33053b7h5s774dl1lm
>
> The results thread of the community vote can be found here:
> https://lists.apache.org/thread/99bbvhd7yb2dh321dvl4s9j415pl9dz2
>
> **Vote Results**:
> No 0 or -1 votes.
>
> 1 (+1) Binding Vote:
> *Trista Pan
>
> 5 (+1) Non Binding:
> *Josh Innis
> *Andrew Ko
> *John Gemegnani
> *Muhammad Shoib
> *VUONG QUOC Viet
>
> To learn more about Apache AGE, please see https://age.apache.org/
>
> Functionality included and addressed in this release:
>
> - Add an upgrading SQL script file from 0.5.0 to 0.6.0
> - Add upgrading file age--0.6.0--0.7.0.sql
> - Refactor function get_agtype_value_object_value
> - Age load issue (issue #188)
> - Refactor agtype_access_operator
> - Bugfix - Remove INLINE from function declaration
> - Rebase VLE code
> - Implement Merge Clause
> - Bugfix: chained union logic
> - Allow a path of one vertex
> - Created functions for load graph from CSV files
> - Add UNION into EXPLAIN grammar rule
> - Implement UNWIND clause(issue #173)
> - Bugfix:(nodejs) Corrects parsing for independence value(issue #177)
> - Feat: Implement OPTIONAL MATCH (issue #175)
> - Update copyright in NOTICE
>
>
> *
>
> The git tag to be discussed and voted upon:
> https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc1
>
> The git commit hash:
>   commit 282c24f4aa7150daceba15742966ac6be77a35c4
>
> The release files for 1.0.0, can be found at:
>  https://dist.apache.org/repos/dist/dev/incubator/age/1.0.0.rc1/
>
> Signatures used for AGE RCs can be found in this file:
> https://downloads.apache.org/incubator/age/KEYS
>
> The fingerprint of key to sign release artifacts:
>   C3F1 A95F 43D0 CCF6 A5EF  92C5 4E03 406A 5227 E499
>
> For information about the contents of this release, see:
> https://github.com/apache/incubator-age/releases/tag/v1.0.0-rc1
>
> *
>
> Please vote:
>
> [ ] +1 Release this package as Apache AGE 1.0.0-rc1
> [ ] 0  I won't get in the way
> [ ] -1 Do not release this package because ...
>
>
> This vote will be open for 72 hours.
>
> Thank you for your time.
>
>
> Best Regards,
> Nick Sorrell
>
>

Re: [VOTE] Release Apache Sedona 1.2.0-incubating-rc2

[Felix Cheung]

+1

On Tue, Apr 12, 2022 at 9:42 PM Jia Yu  wrote:

> Dear all,
>
> We still need one more vote. Can someone help us?
>
> Thanks,
> Jia
>
> On Sun, Apr 10, 2022 at 5:47 PM vongosling  wrote:
>
> > +1, binding,
> > I checked:
> > - incubating is in the name
> > - changes since the last vote
> > - LICENSE, DISCLAIMER-WIP are there and look good
> > - hash and signature are good
> > - no binary in the source archive
> >
> > Paweł Kociński  于2022年4月10日周日 16:55写道：
> >
> > > Hi all,
> > >
> > > This is a call for vote on Apache Sedona 1.2.0-incubating-rc2. Please
> > refer
> > > to the changes listed at the bottom of this email.
> > >
> > > Sedona Community vote thread (
> > > https://lists.apache.org/thread/fpfz5jmr5vomoyh4tkopxq1nzymn74gj):
> > >
> > > Sedona community vote result thread (
> > > https://lists.apache.org/thread/xozcc7p7896d0v7t9oyt643kkofpcfrs):
> > >
> > >
> > > Release notes:
> > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.0-incubating-rc2/docs/setup/release-notes.md
> > >
> > > Build instructions:
> > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.0-incubating-rc2/docs/setup/compile.md
> > >
> > > GitHub tag:
> > >
> > >
> >
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.2.0-incubating-rc2
> > >
> > > GPG public key to verify the Release:
> > > https://downloads.apache.org/incubator/sedona/KEYS
> > >
> > >
> > > Source code and binaries:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.2.0-incubating-rc2/
> > >
> > > The vote will be open for at least 72 hours or until a majority of at
> > least
> > > 3 "approve" PMC votes are cast
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove with the reason
> > >
> > > Checklist for reference (because of DISCLAIMER-WIP, other checklist
> items
> > > are not blockers):
> > >
> > > [ ] Download links are valid.
> > >
> > > [ ] Checksums and PGP signatures are valid.
> > >
> > > [ ] DISCLAIMER is included.
> > >
> > > [ ] Source code artifacts have correct names matching the current
> > release.
> > >
> > > For a detailed checklist  please refer to:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > > 
> > >
> > > Changes according to the comments on the previous release candidate
> > > - NOTICE file has been fix in the PR (
> > > https://github.com/apache/incubator-sedona/pull/594/files) and it's
> > > included in this release (1.2.0-incubating-rc2)
> > >
> > > Regards,
> > > Paweł
> > >
> >
> >
> > --
> > Best Regards :-)
> >
>

Re: [DISCUSS] Incubating Proposal of DevLake

[Felix Cheung]

Thanks.

Can the community comment on

- the project relationship with devstream/dtm

- repo here looks related:
https://github.com/philipjung164/devlake/graphs/contributors


On Fri, Apr 8, 2022 at 6:33 AM Willem Jiang  wrote:

> Hi Felix，
>
> Thanks for the kindly offering, I just added you into the mentor list
> of the proposal.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Apr 8, 2022 at 2:45 AM Felix Cheung 
> wrote:
> >
> > Interesting and unique project for incubator.
> >
> > Would love to help as mentor.
> >
> >
> > On Thu, Apr 7, 2022 at 1:22 AM Willem Jiang 
> wrote:
> >
> > > We want to propose  DevLake[1]  as a new Apache Incubator project.
> > >
> > > DevLake helps developer teams integrate and analyze software
> > > development data throughout the software development life cycle
> > > (SDLC).
> > > Specifically, DevLake provides:
> > >
> > > * High-quality connectors that integrate data from various DevOps
> tools;
> > > * A comprehensive and unified data model and metrics that enable
> > > developers to easily query data and answer questions regarding their
> > > development process;
> > > * A plugin system that allows customizable data connectors and
> enrichers;
> > > * An unified ETL management module that orchestrates data collection
> > > and analysis.
> > >
> > > I'd be happy to be the Champion of this project and many thanks to
> > > Liang Zhang (zhangliang at apache dot org)，Lidong Dai (lidongdai at
> apache
> > > dot org)，Sijie Guo (sijie at apache dot org） for being the mentor of
> > > DevLake
> > > project and helping us to polish the incubating proposal[2].
> > >
> > > Looking forward to your feedback and thank you very much.
> > >
> > > [1]https://github.com/merico-dev/lake
> > > [2]
> https://cwiki.apache.org/confluence/display/INCUBATOR/DevLakeProposal
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Incubating Proposal of DevLake

[Felix Cheung]

Interesting and unique project for incubator.

Would love to help as mentor.


On Thu, Apr 7, 2022 at 1:22 AM Willem Jiang  wrote:

> We want to propose  DevLake[1]  as a new Apache Incubator project.
>
> DevLake helps developer teams integrate and analyze software
> development data throughout the software development life cycle
> (SDLC).
> Specifically, DevLake provides:
>
> * High-quality connectors that integrate data from various DevOps tools;
> * A comprehensive and unified data model and metrics that enable
> developers to easily query data and answer questions regarding their
> development process;
> * A plugin system that allows customizable data connectors and enrichers;
> * An unified ETL management module that orchestrates data collection
> and analysis.
>
> I'd be happy to be the Champion of this project and many thanks to
> Liang Zhang (zhangliang at apache dot org)，Lidong Dai (lidongdai at apache
> dot org)，Sijie Guo (sijie at apache dot org） for being the mentor of
> DevLake
> project and helping us to polish the incubating proposal[2].
>
> Looking forward to your feedback and thank you very much.
>
> [1]https://github.com/merico-dev/lake
> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/DevLakeProposal
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Sedona 1.2.0-incubating-rc1

[Felix Cheung]

If there is a change to NOTICE file, that should be included, the community
should roll a new RC


On Sun, Apr 3, 2022 at 12:45 AM Jia Yu  wrote:

> Dear incubator PPMC,
>
> Since we have fixed the signature issue, do you think we should restart the
> voting process again, or can the PPMC who voted -1 change their votes to
> +1?
>
> Thank you very much!
> Jia
>
> On Sat, Apr 2, 2022 at 8:25 AM Paweł Kociński 
> wrote:
>
> > Hi,
> > The signature issue has been fixes. The NOTICE file has been fixed in PR:
> > https://github.com/apache/incubator-sedona/pull/594/files, it was not
> > included in this release by mistake.
> > Sedona community votes will be more careful in the future (checklist will
> > be included in the voting process). Sorry for inconvenience.
> > Regards,
> > Paweł
> >
> > pon., 28 mar 2022 o 22:47 Paweł Kociński 
> napisał(a):
> >
> > > Hi all,
> > >
> > > This is a call for vote on Apache Sedona 1.2.0-incubating-rc1. Please
> > > refer to the changes listed at the bottom of this email.
> > >
> > > Sedona Community vote thread (
> > > https://lists.apache.org/thread/d7y5d7nm196jb8qoshgt28gqvw6norzb):
> > >
> > > Sedona community vote result thread (
> > > https://lists.apache.org/thread/65jzxnflppvqd1lqw123rxz1zhryy43f):
> > >
> > > Release notes:
> > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.0-incubating-rc1/docs/setup/release-notes.md
> > >
> > > Build instructions:
> > >
> > >
> >
> https://github.com/apache/incubator-sedona/blob/sedona-1.2.0-incubating-rc1/docs/setup/compile.md
> > >
> > > GitHub tag:
> > >
> > >
> >
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.2.0-incubating-rc1
> > >
> > > GPG public key to verify the Release:
> > > https://downloads.apache.org/incubator/sedona/KEYS
> > >
> > > Source code and binaries:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.2.0-incubating-rc1/
> > >
> > > The vote will be open for at least 72 hours or until a majority of at
> > > least 3 "approve" PMC votes are cast
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove with the reason
> > >
> > > Checklist for reference (because of DISCLAIMER-WIP, other checklist
> items
> > > are not blockers):
> > >
> > > [ ] Download links are valid.
> > >
> > > [ ] Checksums and PGP signatures are valid.
> > >
> > > [ ] DISCLAIMER is included.
> > >
> > > [ ] Source code artifacts have correct names matching the current
> > release.
> > >
> > > For a detailed checklist  please refer to:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > > Regards,
> > > Paweł
> > >
> > >
> >
>

Re: [VOTE] Apache AGE Viewer 1.0.0 (rc2) Release

[Felix Cheung]

+1 (binding)


- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- All source files have ASF headers

- No unexpected binary files


- LICENSE and NOTICE are fine*
checked /frontend/src/lib/cytoscape-cxtmenu - there have been major
modifications to /frontend/src/lib/cytoscape-cxtmenu/cxtmenu.js.

however, upon inspection, these are stylistic changes within the spirit of
the original code. (spacing and let/const, layout), also confirmed that the
original license headers are in these source files.


On Sat, Mar 26, 2022 at 11:18 AM Muhammad Usama  wrote:

> +1 for me
>
> Best regards
> Muhammad Usama
>
> On Mon, Mar 21, 2022 at 11:31 AM Jasper Blues 
> wrote:
>
> > +1 for me too.
> >
> > I strongly believe that "release early & often” approach will help to to
> > gain traction and show the community progress on a compelling eco-system.
> >
> > For a graph DB to success toolset is key, and this represents progress in
> > that direction.
> >
> > Remember that perfect is the enemy of good (enough for 1.0)
> >
> > My congratulations to everyone involved.
> >
> > Jasper Blues | Liberation Data 
> > Phone: +61 3 9028 7328
> > Skype: jasperblues
> >
> > > On Mar 21, 2022, at 2:28 PM, Young Seung Andrew Ko <
> > youngseung.and...@gmail.com> wrote:
> > >
> > > +1 (not binding)
> > >
> > > On Tue, Mar 8, 2022 at 11:48 AM Trista Pan  wrote:
> > >
> > >> +1 binding, I checked,
> > >>
> > >> [x] Download links are valid.
> > >> [x] Checksums and PGP signatures are valid.
> > >> [x] LICENSE, NOTICE and DISCLAIMER files exist.
> > >> [x] All files have license headers if necessary.
> > >>
> > >> 
> > >> Trista Pan
> > >> Twitter & Github: tristaZero
> > >>
> > >>> On Mar 4, 2022, at 1:54 PM, Alex Kwak  wrote:
> > >>>
> > >>> Dear Apache Community,
> > >>>
> > >>> This is a call for releasing Apache AGE Viewer 1.0.0 (rc2).
> > >>>
> > >>> The community vote thread can be found here:
> > >> https://lists.apache.org/thread/647z95htsgqbdwbt2xsmn3b245mj1g42
> > >>> The results of the community vote can be found here:
> > >> https://lists.apache.org/thread/z5xjwzttccr84g1xl30wz0b8pn1j34vh
> > >>>
> > >>> 7 +1 Non Bindings
> > >>> Andrew Ko
> > >>> Joe Fagan
> > >>> Eya Badal
> > >>> Josh Innis
> > >>> VUONG QUOC Viet
> > >>> John Gemignani
> > >>> Nicholas Sorrell
> > >>>
> > >>> To learn more about Apache AGE (Incubating), please see
> > >> http://age.apache.org/
> > >>>
> > >>> *
> > >>>
> > >>> Functionalities included and addressed in this release:
> > >>> - Graph visualization for AGE.
> > >>> - Extends edge and vertex point by point.
> > >>>
> > >>> *
> > >>>
> > >>> The git tag to be discussed and voted upon
> > >>>
> https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0-rc2
> > >>>
> > >>> The git commit hash:
> > >>> commit 63ed1882e372ef8cdf6677e9850237650e586848
> > >>>
> > >>> The release files, including signatures, digests, etc. can be found
> at:
> > >>>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/incubator/age/viewer/apache-age-viewer-1.0.0-incubating-rc2/
> > >>>
> > >>> The SHA512 Checksum for these artifacts is:
> > >>>
> > >>
> >
> 683f17b6bfc84d9fd8c88f0856b4dd18fdb24ab429517134880594243601f6810fefe9f7d9da7d5a802e2236622974c4297cee874e0f06685e85a40d5ac90d3d
> > >>>
> > >>> Release artifacts are signed with the following key:
> > >>> https://downloads.apache.org/incubator/age/KEYS
> > >>>
> > >>> The fingerprint of key to sign release artifacts:
> > >>> 0E7F 408D 8C6A 1952 329C B379 D471 FDCE 5F5C 5B82
> > >>>
> > >>> For more information about the contents of this release, see:
> > >>>
> https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0-rc2
> > >>>
> > >>> *
> > >>>
> > >>> The vote will be open for 72 hours.
> > >>> [ ] +1 release this package
> > >>> [ ] +0 no opinion
> > >>> [ ] -1 do not release this package because...
> > >>>
> > >>> Thank you for all your time,
> > >>> Alex Kwak
> > >>>
> > >>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >>> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >>
> > >> -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >>
> >
> >
>

Re: [VOTE] Graduate Apache YuniKorn (Incubating) as a Top Level Project

[Felix Cheung]

+1

On Wed, Feb 16, 2022 at 8:11 PM Xun Liu  wrote:

> +1 (binding) from me,
>
> The App-aware scheduling and Hierarchy Resource Queues of the Apache
> YuniKorn(Incubating)
> can greatly improve the resource scheduling capability of k8s and increase
> the throughput of the App system running in k8s.
> We were impressed with these features during our use.
>
> I think that upgrading Apache YuniKorn(Incubating) to a top-level project
> would be more beneficial to the development of the project.
>
> good luck!
>
> Xun Liu
> Best Regards,
>
> On Thu, Feb 17, 2022 at 11:16 AM Luciano Resende 
> wrote:
>
> > +1 (binding)
> >
> > On Tue, Feb 15, 2022 at 9:04 PM Weiwei Yang  wrote:
> >
> > > Hi Incubator Community
> > >
> > > After the discussion in the YuniKorn community [1], and passed the
> > > community vote [2][3]. We have started the discussion in the
> > > general@incubator list [4]. Based on all positive feedback received,
> we
> > > would like to start this voting thread to request graduating the
> YuniKorn
> > > project from the incubator as a TLP.
> > >
> > > Please provide your vote as one of the following options:
> > >
> > > [ ] +1 - Recommend graduation of Apache YuniKorn as a TLP
> > > [ ]  0 -  I don't feel strongly about it, but don't object
> > > [ ] -1 - Do not recommend the graduation of Apache YuniKorn because…
> > >
> > > The VOTE will remain open for at least 72 hours.
> > >
> > > To summarize what the YuniKorn community has achieved in the incubating
> > > phase:
> > >
> > >- 6 releases were done by 6 different releases managers.
> > >- 41 unique code contributors and over 1300+ commits.
> > >- A growing community that added 2 new mentors, 10 new committers, 4
> > new
> > >PPMC from 6 different organizations
> > >- A diverse community that has 6 mentors, 23 PPMC, and 29 committers
> > >from at least 14 different organizations [5]
> > >- Well documented web site [6]
> > >- The maturity self-assessment [7]
> > >
> > > [1] https://lists.apache.org/thread/dno411y59g2pcy1d3kd7s3kdjz9jw65n
> > > [2] https://lists.apache.org/thread/gx5dmb4yqkw1dfvzf2l91gwhobx6g81m
> > > [3] https://lists.apache.org/thread/dfvdk3dc82pvopxc28h6p4wdgp0xcfk2
> > > [4] https://lists.apache.org/thread/o8y4b3mp21f608745ngqqdhc628qtwxf
> > > [5] https://yunikorn.apache.org/community/people
> > > [6] https://yunikorn.apache.org/
> > > [7] https://yunikorn.apache.org/community/maturity
> > >
> > >
> > >
> >
> --
> > >
> > > Establish the Apache YuniKorn Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > the Foundation and consistent with the Foundation's purpose to
> establish
> > > a Project Management Committee charged with the creation and
> maintenance
> > > of open-source software, for distribution at no charge to the public,
> > > related to a standalone resource scheduler responsible for scheduling
> > > batch jobs and long-running services on large scale distributed systems
> > > running in on-premises environments as well as different public clouds.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache YuniKorn Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache YuniKorn Project be and hereby is responsible
> > > for the creation and maintenance of software related to a standalone
> > > resource scheduler responsible for scheduling batch jobs and
> > > long-running services on large scale distributed systems running in
> > > on-premises environments as well as different public clouds; and be it
> > > further
> > >
> > > RESOLVED, that the office of "Vice President, Apache YuniKorn" be and
> > > hereby is created, the person holding such office to serve at the
> > > direction of the Board of Directors as the chair of the Apache YuniKorn
> > > Project, and to have primary responsibility for management of the
> > > projects within the scope of responsibility of the Apache YuniKorn
> > > Project; and be it further
> > >
> > > RESOLVED, that th

Re: [DISCUSS and VOTE] AGEViewer dockerhub presence

[Felix Cheung]

On "support"- Think you said it -

In reference to the links: Docker is not a replacement for Apache releases,
and should not be considered as such.

Should be clear nightly builds should not be on DockerHub, etc


From: Josh Innis 
Sent: Monday, January 31, 2022 8:08:30 AM
To: dev@age.apache.org 
Subject: Re: [DISCUSS and VOTE] AGEViewer dockerhub presence

The community should have a discussion about the need for a docker image of
AGE Viewer before we vote on it.

A docker image of AGE Viewer will ease the adoption of AGE for graph
related problems. It makes it so that a user of AGE Viewer does not have to
have intimate knowledge of: Postgres, AGE, NodeJs and React before they can
get all the components to work together. I think having a docker image of
AGE-Viewer is a great idea.

In reference to the links: Docker is not a replacement for Apache releases,
and should not be considered as such.

What support model do you think is going to be needed for this? Giving
people a method of visualizing their data in the most convenient way
possible seems to be a good idea, but what do you think are the drawbacks
of this decision?

On Mon, Jan 31, 2022 at 10:32 AM Felix Cheung 
wrote:

> I’d suggest the community to have a discussion of the need. What support
> model that will be etc.
>
> Mentor “vote” is more a proxy of having a clear understanding in the
> community.
>
>
> 
> From: Joe Fagan 
> Sent: Monday, January 24, 2022 10:14:42 PM
> To: dev@age.apache.org 
> Subject: Re: [DISCUSS and VOTE] AGEViewer dockerhub presence
>
> Hi all, please vote to utilise dockerhub as a distribution method for
> Viewer as it is for AGE
>
> @Felix
>
> The direction from Infra team on the incubator AGE dockerhub request was...
> "Neither of these threads expressly confirm the project's desire to adopt
> DockerHub distribution, they are just discussions about issues related to
> it. Please have your project mentors evaluate and approve the requested
> distribution method."
>
> Can I ask you to either vote, or evaluate and approve the
> dockerhub distribution method for Viewer too, whichever is most
> appropriate, or give further specific advice.
>
> Thanks
> Joe
>
> On Tue, 25 Jan 2022 at 05:59, Felix Cheung 
> wrote:
>
> > I guess I’m linking to myself. I see infra asks for mentor, but as a
> > community you should just have a vote. You can explicitly ask a mentor to
> > vote too
> >
> > https://lists.apache.org/thread/oxzo04gxxkqvmtw7rmzkw8t2d8cf3nwo
> > 
> > From: Felix Cheung 
> > Sent: Monday, January 24, 2022 9:51:05 PM
> > To: dev@age.apache.org 
> > Subject: Re: [DISCUSS] AGEViewer dockerhub presence
> >
> > Shouldn’t this be a vote?
> >
> > Please see
> > https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-22356
> > 
> > From: Joe Fagan 
> > Sent: Monday, January 24, 2022 7:34:36 AM
> > To: dev@age.apache.org 
> > Subject: [DISCUSS] AGEViewer dockerhub presence
> >
> > Dear mentors,
> >
> > We would like to have an image for Incubator AGE Viewer at
> hub.docker.com.
> > Is it possible to approve the creation of
> > https://hub.docker.com/r/apache/age-viewer
> > <https://hub.docker.com/r/apache/ageviewer>
> >
> > We will not require push access to this and can instead use automated
> build
> > based on tags in the https://github.com/apache/incubator-age-viewer
> > repository.
> >
> > Once we have your approval we will raise a ticket on JIRA to the Infra
> Team
> > with the relevant details.
> >
> > Thank you
> > Joe
> >
>

Re: [DISCUSS and VOTE] AGEViewer dockerhub presence

[Felix Cheung]

I’d suggest the community to have a discussion of the need. What support model 
that will be etc.

Mentor “vote” is more a proxy of having a clear understanding in the community.



From: Joe Fagan 
Sent: Monday, January 24, 2022 10:14:42 PM
To: dev@age.apache.org 
Subject: Re: [DISCUSS and VOTE] AGEViewer dockerhub presence

Hi all, please vote to utilise dockerhub as a distribution method for
Viewer as it is for AGE

@Felix

The direction from Infra team on the incubator AGE dockerhub request was...
"Neither of these threads expressly confirm the project's desire to adopt
DockerHub distribution, they are just discussions about issues related to
it. Please have your project mentors evaluate and approve the requested
distribution method."

Can I ask you to either vote, or evaluate and approve the
dockerhub distribution method for Viewer too, whichever is most
appropriate, or give further specific advice.

Thanks
Joe

On Tue, 25 Jan 2022 at 05:59, Felix Cheung 
wrote:

> I guess I’m linking to myself. I see infra asks for mentor, but as a
> community you should just have a vote. You can explicitly ask a mentor to
> vote too
>
> https://lists.apache.org/thread/oxzo04gxxkqvmtw7rmzkw8t2d8cf3nwo
> ________
> From: Felix Cheung 
> Sent: Monday, January 24, 2022 9:51:05 PM
> To: dev@age.apache.org 
> Subject: Re: [DISCUSS] AGEViewer dockerhub presence
>
> Shouldn’t this be a vote?
>
> Please see
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-22356
> 
> From: Joe Fagan 
> Sent: Monday, January 24, 2022 7:34:36 AM
> To: dev@age.apache.org 
> Subject: [DISCUSS] AGEViewer dockerhub presence
>
> Dear mentors,
>
> We would like to have an image for Incubator AGE Viewer at hub.docker.com.
> Is it possible to approve the creation of
> https://hub.docker.com/r/apache/age-viewer
> <https://hub.docker.com/r/apache/ageviewer>
>
> We will not require push access to this and can instead use automated build
> based on tags in the https://github.com/apache/incubator-age-viewer
> repository.
>
> Once we have your approval we will raise a ticket on JIRA to the Infra Team
> with the relevant details.
>
> Thank you
> Joe
>

Re: [DISCUSS] AGEViewer dockerhub presence

[Felix Cheung]

I guess I’m linking to myself. I see infra asks for mentor, but as a community 
you should just have a vote. You can explicitly ask a mentor to vote too

https://lists.apache.org/thread/oxzo04gxxkqvmtw7rmzkw8t2d8cf3nwo

From: Felix Cheung 
Sent: Monday, January 24, 2022 9:51:05 PM
To: dev@age.apache.org 
Subject: Re: [DISCUSS] AGEViewer dockerhub presence

Shouldn’t this be a vote?

Please see 
https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-22356

From: Joe Fagan 
Sent: Monday, January 24, 2022 7:34:36 AM
To: dev@age.apache.org 
Subject: [DISCUSS] AGEViewer dockerhub presence

Dear mentors,

We would like to have an image for Incubator AGE Viewer at hub.docker.com.
Is it possible to approve the creation of
https://hub.docker.com/r/apache/age-viewer
<https://hub.docker.com/r/apache/ageviewer>

We will not require push access to this and can instead use automated build
based on tags in the https://github.com/apache/incubator-age-viewer
repository.

Once we have your approval we will raise a ticket on JIRA to the Infra Team
with the relevant details.

Thank you
Joe

Re: [DISCUSS] AGEViewer dockerhub presence

[Felix Cheung]

Shouldn’t this be a vote?

Please see 
https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-22356

From: Joe Fagan 
Sent: Monday, January 24, 2022 7:34:36 AM
To: dev@age.apache.org 
Subject: [DISCUSS] AGEViewer dockerhub presence

Dear mentors,

We would like to have an image for Incubator AGE Viewer at hub.docker.com.
Is it possible to approve the creation of
https://hub.docker.com/r/apache/age-viewer


We will not require push access to this and can instead use automated build
based on tags in the https://github.com/apache/incubator-age-viewer
repository.

Once we have your approval we will raise a ticket on JIRA to the Infra Team
with the relevant details.

Thank you
Joe

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

[Felix Cheung]

Pls add the podling status file
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/

3 ppmc members have not subscribed to private@

These can be found on
https://whimsy.apache.org/roster/ppmc/yunikorn



From: Weiwei Yang 
Sent: Thursday, January 20, 2022 10:05:55 PM
To: dev@yunikorn.apache.org 
Cc: priv...@yunikorn.apache.org 
Subject: Re: Apache YuniKorn (Incubating) - Community Graduation Vote

hi all

Most issues under the graduation preparation JIRA YUNIKORN-1005
 are fixed.
The remaining one is the who-are-we web page, I am currently collecting
info for that, should be done by next week.
Shall we start to vote now? I can start a new thread for the community
voting if nobody has objections.

On Tue, Jan 11, 2022 at 11:02 AM Wilfred Spiegelenburg 
wrote:

> None of the security lists mentioned in the security page [1] are
> moderated. They are private lists, i.e. not openly available for
> browsing in an archive, but not moderated. Using the private@ for
> YuniKorn does not seem to line up with what other projects do either.
> None of the recently graduated projects mention anything like using
> the private@ mailing list on their sites. They all have just used the
> general security link mentioned on their site unless they have a
> specific security@ list. YuniKorn would be the one standing out from
> what seems to be the norm.
> Examples from the last 2 years of graduated projects using a simple
> link or a text pointing to [1]: Pinot, Dolphinscheduler, Ratis,
> Echarts, Gobblin, TVM, Superset and Datasketches. There are more but I
> think this provides an overview of what is expected on graduation.
>
> Wilfred
>
> [1] https://www.apache.org/security/
>
> On Tue, 11 Jan 2022 at 18:21, Weiwei Yang  wrote:
> >
> > Hi Wilfred
> >
> > Adding a security@ mailing list sounds like a good idea, but I do not
> think that is required in the current stage.
> > We can do that post-graduate. For now, the Apache security doc said
> >
> > > We strongly encourage you to report potential security vulnerabilities
> to one of our private security mailing lists first, before disclosing them
> in a public forum.
> >
> > I do not see any issue if we use our private@ mailing list for this
> purpose.
> >
> > On Mon, Jan 10, 2022 at 11:01 PM Wilfred Spiegelenburg <
> wilfr...@apache.org> wrote:
> >>
> >> The private@ is a moderated list. This has two issues: a moderator
> >> needs to approve any message not sent by a PMC member. This will slow
> >> down the process of interaction with the reporter. It would also not
> >> reach the YuniKorn committers group as not all committers are part of
> >> the PMC. Security issues should be handled and worked on by all
> >> committers not just by the PMC members.
> >>
> >> The security notification update made to the website I think does not
> >> line up with the security guidelines referenced in the link provided
> >> in the dropdown menu of the YuniKorn site [1]. In that link there is a
> >> well defined way to report security issues. If we need to enhance and
> >> extend what we do we either establish a security@ mailing list and
> >> provide a static page with security related information on our site or
> >> we leave it as is. My preference would be to establish a security@
> >> list and make all committers a member of that list.
> >>
> >> I think we need to roll back the website changes part of YUNIKORN-1006
> >> [2] in PR [3] for the website.
> >>
> >> Wilfred
> >>
> >> [1] https://www.apache.org/security/
> >> [2] https://issues.apache.org/jira/browse/YUNIKORN-1006
> >> [3] https://github.com/apache/incubator-yunikorn-site/pull/105
> >>
> >> On Tue, 11 Jan 2022 at 04:45, Holden Karau 
> wrote:
> >> >
> >> > For "The project provides a well-documented, secure and private
> channel to report security issues, along with a documented way of
> responding to them.' the standard that I've seen used is to tell people to
> e-mail private@ when they think they might have a security related issue.
> I think that would probably work well for Yunikorn too.
> >> >
> >> >
> >> > On Mon, Jan 10, 2022 at 7:04 AM Chenya Zhang <
> chenyazhangche...@gmail.com> wrote:
> >> >>
> >> >> Hi Weiwei,
> >> >>
> >> >> Thanks for driving this! The evaluation is quite comprehensive
> overall. I checked our Apache project maturity guidelines and noticed the
> below three items. Not sure if we already have them but they are not
> blockers to our graduation. We could think more about them along the way.
> >> >>
> >> >> QU30
> >> >>
> >> >> The project provides a well-documented, secure and private channel
> to report security issues, along with a documented way of responding to
> them.
> >> >>
> >> >> QU40
> >> >>
> >> >> The project puts a high priority on backwards compatibility and aims
> to document any incompatible changes and 

Re: [VOTE] Graduate Apache AGE (Incubating) as a Top Level Project

[Felix Cheung]

I am definitely in private@ and in a bunch of dev@ discussion. Not sure if
that was mis reported.


On Wed, Jan 5, 2022 at 11:15 PM Justin Mclean 
wrote:

> Hi,
>
> > * Dehowe Feng 
> > * Eya Badal   
> > * Felix Cheung
> > * Jasper Blues
> > * John Gemignani  
> > * Josh Innis  
> > * Juan Pan
> > * Kevin Ratnasekera   
> > * Mason Sharp 
> > * Nick Sorrell
> > * Pieterjan De Potter 
> > * Raphael Bircher 
> > * Suneel Marthi   
> > * Von Gosling 
>
> Looking at this list there are several people who:
> a) Are not subscribed to the private list
> b) Have not taken part in discussions on the mailing list (that I can find)
>
> When putting together a graduation proposal, it's a good idea to find out
> if the proposed PMC are willing to be PMC members. While there is no real
> harm in having inactive PMC members, during graduation is a good time to
> trim the PMC to those who will actually do the work.
>
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Official Docker Image for Apache AGE

[Felix Cheung]

Pls see

https://infra.apache.org/release-distribution.html#dockerhub

Example https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-12781

From: Eya Badal 
Sent: Thursday, December 30, 2021 12:58:13 PM
To: dev@age.apache.org 
Subject: Re: [DISCUSS] Official Docker Image for Apache AGE

Mentors, could you please evaluate and approve the Docker distribution method 
currently available at this address 
https://hub.docker.com/r/joefagan/incubator-age so that Apache Infra can create 
a dockerhub account under Apache dockerhub for AGE so we can push the AGE image 
there?

Best regards,
Eya

On 2021/09/13 16:23:37 Joe Fagan wrote:
> Dear Community,
>
> @Mentors please advise on how to make this AGE docker image official and
> hosted on the Apache Docker Hub.
> https://hub.docker.com/repository/docker/joefagan/incubator-age
> Thanks
> Joe
>

Re: [VOTE] Release Apache AGE Viewer (incubating) 1.0.0-rc0

[Felix Cheung]

lots of dependencies - are these licenses reviewed and handled in the LICENSE 
file?
https://github.com/apache/incubator-age-viewer/blob/main/backend/package.json
https://github.com/apache/incubator-age-viewer/blob/main/frontend/package.jso\

this requires a component - again could be a LICENSE check, if it is required 
for execution (at runtime) we should check license of that too. Also what is 
the trademark on the “AgensGraph” name?
https://github.com/apache/incubator-age-viewer/blob/main/backend/src/models/agensgraph/agensGraphRepository.js
'@bitnine-oss/ag-driver');

The
https://github.com/apache/incubator-age-viewer/blob/main/README.md
references  to bitnine/agviewer

From: Eya Badal 
Sent: Thursday, December 30, 2021 6:44:11 AM
To: dev@age.apache.org 
Subject: Re: [VOTE] Release Apache AGE Viewer (incubating) 1.0.0-rc0

Looks good to me
+1

I checked the following:

- Signature and hash - check.
- DISCLAIMER - check.
- LICENSE and NOTICE - check.
- No unexpected binary files - check.
- incubating in name - check.

Best,
Eya

On 2021/12/23 00:58:26 Alex Kwak wrote:
> Dear Apache AGE Community,
>
> This is an official vote for the Apache AGE Viewer release v1.0.0-rc0 that we 
> have been working toward it.
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
> Functionalities included and addressed in this release:
> - Graph visualization for AGE.
> - Extends edge and vertex point by point.
>
>
> The vote is open now and until December 25th at 5:00 PM PST and passes if a 
> majority +1 votes are cast, with a minimum of 3 +1 votes.
>
> [ ] +1 Release this package as Apache AGE 0.6.0
> [ ] 0 I won't get in the way
> [ ] -1 Do not release this package because ...
>
>
> The git tag to be discussed and voted upon
> https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0
>
> The git commit hash:
> commit 2c55b2302875449565674aa039517734cf338031
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/age/viewer/apache-age-viewer-1.0.0-incubating-rc0/
>
> The SHA512 Checksum for these artifacts is:
> 8fa45254bba973678243a78321869aaf88c746b55168d4401931c5d6e87192c80d581d97e927c8b87098aaacba8d6f77bf1ca225e864c49117f5cb1887c699d0
>
> Release artifacts are signed with the following key:
> https://downloads.apache.org/incubator/age/KEYS
>
> The fingerprint of key to sign release artifacts:
> 0E7F 408D 8C6A 1952 329C B379 D471 FDCE 5F5C 5B82
>
> For more information about the contents of this release, see:
> https://github.com/apache/incubator-age-viewer/releases/tag/v1.0.0
>
>
>
> Best regards,
> Alex Kwak
>

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.12.1 (RC1)

[Felix Cheung]

+1

(Sorry my +1 was cut off)

- incubating in name
- signature and hash fine
- DISCLAIMER, LICENSE and NOTICE fine
- No unexpected binary files
- Source files have ASF header



> On Sun, Dec 26, 2021 at 3:37 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> +1 (binding)
>>
>> I checked:
>> - incubating in name
>> - DISCLAIMER exists
>> - LICENSE and NOTICE are fine
>> - No unexpected binary fines in the releases
>> - All files have ASF headers
>> - Can't compile but that’s probably my setup (OSX)
>>
>> I did notice a couple of references to cloudera’s JIRA e.g
>> https://jira.cloudera.com/browse/COMPX-4041and
>> https://jira.cloudera.com/browse/COMPX-4042 which seems a little unusual?
>>
>> Kinds Regards,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.12.1 (RC1)

[Felix Cheung]

+1

- incubating in name
- signature and hash fine
- DISCLAIMER, LICENSE and NOTICE fine
- No unexpected binary files
- Source files have ASF header

On Sun, Dec 26, 2021 at 3:37 PM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - DISCLAIMER exists
> - LICENSE and NOTICE are fine
> - No unexpected binary fines in the releases
> - All files have ASF headers
> - Can't compile but that’s probably my setup (OSX)
>
> I did notice a couple of references to cloudera’s JIRA e.g
> https://jira.cloudera.com/browse/COMPX-4041and
> https://jira.cloudera.com/browse/COMPX-4042 which seems a little unusual?
>
> Kinds Regards,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Looking for a champion: resurrect log4j 1.x

[Felix Cheung]

What are the concerning security vulnerabilities in log4j 1 and the
severity level?

I saw one mentioned in the thread which apparently redhat had fixed (with
socket stream deserialization)


On Mon, Dec 20, 2021 at 3:56 PM Martin Gainty  wrote:

> i would ping the original author ceki gulcu
> Random thoughts by Ceki Gülcü: The forces and vulnerabilities of the
> Apache model<
> https://ceki.blogspot.com/2010/05/forces-and-vulnerabilites-of-apache.html
> >
> Random thoughts by Ceki Gülcü: The forces and vulnerabilities of the
> Apache model<
> https://ceki.blogspot.com/2010/05/forces-and-vulnerabilites-of-apache.html
> >
> Brett Porter said I agree with Bertrand's point. Also, it is necessary
> to be careful not to ascribe too much power to the votes themselves - they
> are only a tool for gauging consensus, which is the main objective.
> ceki.blogspot.com
>
> Best Regards,
> martin-
>
> 
> From: Jungtaek Lim 
> Sent: Monday, December 20, 2021 4:26 PM
> To: general@incubator.apache.org 
> Subject: Re: Looking for a champion: resurrect log4j 1.x
>
> Just wondering, is it even fulfilling the criteria of incubation? Have
> there been any similar cases before?
>
> It was stated that there will be no effort on active development but focus
> only on CVE fixes. This sounds to me as the project will start as only
> fixing a few known CVEs and stop till other CVEs are discovered (there may
> be huge difference between proactively discovering CVEs vs passively fixing
> the reported CVEs by others), and never be attempted to become TLP.
> Majority of status reports will be blank. That said, it doesn't seem that
> sustainability is proven.
>
>
> On Mon, Dec 20, 2021 at 10:51 PM John D. Ament 
> wrote:
>
> > On Mon, Dec 20, 2021 at 8:42 AM Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> > > Guess there are 4 options:
> > >
> > > 1. resurrect log4j1 and let it die again
> > > 2. do a log4j1 release for the CVE under logging umbrella (as a
> > subproject)
> > > - after all log4j1 belongs to logging as a subproject already (
> > > https://logging.apache.org/dormant.html)
> > > 3. the log4j1-log4j2 bridge (but agree this is not a solution and
> > requires
> > > to do 2 to be useful technically since none of log4j1 users will want
> to
> > > import log4j2, at least cause it is not compatible with java version or
> > due
> > > to the injected bytecode like module-info)
> > > 4. do a CVE fix release fork on github or any other hosting
> > >
> > > Personally I don't think 1 or 3 are real options, 4 is but not that
> nice
> > > indeed (due to the fact it would be yet another forks but also cause it
> > > requires some GAV change or build hack to be done properly) so from my
> > > window I would be tempted to push for 2 which sounds like a quick win
> for
> > > everyone.
> > >
> >
> > Questions like this probably should be on one of the logging lists rather
> > than the incubator list.  The Incubator would not create a hostile fork
> > under any circumstance, including of an existing project/sub-project
> within
> > Apache.  In a situation like this it would be purely a call by the
> Logging
> > PMC, whether or not they want the Incubator to create the podling.
> >
> >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Old Blog
> > >  | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn  | Book
> > > <
> > >
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > > >
> > >
> > >
> > > Le lun. 20 déc. 2021 à 14:32, John D. Ament  a
> > > écrit :
> > >
> > > > Hi Vladimir,
> > > >
> > > > I think based on what you're describing and the Logging PMC's
> response,
> > > > re-incubating the project makes sense.  I would be curious if the
> > Logging
> > > > PMC would be interested in restarting the sub-project after a
> > successful
> > > > incubation period.  This seems to match what Ralph is suggesting as
> > well.
> > > >
> > > > Typically this would mean that the VP Logging PMC would serve as the
> > > > champion, and as the sponsor the Logging PMC would still be the one
> to
> > > vote
> > > > to add the project to the incubator.  If the VP Logging isn't
> > interested
> > > in
> > > > doing this, I would recommend starting out the project as a
> standalone
> > > > podling and keeping the Incubator as sponsor rather than Logging.
> See
> > > [1]
> > > > for some details on those notes.  The incubator would be responsible
> > for
> > > > voting on releases, receiving notices for new PPMC members, etc
> > > regardless
> > > > of who is the sponsor.  Given enough contributors and a diverse
> > > contributor
> > > > base then the Incubator PMC and the Logging PMC (if they're the
> > sponsor)
> > > > would vote whether everyone feels the new project can be brought back
> > to
> > > > 

Re: [DISCUSS] Graduate Apache AGE Incubating as a Top Level Project

[Felix Cheung]

The community should definitely fix/address these.

As for Committer bar, the community should review the contributors to look
for sustained contributors that should be voted in. PPMC should discuss
this.

I couldn’t find anything about @agedb.io - can Andrew explain the
connection? At least, this might be a branding / trademark issue that the
PPMC should sort out.



On Sun, Dec 19, 2021 at 12:39 AM Justin Mclean 
wrote:

> Hi,
>
> I’m seeing some issues here:
> - Indications that the committer/PPMC bar may be too high and not all
> forms of contribution recognised.
> - A new PPMC member not being added in the correct way
> - Other than that recent addition no other PPMC members added
> - May be some concern about employment diversity of the PPMC members
> - Issues with headers and licensing a few months back
> - People not signed up to the right mailing lists
> - I see in the maturity guide under releases it mentions docker files but
> these don’t seem to be documented on the website? Where are these located?
> This related JIRA is a little concerning [1].
> - There are some minor trademark issues on the bitnine site e.g [2]
> - Releases of Age-viewer not following ASF policy
> - Links to download 0.5.0 and 0.6.0 on the download page are not correct
> [3]
> - I notice one person replied to this thread had a agedb.io email address
> - what is it relationship with the project?
>
> It would be great if I could get some mentor feedback here t see if these
> are just just minor issues or if some more work needs o be done before the
> project should consider graduation.
>
> Kind Regards.
> Justin
>
> 1. https://issues.apache.org/jira/browse/INFRA-22024
> 2. https://bitnine.net/blog-postgresql/thestack-apache-age/
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Sedona to Top Level Project

[Felix Cheung]

Hi!

Highly recommend the community look at and complete the Maturity mode

https://community.apache.org/apache-way/apache-project-maturity-model.html

Also it is a good idea to compute some community stats: number of contributions 
(commits), number of contributors (and growth since incubation), email 
discussions, releases,  number of release managers, affiliations of committers 
/ PPMC members, new committers or PPMC members since incubation etc


From: Paweł Kociński 
Sent: Friday, December 10, 2021 2:12:57 AM
To: Jia Yu 
Cc: Jinxuan Wu ; Mohamed Sarwat ; 
Netanel Malka ; Zongsi Zhang ; 
dev@sedona.apache.org 
Subject: Re: [DISCUSS] Graduate Sedona to Top Level Project

That sounds awesome. Can I help you somehow with the process ?


W dniu pt., 10.12.2021 o 01:56 Jia Yu  napisał(a):

> Dear all,
>
> It has been 16 months since Apache Sedona joined the Apache Incubator in
> July 2020. We have made 4 Apache releases so far. I think it is a good time
> to start the discussion of  graduating Apache Sedona from the incubator to
> become a Top Level Project.
>
> For graduation, to the best of my knowledge, we need to follow the
> graduation guideline [1] and podling status report [2]. After a brief
> evaluation, I think most of the remaining steps are to clear up the
> copyright issues.
>
> Please feel free to chime in if you think there are any blockers.
> Meanwhile, I will start to fix the issues on our way to graduation.
>
> [1] https://incubator.apache.org/guides/graduation.html
> [2] https://incubator.apache.org/projects/sedona.html
>
> Thanks,
> Jia
>

Re: Apache AGE (Incubating) - Community Graduation Vote

[Felix Cheung]

That looks good to me. +1

To note, 0.6 is not on “Download” on 
https://age.apache.org/


From: John Gemignani 
Sent: Wednesday, December 1, 2021 5:55:40 PM
To: dev@age.apache.org 
Subject: Re: Apache AGE (Incubating) - Community Graduation Vote

I completely agree with all of Eya and Josh's points.

Especially, now that we have v0.6.0 out (which took a lot of extra attention 
and cleaned up a lot of pending issues) and with the upcoming release of 
v0.7.0. The latter release will add a significant amount of new functionality. 
This makes me confident that the project will be able to move forward a lot 
more smoothly.

+1

John

On 2021/12/02 01:39:41 Josh Innis wrote:
> This project has seen incredible growth from when it was originally donated 
> to Apache. The community continues to grow as more people see the 
> opportunities in what the project could be. Now that we are nearly done with 
> our original goal of implementing the openCypher specification in Postgres as 
> an extension, we can now begin to pursue some of these powerful features that 
> the community is requesting in the Github repository. The team is continuing 
> to grow at an accelerated pace, with most of the new committers being 
> accepted in the last six months. I personally think the future of AGE is 
> bright, especially with all the new features that will be coming out in 
> v0.7.0.
>
> On 2021/12/01 02:42:22 Eya Badal wrote:
> > Thank you mentors for your valuable feedback. The feedback is addressed 
> > below.
> >
> > Regarding GitHub issues and pull requests:
> >   It is true that in the earlier months we were sluggish in responding to 
> > and closing out issues. In
> >   April we created SLA to categorise (label), assign, and respond to 
> > issues. Since April, 95% are
> >   responded within 72 hours (80% of issues are responded to within 24 hrs). 
> > In the last month we
> >   have closed 8 issues across the project. Regarding pull requests we are 
> > behind our internal
> >   SLA but have addressed that in the last 48 hrs.
> >
> > Regarding committer and contributor diversity:
> >   The committers and contributors act on their own initiative without 
> > representing a corporation
> >   or organization. Core contributors are indeed employees of a single 
> > company (Bitnine Global,
> >   the project donator) who has interest in the success of AGE but there are 
> > many entirely
> >   independent contributors and committers. Contributions span more than 20 
> > countries across
> >   the globe including Australia, Belarus, Belgium, China, France, Germany, 
> > Ireland, Israel, Italy,
> >   Luxembourg, The Netherlands, Nigeria, The Philippines, Russia, South 
> > Korea, Thailand, UK,
> >   Ukraine, USA and Vietnam.
> >
> > Regarding the breakdown of the PPMC membership on affiliation (companies) 
> > and PPMC growth:
> >
> >  The PPMC representation, excluding mentors is as follows:
> >
> >   Bitnine Global: Eya Badal, Josh Innis, John Gemignani, Dehowe Feng(in 
> > voting process).
> >   Liberation Data: Jasper Blues
> >   Immuta: Mason Sharp
> >
> >  The project has added five new committers taking the total to 10 
> > (excluding mentors).
> >
> >   Bitnine Global: Dehowe Feng
> >   Kroger: Nick Sorrell
> >   Ghent University: Pieterjan De Potter
> >   Agedb: Andrew Ko, Alex Kwak
> >
> > RE CS10 “The project maintains a public list of its contributors who have 
> > decision power”:
> > We now have the list of community members (committer and PPMC) at 
> > age.apache.org
> >
> > Regarding how incubator-age-viewer is released:
> >   Age-viewer has been released 8 times. The age-viewer developers are 
> > looking to release in the
> >   Apache way soon. The age team is coaching the age-viewer developers to 
> > encourage future
> >   releases to comply with Apache guiding principles.
> >
> > The documentation link at incubator.apache.org/projects/age.html is 
> > corrected.
> >
> > Regarding project name search and approval:
> >   We have completed name search and approval. PPMC is actively checking 
> > Apache AGE brand
> >   use.
> >
> > The licensing issue regarding 0.6.0 has been resolved. We’re happy to 
> > announce Apache AGE 0.6.0 is officially out today.
> >
> > Thank you for your feedback and recognition that after 6 releases including 
> > 4 Apache releases, we have demonstrated that this community is able to run 
> > independently outside incubation.
> >
> > We look forward to a positive vote on graduation to a Top Level Project.
> >
> > Thank you
> > Eya
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On 2021/11/09 04:31:33 Eya Badal wrote:
> > > Hi AGE community and Mentors,
> > >
> > > Since entering incubation 18 months ago in April 2020 and with five
> > > versions of AGE released, and 0.6.0 imminent, it's fair to say the AGE
> > > community has demonstrated its ability to build software releases the
> > > 

Re: [VOTE] Accept SeaTunnel into the Apache Incubator

[Felix Cheung]

+1

On Fri, Dec 3, 2021 at 9:52 PM Xun Liu  wrote:

> +1 (binding) from me
>
> Best Regards,
> Xun Liu
>
> On Sat, Dec 4, 2021 at 11:43 AM 张铎(Duo Zhang) 
> wrote:
>
> > +1, binding
> >
> > Lidong Dai 于2021年12月4日 周六10:40写道：
> >
> > > +1 (binding)
> > >
> > > Best Regards
> > >
> > >
> > >
> > >
> > > On Sat, Dec 4, 2021 at 9:52 AM william-guo...@qq.com.INVALID
> > >  wrote:
> > >
> > > > +1 binding
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Apache Software Foundation Member, DolphinScheduler PMC
> > > > William Guo
> > > > guo...@apache.org
> > > >
> > > > From: Willem Jiang
> > > > Date: 2021-12-03 21:56
> > > > To: Incubator General
> > > > Subject: [VOTE] Accept SeaTunnel into the Apache Incubator
> > > > Hi all,
> > > >
> > > > Following up the [DISCUSS] thread on SeaTunnel [1] I would like to
> > call a
> > > > VOTE to accept into the Apache Incubator.
> > > >
> > > > Please cast your vote:
> > > >
> > > >   [ ] +1, bring  into the Incubator
> > > >   [ ] +0, I don't care either way
> > > >   [ ] -1, do not bring SeaTunnel into the Incubator, because...
> > > >
> > > > The vote will open at least for 72 hours and only votes from the
> > > > Incubator PMC are binding, but votes from everyone are welcome.
> > > >
> > > > Please check out the SeaTunnel Proposal from the incubator wiki[2].
> > > >
> > > > [1]https://lists.apache.org/thread/nvp0sxnl0b69wgylxsvmdshfd70om1gk
> > > > [2]
> > >
> https://cwiki.apache.org/confluence/display/INCUBATOR/SeaTunnelProposal
> > > >
> > > > Regards,
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Sedona 1.1.1-incubating-rc1

[Felix Cheung]

+1

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers

Note, these script should probably have the ASF header -
.github/workflows/scripts/install_r_deps.sh
.github/workflows/scripts/install_system_deps_for_r_build.sh
.github/workflows/scripts/prepare_sparklyr_sedona_test_env.sh

On Tue, Nov 23, 2021 at 12:18 AM Jia Yu  wrote:

> Thank you, Justin! I will then fix the notice.
>
> Folks, we need one more binding vote in order to pass. Could you please
> help us?
>
> Thanks,
> Jia
>
> On Mon, Nov 22, 2021 at 11:25 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > Changing my vote to +1 (binding)
> >
> > > 1. Sorry for the confusion on the download page. I just fixed Sedona's
> > > website. Now the download page is at an obvious place:
> > > https://sedona.apache.org/download/ <
> https://sedona.apache.org/download/
> > >
> >
> > Thanks for fixing up your download page. Look like al the links are
> > correct on that page as well.
> >
> > > 2. The reason why we put 2015 - 2021 in the NOTICE is because our
> project
> > > open-sourced in 2015 and joined the incubator in 2020. Do you think I
> > > should change it to 2020 - 2021?
> >
> > Well it wasn’t an ASF project before then and presumably someone else was
> > the copyright owner. Normal what happens is the donated code headers are
> > changed and the copyright notice in that header relocated to the NOTICE
> > file.
> >
> > > Since your -1 binding vote is mainly about the website and NOTICE
> instead
> > > of source code, do you think I should restart the voting process with a
> > new
> > > release candidate RC2?
> >
> > No there’s no need (so far) for an RC2 or to even to stop this vote
> thread.
> >
> > Kind Regards,
> > Justin
>

Re: [VOTE] Apache AGE (incubating) Release v0.6.0

[Felix Cheung]

As a reminder, when a vote is reset, it should have a new git tag and a new 
release share. git tag should increment from rc0, rc1, rc2 etc - optionally, 
this gives reviewers a way to see the changes/diffs and will help move the 
voting process along better.

ie.

https://github.com/apache/incubator-age/releases/tag/v0.6.0-rc1
https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0-rc1/

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers (except those from PostgreSQL project)


From: John Gemignani 
Sent: Monday, November 22, 2021 5:40:08 PM
To: dev@age.apache.org 
Subject: Re: [VOTE] Apache AGE (incubating) Release v0.6.0

+1,

   - Signature and hash - check.
   - DISCLAIMER - check.
   - LICENSE and NOTICE - check.
   - No unexpected binary files - check.
   - incubating in name - check.

John

On Mon, Nov 22, 2021 at 12:51 AM Muhammad Shoaib  wrote:

> +1,
>
>
> I confirm that I have checked the following and they look good to the best
> of my knowledge
>
>
>
>- Signature and hash fine
>- DISCLAIMER is fine
>- LICENSE and NOTICE are fine there is no WIP information there now.
>- No unexpected binary files
>- incubating in name
>
>
> On Sun, Nov 21, 2021 at 10:33 PM Josh Innis  wrote:
>
> > Dear Apache Community,
> >
> > Please vote on releasing the following candidate as Apache AGE version
> > 0.6.0.
> >
> > This release includes the updates to the NOTICE, removing the WIP
> > disclaimer
> > and adding the standard disclaimer, and changing the copyright header in
> > files
> > that are predominately Postgres source code.
> >
> > The vote is open now and until November 24th at 2:30 PM PST and passes if
> > a majority +1 votes are cast, with a minimum of 3 +1 votes.
> >
> > [ ] +1 Release this package as Apache AGE 0.6.0
> > [ ] -1 Do not release this package because ...
> >
> > To learn more about Apache AGE, please see http://age.apache.org/
> >
> > *Functionalities included and addressed in this release:*
> > - Add VLE SRF (Set Returning Function).
> > - Fix Vertex, Edge, and Path serialization bug (AGE2-307)
> > - Fix CREATE passback bug (AGE2-337).
> > - Fix CREATE transaction block bug (AGE2-345).
> > - Fix parallel build errors.
> > - Fix Travis CI compiler warnings.
> >
> > *
> > *The git tag to be discussed and voted upon:*
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> > *The git commit hash:*
> > commit 9786fc32d52c577cf67e9e89409246b9e7a3a063
> >
> > *The release files for 0.6.0, can be found at:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
> >
> > *The signatures, files, etc. can be found at:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/
> >
> > *Signatures used for AGE RCs can be found in this file:*
> > https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> >
> > *The fingerprint of key to sign release artifacts:*
> > 4D57 8595 934A 64F4 8DD9  B39C 7FAD 0CDD C278 09E8
> >
> > *For information about the contents of this release, see:*
> > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> >
> > Thank you for your time.
> > Josh Innis
> >
>
>
> --
>
> * Muhammad Shoaib, PhD*
>
> * Senior Research Engineer *
>
> *P* : +82-70-4800-3517   *F* : +82-70-8677-2552
> 401 Yangcheon-ro A/1201, Gangseo-gu, Seoul, 07528, Korea
>

RE: Re: Apache AGE (Incubating) - Community Graduation Vote

[Felix Cheung]

Great to hear.

I reviewed the maturity model.

1) do you have the breakdown on the PPMC membership on affiliation
(companies)? And PPMC growth?

2) Is there a list of community members (committer and PPMC? It was
mentioned in the maturity model item CS10 but not sure I see it on the
age.Apache.org site.

3) How is
https://github.com/apache/incubator-age-viewer released?

4) the current documentation link is broken on
incubator.apache.org/projects/age.html

5) have the project completed name search and approval? Is the PPMC
checking and defending Apache AGE brand use?

6) Lastly, let’s get 0.6.0 released with licensing resolved.



On 2021/11/14 03:39:21 Andrew Ko wrote:
> Agreeing with the comments made by Juan,
> I think it is imperative for the AGE community and mentors to come to a
> term that the license issue raised before (related to PostgreSQL and ASF)
> is resolved in the new 0.6.0 release.
>
>
> 2021년 11월 13일 (토) 오후 8:46, Juan Pan 님이 작성:
>
> > Hi,
> >
> >
> > 19 months is not a short phase. I am inclined to this graduation
proposal
> > and still well suggest firstly finishing the 0.6 release. The reason is
> > that there are only 3 Apache releases during the incubator, and some
issues
> > are suspending. 0.6 release will be a positive sign that this community
is
> > able to run independently.
> >
> >
> > Best
> > Trista
> >
> >
> >
> >
--
> > Juan Pan(Trista) Twitter: @tristaZero
> >
> >
> > On 11/9/2021 12:31，Eya Badal wrote：
> > Hi AGE community and Mentors,
> >
> > Since entering incubation 18 months ago in April 2020 and with five
> > versions of AGE released, and 0.6.0 imminent, it's fair to say the AGE
> > community has demonstrated its ability to build software releases the
> > Apache Way.
> >
> > We have prepared an assessment of the Apache AGE podling’s maturity,
meant
> > to help inform the decision (of the mentors, community, Incubator PMC,
and
> > ASF Board of Directors) to graduate it as a top-level Apache project. We
> > used the ASF project maturity model
> > <
> >
https://community.apache.org/apache-way/apache-project-maturity-model.html
> > >
> > to evaluate the Apache AGE project and assess itself as having no major
> > areas for concern. The assessment can be found at the Apache AGE website
> >  under the COMMUNITY menu.
> >
> > In addition to building and releasing software, the community has grown
the
> > Apache AGE project in other areas.
> >
> >
> > -
> >
> > There have been 64 unique contributors across the AGE and the subproject
> > AGE Viewer. These Contributors have raised >170 issues or pull requests.
> > -
> >
> > We have been addressing Github issues since the start but timeliness was
> > an issue. In April we created our internal SLA to categorise (label),
> > assign, and respond to issue and pull requests. Since April, 95% are
> > responded within 72 hours (80% of issues are responded to within 24
hrs).
> > -
> >
> > Contributions span more than 20 countries across the globe - Belarus,
> > Belgium, China, France, Germany, Ireland, Israel, Italy, Luxembourg,
> > Netherlands, Russia, South Korea, Thailand, UK, Ukraine, USA, and
Vietnam.
> > -
> >
> > We have amassed positive comments throughout and gathered >470 stars.
> > -
> >
> > We have committers from 4 different companies.
> >
> >
> > AGE mentors, what is your opinion on this?
> >
> > Do you agree that we are ready to graduate?
> >
> > Are there any remaining issues that we can improve on?
> >
> > If we can capture your issues of concern we can then work those issues
to
> > resolution.
> >
> > Your feedback would be very much appreciated!
> >
> > Regards,
> >
> > Eya
> >
>

Fwd: [MENTORS] Podling reports this month

[Felix Cheung]

-- Forwarded message -
From: Justin Mclean 
Date: Sat, Nov 6, 2021 at 4:48 PM
Subject: Re: [MENTORS] Podling reports this month
To: 


Hi,

The report can be found in the usual place:
https://cwiki.apache.org/confluence/display/INCUBATOR/November2021

Kind Regards,
Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache AGE (Incubating) 0.6.0 Release

[Felix Cheung]

I see Bitnine is the company that donated the project AGE to Apache, so the
header change seems to make sense?


On Sat, Oct 23, 2021 at 5:27 PM Justin Mclean 
wrote:

> Hi,
>
> Sorry but it’s -1 (binding) as there is no download page and the download
> links on the home page do not have hashes and signatures. This was brought
> up on this list recently and was asked to be corrected.  Also see other
> issues below.
>
> In the release:
> - incubating in name
> - signatures and hashes are fine
> - LICENSE is missing information from [1][2]
> - NOTICE is incorrect. There should be no need for "This product contains
> software PostgreSQL…” unless headers have been replace with permission or
> there was a software grant from PostgreSQL. This has previously been
> mentioned (in vote on 0.4.0 release). Also see issue with [1][2].
> - If seem unlikely that [1][2] should have ASF headers? In general the
> licensing of the file should stay as it is unless significant modifications
> have ben done. Looking at the history it seems if was originally "Copyright
> 2020 Bitnine Co., Ltd.” Why is this not mentioned in NOTICE? Was permission
> given to change the headers?
> - Probably similar issue with these file [3][4]
> - No unexpected binary files
> - unable to compile but assume that my setup.
> src/backend/catalog/ag_graph.c:67:15: error: assigning to 'Oid'
>   (aka 'unsigned int') from incompatible type 'void'
>
> Kind Regards,
> Justin
>
> 1. ./src/include/utils/agtype_parser.h
> 2. ./src/backend/utils/adt/agtype_parser.c
> 3. ./src/include/utils/agtype.h
> 4. ./src/backend/utils/adt/agtype.c
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Fwd: CRAN submission SparkR 3.2.0

[Felix Cheung]

-- Forwarded message -
From: Gregor Seyer 
Date: Wed, Oct 20, 2021 at 4:42 AM
Subject: Re: CRAN submission SparkR 3.2.0
To: Felix Cheung , CRAN <
cran-submissi...@r-project.org>


Thanks,

Please add \value to .Rd files regarding exported methods and explain
the functions results in the documentation. Please write about the
structure of the output (class) and also what the output means. (If a
function does not return a value, please document that too, e.g.
\value{No return value, called for side effects} or similar)
Missing Rd-tags in up to 102 .Rd files, e.g.:
  attach.Rd: \value
  avg.Rd: \value
  between.Rd: \value
  cache.Rd: \value
  cancelJobGroup.Rd: \value
  cast.Rd: \value
  ...

You have examples for unexported functions.
array_transform() in:
   hashCode.Rd
  Please either omit these examples or export the functions.

Warning: Unexecutable code in man/sparkR.session.Rd:
   sparkR.session(spark.master = "yarn", spark.submit.deployMode =
"client",:
Warning: Unexecutable code in man/write.stream.Rd:
   partitionBy:

Please do not modify the .GlobalEnv. This is not allowed by the CRAN
policies. e.g.: inst/profile/shell.R

Please do not modify the global environment (e.g. by using <<-) in your
functions. This is not allowed by the CRAN policies.  e.g.: R/utils.R


Additionally:
Have the issues why your package was archived been fixed?
Please explain this in the submission comments.


Please fix and resubmit.

Best,
Gregor Seyer

Am 19.10.21 um 19:48 schrieb CRAN submission:
> [This was generated from CRAN.R-project.org/submit.html]
>
> The following package was uploaded to CRAN:
> ===
>
> Package Information:
> Package: SparkR
> Version: 3.2.0
> Title: R Front End for 'Apache Spark'
> Author(s): Shivaram Venkataraman [aut], Xiangrui Meng [aut], Felix Cheung
>[aut, cre], The Apache Software Foundation [aut, cph]
> Maintainer: Felix Cheung 
> Depends: R (>= 3.5), methods
> Suggests: knitr, rmarkdown, markdown, testthat, e1071, survival, arrow
>(>= 1.0.0)
> Description: Provides an R Front end for 'Apache Spark'
><https://spark.apache.org>.
> License: Apache License (== 2.0)
>
>
> The maintainer confirms that he or she
> has read and agrees to the CRAN policies.
>
> =
>
> Original content of DESCRIPTION file:
>
> Package: SparkR
> Type: Package
> Version: 3.2.0
> Title: R Front End for 'Apache Spark'
> Description: Provides an R Front end for 'Apache Spark' <
https://spark.apache.org>.
> Authors@R: c(person("Shivaram", "Venkataraman", role = "aut",
>  email = "shiva...@cs.berkeley.edu"),
>   person("Xiangrui", "Meng", role = "aut",
>  email = "m...@databricks.com"),
>   person("Felix", "Cheung", role = c("aut", "cre"),
>  email = "felixche...@apache.org"),
>   person(family = "The Apache Software Foundation", role =
c("aut", "cph")))
> License: Apache License (== 2.0)
> URL: https://www.apache.org https://spark.apache.org
> BugReports: https://spark.apache.org/contributing.html
> SystemRequirements: Java (>= 8, < 12)
> Depends: R (>= 3.5), methods
> Suggests: knitr, rmarkdown, markdown, testthat, e1071, survival, arrow
>  (>= 1.0.0)
> Collate: 'schema.R' 'generics.R' 'jobj.R' 'column.R' 'group.R' 'RDD.R'
>  'pairRDD.R' 'DataFrame.R' 'SQLContext.R' 'WindowSpec.R'
>  'backend.R' 'broadcast.R' 'catalog.R' 'client.R' 'context.R'
>  'deserialize.R' 'functions.R' 'install.R' 'jvm.R'
>  'mllib_classification.R' 'mllib_clustering.R' 'mllib_fpm.R'
>  'mllib_recommendation.R' 'mllib_regression.R' 'mllib_stat.R'
>  'mllib_tree.R' 'mllib_utils.R' 'serialize.R' 'sparkR.R'
>  'stats.R' 'streaming.R' 'types.R' 'utils.R' 'window.R'
> RoxygenNote: 7.1.1
> VignetteBuilder: knitr
> NeedsCompilation: no
> Encoding: UTF-8
> Packaged: 2021-10-06 13:15:21 UTC; spark-rm
> Author: Shivaram Venkataraman [aut],
>Xiangrui Meng [aut],
>Felix Cheung [aut, cre],
>The Apache Software Foundation [aut, cph]
> Maintainer: Felix Cheung 
>

RE: Re: Re: Re: [VOTE] Release Apache AGE (incubating) version 0.6.0

[Felix Cheung]

In such case, the inclusion of the license is required.

Also, ideally, the 3rd party source code should be retained as separate
source files so we could keep the license header on each file. If they are
code snippet, then it is a bit of a grey area and we should attribute the
source in license (a practice I've seen in other projects)

See
https://www.apache.org/legal/src-headers.html#3party
https://www.apache.org/legal/resolved.html#category-a
"
4. Minor modifications/additions to third-party source files should
typically be licensed under the same terms as the rest of the third-party
source for convenience.

5. The project's PMC should deal with major modifications/additions to
third-party source files on a case-by-case basis."




On 2021/10/13 20:44:15 Josh Innis wrote:
> We resigned the files using an @apache.org account. There is source code
> from Postgres in AGE. There are no files but there are some snippets.
> We create value for our clients by connecting the world's data.
> Josh Innis Software Engineer
> Core R Team
> *P*: (831)278-0327
> 3945 Freedom Circle #260, Santa Clara, CA 95054
> <
https://www.google.com/maps/place/3945+Freedom+Cir+%23260,+Santa+Clara,+CA+95054/
>
> bitnine.net
>
>
> On Sun, Oct 10, 2021 at 5:28 PM Felix Cheung  wrote:
>
> > There bundle also applies to the source release. However, if you are
> > certain none of the source code file or snippet is from the Postgres
code
> > base, then, correct, you don’t need to include Postgres license info.
> >
> > You might want to amend the license and notice, and re-sign with a key
with
> > @apache.org address from my comments earlier.
> >
> > I’m not sure if it will be flagged at IPMC, but it is best since you
have
> > changed the disclaimer in this release.
> >
> >
> > On 2021/10/05 16:54:29 Josh Innis wrote:
> > > Hi Felix,
> > >
> > > We do not have any binary code from Postgres. The key phrase I saw
was "
> > > LICENSE and NOTICE need only be modified to accommodate them *only if
> > their
> > > bits are bundled*." The Apache AGE repository does not have any binary
> > > source files in it. After reading the links you sent, it appears we do
> > not
> > > have to keep the Postgres license info in NOTICE and LICENSE.
> > >
> > >
> > > On Sun, Oct 3, 2021 at 12:11 PM Felix Cheung  wrote:
> > >
> > > > Checking this release, not a blocker but a question:
> > > >
> > > >
> > > > - incubating in name
> > > >
> > > > - signature and hash fine
> > > >
> > > > KEYS file - you should try to sign files with @apache.org issuer
email
> > > >
> > > > - DISCLAIMER is fine
> > > >
> > > > - LICENSE and NOTICE
> > > >
> > > > The PostgreSQL license - is it because of code file taken from the
> > project
> > > > (and then is there license header for these files?)
> > > >
> > > > If it is not coming from code file, then is it because of a binary
> > > > dependency? If so, it should be in a separate LICENSE-binary file
like
> > > > https://github.com/apache/iotdb/blob/master/LICENSE-binary
> > > >
> > > > And potentially the license should be separately stored like
> > > > https://github.com/apache/iotdb/tree/master/licenses
> > > >
> > > > more info:
> > > > https://infra.apache.org/licensing-howto.html#bundled-vs-non-bundled
> > > >
> > > > - No unexpected binary files
> > > > - All source files have ASF headers
> > > >
> > > >
> > > >
> > > > On 2021/09/24 11:34:24 Kevin Ratnasekera wrote:
> > > > > +1
> > > > >
> > > > > I checked the following.
> > > > >
> > > > > - Incubating in name.
> > > > >
> > > > > - PGP Signatures.
> > > > >
> > > > > - SHA512 Checksums.
> > > > >
> > > > > - DISCLAIMER exists.
> > > > >
> > > > > - LICENSE and NOTICE are fine.
> > > > >
> > > > > - ASF headers on source files.
> > > > >
> > > > >
> > > > >
> > > > > Regards
> > > > >
> > > > > Kevin
> > > > >
> > > > > On Tue, Sep 21, 2021 at 8:52 PM Eya Badal 
wrote:
> > > > >
> > > > > > +1, I checked the follwoing:
> > > > &g

RE: Re: Re: [VOTE] Release Apache AGE (incubating) version 0.6.0

[Felix Cheung]

There bundle also applies to the source release. However, if you are
certain none of the source code file or snippet is from the Postgres code
base, then, correct, you don’t need to include Postgres license info.

You might want to amend the license and notice, and re-sign with a key with
@apache.org address from my comments earlier.

I’m not sure if it will be flagged at IPMC, but it is best since you have
changed the disclaimer in this release.


On 2021/10/05 16:54:29 Josh Innis wrote:
> Hi Felix,
>
> We do not have any binary code from Postgres. The key phrase I saw was "
> LICENSE and NOTICE need only be modified to accommodate them *only if
their
> bits are bundled*." The Apache AGE repository does not have any binary
> source files in it. After reading the links you sent, it appears we do not
> have to keep the Postgres license info in NOTICE and LICENSE.
>
>
> On Sun, Oct 3, 2021 at 12:11 PM Felix Cheung  wrote:
>
> > Checking this release, not a blocker but a question:
> >
> >
> > - incubating in name
> >
> > - signature and hash fine
> >
> > KEYS file - you should try to sign files with @apache.org issuer email
> >
> > - DISCLAIMER is fine
> >
> > - LICENSE and NOTICE
> >
> > The PostgreSQL license - is it because of code file taken from the
project
> > (and then is there license header for these files?)
> >
> > If it is not coming from code file, then is it because of a binary
> > dependency? If so, it should be in a separate LICENSE-binary file like
> > https://github.com/apache/iotdb/blob/master/LICENSE-binary
> >
> > And potentially the license should be separately stored like
> > https://github.com/apache/iotdb/tree/master/licenses
> >
> > more info:
> > https://infra.apache.org/licensing-howto.html#bundled-vs-non-bundled
> >
> > - No unexpected binary files
> > - All source files have ASF headers
> >
> >
> >
> > On 2021/09/24 11:34:24 Kevin Ratnasekera wrote:
> > > +1
> > >
> > > I checked the following.
> > >
> > > - Incubating in name.
> > >
> > > - PGP Signatures.
> > >
> > > - SHA512 Checksums.
> > >
> > > - DISCLAIMER exists.
> > >
> > > - LICENSE and NOTICE are fine.
> > >
> > > - ASF headers on source files.
> > >
> > >
> > >
> > > Regards
> > >
> > > Kevin
> > >
> > > On Tue, Sep 21, 2021 at 8:52 PM Eya Badal  wrote:
> > >
> > > > +1, I checked the follwoing:
> > > >
> > > >
> > > > x] Download links are valid.
> > > > [x] Checksums and PGP signatures are valid.
> > > > [x] LICENSE, NOTICE and DISCLAIMER files are correct.
> > > > [x] All files have license headers if necessary.
> > > >
> > > > Best,
> > > > Eya Badal Abdisho
> > > >
> > > > On 2021/09/15 16:11:47, Josh Innis  wrote:
> > > > > Dear Apache Community,
> > > > >
> > > > >
> > > > > Please vote on releasing the following candidate as Apache AGE
> > version
> > > > 0.6.0
> > > > >
> > > > >
> > > > > The vote is open now and until September 18th at 10:30 AM PST and
> > passes
> > > > if
> > > > > a majority +1 votes are cast, with a minimum of 3 +1 votes.
> > > > >
> > > > >
> > > > > [ ] +1 Release this package as Apache AGE 0.6.0
> > > > >
> > > > > [ ] -1 Do not release this package because ...
> > > > >
> > > > >
> > > > > To learn more about Apache AGE, please see http://age.apache.org/
> > > > >
> > > > >
> > > > > *Functionalities included and addressed in this release:*
> > > > >
> > > > > - Add VLE SRF (Set Returning Function).
> > > > >
> > > > > - Fix Vertex, Edge, and Path serialization bug (AGE2-307)
> > > > >
> > > > > - Fix CREATE passback bug (AGE2-337).
> > > > >
> > > > > - Fix CREATE transaction block bug (AGE2-345).
> > > > >
> > > > > - Fix parallel build errors.
> > > > >
> > > > > - Fix Travis CI compiler warnings.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > *

Re: [VOTE] Release Apache Sedona 1.1.0-incubating-rc1

[Felix Cheung]

+1

Because of WIP DISCLAIMER

On Sun, Oct 3, 2021 at 12:02 PM Felix Cheung  wrote:

> - incubating in name
> - signature and hash fine
> - DISCLAIMER is fine
> - LICENSE and NOTICE are fine
> - No unexpected binary files
>
> - source files for ASF headers
>
> is there a reason this file doesn't have a header?
> ./sql/src/main/scala/org/apache/spark/sql/sedona_sql/io/ImageOptions.scala
>
>
> On Sun, Oct 3, 2021 at 12:17 AM Jia Yu  wrote:
>
>> Hi all,
>>
>> This is a call for vote on Apache Sedona 1.1.0-incubating-rc1. This RC has
>> passed the vote in the Sedona community.
>>
>> The result thread:
>>
>> https://lists.apache.org/thread.html/rb46d58958fd21b5af6f32486b08491e3d018bc1128d6e0819b663bdd%40%3Cdev.sedona.apache.org%3E
>>
>> Please refer to the changes listed at the bottom of this email.
>>
>> Release notes:
>>
>> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/docs/download/release-notes.md
>>
>> Build instructions:
>>
>> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/docs/download/compile.md
>>
>> GitHub tag:
>>
>> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.1.0-incubating-rc1
>>
>> GPG public key to verify the Release:
>> https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
>>
>> Source code and binaries:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.1.0-incubating-rc1/
>>
>> The vote will be open for at least 72 hours or until a majority of at
>> least
>> 3 "approve" PMC votes are cast
>>
>> Please vote accordingly:
>>
>> [ ] +1 approve
>>
>> [ ] +0 no opinion
>>
>> [ ] -1 disapprove with the reason
>>
>> Checklist for reference (because of DISCLAIMER-WIP, other checklist items
>> are not blockers):
>>
>> [ ] Download links are valid.
>>
>> [ ] Checksums and PGP signatures are valid.
>>
>> [ ] DISCLAIMER is included.
>>
>> [ ] Source code artifacts have correct names matching the current release.
>>
>> For a detailed checklist  please refer to:
>>
>> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>>
>> Regards,
>> Jia Yu
>>
>> 
>> Changes according to the comments on the previous release
>> Original comment (Permalink from https://lists.apache.org/list.html):
>>
>> https://lists.apache.org/thread.html/rcc3252c2afda7761afb205eb00a2f8a5d71256fc7f4d631efc879629%40%3Cgeneral.incubator.apache.org%3E
>>
>> 1. Fix the header issue in the BSD license
>> This has been fixed.
>>
>> [1]
>>
>> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/zeppelin/index.js
>> [2]
>>
>> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/licenses/LICENSE-zeppelin-helium-plugin
>>
>> 2. Add the license for scalastyle_config.xml
>>
>> [3]
>>
>> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/LICENSE#L210
>>
>> 3. Replace NASA HDF data with some alternatives to avoid the legal issue
>>
>> All NASA data has been removed from the repo.
>>
>

RE: Re: [VOTE] Release Apache AGE (incubating) version 0.6.0

[Felix Cheung]

Checking this release, not a blocker but a question:


- incubating in name

- signature and hash fine

KEYS file - you should try to sign files with @apache.org issuer email

- DISCLAIMER is fine

- LICENSE and NOTICE

The PostgreSQL license - is it because of code file taken from the project
(and then is there license header for these files?)

If it is not coming from code file, then is it because of a binary
dependency? If so, it should be in a separate LICENSE-binary file like
https://github.com/apache/iotdb/blob/master/LICENSE-binary

And potentially the license should be separately stored like
https://github.com/apache/iotdb/tree/master/licenses

more info:
https://infra.apache.org/licensing-howto.html#bundled-vs-non-bundled

- No unexpected binary files
- All source files have ASF headers



On 2021/09/24 11:34:24 Kevin Ratnasekera wrote:
> +1
>
> I checked the following.
>
> - Incubating in name.
>
> - PGP Signatures.
>
> - SHA512 Checksums.
>
> - DISCLAIMER exists.
>
> - LICENSE and NOTICE are fine.
>
> - ASF headers on source files.
>
>
>
> Regards
>
> Kevin
>
> On Tue, Sep 21, 2021 at 8:52 PM Eya Badal  wrote:
>
> > +1, I checked the follwoing:
> >
> >
> > x] Download links are valid.
> > [x] Checksums and PGP signatures are valid.
> > [x] LICENSE, NOTICE and DISCLAIMER files are correct.
> > [x] All files have license headers if necessary.
> >
> > Best,
> > Eya Badal Abdisho
> >
> > On 2021/09/15 16:11:47, Josh Innis  wrote:
> > > Dear Apache Community,
> > >
> > >
> > > Please vote on releasing the following candidate as Apache AGE version
> > 0.6.0
> > >
> > >
> > > The vote is open now and until September 18th at 10:30 AM PST and
passes
> > if
> > > a majority +1 votes are cast, with a minimum of 3 +1 votes.
> > >
> > >
> > > [ ] +1 Release this package as Apache AGE 0.6.0
> > >
> > > [ ] -1 Do not release this package because ...
> > >
> > >
> > > To learn more about Apache AGE, please see http://age.apache.org/
> > >
> > >
> > > *Functionalities included and addressed in this release:*
> > >
> > > - Add VLE SRF (Set Returning Function).
> > >
> > > - Fix Vertex, Edge, and Path serialization bug (AGE2-307)
> > >
> > > - Fix CREATE passback bug (AGE2-337).
> > >
> > > - Fix CREATE transaction block bug (AGE2-345).
> > >
> > > - Fix parallel build errors.
> > >
> > > - Fix Travis CI compiler warnings.
> > >
> > >
> > >
> > >
> > >
> > > *
> > >
> > >
> > >
> > > *The git tag to be discussed and voted upon:*
> > >
> > > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> > >
> > >
> > >
> > > *The git commit hash:*
> > >
> > > commit 3681c90da68353507001db89eb429755d34857f7
> > >
> > >
> > >
> > > *The release files for 0.6.0, can be found at:*
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/age/0.6.0.rc0/
> > >
> > >
> > >
> > > *The signatures, files, etc. can be found at:*
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/age/
> > >
> > >
> > >
> > > *Signatures used for AGE RCs can be found in this file:*
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
> > >
> > >
> > >
> > > *The fingerprint of key to sign release artifacts:*
> > >
> > > 2245 1CFA 0521 1612 A4EA 9F05 6EF7 BD28 B870 8B05
> > >
> > >
> > >
> > > *For information about the contents of this release, see:*
> > >
> > > https://github.com/apache/incubator-age/releases/tag/v0.6.0
> > >
> > >
> > >
> > > Thank you for your time.
> > >
> > >
> > >
> > > Best regards,
> > >
> > > Josh Innis
> > > We create value for our clients by connecting the world's data.
> > > Josh Innis Software Engineer
> > > Core R Team
> > > *P*: (831)278-0327
> > > 3945 Freedom Circle #260, Santa Clara, CA 95054
> > > <
> >
https://www.google.com/maps/place/3945+Freedom+Cir+%23260,+Santa+Clara,+CA+95054/
> > >
> > > bitnine.net
> > >
> >
>

Re: [VOTE] Release Apache Sedona 1.1.0-incubating-rc1

[Felix Cheung]

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files

- source files for ASF headers

is there a reason this file doesn't have a header?
./sql/src/main/scala/org/apache/spark/sql/sedona_sql/io/ImageOptions.scala


On Sun, Oct 3, 2021 at 12:17 AM Jia Yu  wrote:

> Hi all,
>
> This is a call for vote on Apache Sedona 1.1.0-incubating-rc1. This RC has
> passed the vote in the Sedona community.
>
> The result thread:
>
> https://lists.apache.org/thread.html/rb46d58958fd21b5af6f32486b08491e3d018bc1128d6e0819b663bdd%40%3Cdev.sedona.apache.org%3E
>
> Please refer to the changes listed at the bottom of this email.
>
> Release notes:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/docs/download/release-notes.md
>
> Build instructions:
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/docs/download/compile.md
>
> GitHub tag:
>
> https://github.com/apache/incubator-sedona/releases/tag/sedona-1.1.0-incubating-rc1
>
> GPG public key to verify the Release:
> https://dist.apache.org/repos/dist/dev/incubator/sedona/KEYS
>
> Source code and binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.1.0-incubating-rc1/
>
> The vote will be open for at least 72 hours or until a majority of at least
> 3 "approve" PMC votes are cast
>
> Please vote accordingly:
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
> Checklist for reference (because of DISCLAIMER-WIP, other checklist items
> are not blockers):
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] DISCLAIMER is included.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> For a detailed checklist  please refer to:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Regards,
> Jia Yu
>
> 
> Changes according to the comments on the previous release
> Original comment (Permalink from https://lists.apache.org/list.html):
>
> https://lists.apache.org/thread.html/rcc3252c2afda7761afb205eb00a2f8a5d71256fc7f4d631efc879629%40%3Cgeneral.incubator.apache.org%3E
>
> 1. Fix the header issue in the BSD license
> This has been fixed.
>
> [1]
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/zeppelin/index.js
> [2]
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/licenses/LICENSE-zeppelin-helium-plugin
>
> 2. Add the license for scalastyle_config.xml
>
> [3]
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.1.0-incubating-rc1/LICENSE#L210
>
> 3. Replace NASA HDF data with some alternatives to avoid the legal issue
>
> All NASA data has been removed from the repo.
>

Incubator disclaimer missing from podling websites

[Felix Cheung]

Hello,

Please look into the website


-- Forwarded message -
From: sebb 
Date: Fri, Sep 17, 2021 at 5:35 AM
Subject: Incubator disclaimer missing from several podling websites
To: general 


As the subject says: the disclaimer is missing from the following websites:

Age
BlueMarlin (no website at all)
Doris - does not work at all without JavaScript
Inlong - does not work without Javascript
Kyuubi
Liminal
Linkis - no website yet
Nemo

Yunikorn has some incorrect text: ", sponsored by the name of Apache
TLP sponsor."

Milagro looks OK in a browser, but uses a redirect that does not work
for automated checkers.
Given that the redirect is unconditional, this would be better done by
the server, e.g. through .htaccess.

It should be present on all pages.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Download pages and links to podling releases

[Felix Cheung]

Hello,

Could we look into the download page please?


-- Forwarded message -
From: Justin Mclean 
Date: Wed, Sep 15, 2021 at 6:18 PM
Subject: [MENTORS] Download pages and links to podling releases
To: 


Hi,

Can mentors please make themselves familiar with the requirements for
download pages and links [1] as we seem to have a number of projects that
are not providing downloads in the required manner.

In general:
- Please use https://www.apache.org/dyn/closer.lua <
https://www.apache.org/dyn/closer.lua> for releases
- Please use https://downloads.apache.org/  for hashes and signatures


Form a quick check these project don’t seem to have an obvious download
page:
Age
Annotator
BlueMarlin
Liminal
Linkis
Marvin
SDAP
Sedona
Wayang

Now in some cases these are newish projects and they haven’t made a
release, however others on that list have made releases and really should
have a download page. If they do have a download page please provide the
URL.

These projects look to have issue with the download links themselves:
BRPC - https://brpc.apache.org/download/ 
Crail - http://crail.apache.org/download/ 
DataLab - http://datalab.apache.org/#download <
http://datalab.apache.org/#download>
Doris - http://doris.apache.org/master/en/downloads/downloads.html <
http://doris.apache.org/master/en/downloads/downloads.html>
Heron - https://heron.apache.org/download 
Hivemall - https://hivemall.apache.org/download.html <
https://hivemall.apache.org/download.html>
Kyuubi - https://kyuubi.apache.org/releases.html <
https://kyuubi.apache.org/releases.html>
Livy - https://livy.apache.org/download/ 
Milagro - https://milagro.apache.org/docs/downloads/ <
https://milagro.apache.org/docs/downloads/>
Nemo - https://nemo.apache.org/pages/downloads/ <
https://nemo.apache.org/pages/downloads/>
NLPCraft - https://nlpcraft.apache.org/download.html <
https://nlpcraft.apache.org/download.html>
NuttX - https://nuttx.apache.org/download/ <
https://nuttx.apache.org/download/>
PageSpeed - https://pagespeed.apache.org/doc/download <
https://pagespeed.apache.org/doc/download>
PonyMail - https://ponymail.apache.org/downloads.html <
https://ponymail.apache.org/downloads.html>
Spot - https://spot.apache.org/download/ 
Teaclave - https://teaclave.apache.org/download/ <
https://teaclave.apache.org/download/>
Training - https://training.apache.org/downloads.html <
https://training.apache.org/downloads.html>

This list was autogenerated by a script and may have got some things wrong.
If you need details on a particular project and it’s links please check
here. [1]

Thanks,
Justin

1. https://gist.github.com/justinmclean/60a824a2f3fe97e519ed25d7c39a47ed


1. https://infra.apache.org/release-distribution.html#download-links

Download pages and links to podling releases

[Felix Cheung]

Could folks please look into the download link?


-- Forwarded message -
From: Justin Mclean 
Date: Wed, Sep 15, 2021 at 6:18 PM
Subject: [MENTORS] Download pages and links to podling releases
To: 


Hi,

Can mentors please make themselves familiar with the requirements for
download pages and links [1] as we seem to have a number of projects that
are not providing downloads in the required manner.

In general:
- Please use https://www.apache.org/dyn/closer.lua <
https://www.apache.org/dyn/closer.lua> for releases
- Please use https://downloads.apache.org/  for hashes and signatures


Form a quick check these project don’t seem to have an obvious download
page:
Age
Annotator
BlueMarlin
Liminal
Linkis
Marvin
SDAP
Sedona
Wayang

Now in some cases these are newish projects and they haven’t made a
release, however others on that list have made releases and really should
have a download page. If they do have a download page please provide the
URL.

These projects look to have issue with the download links themselves:
BRPC - https://brpc.apache.org/download/ 
Crail - http://crail.apache.org/download/ 
DataLab - http://datalab.apache.org/#download <
http://datalab.apache.org/#download>
Doris - http://doris.apache.org/master/en/downloads/downloads.html <
http://doris.apache.org/master/en/downloads/downloads.html>
Heron - https://heron.apache.org/download 
Hivemall - https://hivemall.apache.org/download.html <
https://hivemall.apache.org/download.html>
Kyuubi - https://kyuubi.apache.org/releases.html <
https://kyuubi.apache.org/releases.html>
Livy - https://livy.apache.org/download/ 
Milagro - https://milagro.apache.org/docs/downloads/ <
https://milagro.apache.org/docs/downloads/>
Nemo - https://nemo.apache.org/pages/downloads/ <
https://nemo.apache.org/pages/downloads/>
NLPCraft - https://nlpcraft.apache.org/download.html <
https://nlpcraft.apache.org/download.html>
NuttX - https://nuttx.apache.org/download/ <
https://nuttx.apache.org/download/>
PageSpeed - https://pagespeed.apache.org/doc/download <
https://pagespeed.apache.org/doc/download>
PonyMail - https://ponymail.apache.org/downloads.html <
https://ponymail.apache.org/downloads.html>
Spot - https://spot.apache.org/download/ 
Teaclave - https://teaclave.apache.org/download/ <
https://teaclave.apache.org/download/>
Training - https://training.apache.org/downloads.html <
https://training.apache.org/downloads.html>

This list was autogenerated by a script and may have got some things wrong.
If you need details on a particular project and it’s links please check
here. [1]

Thanks,
Justin

1. https://gist.github.com/justinmclean/60a824a2f3fe97e519ed25d7c39a47ed


1. https://infra.apache.org/release-distribution.html#download-links

Re: CRAN package SparkR

[Felix Cheung]

I think a few lines to add the prompt might be enough. This checks for
interactive()

https://github.com/apache/spark/blob/c6a2021fec5bab9069fbfba33f75d4415ea76e99/R/pkg/R/sparkR.R#L658


On Tue, Aug 31, 2021 at 5:55 PM Hyukjin Kwon  wrote:

> Oh I missed this. Yes, can we simply get the user' confirmation when we
> install.spark?
> IIRC, the auto installation is only triggered by interactive shell so
> getting user's confirmation should be fine.
>
> 2021년 6월 18일 (금) 오전 2:54, Felix Cheung 님이 작성:
>
>> Any suggestion or comment on this? They are going to remove the package
>> by 6-28
>>
>> Seems to me if we have a switch to opt in to install (and not by default
>> on), or prompt the user in interactive session, should be good as user
>> confirmation.
>>
>>
>>
>> On Sun, Jun 13, 2021 at 11:25 PM Felix Cheung 
>> wrote:
>>
>>> It looks like they would not allow caching the Spark
>>> Distribution.
>>>
>>> I’m not sure what can be done about this.
>>>
>>> If I recall, the package should remove this during test. Or maybe
>>> spark.install() ie optional (hence getting user confirmation?)
>>>
>>>
>>> -- Forwarded message -
>>> Date: Sun, Jun 13, 2021 at 10:19 PM
>>> Subject: CRAN package SparkR
>>> To: Felix Cheung 
>>> CC: 
>>>
>>>
>>> Dear maintainer,
>>>
>>> Checking this apparently creates the default directory as per
>>>
>>> #' @param localDir a local directory where Spark is installed. The
>>> directory con
>>> tains
>>> #' version-specific folders of Spark packages. Default
>>> is path t
>>> o
>>> #' the cache directory:
>>> #' \itemize{
>>> #'   \item Mac OS X: \file{~/Library/Caches/spark}
>>> #'   \item Unix: \env{$XDG_CACHE_HOME} if defined,
>>> otherwise \file{~/.cache/spark}
>>> #'   \item Windows:
>>> \file{\%LOCALAPPDATA\%\\Apache\\Spark\\Cache}.
>>> #' }
>>>
>>> However, the CRAN Policy says
>>>
>>>   - Packages should not write in the user’s home filespace (including
>>> clipboards), nor anywhere else on the file system apart from the R
>>> session’s temporary directory (or during installation in the
>>> location pointed to by TMPDIR: and such usage should be cleaned
>>> up). Installing into the system’s R installation (e.g., scripts to
>>> its bin directory) is not allowed.
>>>
>>> Limited exceptions may be allowed in interactive sessions if the
>>> package obtains confirmation from the user.
>>>
>>> For R version 4.0 or later (hence a version dependency is required
>>> or only conditional use is possible), packages may store
>>> user-specific data, configuration and cache files in their
>>> respective user directories obtained from tools::R_user_dir(),
>>> provided that by default sizes are kept as small as possible and the
>>> contents are actively managed (including removing outdated
>>> material).
>>>
>>> Can you pls fix as necessary?
>>>
>>> Please fix before 2021-06-28 to safely retain your package on CRAN.
>>>
>>> Best
>>> -k
>>>
>>

Re: [MENTORS] Report timeline for August

[Felix Cheung]

I’ve updated it and the podling project page.


On Wed, Aug 4, 2021 at 12:00 PM Dave Fisher  wrote:

> Hi Justin,
>
> Pinot graduated so it seems you will need to remove it from the report.
>
> No one has updated podlings.xml to indicate the graduation.
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content
>
> podlings.xml:
>
>  sponsor="Incubator" startdate="2018-10-17">
> Pinot is a distributed columnar storage engine that
> can ingest data in real-time and serve analytical queries at low
> latency.
> 
> Olivier Lamy
> 
> Kishore Gopalakrishna
> Jim Jagielski
> Olivier Lamy
> Felix Cheung
> 
> 
>
> Regards,
> Dave
>
> > On Jul 31, 2021, at 9:22 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > First off apologies for not sorting out the reports last month, as a
> result of this projects that were expected to report last month will need
> to report this month. DataLab, InLong and YuniKorn’s reports from last
> month have been copied over to this month, you can leave them as they are
> if you want to update them, but don’t forget to have your mentors sign them
> off.
> >
> > You can submit your reports in the usual place:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/August2021
> >
> > Report timeline for August
> >
> > Wed August 04 Podling reports due by end of day
> > Sun August 08 Shepherd reviews due by end of day
> > Sun August 08 Summary due by end of day
> > Tue August 10 Mentor signoff due by end of day
> > Wed August 11 Report submitted to Board
> > Wed August 18 Board meeting
> >
> > Expected to report are:
> > Annotator
> > BlueMarlin
> > DataLab
> > Doris
> > EventMesh
> > Flagon
> > Heron
> > InLong
> > Liminal
> > Livy
> > Milagro
> > MXNet
> > NLPCraft
> > Nuttx
> > PageSpeed
> > Pegasus
> > Pinot
> > Pony Mail
> > Sdap
> > Sedona
> > Shenyu
> > Teaclave
> > Toree
> > Training
> > Tuweni
> > Yunikorn
> >
> > Kind Regards,
> > Justin
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0 (RC2)

[Felix Cheung]

+1
I checked that issues from RC1 are fixed


On Fri, Aug 6, 2021 at 6:43 AM Julia Kinga Marton
 wrote:

> Hello IPMC
>
> The Apache YuniKorn community has voted and approved the release of Apache
> YuniKorn (incubating) 0.11.0 (RC2). We now kindly request the IPMC members
> review
> and vote for this release.
>
> YuniKorn is a standalone, universal resource scheduler that can support
> both long-running and batch workloads. The current release provides some
> gang-scheduling improvements, REST API extensions,UI usability
> enhancements, license improvements etc.
>
> YuniKorn community vote thread:
>
> https://lists.apache.org/thread.html/r97f089bc29e28a991fc3c882fc47014ca3ef77536d8c976f1f4a3573%40%3Cdev.yunikorn.apache.org%3E
>
> Vote result thread:
>
> https://lists.apache.org/thread.html/r2d45645f738608b37449f2e3be72c3ffa9c9405c4d65f36013d72305%40%3Cdev.yunikorn.apache.org%3E
>
> Issues included in this release:
> https://issues.apache.org/jira/projects/YUNIKORN/versions/12350025
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/yunikorn/0.11/
>
> This release has been signed with a PGP available
> here:https://dist.apache.org/repos/dist/dev/incubator/yunikorn/KEYS
>
> Git tag for the release:
>   - https://github.com/apache/incubator-yunikorn-core/tree/v0.11.0
>   - https://github.com/apache/incubator-yunikorn-k8shim/tree/v0.11.0
>   -
>
> https://github.com/apache/incubator-yunikorn-scheduler-interface/tree/v0.11.0
>   - https://github.com/apache/incubator-yunikorn-web/tree/v0.11.0
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 Approve the release of Apache YuniKorn (Incubating) 0.11.0
> [ ] +0
> [ ] -1 Do not approve (please specify the reason)
>
> Thanks,
> Kinga Marton
> Apache YuniKorn (Incubating)
>

Re: [VOTE] Release Apache AGE (incubating) 0.5.0

[Felix Cheung]

Agreed, these were called out in our dev@ vote

https://lists.apache.org/thread.html/r0f291fd923bd0217da1935811b4276699aac28715c1936d713e99002%40%3Cdev.age.apache.org%3E


On Fri, Jul 30, 2021 at 4:03 PM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding) but only because of WIP disclaimer. Normally I would vote -1
> due to compiled code in the source release [1]
>
> I checked:
> - incubating in name
> - signatures and hashes exist
> - disclaimer exists
> - LICENSE is missing [2][3]
> - contains unexpected binary file [1]
> - A large number of source files under [4] are missing ASF headers
>
> Please read [5] and follow the instruction there before the next release.
>
> Kind Regards,
> Justin
>
> 1. ./drivers/jdbc/gradle/wrapper/gradle-wrapper.jar
> 2. ./drivers/jdbc/gradlew
> 3. ./drivers/jdbc/gradlew.bat
> 4. ./drivers/jdbc/lib/src/main/java/org/apache/age/jdbc/
> 5. https://issues.apache.org/jira/browse/LEGAL-469
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache YuniKorn (Incubating) 0.11.0

[Felix Cheung]

Similar questions from me

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- No unexpected binary files

- LICENSE and NOTICE
the ./web component is in the release but I don't see its dependencies
(even as MIT licensed) listed?
Is anything bundled in there?


- these source files do not have ASF headers
./k8shim/test/e2e/predicates/predicates_suite_test.go
./k8shim/test/e2e/predicates/predicates_test.go
./core/pkg/scheduler/mock_plugin_test.go

the project has the normal disclaimer, so I'd think issues with LICENSE and
ASF header applies.
https://incubator.apache.org/guides/releasemanagement.html#choice_of_disclaimers


On Fri, Jul 30, 2021 at 2:31 AM Wilfred Spiegelenburg
 wrote:

> We are not using any of the polyfills except for the one that is mandatory
> (zone.js) which is part of the angular framework.
> The angular framework is not part of the source tar. The zone.js file is
> also not part of the source tar.
>
> The polyfills.ts file just defines that it will be imported when you build
> the app.
> After cleanup the polyfills.ts file would be a license header and 1 import
> statement.
>
> Is that acceptable?
>
> Wilfred
>
> > On 30 Jul 2021, at 18:55, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> >> The base settings are code generated. The software that generates these
> base setting is angular. It shows up as a MIT license [1].
> >> The file content after the generation is part of the created project
> which then gets customised.
> >
> >
> > You might want to double check that. A quick glance that this page [1]
> mentions polyfills that are either public domain, MIT or Apache licensed.
> Obviously all of these licenses are compatible but it would be good to know
> which it is.
> >
> > Kind Regards,
> > Justin
> >
> > 1. https://angular.io/guide/browser-support
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> Wilfred Spiegelenburg
> Staff Software Engineer
>  
>

Re: Release manager for Apache Sedona 1.1.0

[Felix Cheung]

Btw some projects have scripts that automate most of the steps there. It
will be worthwhile look into those.


On Tue, Jul 27, 2021 at 3:53 PM Jia Yu  wrote:

> Hi Sedona PMC members,
>
> We are planning to release Apache Sedona 1.1.0 as soon as possible. For
> this release, I think we should find another release manager to get
> familiar with the release process.
>
> To be honest, the entire process is not very easy:
> https://sedona.apache.org/download/publish/
>
> Do any of you want to be in charge of this particular release?
>
> Thanks,
> Jia
>

Re: [VOTE] Release Apache AGE (incubating) version 0.5.0

[Felix Cheung]

+1

Though it will be great to fix soon:


  *incubating in name

- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files

- Check: All source files have ASF headers
about 20 source files for tests do not have the Apache header.
/drivers/jdbc/lib/src/test/java/org/apache/age/jdbc/

what is the source of this jar?
/drivers/jdbc/gradle/wrapper/gradle-wrapper.jar


From: Dehowe Feng 
Sent: Friday, July 23, 2021 10:41:28 AM
To: dev@age.apache.org 
Subject: Re: [VOTE] Release Apache AGE (incubating) version 0.5.0

Hey Eya,

I can vouch for what you wrote to be true, and am looking forward to the 
release.

+1

On 2021/07/10 14:32:05, Eya Badal  wrote:
> Dear Apache Community,
>
> Please vote on releasing the following candidate as Apache AGE version 0.5.0
>
> The vote is open now and until July 13th at 7:32 AM PST and passes if a 
> majority +1 votes are cast, with a minimum of 3 +1 votes.
>
> [ ] +1 Release this package as Apache AGE 0.5.0
> [ ] -1 Do not release this package because ...
>
>
> To learn more about Apache AGE, please see http://age.apache.org/
>
> *
> The git tag to be discussed and voted upon:
> https://github.com/apache/incubator-age/releases/tag/v0.5.0
>
> The git commit hash:
> commit e36e6d79c2a65259f4b46cd9a3623d69518605a4
>
> The release files for 0.5.0, can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/age/0.5.0.rc0%20/
>
> The signatures, files, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/age/
>
> Signatures used for AGE RCs can be found in this file:
> https://dist.apache.org/repos/dist/dev/incubator/age/KEYS
>
> The fingerprint of key to sign release artifacts:
> FD8B 268F 784A CE10 F201  E63B C063 8775 6375 38D2
>
> For information about the contents of this release, see:
> https://github.com/apache/incubator-age/releases/tag/v0.5.0
>
> Thank you for your time in advance.
>
> Best regards,
> Eya Badal
>
>

Re: [VOTE] Graduate Apache Pinot as TLP

[Felix Cheung]

+1

On Wed, Jun 23, 2021 at 6:55 PM Sheng Wu  wrote:

> +1 binding, good luck
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
>
> Justin Mclean  于2021年6月24日周四 上午9:46写道：
>
> > +1 all the best with the rest of your journey
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

[Felix Cheung]

To add, the thirdeye code directory was excluded from past releases and so
was _not_ part of the Pinot project release. (A topic discussed several
times on list)


On Thu, Jun 17, 2021 at 4:54 PM Mayank Shrivastava 
wrote:

> Hi Justin,
> Thank you for bringing up the discussion aspect. It seems that it may
> purely have been an accidental oversight, but PPMCs were aware of the
> discussions as well as the decision.The key reason was that the ThirdEye
> project did not gain much traction in the open source, and as stated in [1]
> the ThirdEye team felt running it under ASF did not have much return on
> investment. Hope this helps clarify.
>
> [1] Discussion to move ThirdEye of Apache Pinot
> <
> https://lists.apache.org/thread.html/r23c350271bd907718c6b777b0091e493f93ab407443528d4d549172a%40%3Cprivate.pinot.apache.org%3E
> >
> Best Regards,
> Mayank
>
> On Thu, Jun 17, 2021 at 4:09 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > Thanks for taking action on this.
> >
> > Still one things concerns me, the discussion of removal of ThirdEye is
> > unusual as it happened offlist and it seems it was only brought back to
> the
> > list after a decision was made. For decisions like this, all of the PMC
> > need to be informed and the decision needs to be made in the open on the
> > list. The source of the issue to me seems to be commit rights and I
> think a
> > better way of resolving this would have been considering lowering the
> > commit bar. Was that considered in the off list discussions?
> >
> > Kind Regards,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: CRAN package SparkR

[Felix Cheung]

Any suggestion or comment on this? They are going to remove the package by
6-28

Seems to me if we have a switch to opt in to install (and not by default
on), or prompt the user in interactive session, should be good as user
confirmation.



On Sun, Jun 13, 2021 at 11:25 PM Felix Cheung 
wrote:

> It looks like they would not allow caching the Spark
> Distribution.
>
> I’m not sure what can be done about this.
>
> If I recall, the package should remove this during test. Or maybe
> spark.install() ie optional (hence getting user confirmation?)
>
>
> -- Forwarded message -
> Date: Sun, Jun 13, 2021 at 10:19 PM
> Subject: CRAN package SparkR
> To: Felix Cheung 
> CC: 
>
>
> Dear maintainer,
>
> Checking this apparently creates the default directory as per
>
> #' @param localDir a local directory where Spark is installed. The
> directory con
> tains
> #' version-specific folders of Spark packages. Default is
> path t
> o
> #' the cache directory:
> #' \itemize{
> #'   \item Mac OS X: \file{~/Library/Caches/spark}
> #'   \item Unix: \env{$XDG_CACHE_HOME} if defined,
> otherwise \file{~/.cache/spark}
> #'   \item Windows:
> \file{\%LOCALAPPDATA\%\\Apache\\Spark\\Cache}.
> #' }
>
> However, the CRAN Policy says
>
>   - Packages should not write in the user’s home filespace (including
> clipboards), nor anywhere else on the file system apart from the R
> session’s temporary directory (or during installation in the
> location pointed to by TMPDIR: and such usage should be cleaned
> up). Installing into the system’s R installation (e.g., scripts to
> its bin directory) is not allowed.
>
> Limited exceptions may be allowed in interactive sessions if the
> package obtains confirmation from the user.
>
> For R version 4.0 or later (hence a version dependency is required
> or only conditional use is possible), packages may store
> user-specific data, configuration and cache files in their
> respective user directories obtained from tools::R_user_dir(),
> provided that by default sizes are kept as small as possible and the
> contents are actively managed (including removing outdated
> material).
>
> Can you pls fix as necessary?
>
> Please fix before 2021-06-28 to safely retain your package on CRAN.
>
> Best
> -k
>

Re: [DISCUSS] Graduate Apache Pinot (Incubating) as a TLP

[Felix Cheung]

On Wed, Jun 16, 2021 at 5:39 PM Dave Fisher  wrote:

> Adding trademarks@
>
> See https://prestodb.io/docs/current/connector.html
>

This is a great point but to be clear, that https://prestodb.io/
 is the Presto project in
the Presto Foundation, and not the Apache Pinot project.



> There are 11 Apache products with trademark issues.
>
> This issue is extensive enough that a coordinated response is required.
> these can take long enough that this issue should not delay graduation.
>
> >
> > The Presto documentation looks to have a few branding issue that need to
> be corrected [3]. Is the PPMC aware of this and doing something about it? I
> can see some other branding issues with the presto webpage [4][5] (and
> other pages) and Apache projects with Pinot and Hive, Hadoop, Cassandra,
> Spark, Kafka and Druid. There might be others.
>
> Regards,
> Dave
>
> >
> > Thanks,
> > Justin
> >
> > 1.
> https://lists.apache.org/thread.html/rb2bc93448636e3238f72654426ecce232b46c73ed1447b9c47a1d49e%40%3Cgeneral.incubator.apache.org%3E
> > 2. https://github.com/apache/incubator-pinot/issues/6785
> > 3. https://prestodb.io/docs/current/connector/pinot.html
> > 4. https://prestodb.io
> > 5. https://prestodb.io/faq.html
> > 6. https://docs.pinot.apache.org/integrations/thirdeye
> > 7. https://github.com/apache/incubator-pinot/tree/master/thirdeye
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>

Fwd: CRAN package SparkR

[Felix Cheung]

It looks like they would not allow caching the Spark
Distribution.

I’m not sure what can be done about this.

If I recall, the package should remove this during test. Or maybe
spark.install() ie optional (hence getting user confirmation?)


-- Forwarded message -
Date: Sun, Jun 13, 2021 at 10:19 PM
Subject: CRAN package SparkR
To: Felix Cheung 
CC: 


Dear maintainer,

Checking this apparently creates the default directory as per

#' @param localDir a local directory where Spark is installed. The
directory con
tains
#' version-specific folders of Spark packages. Default is
path t
o
#' the cache directory:
#' \itemize{
#'   \item Mac OS X: \file{~/Library/Caches/spark}
#'   \item Unix: \env{$XDG_CACHE_HOME} if defined,
otherwise \file{~/.cache/spark}
#'   \item Windows:
\file{\%LOCALAPPDATA\%\\Apache\\Spark\\Cache}.
#' }

However, the CRAN Policy says

  - Packages should not write in the user’s home filespace (including
clipboards), nor anywhere else on the file system apart from the R
session’s temporary directory (or during installation in the
location pointed to by TMPDIR: and such usage should be cleaned
up). Installing into the system’s R installation (e.g., scripts to
its bin directory) is not allowed.

Limited exceptions may be allowed in interactive sessions if the
package obtains confirmation from the user.

For R version 4.0 or later (hence a version dependency is required
or only conditional use is possible), packages may store
user-specific data, configuration and cache files in their
respective user directories obtained from tools::R_user_dir(),
provided that by default sizes are kept as small as possible and the
contents are actively managed (including removing outdated
material).

Can you pls fix as necessary?

Please fix before 2021-06-28 to safely retain your package on CRAN.

Best
-k