Discussion:
[NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org
Daniel Gruno
2018-12-07 16:52:36 UTC
Permalink
[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 ***@infra.apache.org, not your
project's dev list :-).



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Mechtilde
2018-12-07 17:08:39 UTC
Permalink
Hello

I know there is http://git.apache.org/openoffice.git/

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)
Post by 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.
- 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.
project's dev list :-).
---------------------------------------------------------------------
--
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
JD
2018-12-07 17:28:17 UTC
Permalink
Except that GIT is now owned by MS!!!!

I seriously DOUBT that MS will support a competitor to it's
office software on their "OWNED" enterprise website.

I think it would be a bad idea!!!
Post by Mechtilde
Hello
I know there is http://git.apache.org/openoffice.git/
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)
Post by 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.
- 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.
project's dev list :-).
---------------------------------------------------------------------
Peter Kovacs
2018-12-07 17:41:57 UTC
Permalink
I think you confuse Github [1] and git [2]. The first is a company that
offers a service. Microsoft bought and can influence business decisions.

The other is a technology where participants disclaim their copyrights
(please note that on GPL licenses not all copyrights are disclaimed. The
exception is to change the license.)

I simplify of course to make a point.


All the Best

Peter

[1] github.com

[2] https://git-scm.com/
Post by JD
Except that GIT is now owned by MS!!!!
I seriously DOUBT that MS will support a competitor to it's
office software on their "OWNED" enterprise website.
I think it would be a bad idea!!!
Post by Mechtilde
Hello
I know there is http://git.apache.org/openoffice.git/
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)
Post by 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.
- 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.
project's dev list :-).
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org
Dave Fisher
2018-12-07 17:50:04 UTC
Permalink
Git is open source. https://en.m.wikipedia.org/wiki/Git

GitHub was just acquired by Microsoft.

GitLab is an alternative to GitHub.

GitBox is a service from Apache Infrastructure to coordinate replication of GitHub with internal copies of everything in the Apache space. If GitHub were to go away then nothing is lost and a switch to something like GitLab is possible.


Sent from my iPhone
Post by JD
Except that GIT is now owned by MS!!!!
I seriously DOUBT that MS will support a competitor to it's
office software on their "OWNED" enterprise website.
Microsoft is not concerned about OpenOffice.

For example 50% of the VMs running on Azure are Linux.
Post by JD
I think it would be a bad idea!!!
GitHub repositories will be very convenient for our support configurations - forum, MediaWiki, and updates service.
Post by JD
Post by Mechtilde
Hello
I know there is http://git.apache.org/openoffice.git/
But I didn't know how it works or it should work.
I wonder what’s in there.
Post by JD
Post by Mechtilde
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.
I’m not sure, that’s up to the active developers.

It could make sense for language translations.

Regards,
Dave
Post by JD
Post by Mechtilde
Kind Regards
Mechtilde
(Member of the PMC)
Post by 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.
- 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.
project's dev list :-).
---------------------------------------------------------------------
Dave Fisher
2018-12-07 19:01:40 UTC
Permalink
Hi -
Post by Mechtilde
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 <***@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/***@1848414 13f79535-47bb-0310-9956-ffa450edef68

commit 23744e0c67a04df55971794b54a12afb90354627
Author: Mechtilde Stehmann <***@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/***@1848413 13f79535-47bb-0310-9956-ffa450edef68

commit 6891308ea2b55199eb36583780f62e25d5ac40d4

Regards,
Dave
Post by Mechtilde
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)
Post by 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.
- 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.
project's dev list :-).
---------------------------------------------------------------------
--
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
Dave Fisher
2018-12-07 19:26:38 UTC
Permalink
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
Hi -
Post by Mechtilde
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.
$ git log
commit 58e70bfd505f0598aa6d1cba4b725b43c963ff41 (HEAD -> trunk, origin/trunk, origin/HEAD)
Date: Fri Dec 7 18:30:38 2018 +0000
merged actual translation from pootle with actual code base in trunk for ru
commit 23744e0c67a04df55971794b54a12afb90354627
Date: Fri Dec 7 18:27:01 2018 +0000
merged actual translation from pootle with actual code base in trunk for ja
commit 6891308ea2b55199eb36583780f62e25d5ac40d4
Regards,
Dave
Post by Mechtilde
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)
Post by 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.
- 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.
project's dev list :-).
---------------------------------------------------------------------
--
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-***@openoffice.apache.org
For additional commands, e-mail: dev-***@openoffice.apache.org

Loading...