[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [NOTICE] Mandatory relocation of Apache git repositories on

No strong feelings, so +1 from me

John Campbell
Software Engineer

Cloudsoft | Bringing Business to the Cloud

E: John.campbell@xxxxxxxxxxxxxxxxx
M: 07779 576614
T: -

Need a hand with AWS? Get a Free Consultation.

> On 13 Dec 2018, at 09:31, Duncan Grant <duncan.grant@xxxxxxxxxxxx> wrote:
> +1
> On Wed, 12 Dec 2018 at 16:42 Richard Downer <richard@xxxxxxxxxx> wrote:
>> Brooklyn team,
>> Apart from myself, I don't think anyone has clearly come out in favour or
>> opposed to this. I'd rather we got consensus and moved to gitbox early - so
>> that if some people do object, we have time to work out the objections with
>> infra, before we are involuntarily moved.
>> Thoughts, anyone? Does this need a formal vote to get people responding?
>> Richard.
>> On Fri, 7 Dec 2018 at 16:54, Daniel Gruno <humbedooh@xxxxxxxxxx> wrote:
>>> Hello Apache projects,
>>> I am writing to you because you may have git repositories on the
>>> git-wip-us server, which is slated to be decommissioned in the coming
>>> months. All repositories will be moved to the new gitbox service which
>>> includes direct write access on github as well as the standard ASF
>>> commit access via
>>> ## Why this move? ##
>>> The move comes as a result of retiring the git-wip service, as the
>>> hardware it runs on is longing for retirement. In lieu of this, we
>>> have decided to consolidate the two services (git-wip and gitbox), to
>>> ease the management of our repository systems and future-proof the
>>> underlying hardware. The move is fully automated, and ideally, nothing
>>> will change in your workflow other than added features and access to
>>> GitHub.
>>> ## Timeframe for relocation ##
>>> Initially, we are asking that projects voluntarily request to move
>>> their repositories to gitbox, hence this email. The voluntary
>>> timeframe is between now and January 9th 2019, during which projects
>>> are free to either move over to gitbox or stay put on git-wip. After
>>> this phase, we will be requiring the remaining projects to move within
>>> one month, after which we will move the remaining projects over.
>>> To have your project moved in this initial phase, you will need:
>>> - Consensus in the project (documented via the mailing list)
>>> - File a JIRA ticket with INFRA to voluntarily move your project repos
>>>   over to gitbox (as stated, this is highly automated and will take
>>>   between a minute and an hour, depending on the size and number of
>>>   your repositories)
>>> To sum up the preliminary timeline;
>>> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
>>>   relocation
>>> - January 9th -> February 6th: Mandated (coordinated) relocation
>>> - February 7th: All remaining repositories are mass migrated.
>>> This timeline may change to accommodate various scenarios.
>>> ## Using GitHub with ASF repositories ##
>>> When your project has moved, you are free to use either the ASF
>>> repository system ( OR GitHub for your development
>>> and code pushes. To be able to use GitHub, please follow the primer
>>> at:
>>> We appreciate your understanding of this issue, and hope that your
>>> project can coordinate voluntarily moving your repositories in a
>>> timely manner.
>>> All settings, such as commit mail targets, issue linking, PR
>>> notification schemes etc will automatically be migrated to gitbox as
>>> well.
>>> With regards, Daniel on behalf of ASF Infra.
>>> PS:For inquiries, please reply to users@xxxxxxxxxxxxxxxx, not your
>>> project's dev list :-).
> -- 
> Duncan Grant
> Software Engineer
> *Cloudsoft <> *| Bringing Business to the Cloud
> Need a hand with AWS? Get a Free Consultation.
> <>