One more bit -

Our openoffice.git mirror of svn is not on git-wip-us.apache.org.

Before we switch from SVN to GitBox/GitHun for our main repository we will need 
to understand how to do the hooks to Bugzilla issues. I will use the setup of a 
Git repository for the Forum setup to figure that out.

Meanwhile we can get a sense from the Dev teams when they would want to switch 
early next year.

Regards,
Dave

> On Dec 7, 2018, at 11:01 AM, Dave Fisher <dave2w...@comcast.net> wrote:
> 
> Hi -
> 
>> On Dec 7, 2018, at 9:08 AM, Mechtilde <o...@mechtilde.de> wrote:
>> 
>> Hello
>> 
>> I know there is http://git.apache.org/openoffice.git/
> 
> I “cloned” this to my machine.
> 
> This looks like an update git mirror of svn.
> 
> I see your latest commits:
> 
> $ git log
> commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, origin/trunk, 
> origin/HEAD)
> Author: Mechtilde Stehmann <mechti...@apache.org>
> Date:   Fri Dec 7 18:30:38 2018 +0000
> 
>    merged actual translation from pootle with actual code base in trunk for ru
> 
>    git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848414 
> 13f79535-47bb-0310-9956-ffa450edef68
> 
> commit 23744e0c67a04df55971794b54a12afb90354627
> Author: Mechtilde Stehmann <mechti...@apache.org>
> Date:   Fri Dec 7 18:27:01 2018 +0000
> 
>    merged actual translation from pootle with actual code base in trunk for ja
> 
>    git-svn-id: https://svn.apache.org/repos/asf/openoffice/trunk@1848413 
> 13f79535-47bb-0310-9956-ffa450edef68
> 
> commit 6891308ea2b55199eb36583780f62e25d5ac40d4
> 
> Regards,
> Dave
> 
>> 
>> But I didn't know how it works or it should work.
>> 
>> I hope this is the time for our progejt to switch from svn to git as the
>> main repository.
>> We already discussed it several times in the past.
>> 
>> Kind Regards
>> 
>> Mechtilde
>> (Member of the PMC)
>> 
>> Am 07.12.18 um 17:52 schrieb Daniel Gruno:
>>> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
>>> DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
>>> 
>>> 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 gitbox.apache.org.
>>> 
>>> ## 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 (gitbox.apache.org) OR GitHub for your development
>>> and code pushes. To be able to use GitHub, please follow the primer
>>> at: https://reference.apache.org/committer/github
>>> 
>>> 
>>> 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 us...@infra.apache.org, not your
>>> project's dev list :-).
>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>> 
>> -- 
>> Mechtilde Stehmann
>> ## Apache OpenOffice
>> ## Freie Office Suite für Linux, MacOSX, Windows
>> ## Debian Developer
>> ## Loook, tbsync, libreoffice-canzeley-client
>> ## PGP encryption welcome
>> ## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F
>> 
> 


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

Reply via email to