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 <wu.sheng.841...@gmail.com> 
Sent: Wednesday, November 24, 2021 4:24 AM
To: Incubator <general@incubator.apache.org>
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 <wid...@gmail.com> 于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" <k...@clear-code.com> 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

Reply via email to