Re: Re: Current state of my ideas on moving docs to GIT
| From: | Andreas Heigl | Date: | Fri, 10 Nov 2017 21:18:31 +0000 |
| Subject: | Re: Re: Current state of my ideas on moving docs to GIT | ||
| References: | 1 2 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969386786@lists.php.net to get a copy of this message | ||
Hi Christoph.
Am 10.11.17 um 20:19 schrieb Christoph M. Becker:
> On 04.11.2017 at 15:46, Andreas Heigl wrote:
>
>> What did I do so far to investigate ways of moving the PHP-Docs from SVN
>> to GIT:
>
> Thanks for your work, Andreas!
>
>> The most important change probably is the revcheck.php-file. As the
>> en-repository and the de-repository are now two separate repositories I
>> needed to do some git-hacks to get the information about how many
>> commits there have been between the translated and the base file. And
>> there is definitely room for improvement! I'm looking forward to your ideas!
>
> I'm not sure whether this info is really needed. When going to sync
> with EN, I usually check the SVN log of EN, so I quickly get this info.
> And frankly, it does not really matter if a translation is a single
> commit or many commits behinds; in both cases it is out-dated, and even
> a single commit might have more modifications than a lot of commits in
> total.
Works at the moment and as I tried to keep the current workflow as it is
ATM I had to change that script. Whether we continue using it or not is
a completely different decission and should IMHO not be related to
moving the VCS to git.
>
>> * How shall we reach a decission on how to go on from here? Is an RFC
>> the right approach? Or is there some other form of finding a decission?
>
> That is *the* question! I'm part of the doc team only for a few years,
> and during this time only "minor" changes have been made, and these have
> been *informally* discussed and decided on this list. Guess, we need
> more input from others, especially translators, who might be affected
> heavily by this change (e.g. the Brasilian Portuguese team is using a
> SVN/Git bridge[1]).
I wrote this email 5 days ago and until now didn't get much reply. So I
assume people are fine with the idea…
> Also we have to discuss and decide what happens
> with edit.php.net.
Personally I'd say that we don't need edit.php.net any more as people
can now easily create new PRs on GitHub. Edit.php.net is a great tool to
allow people without karma to edit the docs and create a patch, but
after moving to git that can be done equaly easy using GitHub-PullRequests.
Cheers
Andreas
--
,,,
(o o)
+---------------------------------------------------------ooO-(_)-Ooo-+
| Andreas Heigl |
| mailto:andreas@heigl.org N
50°22'59.5" E 08°23'58" |
| http://andreas.heigl.org http://hei.gl/wiFKy7 |
+---------------------------------------------------------------------+
| http://hei.gl/root-ca
|
+---------------------------------------------------------------------+
Attachment: [application/pgp-keys] 0x5BFCE472.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-keys] 0x5BFCE472.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc