Re: Some questions about PHP in Github

On 30.11.2021 at 07:12, Andreas Heigl wrote:

> On 29.11.21 20:13, Christoph M. Becker wrote:
>
>> I'm forwarding this to the doc mailing list.
>>
>> On 29.11.2021 at 19:58, 구민석 wrote:
>>
>>> Hello, I am studying at a university in Korea.
>>> Korean language is not supported on the PHP site, so we are working on a
>>> translation.
>>> However, it is currently being done by three people, but the amount of
>>> documents is too large, so I want to work with many Korean github users,
>>> but there is no doc-kr in Github.
>>>
>>> I read "http://doc.php.net/tutorial/translating.php"
>>> but it was mentioned about the translation work for what already exists.
>>>
>>> I want to make a doc-kr. I would appreciate it if you could tell me
>>> how to
>>> make it.
>>> I am sending you an email because you are very active.I'm sorry to
>>> send you
>>> an e-mail like this.
>>
>> There is already a Korean translation[1], but it has marked as being
>> unmaintained several years ago[2].  As such, the repository has not been
>> moved to Github, but if you want to work on it, it would make sense to
>> move it.
>>
>> Could someone move <http://svn.php.net/viewvc/phpdoc/kr/> to
>> <https://github.com/php/doc-kr>?  Or are there objections on doing this
>> at all?
>
> I would not recommend starting from the old svn content. The content
> there is over 5 years old. The last commit was Revision 340039 from 15th
> of Sept. 2016. That is from a time where we were getting ready for
> PHP7.0. So the korean docs were at that point in time refering to PHP5.6
> at best. And digging further into those commits reveals that a lot of
> the ones in 2016 were regarding fixing broken builds.
>
> So it looks like starting from the old code will involve a lot of
> checking the current state of the documentation and fixing a lot of
> things. I'm not sure that is going to go well.
>
> I'd therefore opt for starting freshly from scratch.

Okay, that might make more sense.

> If - and to me this is a *huge* if - there is a team available to tackle
> the huge task of translating the PHP-Docs into a further language. No
> matter whether based on an outdated translation or on a fresh start.
> This is an enormous task that consumes a lot of time, energy and
> commitment not only for 2 weeks but for years.

Right.  I'm not suggesting to mark the translation as active, but rather
to have php/doc-kr available on Github.  Maybe a translation team forms,
and works on the translation.  Otherwise, what would be lost?  Nothing
but an unmaintained repo, which can easily be archived.

Christoph

> So the question should be asked whether it makes sense to distribute
> that commitment to translations or to making the existing english
> documentation even more awesome. But that is a question that everyone
> has to answer for themselves.
>
> Just my 0.02€
>
> Cheers
>
> Andreas