Re: Status of doc migration to Git

On Wed, Mar 19, 2014 at 3:12 AM, Peter Cowburn <salathe@php.net> wrote: > - Modules; we can create "wrapper" Git repos with submodules to offer the > same setup if we really want to. I'd argue that it's probably good to > ignore this anyway since it's easy enough to separately check out doc-base > and whatever language(s) you want. The annoying thing is a git submodule won't work as it points to a fixed commit. This means that everyone needs to have two git repos, and cross committing will no longer be possible (eg, when I create and use a new entity, these will be two commits and two pushes). This also adds a command or two to "getting started". As artificial as that sounds, it does make things look more scary for newcomers. > - Translation statuses; we could probably insert the Git hash in place of > the SVN revision number, that doesn't show how out-of-date the file is > though. Is there some other convenient way to replace the usage of > EN-Revision values, with Git? How do translators use this, if at all? Do > you? Are you asking how "professional translators" do this? That would be an interesting question I guess. Surely we aren't the onlyone in the world who keep track of if a translation is up2date.. Are we maybe just enforcing a up2date requirement here for no gain? > Thoughts? Did I miss something that *is* huge and insurmountable? I think it mostly just lacks someone who do the work and push forward and fix whatever comes up. We were, few years ago, afraid that some translators were not hip-and-cool using the new tech and slow on the lingo, so git could be hella confusing for them. I don't think those worries are valid anymore.. Although we will be asking "did you remember to push?" for the next year or so. -Hannes