Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-12-31 Thread Sutou Kouhei
Hi,

https://github.com/JuliaData/Arrow.jl has been transferred
to https://github.com/apache/arrow-julia . Thanks to
everyone who helped with this process.

-- 
kou

In <20211223.114544.60102279684253469@clear-code.com>
  "Re: [RESULT][VOTE] Restart the Julia implementation with new repository and 
process" on Thu, 23 Dec 2021 11:45:44 +0900 (JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> I share the current status.
> 
> We've finished CLA related tasks. See
> https://github.com/JuliaData/Arrow.jl/issues/265 fro
> details.
> 
> I've filled all items in IP clearance form:
> https://incubator.apache.org/ip-clearance/arrow-julia-library2.html
> 
> And I've started IP clearance vote on gene...@incubator.apache.org:
> https://lists.apache.org/thread/f9xck9j8qdrhvw363vjl6qkk2g8t4l6b
> 
> I'll ask INFRA to transfer JuliaData/Arrow.jl to
> apache/arrow-julia after the vote is passed.
> 
> 
> Thanks,
> -- 
> kou
> 
> In 
>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository 
> and process" on Mon, 6 Dec 2021 22:51:33 -0700,
>   Jacob Quinn  wrote:
> 
>> Thanks kou,
>> 
>> I think I've got all the details summarized in [this issue](
>> https://github.com/JuliaData/Arrow.jl/issues/265) where we'll track
>> progress on the required CLAs. I've also reached out to the
>> individuals directly about signing the CLAs.
>> 
>> -Jacob
>> 
>> On Fri, Dec 3, 2021 at 4:02 PM Sutou Kouhei  wrote:
>> 
>>> Hi Jacob,
>>>
>>> Thanks for helping this!
>>>
>>> I'm filling IP clearance form:
>>>
>>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/arrow-julia-library2.xml
>>>
>>> (I think that we can see it at
>>> https://incubator.apache.org/ip-clearance/arrow-julia-library2.html
>>> soon.)
>>>
>>> Could you stop merging any pull requests until this IP
>>> clearance is finished? (I think that it's acceptable because
>>> the last commit of https://github.com/JuliaData/Arrow.jl is
>>> 2021-11-02.)
>>>
>>> Here are TODO items:
>>>
>>>   1. Check that all active committers have a signed CLA on record.
>>>
>>>   2. Remind active committers that they are responsible for
>>>  ensuring that a Corporate CLA is recorded if such is
>>>  required to authorize their contributions under their
>>>  individual CLA.
>>>
>>> I think that people who commit after
>>> https://incubator.apache.org/ip-clearance/arrow-julia-library.html
>>> (8583da8a84a9e355affb42654dcd8c765bcc3134) are target:
>>>
>>> $ git shortlog -sn
>>> 8583da8a84a9e355affb42654dcd8c765bcc3134..1447cb2b13b728729f9a89760ac07a848e31e599
>>> 53  Jacob Quinn
>>> 16  Jarrett Revels
>>> 10  Curtis Vogt
>>>  8  Eric Hanson
>>>  2  Douglas Bates
>>>  2  ExpandingMan
>>>  2  Kristoffer Carlsson
>>>  1  Damien Drix
>>>  1  Denis Barucic
>>>  1  Jon Alm Eriksen
>>>  1  KronosTheLate
>>>  1  Nick Robinson
>>>  1  Pietro Vertechi
>>>  1  Simeon Schaub
>>>  1  Tanmay Mohapatra
>>>  1  Étienne Tétreault-Pinard
>>>
>>> According to the discussion in Ballista's IP clearance process,
>>>   https://lists.apache.org/thread/k0k7x3rrg56nk8s2c1tvrrv76zl2b1m4
>>> we can remove people who has only 1 commit from the target list:
>>>
>>> 53  Jacob Quinn
>>> 16  Jarrett Revels
>>> 10  Curtis Vogt
>>>  8  Eric Hanson
>>>  2  Douglas Bates
>>>  2  ExpandingMan
>>>  2  Kristoffer Carlsson
>>>
>>> And we can also remove people who commit before
>>> (including) 8583da8a84a9e355affb42654dcd8c765bcc3134 because
>>> they signed CLA in the previous IP clearance:
>>>
>>> $ git shortlog -sn
>>> 16b729db74d78ecb010efab855c9e46c8052f59e..8583da8a84a9e355affb42654dcd8c765bcc3134
>>> | cat
>>>103  ExpandingMan
>>> 53  Jacob Quinn
>>>  4  David Anthoff
>>>  2  Jacob Adenbaum
>>>  2  Spencer Lyon
>>>  1  Graham Stark
>>>  1  John Myles White
>>>  1  Michael Savastio
>>>  1  TheCedarPrince
>>>
>>> So here is the target list:
>>>
>>> 16  Jarrett Revels
>>> 10  Curtis Vogt
>>>  8  Eric Hanson
>>>  2  Douglas Bates
>>>  2  Kristoffer Carlsson
>>>
>>> Jacob, could you ask them to sign CLA for the TODO item 1.?
>>> FYI: Ballista used a GitHub issue for this:
>>>
>>> https://github.com/ballista-compute/ballista/issues/646#issuecomment-806820971
>>>
>>> And could you also remind
>>>
>>> 53  Jacob Quinn
>>> 16  Jarrett Revels
>>> 10  Curtis Vogt
>>>  8  Eric Hanson
>>>  2  Douglas Bates
>>>  2  ExpandingMan
>>>  2  Kristoffer Carlsson
>>>
>>> that the TODO item 2.?
>>>
>>>
>>> Thanks,
>>> --
>>> kou
>>>
>>> In 
>>>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository
>>> and process" on Mon, 29 Nov 2021 20:43:32 -0700,
>>>   Jacob Quinn  wrote:
>>>
>>> > Thanks kou,
>>> >
>>> > I'm happy to help in any way I can. I think I know all the Arrow.jl
>>> > contributors personally, so I'm happy to reach out to them for whatever
>>> is
>>> > needed.
>>> >
>>> > -Jacob
>>> >
>>> > On Wed, Nov 

Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-12-22 Thread Sutou Kouhei
Hi,

I share the current status.

We've finished CLA related tasks. See
https://github.com/JuliaData/Arrow.jl/issues/265 fro
details.

I've filled all items in IP clearance form:
https://incubator.apache.org/ip-clearance/arrow-julia-library2.html

And I've started IP clearance vote on gene...@incubator.apache.org:
https://lists.apache.org/thread/f9xck9j8qdrhvw363vjl6qkk2g8t4l6b

I'll ask INFRA to transfer JuliaData/Arrow.jl to
apache/arrow-julia after the vote is passed.


Thanks,
-- 
kou

In 
  "Re: [RESULT][VOTE] Restart the Julia implementation with new repository and 
process" on Mon, 6 Dec 2021 22:51:33 -0700,
  Jacob Quinn  wrote:

> Thanks kou,
> 
> I think I've got all the details summarized in [this issue](
> https://github.com/JuliaData/Arrow.jl/issues/265) where we'll track
> progress on the required CLAs. I've also reached out to the
> individuals directly about signing the CLAs.
> 
> -Jacob
> 
> On Fri, Dec 3, 2021 at 4:02 PM Sutou Kouhei  wrote:
> 
>> Hi Jacob,
>>
>> Thanks for helping this!
>>
>> I'm filling IP clearance form:
>>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/arrow-julia-library2.xml
>>
>> (I think that we can see it at
>> https://incubator.apache.org/ip-clearance/arrow-julia-library2.html
>> soon.)
>>
>> Could you stop merging any pull requests until this IP
>> clearance is finished? (I think that it's acceptable because
>> the last commit of https://github.com/JuliaData/Arrow.jl is
>> 2021-11-02.)
>>
>> Here are TODO items:
>>
>>   1. Check that all active committers have a signed CLA on record.
>>
>>   2. Remind active committers that they are responsible for
>>  ensuring that a Corporate CLA is recorded if such is
>>  required to authorize their contributions under their
>>  individual CLA.
>>
>> I think that people who commit after
>> https://incubator.apache.org/ip-clearance/arrow-julia-library.html
>> (8583da8a84a9e355affb42654dcd8c765bcc3134) are target:
>>
>> $ git shortlog -sn
>> 8583da8a84a9e355affb42654dcd8c765bcc3134..1447cb2b13b728729f9a89760ac07a848e31e599
>> 53  Jacob Quinn
>> 16  Jarrett Revels
>> 10  Curtis Vogt
>>  8  Eric Hanson
>>  2  Douglas Bates
>>  2  ExpandingMan
>>  2  Kristoffer Carlsson
>>  1  Damien Drix
>>  1  Denis Barucic
>>  1  Jon Alm Eriksen
>>  1  KronosTheLate
>>  1  Nick Robinson
>>  1  Pietro Vertechi
>>  1  Simeon Schaub
>>  1  Tanmay Mohapatra
>>  1  Étienne Tétreault-Pinard
>>
>> According to the discussion in Ballista's IP clearance process,
>>   https://lists.apache.org/thread/k0k7x3rrg56nk8s2c1tvrrv76zl2b1m4
>> we can remove people who has only 1 commit from the target list:
>>
>> 53  Jacob Quinn
>> 16  Jarrett Revels
>> 10  Curtis Vogt
>>  8  Eric Hanson
>>  2  Douglas Bates
>>  2  ExpandingMan
>>  2  Kristoffer Carlsson
>>
>> And we can also remove people who commit before
>> (including) 8583da8a84a9e355affb42654dcd8c765bcc3134 because
>> they signed CLA in the previous IP clearance:
>>
>> $ git shortlog -sn
>> 16b729db74d78ecb010efab855c9e46c8052f59e..8583da8a84a9e355affb42654dcd8c765bcc3134
>> | cat
>>103  ExpandingMan
>> 53  Jacob Quinn
>>  4  David Anthoff
>>  2  Jacob Adenbaum
>>  2  Spencer Lyon
>>  1  Graham Stark
>>  1  John Myles White
>>  1  Michael Savastio
>>  1  TheCedarPrince
>>
>> So here is the target list:
>>
>> 16  Jarrett Revels
>> 10  Curtis Vogt
>>  8  Eric Hanson
>>  2  Douglas Bates
>>  2  Kristoffer Carlsson
>>
>> Jacob, could you ask them to sign CLA for the TODO item 1.?
>> FYI: Ballista used a GitHub issue for this:
>>
>> https://github.com/ballista-compute/ballista/issues/646#issuecomment-806820971
>>
>> And could you also remind
>>
>> 53  Jacob Quinn
>> 16  Jarrett Revels
>> 10  Curtis Vogt
>>  8  Eric Hanson
>>  2  Douglas Bates
>>  2  ExpandingMan
>>  2  Kristoffer Carlsson
>>
>> that the TODO item 2.?
>>
>>
>> Thanks,
>> --
>> kou
>>
>> In 
>>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository
>> and process" on Mon, 29 Nov 2021 20:43:32 -0700,
>>   Jacob Quinn  wrote:
>>
>> > Thanks kou,
>> >
>> > I'm happy to help in any way I can. I think I know all the Arrow.jl
>> > contributors personally, so I'm happy to reach out to them for whatever
>> is
>> > needed.
>> >
>> > -Jacob
>> >
>> > On Wed, Nov 24, 2021 at 1:04 AM Sutou Kouhei  wrote:
>> >
>> >> Hi,
>> >>
>> >> Sorry for not working on this. I asked this on
>> >> gene...@incubator.apache.org [1] and got a reply that there
>> >> is a project that use the GitHub's transfer repository
>> >> feature [2].
>> >>
>> >> Let's start IP clearance process against
>> >> https://github.com/JuliaData/Arrow.jl and use the GitHub's
>> >> transfer repository feature after the IP clearance is
>> >> passed.
>> >>
>> >> Are there any people who help this process? I think that we
>> >> need to fill IP clearance form based 

Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-12-06 Thread Jacob Quinn
Thanks kou,

I think I've got all the details summarized in [this issue](
https://github.com/JuliaData/Arrow.jl/issues/265) where we'll track
progress on the required CLAs. I've also reached out to the
individuals directly about signing the CLAs.

-Jacob

On Fri, Dec 3, 2021 at 4:02 PM Sutou Kouhei  wrote:

> Hi Jacob,
>
> Thanks for helping this!
>
> I'm filling IP clearance form:
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/arrow-julia-library2.xml
>
> (I think that we can see it at
> https://incubator.apache.org/ip-clearance/arrow-julia-library2.html
> soon.)
>
> Could you stop merging any pull requests until this IP
> clearance is finished? (I think that it's acceptable because
> the last commit of https://github.com/JuliaData/Arrow.jl is
> 2021-11-02.)
>
> Here are TODO items:
>
>   1. Check that all active committers have a signed CLA on record.
>
>   2. Remind active committers that they are responsible for
>  ensuring that a Corporate CLA is recorded if such is
>  required to authorize their contributions under their
>  individual CLA.
>
> I think that people who commit after
> https://incubator.apache.org/ip-clearance/arrow-julia-library.html
> (8583da8a84a9e355affb42654dcd8c765bcc3134) are target:
>
> $ git shortlog -sn
> 8583da8a84a9e355affb42654dcd8c765bcc3134..1447cb2b13b728729f9a89760ac07a848e31e599
> 53  Jacob Quinn
> 16  Jarrett Revels
> 10  Curtis Vogt
>  8  Eric Hanson
>  2  Douglas Bates
>  2  ExpandingMan
>  2  Kristoffer Carlsson
>  1  Damien Drix
>  1  Denis Barucic
>  1  Jon Alm Eriksen
>  1  KronosTheLate
>  1  Nick Robinson
>  1  Pietro Vertechi
>  1  Simeon Schaub
>  1  Tanmay Mohapatra
>  1  Étienne Tétreault-Pinard
>
> According to the discussion in Ballista's IP clearance process,
>   https://lists.apache.org/thread/k0k7x3rrg56nk8s2c1tvrrv76zl2b1m4
> we can remove people who has only 1 commit from the target list:
>
> 53  Jacob Quinn
> 16  Jarrett Revels
> 10  Curtis Vogt
>  8  Eric Hanson
>  2  Douglas Bates
>  2  ExpandingMan
>  2  Kristoffer Carlsson
>
> And we can also remove people who commit before
> (including) 8583da8a84a9e355affb42654dcd8c765bcc3134 because
> they signed CLA in the previous IP clearance:
>
> $ git shortlog -sn
> 16b729db74d78ecb010efab855c9e46c8052f59e..8583da8a84a9e355affb42654dcd8c765bcc3134
> | cat
>103  ExpandingMan
> 53  Jacob Quinn
>  4  David Anthoff
>  2  Jacob Adenbaum
>  2  Spencer Lyon
>  1  Graham Stark
>  1  John Myles White
>  1  Michael Savastio
>  1  TheCedarPrince
>
> So here is the target list:
>
> 16  Jarrett Revels
> 10  Curtis Vogt
>  8  Eric Hanson
>  2  Douglas Bates
>  2  Kristoffer Carlsson
>
> Jacob, could you ask them to sign CLA for the TODO item 1.?
> FYI: Ballista used a GitHub issue for this:
>
> https://github.com/ballista-compute/ballista/issues/646#issuecomment-806820971
>
> And could you also remind
>
> 53  Jacob Quinn
> 16  Jarrett Revels
> 10  Curtis Vogt
>  8  Eric Hanson
>  2  Douglas Bates
>  2  ExpandingMan
>  2  Kristoffer Carlsson
>
> that the TODO item 2.?
>
>
> Thanks,
> --
> kou
>
> In 
>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository
> and process" on Mon, 29 Nov 2021 20:43:32 -0700,
>   Jacob Quinn  wrote:
>
> > Thanks kou,
> >
> > I'm happy to help in any way I can. I think I know all the Arrow.jl
> > contributors personally, so I'm happy to reach out to them for whatever
> is
> > needed.
> >
> > -Jacob
> >
> > On Wed, Nov 24, 2021 at 1:04 AM Sutou Kouhei  wrote:
> >
> >> Hi,
> >>
> >> Sorry for not working on this. I asked this on
> >> gene...@incubator.apache.org [1] and got a reply that there
> >> is a project that use the GitHub's transfer repository
> >> feature [2].
> >>
> >> Let's start IP clearance process against
> >> https://github.com/JuliaData/Arrow.jl and use the GitHub's
> >> transfer repository feature after the IP clearance is
> >> passed.
> >>
> >> Are there any people who help this process? I think that we
> >> need to fill IP clearance form based on
> >> https://incubator.apache.org/ip-clearance/ip-clearance-template.html
> >> .
> >>
> >>
> >> [1] https://lists.apache.org/thread/6nqbzkp4owt43l66283d55302mjrjkzf
> >> [2] https://lists.apache.org/thread/15fx1j0zdnwmxxr0zo1mjf34gjwkxxly
> >>
> >>
> >> Thanks,
> >> --
> >> kou
> >>
> >> In <20211013.053514.2154036949522056512@clear-code.com>
> >>   "Re: [RESULT][VOTE] Restart the Julia implementation with new
> repository
> >> and process" on Wed, 13 Oct 2021 05:35:14 +0900 (JST),
> >>   Sutou Kouhei  wrote:
> >>
> >> > Hi Jacob,
> >> >
> >> > It's a good idea if we can do this.
> >> >
> >> > Does anyone know where we can ask this?
> >> >
> >> > gene...@incubator.apache.org ?
> >> > https://lists.apache.org/list.html?gene...@incubator.apache.org
> >> >
> >> > INFRA JIRA?
> >> > 

Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-12-03 Thread Sutou Kouhei
Hi Jacob,

Thanks for helping this!

I'm filling IP clearance form:
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/arrow-julia-library2.xml

(I think that we can see it at
https://incubator.apache.org/ip-clearance/arrow-julia-library2.html
soon.)

Could you stop merging any pull requests until this IP
clearance is finished? (I think that it's acceptable because
the last commit of https://github.com/JuliaData/Arrow.jl is
2021-11-02.)

Here are TODO items:

  1. Check that all active committers have a signed CLA on record.

  2. Remind active committers that they are responsible for
 ensuring that a Corporate CLA is recorded if such is
 required to authorize their contributions under their
 individual CLA.

I think that people who commit after
https://incubator.apache.org/ip-clearance/arrow-julia-library.html
(8583da8a84a9e355affb42654dcd8c765bcc3134) are target:

$ git shortlog -sn 
8583da8a84a9e355affb42654dcd8c765bcc3134..1447cb2b13b728729f9a89760ac07a848e31e599
53  Jacob Quinn
16  Jarrett Revels
10  Curtis Vogt
 8  Eric Hanson
 2  Douglas Bates
 2  ExpandingMan
 2  Kristoffer Carlsson
 1  Damien Drix
 1  Denis Barucic
 1  Jon Alm Eriksen
 1  KronosTheLate
 1  Nick Robinson
 1  Pietro Vertechi
 1  Simeon Schaub
 1  Tanmay Mohapatra
 1  Étienne Tétreault-Pinard

According to the discussion in Ballista's IP clearance process,
  https://lists.apache.org/thread/k0k7x3rrg56nk8s2c1tvrrv76zl2b1m4
we can remove people who has only 1 commit from the target list:

53  Jacob Quinn
16  Jarrett Revels
10  Curtis Vogt
 8  Eric Hanson
 2  Douglas Bates
 2  ExpandingMan
 2  Kristoffer Carlsson

And we can also remove people who commit before
(including) 8583da8a84a9e355affb42654dcd8c765bcc3134 because
they signed CLA in the previous IP clearance:

$ git shortlog -sn 
16b729db74d78ecb010efab855c9e46c8052f59e..8583da8a84a9e355affb42654dcd8c765bcc3134
 | cat   
   103  ExpandingMan
53  Jacob Quinn
 4  David Anthoff
 2  Jacob Adenbaum
 2  Spencer Lyon
 1  Graham Stark
 1  John Myles White
 1  Michael Savastio
 1  TheCedarPrince

So here is the target list:

16  Jarrett Revels
10  Curtis Vogt
 8  Eric Hanson
 2  Douglas Bates
 2  Kristoffer Carlsson

Jacob, could you ask them to sign CLA for the TODO item 1.?
FYI: Ballista used a GitHub issue for this:
https://github.com/ballista-compute/ballista/issues/646#issuecomment-806820971

And could you also remind

53  Jacob Quinn
16  Jarrett Revels
10  Curtis Vogt
 8  Eric Hanson
 2  Douglas Bates
 2  ExpandingMan
 2  Kristoffer Carlsson

that the TODO item 2.?


Thanks,
-- 
kou

In 
  "Re: [RESULT][VOTE] Restart the Julia implementation with new repository and 
process" on Mon, 29 Nov 2021 20:43:32 -0700,
  Jacob Quinn  wrote:

> Thanks kou,
> 
> I'm happy to help in any way I can. I think I know all the Arrow.jl
> contributors personally, so I'm happy to reach out to them for whatever is
> needed.
> 
> -Jacob
> 
> On Wed, Nov 24, 2021 at 1:04 AM Sutou Kouhei  wrote:
> 
>> Hi,
>>
>> Sorry for not working on this. I asked this on
>> gene...@incubator.apache.org [1] and got a reply that there
>> is a project that use the GitHub's transfer repository
>> feature [2].
>>
>> Let's start IP clearance process against
>> https://github.com/JuliaData/Arrow.jl and use the GitHub's
>> transfer repository feature after the IP clearance is
>> passed.
>>
>> Are there any people who help this process? I think that we
>> need to fill IP clearance form based on
>> https://incubator.apache.org/ip-clearance/ip-clearance-template.html
>> .
>>
>>
>> [1] https://lists.apache.org/thread/6nqbzkp4owt43l66283d55302mjrjkzf
>> [2] https://lists.apache.org/thread/15fx1j0zdnwmxxr0zo1mjf34gjwkxxly
>>
>>
>> Thanks,
>> --
>> kou
>>
>> In <20211013.053514.2154036949522056512@clear-code.com>
>>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository
>> and process" on Wed, 13 Oct 2021 05:35:14 +0900 (JST),
>>   Sutou Kouhei  wrote:
>>
>> > Hi Jacob,
>> >
>> > It's a good idea if we can do this.
>> >
>> > Does anyone know where we can ask this?
>> >
>> > gene...@incubator.apache.org ?
>> > https://lists.apache.org/list.html?gene...@incubator.apache.org
>> >
>> > INFRA JIRA?
>> > https://issues.apache.org/jira/projects/INFRA
>> >
>> > Or ...?
>> >
>> >
>> > It seems that we can use existing GitHub repository's
>> > codebase for IP clearance. Some items listed in
>> > https://incubator.apache.org/ip-clearance/ does so such as
>> > https://incubator.apache.org/ip-clearance/daffodil-vscode-debugger
>> > .
>> >
>> >
>> > Thanks,
>> > --
>> > kou
>> >
>> > In 
>> >   "Re: [RESULT][VOTE] Restart the Julia implementation with new
>> repository and process" on Tue, 12 Oct 2021 09:24:36 -0600,
>> >   Jacob Quinn  wrote:
>> >
>> >> Hi kou,
>> >>
>> >> I'm looking into the next steps and 

Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-11-29 Thread Jacob Quinn
Thanks kou,

I'm happy to help in any way I can. I think I know all the Arrow.jl
contributors personally, so I'm happy to reach out to them for whatever is
needed.

-Jacob

On Wed, Nov 24, 2021 at 1:04 AM Sutou Kouhei  wrote:

> Hi,
>
> Sorry for not working on this. I asked this on
> gene...@incubator.apache.org [1] and got a reply that there
> is a project that use the GitHub's transfer repository
> feature [2].
>
> Let's start IP clearance process against
> https://github.com/JuliaData/Arrow.jl and use the GitHub's
> transfer repository feature after the IP clearance is
> passed.
>
> Are there any people who help this process? I think that we
> need to fill IP clearance form based on
> https://incubator.apache.org/ip-clearance/ip-clearance-template.html
> .
>
>
> [1] https://lists.apache.org/thread/6nqbzkp4owt43l66283d55302mjrjkzf
> [2] https://lists.apache.org/thread/15fx1j0zdnwmxxr0zo1mjf34gjwkxxly
>
>
> Thanks,
> --
> kou
>
> In <20211013.053514.2154036949522056512@clear-code.com>
>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository
> and process" on Wed, 13 Oct 2021 05:35:14 +0900 (JST),
>   Sutou Kouhei  wrote:
>
> > Hi Jacob,
> >
> > It's a good idea if we can do this.
> >
> > Does anyone know where we can ask this?
> >
> > gene...@incubator.apache.org ?
> > https://lists.apache.org/list.html?gene...@incubator.apache.org
> >
> > INFRA JIRA?
> > https://issues.apache.org/jira/projects/INFRA
> >
> > Or ...?
> >
> >
> > It seems that we can use existing GitHub repository's
> > codebase for IP clearance. Some items listed in
> > https://incubator.apache.org/ip-clearance/ does so such as
> > https://incubator.apache.org/ip-clearance/daffodil-vscode-debugger
> > .
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In 
> >   "Re: [RESULT][VOTE] Restart the Julia implementation with new
> repository and process" on Tue, 12 Oct 2021 09:24:36 -0600,
> >   Jacob Quinn  wrote:
> >
> >> Hi kou,
> >>
> >> I'm looking into the next steps and wondering if it's possible to use
> the
> >> Github mechanism of "transferring a repository" (
> >>
> https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository
> ),
> >> since that could simplify a lot of things. It would retain existing
> github
> >> actions CI and other repository settings, auto-generate a redirect from
> the
> >> existing JuliaData/Arrow.jl repo, and completely preserve the commit/git
> >> history already in place.
> >>
> >> Do we know if this is a possibility? I realize we'd need to do the IP
> >> clearance before transferring, which is fine; just wondering if we can
> >> leverage this functionality from github?
> >>
> >> On Sat, Oct 2, 2021 at 11:19 PM Sutou Kouhei 
> wrote:
> >>
> >>> Hi Jacob,
> >>>
> >>> Could you open a pull request to import
> >>> https://github.com/JuliaData/Arrow.jl on
> >>> https://github.com/apache/arrow-julia like
> >>> https://github.com/apache/arrow/pull/8547 ?
> >>>
> >>>
> >>> Thanks,
> >>> --
> >>> kou
> >>>
> >>> In <20211003.140948.2107475918212883624@clear-code.com>
> >>>   "Re: [RESULT][VOTE] Restart the Julia implementation with new
> repository
> >>> and process" on Sun, 03 Oct 2021 14:09:48 +0900 (JST),
> >>>   Sutou Kouhei  wrote:
> >>>
> >>> > Hi,
> >>> >
> >>> >>   * GitHub notification list: comm...@arrow.apache.org
> >>> >
> >>> > I should have used git...@arrow.apache.org for this. I've
> >>> > fixed this by pushing .asf.yaml to apache/arrow-julia:
> >>> >
> >>> >   https://github.com/apache/arrow-julia/blob/main/.asf.yaml
> >>> >
> >>> > I needed to use
> >>> > https://gitbox.apache.org/repos/asf/arrow-julia.git for the
> >>> > first push. I couldn't use
> >>> > g...@github.com:apache/arrow-julia.git .
> >>> >
> >>> >
> >>> > Thanks,
> >>> > --
> >>> > kou
> >>> >
> >>> > In <20211003.134022.661649063345488310@clear-code.com>
> >>> >   "Re: [RESULT][VOTE] Restart the Julia implementation with new
> >>> repository and process" on Sun, 03 Oct 2021 13:40:22 +0900 (JST),
> >>> >   Sutou Kouhei  wrote:
> >>> >
> >>> >> Hi,
> >>> >>
> >>> >> I've created apache/arrow-julia from
> >>> >> https://gitbox.apache.org/setup/newrepo.html with:
> >>> >>
> >>> >>   * PMC: arrow
> >>> >>   * Repository name: julia
> >>> >>   * Generated name: arrow-jlia.git
> >>> >>   * Repository description: Apache Arrow Julia
> >>> >>   * Commit notification list: comm...@arrow.apache.org
> >>> >>   * GitHub notification list: comm...@arrow.apache.org
> >>> >>
> >>> >> Thanks,
> >>> >> --
> >>> >> kou
> >>> >>
> >>> >> In <20211003.132505.1038511014845186183@clear-code.com>
> >>> >>   "[RESULT][VOTE] Restart the Julia implementation with new
> repository
> >>> and process" on Sun, 03 Oct 2021 13:25:05 +0900 (JST),
> >>> >>   Sutou Kouhei  wrote:
> >>> >>
> >>> >>> Hi,
> >>> >>>
> >>> >>> The vote carries with 8 +1 binding votes, 3 +1 non-binding
> >>> >>> votes and no -1 votes.
> >>> >>>
> >>> >>> I'll create apache/arrow-julia and start IP clearance
> >>> >>> 

Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-11-24 Thread Sutou Kouhei
Hi,

Sorry for not working on this. I asked this on
gene...@incubator.apache.org [1] and got a reply that there
is a project that use the GitHub's transfer repository
feature [2].

Let's start IP clearance process against
https://github.com/JuliaData/Arrow.jl and use the GitHub's
transfer repository feature after the IP clearance is
passed.

Are there any people who help this process? I think that we
need to fill IP clearance form based on
https://incubator.apache.org/ip-clearance/ip-clearance-template.html
.


[1] https://lists.apache.org/thread/6nqbzkp4owt43l66283d55302mjrjkzf
[2] https://lists.apache.org/thread/15fx1j0zdnwmxxr0zo1mjf34gjwkxxly


Thanks,
-- 
kou

In <20211013.053514.2154036949522056512@clear-code.com>
  "Re: [RESULT][VOTE] Restart the Julia implementation with new repository and 
process" on Wed, 13 Oct 2021 05:35:14 +0900 (JST),
  Sutou Kouhei  wrote:

> Hi Jacob,
> 
> It's a good idea if we can do this.
> 
> Does anyone know where we can ask this?
> 
> gene...@incubator.apache.org ?
> https://lists.apache.org/list.html?gene...@incubator.apache.org
> 
> INFRA JIRA?
> https://issues.apache.org/jira/projects/INFRA
> 
> Or ...?
> 
> 
> It seems that we can use existing GitHub repository's
> codebase for IP clearance. Some items listed in
> https://incubator.apache.org/ip-clearance/ does so such as
> https://incubator.apache.org/ip-clearance/daffodil-vscode-debugger
> .
> 
> 
> Thanks,
> -- 
> kou
> 
> In 
>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository 
> and process" on Tue, 12 Oct 2021 09:24:36 -0600,
>   Jacob Quinn  wrote:
> 
>> Hi kou,
>> 
>> I'm looking into the next steps and wondering if it's possible to use the
>> Github mechanism of "transferring a repository" (
>> https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository),
>> since that could simplify a lot of things. It would retain existing github
>> actions CI and other repository settings, auto-generate a redirect from the
>> existing JuliaData/Arrow.jl repo, and completely preserve the commit/git
>> history already in place.
>> 
>> Do we know if this is a possibility? I realize we'd need to do the IP
>> clearance before transferring, which is fine; just wondering if we can
>> leverage this functionality from github?
>> 
>> On Sat, Oct 2, 2021 at 11:19 PM Sutou Kouhei  wrote:
>> 
>>> Hi Jacob,
>>>
>>> Could you open a pull request to import
>>> https://github.com/JuliaData/Arrow.jl on
>>> https://github.com/apache/arrow-julia like
>>> https://github.com/apache/arrow/pull/8547 ?
>>>
>>>
>>> Thanks,
>>> --
>>> kou
>>>
>>> In <20211003.140948.2107475918212883624@clear-code.com>
>>>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository
>>> and process" on Sun, 03 Oct 2021 14:09:48 +0900 (JST),
>>>   Sutou Kouhei  wrote:
>>>
>>> > Hi,
>>> >
>>> >>   * GitHub notification list: comm...@arrow.apache.org
>>> >
>>> > I should have used git...@arrow.apache.org for this. I've
>>> > fixed this by pushing .asf.yaml to apache/arrow-julia:
>>> >
>>> >   https://github.com/apache/arrow-julia/blob/main/.asf.yaml
>>> >
>>> > I needed to use
>>> > https://gitbox.apache.org/repos/asf/arrow-julia.git for the
>>> > first push. I couldn't use
>>> > g...@github.com:apache/arrow-julia.git .
>>> >
>>> >
>>> > Thanks,
>>> > --
>>> > kou
>>> >
>>> > In <20211003.134022.661649063345488310@clear-code.com>
>>> >   "Re: [RESULT][VOTE] Restart the Julia implementation with new
>>> repository and process" on Sun, 03 Oct 2021 13:40:22 +0900 (JST),
>>> >   Sutou Kouhei  wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> I've created apache/arrow-julia from
>>> >> https://gitbox.apache.org/setup/newrepo.html with:
>>> >>
>>> >>   * PMC: arrow
>>> >>   * Repository name: julia
>>> >>   * Generated name: arrow-jlia.git
>>> >>   * Repository description: Apache Arrow Julia
>>> >>   * Commit notification list: comm...@arrow.apache.org
>>> >>   * GitHub notification list: comm...@arrow.apache.org
>>> >>
>>> >> Thanks,
>>> >> --
>>> >> kou
>>> >>
>>> >> In <20211003.132505.1038511014845186183@clear-code.com>
>>> >>   "[RESULT][VOTE] Restart the Julia implementation with new repository
>>> and process" on Sun, 03 Oct 2021 13:25:05 +0900 (JST),
>>> >>   Sutou Kouhei  wrote:
>>> >>
>>> >>> Hi,
>>> >>>
>>> >>> The vote carries with 8 +1 binding votes, 3 +1 non-binding
>>> >>> votes and no -1 votes.
>>> >>>
>>> >>> I'll create apache/arrow-julia and start IP clearance
>>> >>> process to import JuliaData/Arrow.jl to apache/arrow-julia.
>>> >>>
>>> >>>
>>> >>> Thanks,
>>> >>> --
>>> >>> kou
>>> >>>
>>> >>> In <20210927.115838.114416636593478@clear-code.com>
>>> >>>   "[VOTE] Restart the Julia implementation with new repository and
>>> process" on Mon, 27 Sep 2021 11:58:38 +0900 (JST),
>>> >>>   Sutou Kouhei  wrote:
>>> >>>
>>>  Hi,
>>> 
>>>  This vote is to determine if the Arrow PMC is in favor of
>>>  the Julia community moving the Julia implementation 

Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-10-12 Thread Sutou Kouhei
Hi Jacob,

It's a good idea if we can do this.

Does anyone know where we can ask this?

gene...@incubator.apache.org ?
https://lists.apache.org/list.html?gene...@incubator.apache.org

INFRA JIRA?
https://issues.apache.org/jira/projects/INFRA

Or ...?


It seems that we can use existing GitHub repository's
codebase for IP clearance. Some items listed in
https://incubator.apache.org/ip-clearance/ does so such as
https://incubator.apache.org/ip-clearance/daffodil-vscode-debugger
.


Thanks,
-- 
kou

In 
  "Re: [RESULT][VOTE] Restart the Julia implementation with new repository and 
process" on Tue, 12 Oct 2021 09:24:36 -0600,
  Jacob Quinn  wrote:

> Hi kou,
> 
> I'm looking into the next steps and wondering if it's possible to use the
> Github mechanism of "transferring a repository" (
> https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository),
> since that could simplify a lot of things. It would retain existing github
> actions CI and other repository settings, auto-generate a redirect from the
> existing JuliaData/Arrow.jl repo, and completely preserve the commit/git
> history already in place.
> 
> Do we know if this is a possibility? I realize we'd need to do the IP
> clearance before transferring, which is fine; just wondering if we can
> leverage this functionality from github?
> 
> On Sat, Oct 2, 2021 at 11:19 PM Sutou Kouhei  wrote:
> 
>> Hi Jacob,
>>
>> Could you open a pull request to import
>> https://github.com/JuliaData/Arrow.jl on
>> https://github.com/apache/arrow-julia like
>> https://github.com/apache/arrow/pull/8547 ?
>>
>>
>> Thanks,
>> --
>> kou
>>
>> In <20211003.140948.2107475918212883624@clear-code.com>
>>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository
>> and process" on Sun, 03 Oct 2021 14:09:48 +0900 (JST),
>>   Sutou Kouhei  wrote:
>>
>> > Hi,
>> >
>> >>   * GitHub notification list: comm...@arrow.apache.org
>> >
>> > I should have used git...@arrow.apache.org for this. I've
>> > fixed this by pushing .asf.yaml to apache/arrow-julia:
>> >
>> >   https://github.com/apache/arrow-julia/blob/main/.asf.yaml
>> >
>> > I needed to use
>> > https://gitbox.apache.org/repos/asf/arrow-julia.git for the
>> > first push. I couldn't use
>> > g...@github.com:apache/arrow-julia.git .
>> >
>> >
>> > Thanks,
>> > --
>> > kou
>> >
>> > In <20211003.134022.661649063345488310@clear-code.com>
>> >   "Re: [RESULT][VOTE] Restart the Julia implementation with new
>> repository and process" on Sun, 03 Oct 2021 13:40:22 +0900 (JST),
>> >   Sutou Kouhei  wrote:
>> >
>> >> Hi,
>> >>
>> >> I've created apache/arrow-julia from
>> >> https://gitbox.apache.org/setup/newrepo.html with:
>> >>
>> >>   * PMC: arrow
>> >>   * Repository name: julia
>> >>   * Generated name: arrow-jlia.git
>> >>   * Repository description: Apache Arrow Julia
>> >>   * Commit notification list: comm...@arrow.apache.org
>> >>   * GitHub notification list: comm...@arrow.apache.org
>> >>
>> >> Thanks,
>> >> --
>> >> kou
>> >>
>> >> In <20211003.132505.1038511014845186183@clear-code.com>
>> >>   "[RESULT][VOTE] Restart the Julia implementation with new repository
>> and process" on Sun, 03 Oct 2021 13:25:05 +0900 (JST),
>> >>   Sutou Kouhei  wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> The vote carries with 8 +1 binding votes, 3 +1 non-binding
>> >>> votes and no -1 votes.
>> >>>
>> >>> I'll create apache/arrow-julia and start IP clearance
>> >>> process to import JuliaData/Arrow.jl to apache/arrow-julia.
>> >>>
>> >>>
>> >>> Thanks,
>> >>> --
>> >>> kou
>> >>>
>> >>> In <20210927.115838.114416636593478@clear-code.com>
>> >>>   "[VOTE] Restart the Julia implementation with new repository and
>> process" on Mon, 27 Sep 2021 11:58:38 +0900 (JST),
>> >>>   Sutou Kouhei  wrote:
>> >>>
>>  Hi,
>> 
>>  This vote is to determine if the Arrow PMC is in favor of
>>  the Julia community moving the Julia implementation of
>>  Apache Arrow out of apache/arrow into apache/arrow-julia.
>> 
>>  The Julia community uses a process like the Rust community
>>  uses [1][2].
>> 
>>  Here is a summary of the process:
>> 
>>    1. Use GitHub instead of JIRA for issue management platform
>> 
>>   Note: Contributors will be required to write issues for
>>   planned features and bug fixes so that we have
>>   visibility and opportunities for collaboration before a
>>   PR shows up.
>> 
>>   (This is for the Apache way.)
>> 
>>   [1]
>> 
>>    2. Release on demand
>> 
>>   Like DataFusion.
>> 
>>   Release for apache/arrow doesn't include the Julia
>>   implementation.
>> 
>>   The Julia implementation uses separated version
>>   scheme. (apache/arrow uses 6.0.0 as the next version
>>   but the next Julia implementation release doesn't use
>>   6.0.0.)
>> 
>>   [2]
>> 
>>  We'll 

Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-10-12 Thread Jacob Quinn
Hi kou,

I'm looking into the next steps and wondering if it's possible to use the
Github mechanism of "transferring a repository" (
https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository),
since that could simplify a lot of things. It would retain existing github
actions CI and other repository settings, auto-generate a redirect from the
existing JuliaData/Arrow.jl repo, and completely preserve the commit/git
history already in place.

Do we know if this is a possibility? I realize we'd need to do the IP
clearance before transferring, which is fine; just wondering if we can
leverage this functionality from github?

On Sat, Oct 2, 2021 at 11:19 PM Sutou Kouhei  wrote:

> Hi Jacob,
>
> Could you open a pull request to import
> https://github.com/JuliaData/Arrow.jl on
> https://github.com/apache/arrow-julia like
> https://github.com/apache/arrow/pull/8547 ?
>
>
> Thanks,
> --
> kou
>
> In <20211003.140948.2107475918212883624@clear-code.com>
>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository
> and process" on Sun, 03 Oct 2021 14:09:48 +0900 (JST),
>   Sutou Kouhei  wrote:
>
> > Hi,
> >
> >>   * GitHub notification list: comm...@arrow.apache.org
> >
> > I should have used git...@arrow.apache.org for this. I've
> > fixed this by pushing .asf.yaml to apache/arrow-julia:
> >
> >   https://github.com/apache/arrow-julia/blob/main/.asf.yaml
> >
> > I needed to use
> > https://gitbox.apache.org/repos/asf/arrow-julia.git for the
> > first push. I couldn't use
> > g...@github.com:apache/arrow-julia.git .
> >
> >
> > Thanks,
> > --
> > kou
> >
> > In <20211003.134022.661649063345488310@clear-code.com>
> >   "Re: [RESULT][VOTE] Restart the Julia implementation with new
> repository and process" on Sun, 03 Oct 2021 13:40:22 +0900 (JST),
> >   Sutou Kouhei  wrote:
> >
> >> Hi,
> >>
> >> I've created apache/arrow-julia from
> >> https://gitbox.apache.org/setup/newrepo.html with:
> >>
> >>   * PMC: arrow
> >>   * Repository name: julia
> >>   * Generated name: arrow-jlia.git
> >>   * Repository description: Apache Arrow Julia
> >>   * Commit notification list: comm...@arrow.apache.org
> >>   * GitHub notification list: comm...@arrow.apache.org
> >>
> >> Thanks,
> >> --
> >> kou
> >>
> >> In <20211003.132505.1038511014845186183@clear-code.com>
> >>   "[RESULT][VOTE] Restart the Julia implementation with new repository
> and process" on Sun, 03 Oct 2021 13:25:05 +0900 (JST),
> >>   Sutou Kouhei  wrote:
> >>
> >>> Hi,
> >>>
> >>> The vote carries with 8 +1 binding votes, 3 +1 non-binding
> >>> votes and no -1 votes.
> >>>
> >>> I'll create apache/arrow-julia and start IP clearance
> >>> process to import JuliaData/Arrow.jl to apache/arrow-julia.
> >>>
> >>>
> >>> Thanks,
> >>> --
> >>> kou
> >>>
> >>> In <20210927.115838.114416636593478@clear-code.com>
> >>>   "[VOTE] Restart the Julia implementation with new repository and
> process" on Mon, 27 Sep 2021 11:58:38 +0900 (JST),
> >>>   Sutou Kouhei  wrote:
> >>>
>  Hi,
> 
>  This vote is to determine if the Arrow PMC is in favor of
>  the Julia community moving the Julia implementation of
>  Apache Arrow out of apache/arrow into apache/arrow-julia.
> 
>  The Julia community uses a process like the Rust community
>  uses [1][2].
> 
>  Here is a summary of the process:
> 
>    1. Use GitHub instead of JIRA for issue management platform
> 
>   Note: Contributors will be required to write issues for
>   planned features and bug fixes so that we have
>   visibility and opportunities for collaboration before a
>   PR shows up.
> 
>   (This is for the Apache way.)
> 
>   [1]
> 
>    2. Release on demand
> 
>   Like DataFusion.
> 
>   Release for apache/arrow doesn't include the Julia
>   implementation.
> 
>   The Julia implementation uses separated version
>   scheme. (apache/arrow uses 6.0.0 as the next version
>   but the next Julia implementation release doesn't use
>   6.0.0.)
> 
>   [2]
> 
>  We'll create apache/arrow-julia and start IP clearance
>  process to import JuliaData/Arrow.jl to apache/arrow after
>  the vote is passed. (We don't use julia/arrow/ in
>  apache/arrow.)
> 
>  See also discussions about this: [3][4]
> 
> 
>  Please vote whether to accept the proposal and allow the
>  Julia community to proceed with the work.
> 
>  The vote will be open for at least 72 hours.
> 
>  [ ] +1 : Accept the proposal
>  [ ] 0 : No opinion
>  [ ] -1 : Reject proposal because...
> 
> 
>  [1]
> https://docs.google.com/document/d/1TyrUP8_UWXqk97a8Hvb1d0UYWigch0HAephIjW7soSI/edit
>  [2]
> https://github.com/apache/arrow-datafusion/blob/master/dev/release/README.md
>  [3]
> 

Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-10-02 Thread Sutou Kouhei
Hi Jacob,

Could you open a pull request to import
https://github.com/JuliaData/Arrow.jl on
https://github.com/apache/arrow-julia like
https://github.com/apache/arrow/pull/8547 ?


Thanks,
-- 
kou

In <20211003.140948.2107475918212883624@clear-code.com>
  "Re: [RESULT][VOTE] Restart the Julia implementation with new repository and 
process" on Sun, 03 Oct 2021 14:09:48 +0900 (JST),
  Sutou Kouhei  wrote:

> Hi,
> 
>>   * GitHub notification list: comm...@arrow.apache.org
> 
> I should have used git...@arrow.apache.org for this. I've
> fixed this by pushing .asf.yaml to apache/arrow-julia:
> 
>   https://github.com/apache/arrow-julia/blob/main/.asf.yaml
> 
> I needed to use
> https://gitbox.apache.org/repos/asf/arrow-julia.git for the
> first push. I couldn't use
> g...@github.com:apache/arrow-julia.git .
> 
> 
> Thanks,
> -- 
> kou
> 
> In <20211003.134022.661649063345488310@clear-code.com>
>   "Re: [RESULT][VOTE] Restart the Julia implementation with new repository 
> and process" on Sun, 03 Oct 2021 13:40:22 +0900 (JST),
>   Sutou Kouhei  wrote:
> 
>> Hi,
>> 
>> I've created apache/arrow-julia from
>> https://gitbox.apache.org/setup/newrepo.html with:
>> 
>>   * PMC: arrow
>>   * Repository name: julia
>>   * Generated name: arrow-jlia.git
>>   * Repository description: Apache Arrow Julia
>>   * Commit notification list: comm...@arrow.apache.org
>>   * GitHub notification list: comm...@arrow.apache.org
>> 
>> Thanks,
>> -- 
>> kou
>> 
>> In <20211003.132505.1038511014845186183@clear-code.com>
>>   "[RESULT][VOTE] Restart the Julia implementation with new repository and 
>> process" on Sun, 03 Oct 2021 13:25:05 +0900 (JST),
>>   Sutou Kouhei  wrote:
>> 
>>> Hi,
>>> 
>>> The vote carries with 8 +1 binding votes, 3 +1 non-binding
>>> votes and no -1 votes.
>>> 
>>> I'll create apache/arrow-julia and start IP clearance
>>> process to import JuliaData/Arrow.jl to apache/arrow-julia.
>>> 
>>> 
>>> Thanks,
>>> -- 
>>> kou
>>> 
>>> In <20210927.115838.114416636593478@clear-code.com>
>>>   "[VOTE] Restart the Julia implementation with new repository and process" 
>>> on Mon, 27 Sep 2021 11:58:38 +0900 (JST),
>>>   Sutou Kouhei  wrote:
>>> 
 Hi,
 
 This vote is to determine if the Arrow PMC is in favor of
 the Julia community moving the Julia implementation of
 Apache Arrow out of apache/arrow into apache/arrow-julia.
 
 The Julia community uses a process like the Rust community
 uses [1][2].
 
 Here is a summary of the process:
 
   1. Use GitHub instead of JIRA for issue management platform
 
  Note: Contributors will be required to write issues for
  planned features and bug fixes so that we have
  visibility and opportunities for collaboration before a
  PR shows up.
 
  (This is for the Apache way.)
 
  [1]
 
   2. Release on demand
 
  Like DataFusion.
 
  Release for apache/arrow doesn't include the Julia
  implementation.
 
  The Julia implementation uses separated version
  scheme. (apache/arrow uses 6.0.0 as the next version
  but the next Julia implementation release doesn't use
  6.0.0.)
 
  [2]
 
 We'll create apache/arrow-julia and start IP clearance
 process to import JuliaData/Arrow.jl to apache/arrow after
 the vote is passed. (We don't use julia/arrow/ in
 apache/arrow.)
 
 See also discussions about this: [3][4]
 
 
 Please vote whether to accept the proposal and allow the
 Julia community to proceed with the work.
 
 The vote will be open for at least 72 hours.
 
 [ ] +1 : Accept the proposal
 [ ] 0 : No opinion
 [ ] -1 : Reject proposal because...
 
 
 [1] 
 https://docs.google.com/document/d/1TyrUP8_UWXqk97a8Hvb1d0UYWigch0HAephIjW7soSI/edit
 [2] 
 https://github.com/apache/arrow-datafusion/blob/master/dev/release/README.md
 [3] 
 https://lists.apache.org/x/thread.html/r6d91286686d92837fbe21dd042801a57e3a7b00b5903ea90a754ac7b%40%3Cdev.arrow.apache.org%3E
 [4] 
 https://lists.apache.org/x/thread.html/r0df7f44f7e1ed7f6e4352d34047d53076208aa78aad308e30b58f83a%40%3Cdev.arrow.apache.org%3E
 
 
 Thanks,
 -- 
 kou


Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-10-02 Thread Sutou Kouhei
Hi,

>   * GitHub notification list: comm...@arrow.apache.org

I should have used git...@arrow.apache.org for this. I've
fixed this by pushing .asf.yaml to apache/arrow-julia:

  https://github.com/apache/arrow-julia/blob/main/.asf.yaml

I needed to use
https://gitbox.apache.org/repos/asf/arrow-julia.git for the
first push. I couldn't use
g...@github.com:apache/arrow-julia.git .


Thanks,
-- 
kou

In <20211003.134022.661649063345488310@clear-code.com>
  "Re: [RESULT][VOTE] Restart the Julia implementation with new repository and 
process" on Sun, 03 Oct 2021 13:40:22 +0900 (JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> I've created apache/arrow-julia from
> https://gitbox.apache.org/setup/newrepo.html with:
> 
>   * PMC: arrow
>   * Repository name: julia
>   * Generated name: arrow-jlia.git
>   * Repository description: Apache Arrow Julia
>   * Commit notification list: comm...@arrow.apache.org
>   * GitHub notification list: comm...@arrow.apache.org
> 
> Thanks,
> -- 
> kou
> 
> In <20211003.132505.1038511014845186183@clear-code.com>
>   "[RESULT][VOTE] Restart the Julia implementation with new repository and 
> process" on Sun, 03 Oct 2021 13:25:05 +0900 (JST),
>   Sutou Kouhei  wrote:
> 
>> Hi,
>> 
>> The vote carries with 8 +1 binding votes, 3 +1 non-binding
>> votes and no -1 votes.
>> 
>> I'll create apache/arrow-julia and start IP clearance
>> process to import JuliaData/Arrow.jl to apache/arrow-julia.
>> 
>> 
>> Thanks,
>> -- 
>> kou
>> 
>> In <20210927.115838.114416636593478@clear-code.com>
>>   "[VOTE] Restart the Julia implementation with new repository and process" 
>> on Mon, 27 Sep 2021 11:58:38 +0900 (JST),
>>   Sutou Kouhei  wrote:
>> 
>>> Hi,
>>> 
>>> This vote is to determine if the Arrow PMC is in favor of
>>> the Julia community moving the Julia implementation of
>>> Apache Arrow out of apache/arrow into apache/arrow-julia.
>>> 
>>> The Julia community uses a process like the Rust community
>>> uses [1][2].
>>> 
>>> Here is a summary of the process:
>>> 
>>>   1. Use GitHub instead of JIRA for issue management platform
>>> 
>>>  Note: Contributors will be required to write issues for
>>>  planned features and bug fixes so that we have
>>>  visibility and opportunities for collaboration before a
>>>  PR shows up.
>>> 
>>>  (This is for the Apache way.)
>>> 
>>>  [1]
>>> 
>>>   2. Release on demand
>>> 
>>>  Like DataFusion.
>>> 
>>>  Release for apache/arrow doesn't include the Julia
>>>  implementation.
>>> 
>>>  The Julia implementation uses separated version
>>>  scheme. (apache/arrow uses 6.0.0 as the next version
>>>  but the next Julia implementation release doesn't use
>>>  6.0.0.)
>>> 
>>>  [2]
>>> 
>>> We'll create apache/arrow-julia and start IP clearance
>>> process to import JuliaData/Arrow.jl to apache/arrow after
>>> the vote is passed. (We don't use julia/arrow/ in
>>> apache/arrow.)
>>> 
>>> See also discussions about this: [3][4]
>>> 
>>> 
>>> Please vote whether to accept the proposal and allow the
>>> Julia community to proceed with the work.
>>> 
>>> The vote will be open for at least 72 hours.
>>> 
>>> [ ] +1 : Accept the proposal
>>> [ ] 0 : No opinion
>>> [ ] -1 : Reject proposal because...
>>> 
>>> 
>>> [1] 
>>> https://docs.google.com/document/d/1TyrUP8_UWXqk97a8Hvb1d0UYWigch0HAephIjW7soSI/edit
>>> [2] 
>>> https://github.com/apache/arrow-datafusion/blob/master/dev/release/README.md
>>> [3] 
>>> https://lists.apache.org/x/thread.html/r6d91286686d92837fbe21dd042801a57e3a7b00b5903ea90a754ac7b%40%3Cdev.arrow.apache.org%3E
>>> [4] 
>>> https://lists.apache.org/x/thread.html/r0df7f44f7e1ed7f6e4352d34047d53076208aa78aad308e30b58f83a%40%3Cdev.arrow.apache.org%3E
>>> 
>>> 
>>> Thanks,
>>> -- 
>>> kou


Re: [RESULT][VOTE] Restart the Julia implementation with new repository and process

2021-10-02 Thread Sutou Kouhei
Hi,

I've created apache/arrow-julia from
https://gitbox.apache.org/setup/newrepo.html with:

  * PMC: arrow
  * Repository name: julia
  * Generated name: arrow-jlia.git
  * Repository description: Apache Arrow Julia
  * Commit notification list: comm...@arrow.apache.org
  * GitHub notification list: comm...@arrow.apache.org

Thanks,
-- 
kou

In <20211003.132505.1038511014845186183@clear-code.com>
  "[RESULT][VOTE] Restart the Julia implementation with new repository and 
process" on Sun, 03 Oct 2021 13:25:05 +0900 (JST),
  Sutou Kouhei  wrote:

> Hi,
> 
> The vote carries with 8 +1 binding votes, 3 +1 non-binding
> votes and no -1 votes.
> 
> I'll create apache/arrow-julia and start IP clearance
> process to import JuliaData/Arrow.jl to apache/arrow-julia.
> 
> 
> Thanks,
> -- 
> kou
> 
> In <20210927.115838.114416636593478@clear-code.com>
>   "[VOTE] Restart the Julia implementation with new repository and process" 
> on Mon, 27 Sep 2021 11:58:38 +0900 (JST),
>   Sutou Kouhei  wrote:
> 
>> Hi,
>> 
>> This vote is to determine if the Arrow PMC is in favor of
>> the Julia community moving the Julia implementation of
>> Apache Arrow out of apache/arrow into apache/arrow-julia.
>> 
>> The Julia community uses a process like the Rust community
>> uses [1][2].
>> 
>> Here is a summary of the process:
>> 
>>   1. Use GitHub instead of JIRA for issue management platform
>> 
>>  Note: Contributors will be required to write issues for
>>  planned features and bug fixes so that we have
>>  visibility and opportunities for collaboration before a
>>  PR shows up.
>> 
>>  (This is for the Apache way.)
>> 
>>  [1]
>> 
>>   2. Release on demand
>> 
>>  Like DataFusion.
>> 
>>  Release for apache/arrow doesn't include the Julia
>>  implementation.
>> 
>>  The Julia implementation uses separated version
>>  scheme. (apache/arrow uses 6.0.0 as the next version
>>  but the next Julia implementation release doesn't use
>>  6.0.0.)
>> 
>>  [2]
>> 
>> We'll create apache/arrow-julia and start IP clearance
>> process to import JuliaData/Arrow.jl to apache/arrow after
>> the vote is passed. (We don't use julia/arrow/ in
>> apache/arrow.)
>> 
>> See also discussions about this: [3][4]
>> 
>> 
>> Please vote whether to accept the proposal and allow the
>> Julia community to proceed with the work.
>> 
>> The vote will be open for at least 72 hours.
>> 
>> [ ] +1 : Accept the proposal
>> [ ] 0 : No opinion
>> [ ] -1 : Reject proposal because...
>> 
>> 
>> [1] 
>> https://docs.google.com/document/d/1TyrUP8_UWXqk97a8Hvb1d0UYWigch0HAephIjW7soSI/edit
>> [2] 
>> https://github.com/apache/arrow-datafusion/blob/master/dev/release/README.md
>> [3] 
>> https://lists.apache.org/x/thread.html/r6d91286686d92837fbe21dd042801a57e3a7b00b5903ea90a754ac7b%40%3Cdev.arrow.apache.org%3E
>> [4] 
>> https://lists.apache.org/x/thread.html/r0df7f44f7e1ed7f6e4352d34047d53076208aa78aad308e30b58f83a%40%3Cdev.arrow.apache.org%3E
>> 
>> 
>> Thanks,
>> -- 
>> kou