--===============0136192110==
Content-Type: multipart/signed;
  boundary="nextPart4201869.k4Pp44stBX";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart4201869.k4Pp44stBX
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

[Stephan Kulow, Mittwoch, 30. M=C3=A4rz 2005 20:36]
> Someone is complaining we're not talking in private but keep things
> open on kde-core-devel? I don't understand.
>

I realize that answering sarcasm with more sarcasms doesn't help to ease=20
communication. Sorry.

I was trying to explain why I posted my questions so late: I expected the=20
web server admins to read both the kde-www and kde-core-devel mailing=20
lists and to respond to the questions about what the svn move means for=20
the websites. When the date came close, I realized that I had to speak up=20
in order to prevent that website maintenance and mirrors will be broken=20
without people realising what its going on.

I don't think every contributor to the websites needs to be subscribed to=20
kde-core-devel, so it would have been nice if the KDE server admins had=20
send a mail to kde-www replying to the questions that were asked=20
concerning the move.

Olaf

=2D-=20
KDE Accessibility Project

--nextPart4201869.k4Pp44stBX
Content-Type: application/pgp-signature

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

iD8DBQBCSuxdoLYC8AehV8cRAtqwAKCoktH1qd6WXTLOBiHbhNpNiLNxcwCginDm
72Fnj70HB0a/cCqdpl2It9Q=
=EmtT
-----END PGP SIGNATURE-----

--nextPart4201869.k4Pp44stBX--

--===============0136192110==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-www mailing list
kde-www@kde.org
https://mail.kde.org/mailman/listinfo/kde-www

--===============0136192110==--