--Boundary-02=_Q/JLBUr9H/JmJKF
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Mittwoch, 25. August 2004 15:20 schrieb Aaron Seigo:
> only the maintainers (more on them in a bit) will have commit rights and
> final paches to the guidliens will appear on a kde-guidelines list. this
> will allow domain-specific discussion to occur where appropriate with ite=
ms
> considered ready by the respective teams to be reviewed for correctness.
> this is important as proposed usability guidelines may have accessibility
> impacts, for instance.

Is access control really needed? Where is the trust among the KDE community=
?=20
Doesn't it work in all other cvs modules (except www, for whatever reason)=
=20
that there is a rule maintainer-reviews-before-commit? Do we really need to=
=20
enforce this here? Gives a really bad feeling. Are guideline writers more=20
special than code writers?
What about missspelled words or syntax errors? Should we really wait until =
the=20
maintainer had the time to review the little fix? And stay with a broken=20
docbook until?=20

Please, give a reasoning for this.=20

Regards
=46riedrich

--Boundary-02=_Q/JLBUr9H/JmJKF
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBLJ/QECqmVFXwdrMRAsT8AJ92tYpO5aYhS3t0B8ZI/dA1Ag6CbACfdHOn
4hQj3VlZfMtsHJ1mqzXWdJI=
=+9dP
-----END PGP SIGNATURE-----

--Boundary-02=_Q/JLBUr9H/JmJKF--