Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@httpd.apache.org
MIME-Version: 1.0
In-Reply-To: <20161020194642.GE21091@toftum.dk>
References: <8b7e6fa1-4042-603b-78e4-54e7a727ce4c@rcbowen.com>
 <201610202136.51398@news.perlig.de> <20161020194642.GE21091@toftum.dk>
From: Luca Toscano <toscano.luca@gmail.com>
Date: Sun, 23 Oct 2016 12:55:00 +0200
Message-ID: <CAFedD40ZLWMKb9_J4=s3hON-JysKAhBp-hPBvixzLNFM56CjgA@mail.gmail.com>
Subject: Re: Translations (IRC conversation)
To: docs@httpd.apache.org
Content-Type: multipart/alternative; boundary=001a114428f064309d053f861b02
archived-at: Sun, 23 Oct 2016 10:55:13 -0000

--001a114428f064309d053f861b02
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2016-10-20 21:46 GMT+02:00 Mads Toftum <mads@toftum.dk>:

> On Thu, Oct 20, 2016 at 09:36:51PM +0200, Andr=C3=A9 Malo wrote:
> > * Rich Bowen wrote:
> > > * We have translations that are grossly out of date. We should drop
> > > them. It remains only to define what "tool old" means? If a translati=
on
> > > hasn't been touched since 2.4.0, I would recommend dropping it.
> > > Discussion?
> >
> > Guilty... However, I think, it would be waste to throw them away. I'm
> > proposing a "do not transform (and remove html) until current" solution
> > instead. I can also take a look at the build system to make that happen=
.
> >
> Sounds like a much better solution.
>

I'd be +1 only if there is a clean way to mark these files as
"old/stale/out-of-sync", together with a clean statement/note somewhere
about what to do with them in the medium longer term (even in a page like
https://httpd.apache.org/docs-project/).


> >
> > > * All of this hinges on actually getting translators. It *seems* that
> > > this used to be easier, but lately we have really stunk at attracting
> > > new translators. I think that this might be because our review proces=
s
> > > is so rigorous, and it's hard to find reviewers.
> >
> > Maybe, maybe not. I think, the project itself lost traction in terms of
> > contributions (from non-developers). It's not that cool anymore (or the
> hot
> > shit, take your pick).
> >
> I think you're right. httpd moves slower too.
>

Can we do something about it? It seems like other "cool" projects are so
successful not only because of the good quality of the product but also of
its marketing strategy.

Thanks!

Luca

--001a114428f064309d053f861b02
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">2016-10-20 21:46 GMT+02:00 Mads Toftum <span dir=3D"ltr">&lt;<a href=3D=
"mailto:mads@toftum.dk" target=3D"_blank">mads@toftum.dk</a>&gt;</span>:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">O=
n Thu, Oct 20, 2016 at 09:36:51PM +0200, Andr=C3=A9 Malo wrote:<br>
&gt; * Rich Bowen wrote:<br>
&gt; &gt; * We have translations that are grossly out of date. We should dr=
op<br>
&gt; &gt; them. It remains only to define what &quot;tool old&quot; means? =
If a translation<br>
&gt; &gt; hasn&#39;t been touched since 2.4.0, I would recommend dropping i=
t.<br>
&gt; &gt; Discussion?<br>
&gt;<br>
&gt; Guilty... However, I think, it would be waste to throw them away. I=
9;m<br>
&gt; proposing a &quot;do not transform (and remove html) until current&quo=
t; solution<br>
&gt; instead. I can also take a look at the build system to make that happe=
n.<br>
&gt;<br>
</span>Sounds like a much better solution.<br></blockquote><div><br></div><=
div>I&#39;d be +1 only if there is a clean way to mark these files as &quot=
;old/stale/out-of-sync&quot;, together with a clean statement/note somewher=
e about what to do with them in the medium longer term (even in a page like=
=C2=A0<a href=3D"https://httpd.apache.org/docs-project/">https://httpd.apac=
he.org/docs-project/</a>).</div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">
<span class=3D"gmail-">&gt;<br>
&gt; &gt; * All of this hinges on actually getting translators. It *seems* =
that<br>
&gt; &gt; this used to be easier, but lately we have really stunk at attrac=
ting<br>
&gt; &gt; new translators. I think that this might be because our review pr=
ocess<br>
&gt; &gt; is so rigorous, and it&#39;s hard to find reviewers.<br>
&gt;<br>
&gt; Maybe, maybe not. I think, the project itself lost traction in terms o=
f<br>
&gt; contributions (from non-developers). It&#39;s not that cool anymore (o=
r the hot<br>
&gt; shit, take your pick).<br>
&gt;<br>
</span>I think you&#39;re right. httpd moves slower too.<br></blockquote><d=
iv><br></div><div>Can we do something about it? It seems like other &quot;c=
ool&quot; projects are so successful not only because of the good quality o=
f the product but also of its marketing strategy.=C2=A0</div><div><br></div=
><div>Thanks!</div><div><br></div><div>Luca =C2=A0</div></div></div></div>

--001a114428f064309d053f861b02--