Re: Current state of my ideas on moving docs to GIT
| From: | Nikita Popov | Date: | Fri, 01 Feb 2019 15:34:06 +0000 |
| Subject: | Re: Current state of my ideas on moving docs to GIT | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969387151@lists.php.net to get a copy of this message | ||
On Fri, Feb 1, 2019 at 4:11 PM André L F S Bacci <
andrebacci.listas@gmail.com> wrote:
> On Fri, Feb 1, 2019 at 9:02 AM Nikita Popov <nikita.ppv@gmail.com> wrote:
>
>> I would like to bump this topic again.
>>
>> Here is the first step that I think needs to happen: Perform a svn2git
>> conversion of the doc-en repo, push it to git@git.php.net:/doc/en.git
>> and setup a cron job to keep it up to date with new changes coming in from
>> SVN.
>>
>
> There is a little more, here. Every SVN commit number must be mapped to
> respective git hash, for past and future commits. So every translation tag,
> who points to SVN numbers, can be latter converted. These SVN number are
> old and new. Some of then, very, very old.
>
Yes, of course. That is why I suggested to start with a conversion of
doc-en first, because no revision remapping is necessary there. Translation
repositories are the next step, which will first require a filter-branch
rewrite of history and then on-the-fly rewrites whenever we sync new svn
commits.
>
>> Any takers? I can grant you access to the git repo and can also provide
>> you with an author mapping file for the conversion.
>>
>
> It's possible to develop such tool and repository outside de official repo
> and after only "pump" all history on official repo?
>
> If so, I may develop these on GitHub, first for validation. On author
> mapping file, SVN credentials are different of git?
>
This has already been prototyped on GitHub: https://github.com/phpdoctest
However, this project has been stalled for a long time in this state, so I
think it is time to move things forward to the PHP infrastructure.
> The next step would be to do the same for doc-de, while also rewriting SVN
>> revision references.
>>
>
> Or activate such tool on all projects and them:
>
> 1. remap SVN numbers on translations
> 2. disable write access no SVN
>
> on language basis.
>
I don't think that we'll make any progress here if the svn to git migration
requires all the tooling to be fully migrated in advance and everything
switched over at once, with the SVN repo being disabled immediately. That's
why I am suggesting to set things up so that git and svn stay in sync for
now and we can migrate to git gradually.
Nikita