date:20211123

Re: Can we use the GitHub's "transferring a repository" feature after IP clearance

2021-11-23 Thread Sutou Kouhei

Hi,

Thanks for all your replies!
It seems that Apache Arrow project can also use the GitHub's
"transferring a repository" feature.


Thanks,
-- 
kou

In <010701d7e104$5bb0c830$13125890$@apache.org>
  "RE: Can we use the GitHub's "transferring a repository" feature after IP 
clearance" on Wed, 24 Nov 2021 08:24:46 +0100,
  "Dominik Riemer"  wrote:

> Hi,
> 
> we used the "transfer repository" feature when we were transferring 
> StreamPipes to the incubator, which worked smoothly.
> Infra performs the transfer upon request, the only requirement is that you 
> are able to add someone from Infra as an owner to your existing repository, 
> as only Infra can initiate the transfer due to access rights.
> 
> Dominik
> 
> -Original Message-
> From: Sheng Wu  
> Sent: Wednesday, November 24, 2021 4:24 AM
> To: Incubator 
> Subject: Re: Can we use the GitHub's "transferring a repository" feature 
> after IP clearance
> 
> Hi
> 
> I believe this gets to be accepted once you have IP clearance passed, SGA and 
> ICLA filed, then INFRA will provide a way to do this.
> Just submit a ticket to Infra team once everything is ready.
> 
> Sheng Wu 吴晟
> Twitter, wusheng1108
> 
> 
> Daniel Widdis  于2021年11月24日周三 上午10:42写道：
> 
>> I can't speak to the specifics of Apache, but I have used the 
>> repository transfer feature to move a project from a personal account 
>> to an organizational account, and it preserves all the issues, PRs, commit
>> history, etc., simply changing the Github URL.   I wouldn't think there
>> would be any issues at all from an IP standpoint.
>>
>> The only "hiccup" I experienced the presence of older releases with 
>> older coordinates in a central repository, for which there should be a 
>> one-time special release process to redirect the groupid for the first 
>> release at new coordinates, e.g. [1]
>>
>> [1] - https://maven.apache.org/guides/mini/guide-relocation.html
>>
>> On 11/23/21, 6:33 PM, "Sutou Kouhei"  wrote:
>>
>> Hi,
>>
>> I'm not sure that here is a right place to discuss this. If
>> this is not a right place, please tell me where is a right
>> place.
>>
>> Question:
>>
>> Can we use the GitHub's "transferring a repository"[1] after
>> IP clearance is passed? Apache Arrow project used pull
>> requests to import donated codes that pass IP clearance but
>> has never used the GitHub's "transferring a repository". If
>> there is a case that uses the GitHub's "transferring a
>> repository", please share it. Any advice is appreciated as
>> well.
>>
>> Background:
>>
>> Apache Arrow project has accepted the donation of the Julia
>> implementation before[2]. But there is a problem in
>> development process, https://github.com/JuliaData/Arrow.jl
>> is upstream and
>> https://github.com/apache/arrow/tree/master/julia/Arrow is
>> downstream[3].
>>
>> So, Apache Arrow project wants to restart the Julia
>> implementation with the Apache way development process from
>> IP clearance. Apache Arrow project wants to use a separated
>> repository https://github.com/apache/arrow-julia instead of
>> Apache Arrow's monorepo https://github.com/apache/arrow with
>> the new development process. Apache Arrow PMC accepted
>> this[4][5].
>>
>> I assumed that Apache Arrow project uses a pull request for
>> IP clearance and importing passed codes at import
>> https://github.com/JuliaData/Arrow.jl . So I've created an
>> empty Git repository https://github.com/apache/arrow-julia
>> . But an idea is raised: How about using the GitHub's
>> "transferring a repository" feature to move existing issues
>> and pull requests as-is, set redirect to
>> https://github.com/apache/arrow-julia from
>> https://github.com/JuliaData/Arrow.jl and so on?
>>
>> But I don't know that Apache Arrow project can use the
>> GitHub's "transferring a repository" feature. So I'm asking
>> this here.
>>
>>
>> [1]
>> https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
>> [2] https://lists.apache.org/thread/w7szf06rf0qomc5dolhg57x0pcxvqvxr
>> [3] https://lists.apache.org/thread/1ofhjn37rrlvyv9phhg34hnbrk0dgf4r
>> [4] https://lists.apache.org/thread/6q333y875v7mfyl2g988b01hqtgr52pt
>> [5] 
>> https://lists.apache.org/thread/0fty9370vt5rmp48kbjkdzc0g8vc5cgf
>>
>>
>> Thanks,
>> --
>> kou
>>
>> -
>> 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

RE: Can we use the GitHub's "transferring a repository" feature after IP clearance

2021-11-23 Thread Dominik Riemer

Hi,

we used the "transfer repository" feature when we were transferring StreamPipes 
to the incubator, which worked smoothly.
Infra performs the transfer upon request, the only requirement is that you are 
able to add someone from Infra as an owner to your existing repository, as only 
Infra can initiate the transfer due to access rights.

Dominik

-Original Message-
From: Sheng Wu  
Sent: Wednesday, November 24, 2021 4:24 AM
To: Incubator 
Subject: Re: Can we use the GitHub's "transferring a repository" feature after 
IP clearance

Hi

I believe this gets to be accepted once you have IP clearance passed, SGA and 
ICLA filed, then INFRA will provide a way to do this.
Just submit a ticket to Infra team once everything is ready.

Sheng Wu 吴晟
Twitter, wusheng1108


Daniel Widdis  于2021年11月24日周三 上午10:42写道：

> I can't speak to the specifics of Apache, but I have used the 
> repository transfer feature to move a project from a personal account 
> to an organizational account, and it preserves all the issues, PRs, commit
> history, etc., simply changing the Github URL.   I wouldn't think there
> would be any issues at all from an IP standpoint.
>
> The only "hiccup" I experienced the presence of older releases with 
> older coordinates in a central repository, for which there should be a 
> one-time special release process to redirect the groupid for the first 
> release at new coordinates, e.g. [1]
>
> [1] - https://maven.apache.org/guides/mini/guide-relocation.html
>
> On 11/23/21, 6:33 PM, "Sutou Kouhei"  wrote:
>
> Hi,
>
> I'm not sure that here is a right place to discuss this. If
> this is not a right place, please tell me where is a right
> place.
>
> Question:
>
> Can we use the GitHub's "transferring a repository"[1] after
> IP clearance is passed? Apache Arrow project used pull
> requests to import donated codes that pass IP clearance but
> has never used the GitHub's "transferring a repository". If
> there is a case that uses the GitHub's "transferring a
> repository", please share it. Any advice is appreciated as
> well.
>
> Background:
>
> Apache Arrow project has accepted the donation of the Julia
> implementation before[2]. But there is a problem in
> development process, https://github.com/JuliaData/Arrow.jl
> is upstream and
> https://github.com/apache/arrow/tree/master/julia/Arrow is
> downstream[3].
>
> So, Apache Arrow project wants to restart the Julia
> implementation with the Apache way development process from
> IP clearance. Apache Arrow project wants to use a separated
> repository https://github.com/apache/arrow-julia instead of
> Apache Arrow's monorepo https://github.com/apache/arrow with
> the new development process. Apache Arrow PMC accepted
> this[4][5].
>
> I assumed that Apache Arrow project uses a pull request for
> IP clearance and importing passed codes at import
> https://github.com/JuliaData/Arrow.jl . So I've created an
> empty Git repository https://github.com/apache/arrow-julia
> . But an idea is raised: How about using the GitHub's
> "transferring a repository" feature to move existing issues
> and pull requests as-is, set redirect to
> https://github.com/apache/arrow-julia from
> https://github.com/JuliaData/Arrow.jl and so on?
>
> But I don't know that Apache Arrow project can use the
> GitHub's "transferring a repository" feature. So I'm asking
> this here.
>
>
> [1]
> https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
> [2] https://lists.apache.org/thread/w7szf06rf0qomc5dolhg57x0pcxvqvxr
> [3] https://lists.apache.org/thread/1ofhjn37rrlvyv9phhg34hnbrk0dgf4r
> [4] https://lists.apache.org/thread/6q333y875v7mfyl2g988b01hqtgr52pt
> [5] 
> https://lists.apache.org/thread/0fty9370vt5rmp48kbjkdzc0g8vc5cgf
>
>
> Thanks,
> --
> kou
>
> -
> 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: [DISCUSS] Incubating Proposal of SeaTunnel

2021-11-23 Thread JB Onofré

Hi

It looks interesting. I gonna take a deeper look. 

Please let me know if you need an additional mentor. We can have a chat 
together. 

Thanks
Regards 
JB

> Le 24 nov. 2021 à 02:31, Sheng Wu  a écrit :
> 
> Heard about this project for months. It is good to see this proposal, and
> it is great having DolphinScheduler's PMC join SeaTunnel project to help.
> 
> Sheng Wu 吴晟
> Twitter, wusheng1108
> 
> 
> Willem Jiang  于2021年11月24日周三 上午8:47写道：
> 
>> Hi all,
>> 
>> We want to propose SeaTunnel as a new Apache Incubator project.
>> 
>> SeaTunnel is a distributed, high-performance data integration platform
>> for the synchronization and transformation of massive data (offline &
>> real-time). It has
>> following features:
>> 1. Real-time integrate data from different data platforms
>> 2. High performance with billions of rows of data
>> 3. Assure 0 data loss and duplication
>> 4. Easily Monitor the whole status of the system
>> 
>> It was initially known as Waterdrop and renamed SeaTunnel[1] on
>> October 12, 2021.
>> 
>> I'd happy to be the Champion of this project and may Thanks to  Lidong
>> Dai (lidong...@apache.org),Ted Liu (ted...@apache.org), William
>> Guo(guo...@apache.org), Zhenxu Ke (kezhenx...@apache.org) and Kevin
>> Ratnasekera (djkevincr1...@gmail.com) for being the mentor of
>> SeaTunnel project and
>> helping us to polish the incubating proposal[2].
>> 
>> Looking forward to your feedback and thank you very much.
>> 
>> [1]https://github.com/InterestingLab/SeaTunnel
>> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/SeaTunnelProposal
>> 
>> 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
>> 
>> 


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

Re: Can we use the GitHub's "transferring a repository" feature after IP clearance

2021-11-23 Thread Sheng Wu

Hi

I believe this gets to be accepted once you have IP clearance passed, SGA
and ICLA filed, then INFRA will provide a way to do this.
Just submit a ticket to Infra team once everything is ready.

Sheng Wu 吴晟
Twitter, wusheng1108


Daniel Widdis  于2021年11月24日周三 上午10:42写道：

> I can't speak to the specifics of Apache, but I have used the repository
> transfer feature to move a project from a personal account to an
> organizational account, and it preserves all the issues, PRs, commit
> history, etc., simply changing the Github URL.   I wouldn't think there
> would be any issues at all from an IP standpoint.
>
> The only "hiccup" I experienced the presence of older releases with older
> coordinates in a central repository, for which there should be a one-time
> special release process to redirect the groupid for the first release at
> new coordinates, e.g. [1]
>
> [1] - https://maven.apache.org/guides/mini/guide-relocation.html
>
> On 11/23/21, 6:33 PM, "Sutou Kouhei"  wrote:
>
> Hi,
>
> I'm not sure that here is a right place to discuss this. If
> this is not a right place, please tell me where is a right
> place.
>
> Question:
>
> Can we use the GitHub's "transferring a repository"[1] after
> IP clearance is passed? Apache Arrow project used pull
> requests to import donated codes that pass IP clearance but
> has never used the GitHub's "transferring a repository". If
> there is a case that uses the GitHub's "transferring a
> repository", please share it. Any advice is appreciated as
> well.
>
> Background:
>
> Apache Arrow project has accepted the donation of the Julia
> implementation before[2]. But there is a problem in
> development process, https://github.com/JuliaData/Arrow.jl
> is upstream and
> https://github.com/apache/arrow/tree/master/julia/Arrow is
> downstream[3].
>
> So, Apache Arrow project wants to restart the Julia
> implementation with the Apache way development process from
> IP clearance. Apache Arrow project wants to use a separated
> repository https://github.com/apache/arrow-julia instead of
> Apache Arrow's monorepo https://github.com/apache/arrow with
> the new development process. Apache Arrow PMC accepted
> this[4][5].
>
> I assumed that Apache Arrow project uses a pull request for
> IP clearance and importing passed codes at import
> https://github.com/JuliaData/Arrow.jl . So I've created an
> empty Git repository https://github.com/apache/arrow-julia
> . But an idea is raised: How about using the GitHub's
> "transferring a repository" feature to move existing issues
> and pull requests as-is, set redirect to
> https://github.com/apache/arrow-julia from
> https://github.com/JuliaData/Arrow.jl and so on?
>
> But I don't know that Apache Arrow project can use the
> GitHub's "transferring a repository" feature. So I'm asking
> this here.
>
>
> [1]
> https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
> [2] https://lists.apache.org/thread/w7szf06rf0qomc5dolhg57x0pcxvqvxr
> [3] https://lists.apache.org/thread/1ofhjn37rrlvyv9phhg34hnbrk0dgf4r
> [4] https://lists.apache.org/thread/6q333y875v7mfyl2g988b01hqtgr52pt
> [5] https://lists.apache.org/thread/0fty9370vt5rmp48kbjkdzc0g8vc5cgf
>
>
> Thanks,
> --
> kou
>
> -
> 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: Can we use the GitHub's "transferring a repository" feature after IP clearance

2021-11-23 Thread Daniel Widdis

I can't speak to the specifics of Apache, but I have used the repository
transfer feature to move a project from a personal account to an organizational
account, and it preserves all the issues, PRs, commit history, etc., simply
changing the Github URL. I wouldn't think there would be any issues at all
from an IP standpoint.

The only "hiccup" I experienced the presence of older releases with older
coordinates in a central repository, for which there should be a one-time
special release process to redirect the groupid for the first release at new
coordinates, e.g. [1]

[1] - https://maven.apache.org/guides/mini/guide-relocation.html

On 11/23/21, 6:33 PM, "Sutou Kouhei" wrote:

Hi,

I'm not sure that here is a right place to discuss this. If
this is not a right place, please tell me where is a right
place.

Question:

Can we use the GitHub's "transferring a repository"[1] after
IP clearance is passed? Apache Arrow project used pull
requests to import donated codes that pass IP clearance but
has never used the GitHub's "transferring a repository". If
there is a case that uses the GitHub's "transferring a
repository", please share it. Any advice is appreciated as
well.

Background:

Apache Arrow project has accepted the donation of the Julia
implementation before[2]. But there is a problem in
development process, https://github.com/JuliaData/Arrow.jl
is upstream and
https://github.com/apache/arrow/tree/master/julia/Arrow is
downstream[3].

So, Apache Arrow project wants to restart the Julia
implementation with the Apache way development process from
IP clearance. Apache Arrow project wants to use a separated
repository https://github.com/apache/arrow-julia instead of
Apache Arrow's monorepo https://github.com/apache/arrow with
the new development process. Apache Arrow PMC accepted
this[4][5].

I assumed that Apache Arrow project uses a pull request for
IP clearance and importing passed codes at import
https://github.com/JuliaData/Arrow.jl . So I've created an
empty Git repository https://github.com/apache/arrow-julia
. But an idea is raised: How about using the GitHub's
"transferring a repository" feature to move existing issues
and pull requests as-is, set redirect to
https://github.com/apache/arrow-julia from
https://github.com/JuliaData/Arrow.jl and so on?

But I don't know that Apache Arrow project can use the
GitHub's "transferring a repository" feature. So I'm asking
this here.

[1]
https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
[2] https://lists.apache.org/thread/w7szf06rf0qomc5dolhg57x0pcxvqvxr
[3] https://lists.apache.org/thread/1ofhjn37rrlvyv9phhg34hnbrk0dgf4r
[4] https://lists.apache.org/thread/6q333y875v7mfyl2g988b01hqtgr52pt
[5] https://lists.apache.org/thread/0fty9370vt5rmp48kbjkdzc0g8vc5cgf

Thanks,
--
kou

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

Can we use the GitHub's "transferring a repository" feature after IP clearance

2021-11-23 Thread Sutou Kouhei

Hi,

I'm not sure that here is a right place to discuss this. If
this is not a right place, please tell me where is a right
place.

Question:

Background:

But I don't know that Apache Arrow project can use the
GitHub's "transferring a repository" feature. So I'm asking
this here.

Thanks,
--
kou

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

Re:Re: [VOTE] Release Apache Doris 0.15.0-incubating-rc04

2021-11-23 Thread 陈明雨

Hi Sebb:

> Please ONLY use downloads for KEYS, i.e.
> https://downloads.apache.org/incubator/doris/KEYS
>See recent Shenyu and Kyuubi threads for reasons why.
Thanks for your remind.
I have updated the KEYS in [1], and it will be synced to [2] very soon.


[1] https://dist.apache.org/repos/dist/release/incubator/doris/
[2] https://downloads.apache.org/incubator/doris/KEYS



--

此致！Best Regards
陈明雨 Mingyu Chen

Email:
chenmin...@apache.org





在 2021-11-22 18:39:30，"sebb"  写道：
>On Mon, 22 Nov 2021 at 09:25, 陈明雨  wrote:
>>
>> Hi all,
>>
>>
>>
>>
>> Please review and vote on Apache Doris 0.15.0-incubating-rc04 release.
>>
>>
>>
>>
>> Apache Doris is an MPP-based interactive SQL data warehousing for reporting 
>> and analysis. The official website is:
>> http://doris.incubator.apache.org/
>>
>>
>>
>>
>> The Apache Doris community has voted on and approved this release:
>>
>> https://lists.apache.org/thread.html/d70f7c8a8ae448bf6680a15914646005c6483564464cfa15f4ddc2fc@%3Cdev.doris.apache.org%3E
>>
>>
>>
>>
>> The vote result email thread:
>>
>> https://lists.apache.org/thread/lhnp6fnfddzc44hm1wmo2x5sqpp2by4k
>>
>>
>>
>>
>> The release candidate has been tagged in GitHub as 0.15.0-rc04, available 
>> here:
>>
>> https://github.com/apache/incubator-doris/tree/0.15.0-rc04
>>
>>
>>
>>
>> Thanks to everyone who has contributed to this release, and the CHANGE LOG 
>> can be found here:
>>
>> https://github.com/apache/incubator-doris/issues/6806
>>
>>
>>
>>
>> The artifacts (source, signature and checksum) corresponding to this release 
>> candidate can be found here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/doris/0.15/0.15.0-rc04/
>>
>>
>>
>>
>> This has been signed with PGP key 7C392A1E9C66C9CCCF388618F10626E3624583CB, 
>> corresponding to chenmin...@apache.org.
>>
>> KEYS file is available here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
>
>Please ONLY use downloads for KEYS, i.e.
>
>https://downloads.apache.org/incubator/doris/KEYS
>
>See recent Shenyu and Kyuubi threads for reasons why.
>
>> It is also listed here:
>>
>> https://people.apache.org/keys/committer/morningman.asc
>
>That is also not suitable as a link, as it may disappear at any time.
>Only download KEYS are suitable.
>
>>
>>
>>
>>
>> The vote will be open for at least 72 hours.
>>
>> [ ] +1 Approve the release
>>
>> [ ] +0 No opinion
>>
>> [ ] -1 Do not release this package because ...
>>
>>
>>
>>
>> To verify and build, you can refer to following instruction:
>>
>>
>>
>>
>> Firstly, you must be install and start docker service, and then you could 
>> build Doris as following steps:
>>
>>
>>
>>
>> Step1: Pull the docker image with Doris building environment
>>
>> $ docker pull apache/incubator-doris:build-env-1.4.1
>>
>> You can check it by listing images, its size is about 3.28GB.
>>
>>
>>
>>
>> Step2: Run the Docker image
>>
>> You can run image directly:
>>
>> $ docker run -it apache/incubator-doris:build-env-1.4.1
>>
>>
>>
>>
>> Step3: Download Doris source
>>
>> Now you should in docker environment, and you can download Doris source 
>> package.
>>
>> (If you have downloaded source and it is not in image, you can map its path 
>> to image in Step2.)
>>
>> $ wget 
>> https://dist.apache.org/repos/dist/dev/incubator/doris/0.15/0.15.0-rc04/apache-doris-0.15.0.rc04-incubating-src.tar.gz
>>
>>
>>
>>
>> Step4: Build Doris
>>
>> Now you can decompress and enter Doris source path and build Doris.
>>
>> $ tar zxvf apache-doris-0.15.0.rc04-incubating-src.tar.gz
>>
>> $ cd apache-doris-0.15.0.rc04-incubating-src
>>
>> $ sh build.sh
>>
>>
>>
>> --
>>
>> 此致！Best Regards
>> 陈明雨 Mingyu Chen
>>
>> Email:
>> chenmin...@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 SeaTunnel

2021-11-23 Thread Sheng Wu

Heard about this project for months. It is good to see this proposal, and
it is great having DolphinScheduler's PMC join SeaTunnel project to help.

Sheng Wu 吴晟
Twitter, wusheng1108


Willem Jiang  于2021年11月24日周三 上午8:47写道：

> Hi all,
>
> We want to propose SeaTunnel as a new Apache Incubator project.
>
> SeaTunnel is a distributed, high-performance data integration platform
> for the synchronization and transformation of massive data (offline &
> real-time). It has
> following features:
>  1. Real-time integrate data from different data platforms
>  2. High performance with billions of rows of data
>  3. Assure 0 data loss and duplication
>  4. Easily Monitor the whole status of the system
>
> It was initially known as Waterdrop and renamed SeaTunnel[1] on
> October 12, 2021.
>
> I'd happy to be the Champion of this project and may Thanks to  Lidong
> Dai (lidong...@apache.org),Ted Liu (ted...@apache.org), William
> Guo(guo...@apache.org), Zhenxu Ke (kezhenx...@apache.org) and Kevin
> Ratnasekera (djkevincr1...@gmail.com) for being the mentor of
> SeaTunnel project and
> helping us to polish the incubating proposal[2].
>
> Looking forward to your feedback and thank you very much.
>
> [1]https://github.com/InterestingLab/SeaTunnel
> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/SeaTunnelProposal
>
> 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
>
>

Re: [VOTE] Release Apache Doris 0.15.0-incubating-rc04

2021-11-23 Thread Willem Jiang

+1 bing

I checked,

- incubating in name

- signed key and checksum.

- the License and Notice file.

- There is no binary file in the source Kit.

- all ASF files have ASF headers

- I didn’t compile the code in Mac OSX


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Nov 22, 2021 at 5:25 PM 陈明雨  wrote:
>
> Hi all,
>
>
>
>
> Please review and vote on Apache Doris 0.15.0-incubating-rc04 release.
>
>
>
>
> Apache Doris is an MPP-based interactive SQL data warehousing for reporting 
> and analysis. The official website is:
> http://doris.incubator.apache.org/
>
>
>
>
> The Apache Doris community has voted on and approved this release:
>
> https://lists.apache.org/thread.html/d70f7c8a8ae448bf6680a15914646005c6483564464cfa15f4ddc2fc@%3Cdev.doris.apache.org%3E
>
>
>
>
> The vote result email thread:
>
> https://lists.apache.org/thread/lhnp6fnfddzc44hm1wmo2x5sqpp2by4k
>
>
>
>
> The release candidate has been tagged in GitHub as 0.15.0-rc04, available 
> here:
>
> https://github.com/apache/incubator-doris/tree/0.15.0-rc04
>
>
>
>
> Thanks to everyone who has contributed to this release, and the CHANGE LOG 
> can be found here:
>
> https://github.com/apache/incubator-doris/issues/6806
>
>
>
>
> The artifacts (source, signature and checksum) corresponding to this release 
> candidate can be found here:
>
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.15/0.15.0-rc04/
>
>
>
>
> This has been signed with PGP key 7C392A1E9C66C9CCCF388618F10626E3624583CB, 
> corresponding to chenmin...@apache.org.
>
> KEYS file is available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/doris/KEYS
>
> It is also listed here:
>
> https://people.apache.org/keys/committer/morningman.asc
>
>
>
>
> The vote will be open for at least 72 hours.
>
> [ ] +1 Approve the release
>
> [ ] +0 No opinion
>
> [ ] -1 Do not release this package because ...
>
>
>
>
> To verify and build, you can refer to following instruction:
>
>
>
>
> Firstly, you must be install and start docker service, and then you could 
> build Doris as following steps:
>
>
>
>
> Step1: Pull the docker image with Doris building environment
>
> $ docker pull apache/incubator-doris:build-env-1.4.1
>
> You can check it by listing images, its size is about 3.28GB.
>
>
>
>
> Step2: Run the Docker image
>
> You can run image directly:
>
> $ docker run -it apache/incubator-doris:build-env-1.4.1
>
>
>
>
> Step3: Download Doris source
>
> Now you should in docker environment, and you can download Doris source 
> package.
>
> (If you have downloaded source and it is not in image, you can map its path 
> to image in Step2.)
>
> $ wget 
> https://dist.apache.org/repos/dist/dev/incubator/doris/0.15/0.15.0-rc04/apache-doris-0.15.0.rc04-incubating-src.tar.gz
>
>
>
>
> Step4: Build Doris
>
> Now you can decompress and enter Doris source path and build Doris.
>
> $ tar zxvf apache-doris-0.15.0.rc04-incubating-src.tar.gz
>
> $ cd apache-doris-0.15.0.rc04-incubating-src
>
> $ sh build.sh
>
>
>
> --
>
> 此致！Best Regards
> 陈明雨 Mingyu Chen
>
> Email:
> chenmin...@apache.org

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

[DISCUSS] Incubating Proposal of SeaTunnel

2021-11-23 Thread Willem Jiang

Hi all,

We want to propose SeaTunnel as a new Apache Incubator project.

SeaTunnel is a distributed, high-performance data integration platform
for the synchronization and transformation of massive data (offline &
real-time). It has
following features:
 1. Real-time integrate data from different data platforms
 2. High performance with billions of rows of data
 3. Assure 0 data loss and duplication
 4. Easily Monitor the whole status of the system

It was initially known as Waterdrop and renamed SeaTunnel[1] on
October 12, 2021.

I'd happy to be the Champion of this project and may Thanks to  Lidong
Dai (lidong...@apache.org),Ted Liu (ted...@apache.org), William
Guo(guo...@apache.org), Zhenxu Ke (kezhenx...@apache.org) and Kevin
Ratnasekera (djkevincr1...@gmail.com) for being the mentor of
SeaTunnel project and
helping us to polish the incubating proposal[2].

Looking forward to your feedback and thank you very much.

[1]https://github.com/InterestingLab/SeaTunnel
[2]https://cwiki.apache.org/confluence/display/INCUBATOR/SeaTunnelProposal

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

[ANNOUNCE] Apache Sedona 1.1.1-incubating released

2021-11-23 Thread Jia Yu

Dear all, We are happy to report that we have released Apache Sedona
(incubating) 1.1.1-incubating. Thank you again for your help. Apache Sedona
(incubating) is a cluster computing system for processing large-scale
spatial data. Vote thread (Permalink from https://lists.apache.org/list.html):
https://lists.apache.org/thread/kjvv5nsg1rwddjll1xd6b9l9o8r7zkoc Vote
result thread (Permalink from https://lists.apache.org/list.html):
https://lists.apache.org/thread/d2wbfqmmrnvd8wlfgyynt87xq8cs1k4v Website:
http://sedona.apache.org/ Release notes:
https://github.com/apache/incubator-sedona/blob/sedona-1.1.1-incubating/docs/setup/release-notes.md
Download links:
https://github.com/apache/incubator-sedona/releases/tag/sedona-1.1.1-incubating
Additional resources: Get started: http://sedona.apache.org/setup/overview/
Tutorials: http://sedona.apache.org/tutorial/rdd/ Mailing list:
d...@sedona.apache.org Twitter: https://twitter.com/ApacheSedona Gitter:
https://gitter.im/apache/sedona Regards, Apache Sedona (incubating) Team

[RESULT][VOTE] Release Apache Sedona 1.1.1-incubating-rc1

2021-11-23 Thread Jia Yu

Dear all, The vote closes now as 72hr have passed. The vote PASSES with +3
(binding): Felix, Justin, Xun Liu +0 (non-binding) No -1 votes The vote
thread (Permalink from https://lists.apache.org/list.html):
https://lists.apache.org/thread/kjvv5nsg1rwddjll1xd6b9l9o8r7zkoc
I will now publish the release and make an announcement once it is done.

-
1. Include community vote thread and vote result thread in the vote email @
incubator
2. Issues to be fixed in the next release
3. NOTICE file
4. headers for R workflow scripts
5. checksum and signature name on Sedona website download page

Thanks,
Jia

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

2021-11-23 Thread Jia Yu

Thank you guys. I will fix these issues accordingly!

On Tue, Nov 23, 2021 at 10:00 AM sebb  wrote:

> On Tue, 23 Nov 2021 at 07:09, Jia Yu  wrote:
> >
> > Hi Justin,
> >
> > 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/
>
> Looks good.
>
> However the hash and sig display names are a bit unusual: normally
> these are denoted by just 'sha512' or 'asc' rather than 'src.sha512'
> and 'src.asc'.
>
> Personally, I think it would be clearer to drop the 'src.' and 'bin.'
> prefix.
>
>
>
> > 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?
> >
> > 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?
> >
> > Thanks,
> > Jia
> >
> >
> > On Sun, Nov 21, 2021 at 4:02 AM Justin Mclean 
> > wrote:
> >
> > > Hi,
> > >
> > > I’m -1 (binding) on this release as the project website doesn’t have an
> > > obvious download page and they have made previous releases. This has
> been
> > > brought up on this list before and there was no response from the
> project.
> > >
> > > For this release:
> > > - incubating in name
> > > - signatures and hashes are fine
> > > - disclaimer exists
> > > - LICENSE and NOTICE look OK but I didn’t do a detailed check
> > > - The year in NOTICE looks incorrect as Sedona only started in the
> > > incubator in 2020?
> > > - ASF files have headers
> > > - No unexpected binary files
> > > - Can compile from source
> > >
> > > 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 Sedona 1.1.1-incubating-rc1

2021-11-23 Thread sebb

On Tue, 23 Nov 2021 at 07:09, Jia Yu  wrote:
>
> Hi Justin,
>
> 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/

Looks good.

However the hash and sig display names are a bit unusual: normally
these are denoted by just 'sha512' or 'asc' rather than 'src.sha512'
and 'src.asc'.

Personally, I think it would be clearer to drop the 'src.' and 'bin.' prefix.



> 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?
>
> 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?
>
> Thanks,
> Jia
>
>
> On Sun, Nov 21, 2021 at 4:02 AM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > I’m -1 (binding) on this release as the project website doesn’t have an
> > obvious download page and they have made previous releases. This has been
> > brought up on this list before and there was no response from the project.
> >
> > For this release:
> > - incubating in name
> > - signatures and hashes are fine
> > - disclaimer exists
> > - LICENSE and NOTICE look OK but I didn’t do a detailed check
> > - The year in NOTICE looks incorrect as Sedona only started in the
> > incubator in 2020?
> > - ASF files have headers
> > - No unexpected binary files
> > - Can compile from source
> >
> > 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 Sedona 1.1.1-incubating-rc1

2021-11-23 Thread 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] Release Apache Sedona 1.1.1-incubating-rc1

2021-11-23 Thread Jia Yu

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/  >
>
> 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: Can we use the GitHub's "transferring a repository" feature after IP clearance

RE: Can we use the GitHub's "transferring a repository" feature after IP clearance

Re: [DISCUSS] Incubating Proposal of SeaTunnel

Re: Can we use the GitHub's "transferring a repository" feature after IP clearance

Re: Can we use the GitHub's "transferring a repository" feature after IP clearance

Can we use the GitHub's "transferring a repository" feature after IP clearance

Re:Re: [VOTE] Release Apache Doris 0.15.0-incubating-rc04

Re: [DISCUSS] Incubating Proposal of SeaTunnel

Re: [VOTE] Release Apache Doris 0.15.0-incubating-rc04

[DISCUSS] Incubating Proposal of SeaTunnel

[ANNOUNCE] Apache Sedona 1.1.1-incubating released

[RESULT][VOTE] Release Apache Sedona 1.1.1-incubating-rc1

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

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

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

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

16 matches

Site Navigation

Mail list logo

Footer information