--===============2038408144==
Content-Type: multipart/signed;
  boundary="nextPart1687458.i6FOsMTX75";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

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

[Stephan Kulow, Mittwoch, 30. M=C3=A4rz 2005 17:13]
> Ah! Someone else woke up. Finally! I knew it would take till the moving
> day will be tomorrow before people start thinking about the problems.

I presumed that those people who have admin rights to the KDE servers are=20
talking to each other about planned changes, which doesn't seem to be the=20
case.

Another problem is that the kde-www list was never informed about the=20
moving date, so no one was able to respond apart from the people who also=20
happen to read kde-core-devel.


> > How does the svn migration affect the websites?
>
> Some webmaster should have checked since we were thinking about it?

I don't have web server administration rights, and most webmasters don't=20
have them either. All we could do is discuss the topic on the kde-www=20
list. But is seem that the web server admins aren't reading that list, so=20
our questions were left unanswered.


> Before the move? That was the actual plan actually. The current HOWTO
> is in in wiki, which is not affected at all.

OK, fine.


> One possible way is to leave cvs/www open for a specific sync account
> and setup a svn/www -> cvs/www mirror script. Then you can migrate the
> servers and mirrors independent on the master repository. =20

Sounds reasonable.

The modules developer.kde.org and bugs would need to be included, too.=20


> Then you can migrate the servers and mirrors independent on the master
> repository. Of course you would need one day where you stop that mirror
> script and start moving your SVN - and when you're done with moving, the
> servers and mirrors need to be changed to use SVN exclusively.

If we want to keep the script SVN->CVS simple, then it would be easiest to=
=20
deal with the subdomain repository moves at the same point of time when=20
the webserver configuration changes.


> A svn->cvs mirror script can be done quickly if it only has to handle
> www and HEAD, it might even exist already out there.

Can you set it up, or would someone else need to do it? I am neither=20
familiar enough with svn, nor do I have the necessary admin rights.

Olaf


=2D-=20
KDE Accessibility Project

--nextPart1687458.i6FOsMTX75
Content-Type: application/pgp-signature

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

iD8DBQBCSsBooLYC8AehV8cRAgtkAKDbQxWzvVnY0JWF+e3gtsY22XCX2ACgt3sa
0VhyoEyes+nYTFB+XvUepwE=
=UxKS
-----END PGP SIGNATURE-----

--nextPart1687458.i6FOsMTX75--

--===============2038408144==
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

--===============2038408144==--