Hello Peter and other doc geeks,
To be frank, I'd rather have the documentation sources on Git now even if there are things that might be temporarily broken (that's probably good motivation to fix small issues), than sit back on our laurels, tootling along with SVN.
<snip>
I’m not sure how best to handle the translation process but
simplifying it (e.g., not requiring us to track the number
of revisions) sounds okay to me. We don’t have to keep the
exact system we have, a system that was designed with CVS.
Agree. The only problem I can see it what I mentioned earlier. Using current system (incremental revision numbers) allow translators to check detailed diff between their version and original.
The simpler it is to make a commit the better. It should be
easy for a random person to make a change via github without
requiring extra steps like installing hooks and such. The
clearer this "make a commit" path is the better.
I’m +1 for moving to git, and trust someone like Peter to
take charge with figuring out the details.
I’d also be +1 for moving to github and skipping git.php.net
but that might not be feasible or wise, and is off topic,
and is a little crazy. :)
IMO moving to Github is not necessary. Firstly, I think that dividing our infrastructure between two places is not a good idea. With current setup, so repositories on git.php.net and read-only mirror on Github we still allow people to contribute via Pull Requests - I think that's enough.
Comparing to the current state it will be significant improvment.
Regards,
Philip