<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;"><div>A task shows this attitude much better as it is something that will be completed eventually. "[WIP] Migrate translations from SVN to Git" to me sounds like a clear intention.<br></div><div><br></div><div>Docs, in contrast, are static and do not display any motivation for migration. "Top 10 Reasons Why We Can't Use Git".<br></div><div><br></div><div>Best regards,<br></div><div>Ilya.<br></div><div data-zbluepencil-ignore="true" style="" class="zmail_extra"><div><br></div><div id="Zm-_Id_-Sgn1">---- Дата: Вт, 12 ноя 2019 14:12:28 +0300 <b>Luigi Toscano <luigi.toscano@tiscali.it></b> написал(а) ----<br></div><div><br></div><blockquote style="border-left: 1px solid rgb(204, 204, 204); padding-left: 6px; margin: 0px 0px 0px 5px;"><div>Ben Cooksley ha scritto: <br>> On Tue, Nov 12, 2019 at 10:00 AM Alexander Potashev <br>> <<a target="_blank" href="mailto:aspotashev@gmail.com">aspotashev@gmail.com</a>> wrote: <br>>> <br>>> пн, 11 нояб. 2019 г. в 17:02, Luigi Toscano <<a target="_blank" href="mailto:luigi.toscano@tiscali.it">luigi.toscano@tiscali.it</a>>: <br>>>> <br>>>> Alexander Potashev ha scritto: <br>>>>> вс, 10 нояб. 2019 г. в 18:09, Luigi Toscano <<a target="_blank" href="mailto:luigi.toscano@tiscali.it">luigi.toscano@tiscali.it</a>>: <br>>>>>> Most of translators are not so technical as the developers. And even <br>>>>>> developers can shoot them in the foot with git, I see many issues coming from <br>>>>>> unwanted merges. <br>>>>> <br>>>>> We can block unwanted merged on the server with a Git hook like this: <br>>>>> <a target="_blank" href="https://github.com/FabreFrederic/git-hook-pre-receive-reject-merge-commit">https://github.com/FabreFrederic/git-hook-pre-receive-reject-merge-commit</a> <br>>>> <br>>>> When I talk about local merges, I foresee a bit of mess when resolving a merge <br>>>> locally, which may result in proper commits whose content has an invalid syntax. <br>>> <br>>> I don't get it. <br>>> <br>>> If you have conflicting changes, either with SVN or Git, you have to <br>>> resolve the conflict manually. Of course it's easy to break the syntax <br>>> while doing so, however SVN does not make it any easier than Git. <br>>> <br>>>>> Cloning the whole repo would be too much for some translators, however <br>>>>> the new Git feature "git clone --filter" might be a solution: <br>>>>> <a target="_blank" href="https://unix.stackexchange.com/a/468182">https://unix.stackexchange.com/a/468182</a> <br>>>> <br>>>> Documentation does not seem to help (or at least I don't seem to find it in <br>>>> the man pages for git 2.24). Do you know how it could filter just some <br>>>> directories? It seems more focused on filtering by object type. <br>>> <br>>> OK, I now tried this approach with Git 2.23 (see attached log) and <br>>> found horrible problems that make it basically unusable: <br>>> <br>>> 1. git-checkout downloads each file in a new SSH connection. It make <br>>> the download really slow: less than 1 file per second in my setup. <br>>> That means downloading of translations into one language would take <br>>> more than an hour. <br>>> <br>>> 2. git-status silently tries to download to whole Git repository. <br>>> <br>>> 3. git-commit tries to download some files one by one again. <br>>> <br>>>>> Shall I create a new Phabricator task "[WIP] Migrate translations from <br>>>>> SVN to Git" so we can put relevant ideas in one place? <br>>>> <br>>>> I don't know. For me having a board and tasks (it's not just a single task, <br>>>> it's an entire project) sounds like there is something that can be <br>>>> implemented, and I don't think it's the case. <br>>> <br>>> The tag [WIP] would hint that we are not sure if it can be <br>>> implemented. We can even name it "Reasons why translations cannot <br>>> migrate to Git", if necessary. <br>> <br>> Sorry, but if you proceed with using a title such as that one, then <br>> you are not being constructive or helpful towards this conversation. <br>> <br>> That title would indicate to me that the translation community is <br>> completely unwilling to consider change of any form. <br> <br>That's why it shouldn't be a task at this point, but a document showing why we <br>can't migrate. <br>It's not a matter that we are unwilling to consider. The problem is that the <br>current state makes it almost impossible to migrate. The document would <br>explain why. <br> <br> <br>-- <br>Luigi <br></div></blockquote></div><div><br></div></div><br></body></html>