From kde-i18n-doc  Mon Jan 11 18:09:09 2010
From: Rolf Eike Beer <kde () opensource ! sf-tec ! de>
Date: Mon, 11 Jan 2010 18:09:09 +0000
To: kde-i18n-doc
Subject: Re: [RFC] Documentation Freeze Policy
Message-Id: <201001111909.19405.kde () opensource ! sf-tec ! de>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=126323340314587
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart2981926.CDb4OFIhJ3"

--nextPart2981926.CDb4OFIhJ3
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Am Montag, 11. Januar 2010 schrieb Burkhard L=FCck:
> Hello translators,
>=20
> techbase.kde.org/Schedules says about doc freeze (usually around 9 weeks
> before tagging a major release like 4.x.0):
>=20
> 1) "Documentation/Handbook Freeze
> No more substantive changes to documentation or handbooks after this date.
> Typos, spelling and simple grammar changes are permitted."
>=20
> The second sentence should be changed to something like:
> "Exception: Typo, spelling fixes and simple grammar changes are permitted
> until RC1 but you have to mail kde-i18n-doc saying you made such a
> change."
>=20
> Then it is similar to the current Message Freeze policy.

That sounds reasonable.

=46rom my point of view as application developer it would be helpful if the=
 doc=20
freeze would be moved a bit closer to the release data. For 4.4 it was one=
=20
week after the code freeze (i.e. the scheduled release of beta1). I suggest=
=20
moving it to the same time as beta2.

The idea behind this is:

=2DOne would only have one week to write/update documentation, especially f=
or=20
small projects (e.g. KGpg is a one-man-show). In a timeframe of 3 weeks it'=
s=20
much more likely that the developers will finally sit down and write that=20
stuff. Until the feature freeze everyone is coding, and new features don't=
=20
make sense to be documented if it's unclear if and how they will show up in=
=20
the upcoming release. After all we are all lazy humans and will be in a hur=
ry=20
before feature freeze ;)

=2DTranslators will do messages first anyway. Most teams (even bigger ones)=
 will=20
not be done even with core modules messages until long after beta2. Current=
ly=20
e.g. Spanish and German teams (listed as 5th and 6th on=20
http://l10n.kde.org/stats/gui/trunk-kde4/toplist/) are not completely done=
=20
with the core SC components (well, probably mostly the weather strings) but=
=20
that was way worse like 3 weeks ago. So it's very unlikely that a later fre=
eze=20
of documentation would lead to a greater hurry for translators than they ha=
ve=20
anyway.

Greetings,

Eike

--nextPart2981926.CDb4OFIhJ3
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEABECAAYFAktLaUwACgkQXKSJPmm5/E6XbgCgjFHh4IJUL3IlAyVdg+M6dN6M
GJAAn31ZXoZB9jitXTsgkAO24Yn0xHxa
=2O2F
-----END PGP SIGNATURE-----

--nextPart2981926.CDb4OFIhJ3--