Re: Current state of my ideas on moving docs to GIT
| From: | Andreas Heigl | Date: | Sat, 18 Nov 2017 07:09:35 +0000 |
| Subject: | Re: Current state of my ideas on moving docs to GIT | ||
| References: | 1 2 3 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969386808@lists.php.net to get a copy of this message | ||
Hey All!
Am 18.11.17 um 06:59 schrieb Maciej Sobaczewski:
> W dniu 13.11.2017 o 23:24, Peter Cowburn pisze:
>> Hi Andreas and doc geeks,
>
> Hi Peter!
[...]
>
>> Let's give it a go and see how it works in practice.
>
> I would love to and appreciate this call to action but there are many
> steps in the plan that cannot be done without karma/permissions all over
> the PHP.net - like creating new git.php.net repositories (I think that
> at first step we can avoid setting up GitHub mirrors to speed up and
> add it later if it will turn out to be a success; it would also prevent
> the confusion for newcomers which would see github repos for the manual
> which is still primarily using SVN).
>
> Then I think we should focus on trying to make doc.php.net working like
> it is now (but with git obviously). Once we will have the solution for
> translators to update their language versions against English one, I
> would assume it's quite safe to proceed.
>
> But the thing here is that we cannot really have both at the same time.
> Let's assume I can cooperate with Andreas and prepare the branch to
> migrate whole doc.php.net to support git... but how can we test it
> then? The only things I can think of are setting up new doc.php.net
> instance (with the sources from other branch than master) but it
> requires spinning up new machine which is money and time consuming
> OR switching between SVN's and git's implementations with some
> hidden URL parameters which requires a transition state with the
> code full of conditionals (and we know that temporary things tend
> to stay forever...).
I'm absolutely with you here. Running SVN and GIT at thev same time
makes it really hard. Additionally I'd like to point out that it is very
error-prone to keep svn and git in sync (which we would need). And as we
all know, we only use new tools when we're forced to, so I'd believe
that the SVN-side will still be heavily used and the git side might not
get all the tests we need. So I'm absolutely in favour of actually doing
the switch and then removing the few remaining glitches and then
improving the flow.
So let's get moving!
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