Re: Time to publish the Polish translation?

On Sat, Oct 26, 2024, at 8:20 AM, André L F S Bacci wrote: > On Thu, Oct 24, 2024 at 9:03 PM Jim Winstead <jimw@trainedmonkey.com> wrote: >> First, my apologies for having incorrectly disabled the doc-pl@lists.php.net mailing list a >> couple of months ago when we cleaned up inactive mailing lists. I had incorrectly identified the >> Polish translation efforts as having gone dormant. > > Incidentally, I may ask you to check the pt_BR maillist? Its commit's trigger stopped > sending mails a while ago, so the very small Portuguese community it's at loss of actively > reviewing all commits. I don't see anything abnormal in the list setup, but it looks to me like none of the language lists are getting commit messages and haven't for years, maybe since the switchover to Git from SVN? > >> We don't have any guidelines on what constitutes an active translation, which is maybe >> a discussion we should have on the phpdoc@lists.php.net list, but according to the translation >> status (https://doc.php.net/revcheck.php?lang=pl), it looks like about 9% of the Polish translation >> is up to date. This is already more than a couple of other languages that are currently active on >> PHP.net. > > I would argue about issuing two different guidelines, instead of one. One guideline for > enabling, and another for disabling. For enabling, the translation compilation must be ok and has > all files on chapters/ and language/ translated (instead of a percentual). And for disabling, for > having the manual build failing or no commits for 3 months. > > Beyond chapters/ and language/, maybe faq/ and security/ may be included, but any inclusion may > further hinder any nascent new language translation. Yes, I think different enabling and disabling guidelines are a good idea and your enabling proposal is in line with what I was thinking and had discussed with Gina on IRC. I would want to include security because it helps emphasize that it is an important part of the documentation. Jim