[Discussion] Switch to Git?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[Discussion] Switch to Git?

Damjan Jovanovic
Hi

Can we please switch to using Git instead of Subversion for AOO's source?

I don't know how much justification you want/need. Git is huge nowdays, by
far the most popular VCS worldwide, the one most developers know and IDEs
support (https://rhodecode.com/insights/version-control-systems-2016). It
would help us with local branches for testing and experimenting offline,
git bisect for regression testing, it's efficient with large projects, it
would integrate with GitHub better, etc.

What do people think?

Damjan
Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Patricia Shanahan
I know Git is the repository-of-the-decade, and therefore a switch to it
is probably inevitable, just like the switch from RCS to SCCS and from
SCCS to Subversion.

Just as a matter of curiosity, which IDE's do not support Subversion? I
know I was using a it with Eclipse before I heard of Git.

On 9/14/2017 4:10 AM, Damjan Jovanovic wrote:

> Hi
>
> Can we please switch to using Git instead of Subversion for AOO's source?
>
> I don't know how much justification you want/need. Git is huge nowdays, by
> far the most popular VCS worldwide, the one most developers know and IDEs
> support (https://rhodecode.com/insights/version-control-systems-2016). It
> would help us with local branches for testing and experimenting offline,
> git bisect for regression testing, it's efficient with large projects, it
> would integrate with GitHub better, etc.
>
> What do people think?
>
> Damjan
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Damjan Jovanovic
On Thu, Sep 14, 2017 at 2:59 PM, Patricia Shanahan <[hidden email]> wrote:

> I know Git is the repository-of-the-decade, and therefore a switch to it
> is probably inevitable, just like the switch from RCS to SCCS and from SCCS
> to Subversion.
>
> Just as a matter of curiosity, which IDE's do not support Subversion? I
> know I was using a it with Eclipse before I heard of Git.
>
>
Visual Studio Code only supports Git out of the box.
Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Dave Fisher
Hi -

Here is a difference between Git and SVN that could be important.

In GIT you check out the whole repository.
In SVN you can check out parts.

Another would be does SVN vs. GIT prevent new developers from volunteering?

Historical note - when OpenOffice came to Apache it had just been moved to Mercurial...

Regards,
Dave

> On Sep 14, 2017, at 6:32 AM, Damjan Jovanovic <[hidden email]> wrote:
>
> On Thu, Sep 14, 2017 at 2:59 PM, Patricia Shanahan <[hidden email]> wrote:
>
>> I know Git is the repository-of-the-decade, and therefore a switch to it
>> is probably inevitable, just like the switch from RCS to SCCS and from SCCS
>> to Subversion.
>>
>> Just as a matter of curiosity, which IDE's do not support Subversion? I
>> know I was using a it with Eclipse before I heard of Git.
>>
>>
> Visual Studio Code only supports Git out of the box.


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Raphael Bircher-3
In reply to this post by Damjan Jovanovic
+1

Am .09.2017, 13:10 Uhr, schrieb Damjan Jovanovic <[hidden email]>:

> Hi
>
> Can we please switch to using Git instead of Subversion for AOO's source?
>
> I don't know how much justification you want/need. Git is huge nowdays,  
> by
> far the most popular VCS worldwide, the one most developers know and IDEs
> support (https://rhodecode.com/insights/version-control-systems-2016). It
> would help us with local branches for testing and experimenting offline,
> git bisect for regression testing, it's efficient with large projects, it
> would integrate with GitHub better, etc.
>
> What do people think?
>
> Damjan


--
My introduction https://youtu.be/Ln4vly5sxYU

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Peter Kovacs-3
In reply to this post by Damjan Jovanovic

On 14.09.2017 13:10, Damjan Jovanovic wrote:

> Hi
>
> Can we please switch to using Git instead of Subversion for AOO's source?
>
> I don't know how much justification you want/need. Git is huge nowdays, by
> far the most popular VCS worldwide, the one most developers know and IDEs
> support (https://rhodecode.com/insights/version-control-systems-2016). It
> would help us with local branches for testing and experimenting offline,
> git bisect for regression testing, it's efficient with large projects, it
> would integrate with GitHub better, etc.
>
> What do people think?
>
> Damjan
>
As much as I prefer GIT for Codemaintenance, I think the central REPO
should be maintained by Apache Infra.
If Infra can move to git, fine. If they do not support it, it is also
fine to me.

I am at -1 to have our official REPO on GITHUB or another service provider.

And I am not sure if we can not work around the problem to commit to SVN
from a GIT repo.
Have to check.


All the best
Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Herbert Duerr-3
In reply to this post by Damjan Jovanovic
Hi,

FWIW we already have an official git mirror of our svn repository. Do a
        git clone git://git.apache.org/openoffice.git
to check it out. Such a repo is currently read-only of course until the
project switches officially to git.

Herbert

On 09/14/2017 11:10 AM, Damjan Jovanovic wrote:

> Hi
>
> Can we please switch to using Git instead of Subversion for AOO's source?
>
> I don't know how much justification you want/need. Git is huge nowdays, by
> far the most popular VCS worldwide, the one most developers know and IDEs
> support (https://rhodecode.com/insights/version-control-systems-2016). It
> would help us with local branches for testing and experimenting offline,
> git bisect for regression testing, it's efficient with large projects, it
> would integrate with GitHub better, etc.
>
> What do people think?
>
> Damjan


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Marcus (OOo)
In reply to this post by Peter Kovacs-3
Even when I'm not a real developer, please let me add some points:

IMHO we could switch when

- ASF Infra can and will support it
- the CMS (it manages the webpages) is supporting Git
- the big majority of us is wanting Git
- it is known how and save that the SVN commit history can be migrated
   to Git

PS:
As Apache project the code has to be at the ASF. I think it's not
possible to store it somewhere else like, e.g., GitHub.

Marcus



Am 14.09.2017 um 19:24 schrieb Peter Kovacs:

>
> On 14.09.2017 13:10, Damjan Jovanovic wrote:
>> Hi
>>
>> Can we please switch to using Git instead of Subversion for AOO's source?
>>
>> I don't know how much justification you want/need. Git is huge
>> nowdays, by
>> far the most popular VCS worldwide, the one most developers know and IDEs
>> support (https://rhodecode.com/insights/version-control-systems-2016). It
>> would help us with local branches for testing and experimenting offline,
>> git bisect for regression testing, it's efficient with large projects, it
>> would integrate with GitHub better, etc.
>>
>> What do people think?
>>
>> Damjan
>>
> As much as I prefer GIT for Codemaintenance, I think the central REPO
> should be maintained by Apache Infra.
> If Infra can move to git, fine. If they do not support it, it is also
> fine to me.
>
> I am at -1 to have our official REPO on GITHUB or another service provider.
>
> And I am not sure if we can not work around the problem to commit to SVN
> from a GIT repo.
> Have to check.
>
>
> All the best
> Peter


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Dave Fisher

> On Sep 14, 2017, at 11:16 AM, Marcus <[hidden email]> wrote:
>
> Even when I'm not a real developer, please let me add some points:
>
> IMHO we could switch when
>
> - ASF Infra can and will support it
> - the CMS (it manages the webpages) is supporting Git
> - the big majority of us is wanting Git
> - it is known how and save that the SVN commit history can be migrated
>  to Git
>
> PS:
> As Apache project the code has to be at the ASF. I think it's not possible to store it somewhere else like, e.g., GitHub.
GitBox is being experimented with and there are a few projects that use GitHub with the mirror being on the Apache side. Infra is not offering this to all. Ask Greg Stein about it.

Regards,
Dave


>
> Marcus
>
>
>
> Am 14.09.2017 um 19:24 schrieb Peter Kovacs:
>> On 14.09.2017 13:10, Damjan Jovanovic wrote:
>>> Hi
>>>
>>> Can we please switch to using Git instead of Subversion for AOO's source?
>>>
>>> I don't know how much justification you want/need. Git is huge nowdays, by
>>> far the most popular VCS worldwide, the one most developers know and IDEs
>>> support (https://rhodecode.com/insights/version-control-systems-2016). It
>>> would help us with local branches for testing and experimenting offline,
>>> git bisect for regression testing, it's efficient with large projects, it
>>> would integrate with GitHub better, etc.
>>>
>>> What do people think?
>>>
>>> Damjan
>>>
>> As much as I prefer GIT for Codemaintenance, I think the central REPO should be maintained by Apache Infra.
>> If Infra can move to git, fine. If they do not support it, it is also fine to me.
>> I am at -1 to have our official REPO on GITHUB or another service provider.
>> And I am not sure if we can not work around the problem to commit to SVN from a GIT repo.
>> Have to check.
>> All the best
>> Peter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


signature.asc (817 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Patricia Shanahan
In reply to this post by Marcus (OOo)
I would like to add one more condition: We should not move until the
process we will use has been applied successfully to smaller projects.

I am relatively neutral on the choice of repository, and a lot of people
seem to like Git.

On 9/14/2017 11:16 AM, Marcus wrote:

> Even when I'm not a real developer, please let me add some points:
>
> IMHO we could switch when
>
> - ASF Infra can and will support it
> - the CMS (it manages the webpages) is supporting Git
> - the big majority of us is wanting Git
> - it is known how and save that the SVN commit history can be migrated
>    to Git
>
> PS:
> As Apache project the code has to be at the ASF. I think it's not
> possible to store it somewhere else like, e.g., GitHub.
>
> Marcus
>
>
>
> Am 14.09.2017 um 19:24 schrieb Peter Kovacs:
>>
>> On 14.09.2017 13:10, Damjan Jovanovic wrote:
>>> Hi
>>>
>>> Can we please switch to using Git instead of Subversion for AOO's
>>> source?
>>>
>>> I don't know how much justification you want/need. Git is huge
>>> nowdays, by
>>> far the most popular VCS worldwide, the one most developers know and
>>> IDEs
>>> support
>>> (https://rhodecode.com/insights/version-control-systems-2016). It
>>> would help us with local branches for testing and experimenting offline,
>>> git bisect for regression testing, it's efficient with large
>>> projects, it
>>> would integrate with GitHub better, etc.
>>>
>>> What do people think?
>>>
>>> Damjan
>>>
>> As much as I prefer GIT for Codemaintenance, I think the central REPO
>> should be maintained by Apache Infra.
>> If Infra can move to git, fine. If they do not support it, it is also
>> fine to me.
>>
>> I am at -1 to have our official REPO on GITHUB or another service
>> provider.
>>
>> And I am not sure if we can not work around the problem to commit to
>> SVN from a GIT repo.
>> Have to check.
>>
>>
>> All the best
>> Peter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Damjan Jovanovic
The process is, we vote, then get Infra to switch us.

Many big and small Apache projects have switched to Git, eg. Apache Commons.

On Fri, Sep 15, 2017 at 4:26 AM, Patricia Shanahan <[hidden email]> wrote:

> I would like to add one more condition: We should not move until the
> process we will use has been applied successfully to smaller projects.
>
> I am relatively neutral on the choice of repository, and a lot of people
> seem to like Git.
>
>
> On 9/14/2017 11:16 AM, Marcus wrote:
>
>> Even when I'm not a real developer, please let me add some points:
>>
>> IMHO we could switch when
>>
>> - ASF Infra can and will support it
>> - the CMS (it manages the webpages) is supporting Git
>> - the big majority of us is wanting Git
>> - it is known how and save that the SVN commit history can be migrated
>>    to Git
>>
>> PS:
>> As Apache project the code has to be at the ASF. I think it's not
>> possible to store it somewhere else like, e.g., GitHub.
>>
>> Marcus
>>
>>
>>
>> Am 14.09.2017 um 19:24 schrieb Peter Kovacs:
>>
>>>
>>> On 14.09.2017 13:10, Damjan Jovanovic wrote:
>>>
>>>> Hi
>>>>
>>>> Can we please switch to using Git instead of Subversion for AOO's
>>>> source?
>>>>
>>>> I don't know how much justification you want/need. Git is huge nowdays,
>>>> by
>>>> far the most popular VCS worldwide, the one most developers know and
>>>> IDEs
>>>> support (https://rhodecode.com/insights/version-control-systems-2016).
>>>> It
>>>> would help us with local branches for testing and experimenting offline,
>>>> git bisect for regression testing, it's efficient with large projects,
>>>> it
>>>> would integrate with GitHub better, etc.
>>>>
>>>> What do people think?
>>>>
>>>> Damjan
>>>>
>>>> As much as I prefer GIT for Codemaintenance, I think the central REPO
>>> should be maintained by Apache Infra.
>>> If Infra can move to git, fine. If they do not support it, it is also
>>> fine to me.
>>>
>>> I am at -1 to have our official REPO on GITHUB or another service
>>> provider.
>>>
>>> And I am not sure if we can not work around the problem to commit to SVN
>>> from a GIT repo.
>>> Have to check.
>>>
>>>
>>> All the best
>>> Peter
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Dave Fisher
We must not block 4.1.4. We must release soon.

Regards,
Dave

Sent from my iPhone

> On Sep 14, 2017, at 7:36 PM, Damjan Jovanovic <[hidden email]> wrote:
>
> The process is, we vote, then get Infra to switch us.
>
> Many big and small Apache projects have switched to Git, eg. Apache Commons.
>
>> On Fri, Sep 15, 2017 at 4:26 AM, Patricia Shanahan <[hidden email]> wrote:
>>
>> I would like to add one more condition: We should not move until the
>> process we will use has been applied successfully to smaller projects.
>>
>> I am relatively neutral on the choice of repository, and a lot of people
>> seem to like Git.
>>
>>
>>> On 9/14/2017 11:16 AM, Marcus wrote:
>>>
>>> Even when I'm not a real developer, please let me add some points:
>>>
>>> IMHO we could switch when
>>>
>>> - ASF Infra can and will support it
>>> - the CMS (it manages the webpages) is supporting Git
>>> - the big majority of us is wanting Git
>>> - it is known how and save that the SVN commit history can be migrated
>>>   to Git
>>>
>>> PS:
>>> As Apache project the code has to be at the ASF. I think it's not
>>> possible to store it somewhere else like, e.g., GitHub.
>>>
>>> Marcus
>>>
>>>
>>>
>>>> Am 14.09.2017 um 19:24 schrieb Peter Kovacs:
>>>>
>>>>
>>>>> On 14.09.2017 13:10, Damjan Jovanovic wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Can we please switch to using Git instead of Subversion for AOO's
>>>>> source?
>>>>>
>>>>> I don't know how much justification you want/need. Git is huge nowdays,
>>>>> by
>>>>> far the most popular VCS worldwide, the one most developers know and
>>>>> IDEs
>>>>> support (https://rhodecode.com/insights/version-control-systems-2016).
>>>>> It
>>>>> would help us with local branches for testing and experimenting offline,
>>>>> git bisect for regression testing, it's efficient with large projects,
>>>>> it
>>>>> would integrate with GitHub better, etc.
>>>>>
>>>>> What do people think?
>>>>>
>>>>> Damjan
>>>>>
>>>>> As much as I prefer GIT for Codemaintenance, I think the central REPO
>>>> should be maintained by Apache Infra.
>>>> If Infra can move to git, fine. If they do not support it, it is also
>>>> fine to me.
>>>>
>>>> I am at -1 to have our official REPO on GITHUB or another service
>>>> provider.
>>>>
>>>> And I am not sure if we can not work around the problem to commit to SVN
>>>> from a GIT repo.
>>>> Have to check.
>>>>
>>>>
>>>> All the best
>>>> Peter
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Peter Kovacs-2
+1 in the release First Switch After.

Am 15. September 2017 04:51:29 MESZ schrieb Dave Fisher <[hidden email]>:

>We must not block 4.1.4. We must release soon.
>
>Regards,
>Dave
>
>Sent from my iPhone
>
>> On Sep 14, 2017, at 7:36 PM, Damjan Jovanovic <[hidden email]>
>wrote:
>>
>> The process is, we vote, then get Infra to switch us.
>>
>> Many big and small Apache projects have switched to Git, eg. Apache
>Commons.
>>
>>> On Fri, Sep 15, 2017 at 4:26 AM, Patricia Shanahan <[hidden email]>
>wrote:
>>>
>>> I would like to add one more condition: We should not move until the
>>> process we will use has been applied successfully to smaller
>projects.
>>>
>>> I am relatively neutral on the choice of repository, and a lot of
>people
>>> seem to like Git.
>>>
>>>
>>>> On 9/14/2017 11:16 AM, Marcus wrote:
>>>>
>>>> Even when I'm not a real developer, please let me add some points:
>>>>
>>>> IMHO we could switch when
>>>>
>>>> - ASF Infra can and will support it
>>>> - the CMS (it manages the webpages) is supporting Git
>>>> - the big majority of us is wanting Git
>>>> - it is known how and save that the SVN commit history can be
>migrated
>>>>   to Git
>>>>
>>>> PS:
>>>> As Apache project the code has to be at the ASF. I think it's not
>>>> possible to store it somewhere else like, e.g., GitHub.
>>>>
>>>> Marcus
>>>>
>>>>
>>>>
>>>>> Am 14.09.2017 um 19:24 schrieb Peter Kovacs:
>>>>>
>>>>>
>>>>>> On 14.09.2017 13:10, Damjan Jovanovic wrote:
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Can we please switch to using Git instead of Subversion for AOO's
>>>>>> source?
>>>>>>
>>>>>> I don't know how much justification you want/need. Git is huge
>nowdays,
>>>>>> by
>>>>>> far the most popular VCS worldwide, the one most developers know
>and
>>>>>> IDEs
>>>>>> support
>(https://rhodecode.com/insights/version-control-systems-2016).
>>>>>> It
>>>>>> would help us with local branches for testing and experimenting
>offline,
>>>>>> git bisect for regression testing, it's efficient with large
>projects,
>>>>>> it
>>>>>> would integrate with GitHub better, etc.
>>>>>>
>>>>>> What do people think?
>>>>>>
>>>>>> Damjan
>>>>>>
>>>>>> As much as I prefer GIT for Codemaintenance, I think the central
>REPO
>>>>> should be maintained by Apache Infra.
>>>>> If Infra can move to git, fine. If they do not support it, it is
>also
>>>>> fine to me.
>>>>>
>>>>> I am at -1 to have our official REPO on GITHUB or another service
>>>>> provider.
>>>>>
>>>>> And I am not sure if we can not work around the problem to commit
>to SVN
>>>>> from a GIT repo.
>>>>> Have to check.
>>>>>
>>>>>
>>>>> All the best
>>>>> Peter
>>>>>
>>>>
>>>>
>>>>
>---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Andrea Pescetti-2
In reply to this post by Dave Fisher
On 14/09/2017 Dave Fisher wrote:
> does SVN vs. GIT prevent new developers from volunteering?

I think this is the key question, even though there are many good points
also in what others replied.

We currently have a couple semi-official GIT mirrors: one on Github in
the ASF organization page and the internal one Herbert pointed out. I
also remember that Herbert once presented a big GIT repository he had
built with all the available history of the OpenOffice code, but I don't
know if it is available somewhere.

I believe that the interested developers (including me, at times) use
the git-svn tool when convenient. I think that this is enough to allow
the local workflow improvements Damjan was requesting. Or do you see
reasons not to use it?

As for the new developers, most new developers are probably familiar
with the "pull request" convention. This is not supported by either of
the current repositories, mostly due to ASF policy. Last time I checked,
Infra was still discussing how we can allow pull requests in a way that
complies with the policy and I have no idea whether this is resolved.
Once we have official support from Infra and a friendly pull request
system, this might indeed improve the approach for new developers.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Patricia Shanahan


On 9/17/2017 9:04 AM, Andrea Pescetti wrote:

> On 14/09/2017 Dave Fisher wrote:
>> does SVN vs. GIT prevent new developers from volunteering?
>
> I think this is the key question, even though there are many good points
> also in what others replied.
>
> We currently have a couple semi-official GIT mirrors: one on Github in
> the ASF organization page and the internal one Herbert pointed out. I
> also remember that Herbert once presented a big GIT repository he had
> built with all the available history of the OpenOffice code, but I don't
> know if it is available somewhere.
>
> I believe that the interested developers (including me, at times) use
> the git-svn tool when convenient. I think that this is enough to allow
> the local workflow improvements Damjan was requesting. Or do you see
> reasons not to use it?
>
> As for the new developers, most new developers are probably familiar
> with the "pull request" convention. This is not supported by either of
> the current repositories, mostly due to ASF policy. Last time I checked,
> Infra was still discussing how we can allow pull requests in a way that
> complies with the policy and I have no idea whether this is resolved.
> Once we have official support from Infra and a friendly pull request
> system, this might indeed improve the approach for new developers.

The big new developer issue may be lack of Subversion experience. Git
seems to be the repository-of-the-decade. In the past, people have
stopped learning about older repositories, so new developers only know
the current winner.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Andrea Pescetti-2
Patricia Shanahan wrote:
> The big new developer issue may be lack of Subversion experience. Git
> seems to be the repository-of-the-decade.

This can be circumvented by using git as follows:

$ git svn clone https://svn.apache.org/repos/asf/openoffice/branches/AOO414

and similar. I would honestly use one of the two mirrors I mentioned
earlier, but we could include a section describing these methods to get
the code without using a dedicated Subversion client.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Peter Kovacs-3
I failed using git svn clone ...
Git is doing some history scans that cause to run for forever. I have not found any way to circumvent that scan.

I have forked the apache repo on github and then pulled from there. That's an easier workflow for me.
What I miss is a push functionallity. But that's for me only convenience. I can work with git and svn. No issue for me.

So I am quite neutral on the topic.

All the best
Peter

Am 17. September 2017 20:12:13 MESZ schrieb Andrea Pescetti <[hidden email]>:

>Patricia Shanahan wrote:
>> The big new developer issue may be lack of Subversion experience. Git
>> seems to be the repository-of-the-decade.
>
>This can be circumvented by using git as follows:
>
>$ git svn clone
>https://svn.apache.org/repos/asf/openoffice/branches/AOO414
>
>and similar. I would honestly use one of the two mirrors I mentioned
>earlier, but we could include a section describing these methods to get
>
>the code without using a dedicated Subversion client.
>
>Regards,
>   Andrea.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Damjan Jovanovic
Yes, git-svn lacks quite a few features and can be problematic.

Besides, 1 VCS and 1 way of doing things (ie. Git only everywhere) is
always easier to manage than SVN here, a read-only delayed (possibly by
months, when it breaks) Git copy on GitHub, and possibly git-svn on the
users' end.

On Mon, Sep 18, 2017 at 9:25 AM, Peter kovacs <[hidden email]> wrote:

> I failed using git svn clone ...
> Git is doing some history scans that cause to run for forever. I have not
> found any way to circumvent that scan.
>
> I have forked the apache repo on github and then pulled from there. That's
> an easier workflow for me.
> What I miss is a push functionallity. But that's for me only convenience.
> I can work with git and svn. No issue for me.
>
> So I am quite neutral on the topic.
>
> All the best
> Peter
>
> Am 17. September 2017 20:12:13 MESZ schrieb Andrea Pescetti <
> [hidden email]>:
> >Patricia Shanahan wrote:
> >> The big new developer issue may be lack of Subversion experience. Git
> >> seems to be the repository-of-the-decade.
> >
> >This can be circumvented by using git as follows:
> >
> >$ git svn clone
> >https://svn.apache.org/repos/asf/openoffice/branches/AOO414
> >
> >and similar. I would honestly use one of the two mirrors I mentioned
> >earlier, but we could include a section describing these methods to get
> >
> >the code without using a dedicated Subversion client.
> >
> >Regards,
> >   Andrea.
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [hidden email]
> >For additional commands, e-mail: [hidden email]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Herbert Duerr-3
In reply to this post by Andrea Pescetti-2
On 09/17/2017 04:04 PM, Andrea Pescetti wrote:

> On 14/09/2017 Dave Fisher wrote:
>> does SVN vs. GIT prevent new developers from volunteering?
>
> I think this is the key question, even though there are many good points
> also in what others replied.
>
> We currently have a couple semi-official GIT mirrors: one on Github in
> the ASF organization page and the internal one Herbert pointed out. I
> also remember that Herbert once presented a big GIT repository he had
> built with all the available history of the OpenOffice code, but I don't
> know if it is available somewhere.

I had that 2GB blob on my Apache homepage for a couple of years. When
that home was migrated to the newer locations it was apparently dropped.
Unless someone mirrored the blob it is currently not available anymore.
If anyone is really interested in that ancient history I can probably
resurrect it unless 2+GB blobs are no longer allowed in committer's home
directories.

> I believe that the interested developers (including me, at times) use
> the git-svn tool when convenient. I think that this is enough to allow
> the local workflow improvements Damjan was requesting. Or do you see
> reasons not to use it?

OpenOffice is only a small part of the Apache subversion repository that
contains many more projects. Most revisions in that repo are not for OOo
and git-svn apparently has a hard time with this. It is possible but not
much fun.

> As for the new developers, most new developers are probably familiar
> with the "pull request" convention. This is not supported by either of
> the current repositories, mostly due to ASF policy. Last time I checked,
> Infra was still discussing how we can allow pull requests in a way that
> complies with the policy and I have no idea whether this is resolved.
> Once we have official support from Infra and a friendly pull request
> system, this might indeed improve the approach for new developers.

Agreed. The workflow with pull request is so much nicer than handling
patches...

Best regards,
Herbert

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [Discussion] Switch to Git?

Damjan Jovanovic
On Mon, Sep 18, 2017 at 7:44 PM, Herbert Duerr <[hidden email]> wrote:

> On 09/17/2017 04:04 PM, Andrea Pescetti wrote:
> > On 14/09/2017 Dave Fisher wrote:
> >> does SVN vs. GIT prevent new developers from volunteering?
> >
> > I think this is the key question, even though there are many good points
> > also in what others replied.
> >
> > We currently have a couple semi-official GIT mirrors: one on Github in
> > the ASF organization page and the internal one Herbert pointed out. I
> > also remember that Herbert once presented a big GIT repository he had
> > built with all the available history of the OpenOffice code, but I don't
> > know if it is available somewhere.
>
> I had that 2GB blob on my Apache homepage for a couple of years. When
> that home was migrated to the newer locations it was apparently dropped.
> Unless someone mirrored the blob it is currently not available anymore.
> If anyone is really interested in that ancient history I can probably
> resurrect it unless 2+GB blobs are no longer allowed in committer's home
> directories.
>
>
That would be great. I need the old repository to regression test an old
bug in Base. However, is it legal to have commits from the pre-ASLv2 era?


> > I believe that the interested developers (including me, at times) use
> > the git-svn tool when convenient. I think that this is enough to allow
> > the local workflow improvements Damjan was requesting. Or do you see
> > reasons not to use it?
>
> OpenOffice is only a small part of the Apache subversion repository that
> contains many more projects. Most revisions in that repo are not for OOo
> and git-svn apparently has a hard time with this. It is possible but not
> much fun.
>
>
Excellent insight. Never thought of that. git-svn is almost unusable then.


> > As for the new developers, most new developers are probably familiar
> > with the "pull request" convention. This is not supported by either of
> > the current repositories, mostly due to ASF policy. Last time I checked,
> > Infra was still discussing how we can allow pull requests in a way that
> > complies with the policy and I have no idea whether this is resolved.
> > Once we have official support from Infra and a friendly pull request
> > system, this might indeed improve the approach for new developers.
>
> Agreed. The workflow with pull request is so much nicer than handling
> patches...
>
> Best regards,
> Herbert
>
>
Damjan
12