Fwd: [PHP-DOC] Current state of my ideas on moving docs to GIT

From: Date: Sun, 07 Oct 2018 13:06:50 +0000
Subject: Fwd: [PHP-DOC] Current state of my ideas on moving docs to GIT
References: 1 2 3 4 5 6 7  Groups: php.doc 
Request: Send a blank email to phpdoc+get-969387044@lists.php.net to get a copy of this message
This email got lost in the last mail failure. André ---------- Forwarded message --------- From: André L F S Bacci <andrebacci.listas@gmail.com> Date: Mon, Aug 20, 2018 at 8:43 PM Subject: Re: [PHP-DOC] Current state of my ideas on moving docs to GIT To: Peter Kokot <peterkokot@gmail.com> Cc: Maciej Sobaczewski <sobak@php.net>, PHP Documentation ML < phpdoc@lists.php.net>, Andreas Heigl <andreas@heigl.org>, < nikita.ppv@gmail.com> On Sat, Jun 16, 2018 at 7:10 PM, Peter Kokot <peterkokot@gmail.com> wrote: > Also another idea, if there is no response from the people with server > access to create a Git repository (this also means that all current > repositories on the git.php.net are doomed anyway). Why not just creating > a root repositories on the github.com/php and get on with the docs > migration process? When people with Git access will be able to create the > needed repos on the git.php.net the root repo can be set there (moved > from the GitHub) and the mirror created on GitHub (as it should be now). > The discussion where to host the git repository is important: to have very official, very stable of SVN rev to git hashs list. It's not so much of a rocket science. But syncing people is a rocket > science. This is a task for over a weekend for a system oriented human with > enough knowledge and all overall access of these. > I think there are some tasks before trying to sync people: make a official -- or at least a very functional -- revision-to-hash list. The immediate steps: 1. Create the official git repo. 2. Create a "individual pusher". For every SVN revision not in git: 2.1 Push that individual revision to git; 2.2. Create a new line on phpdoc-revision-to-hash.txt, say, "$revision $hash $timestamp\n" . This will create a map for every revision, and maybe some duplicated hashs (on empty diffs); I discovered a lot of translated files who point to not existent file-revisions combinations, and tooling will fail badly without a reference. So a bad/stale reference is better than alternative. 3. Make said pusher automatic, cron or triggered. Let it collect all revision to hashs, and then wait to see if it is working without glitches. 4. Adapt the translators tooling to work with both reference styles. 4.1 the "long" style, who uses hashs and git for every thing. 4.2 the "short" style, who uses phpdoc-revision-to-hash.txt and git for every thing. After this all <!-- $Revision$ --> on en/ could be removed. This will make translators dependent on git en/ hashs, and independent of SVN en/ revisions. On this point work on syncing people may start. Each language may migrate by freezing access on SVN $lang/ and granting access on git $lang/. Editors and translators can make their move independently. Small migrations instead a bit one. One last small tool will be necessary on this step, for translators: a revision to hash updater. And then, for that translation, no more SVN references. André

« previous php.doc (#969387044) next »