--===============0095567627==
Content-type: multipart/signed; boundary=nextPart4262707.L6DRbuuAgA;
 protocol="application/pgp-signature"; micalg=pgp-sha1
Content-transfer-encoding: 7bit

--nextPart4262707.L6DRbuuAgA
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Replying to myself...

On Thursday 18 September 2008, Ingo Kl=F6cker wrote:
> On Thursday 18 September 2008, Adriaan de Groot wrote:
> > What we really want is a webmaster who follows the development as
> > it happens (e.g. on this list or on the IRC channel) and who
> > handles updating the website when there are interesting things to
> > change. Tying in to the KDE.org website upgrade (away from
> > websites-in-svn) would also be good.
> >
> > We have a critical shortage of developers as it is; spending a few
> > hours on the website -- which is something most of us developers
> > are *not* good at -- does not feel like a productive investment of
> > time. It's an uncomfortable trade off, because at the same time we
> > need to attract a webmaster (see above) who wants to push the sites
> > back into the 21st century.
>
> Note, that we will transfer most if not all of the contents of the
> kontact.kde.org to userbase.kde.org (a wiki). Anne has already
> transferred some of the contents. This will make it much easier to
> keep the pages up-to-date because anybody will be able to help.
>
> FWIW, we have tried to find a webmaster for many years and even
> though from time to time someone willing to help popped up, soon
> afterwards he vanished again probably because he got frustrated about
> getting no input from us, the developers. I'm putting all my hopes
> into userbase.kde.org now.

After re-reading Anne's message I see that she only planned to add a=20
short introduction for each component of Kontact to userbase.kde.org=20
[1] linking to http://kontact.kde.org/ for further info. I don't think=20
this approach is a good idea because it means there would be two places=20
that needed to be updated and kept in sync. I'm much more in favor of=20
Thorsten's suggestion [2]. So, Anne's work is just the first step.


Regards,
Ingo

[1] http://userbase.kde.org/Applications/Office#Kontact
[2] http://kde.markmail.org/message/vn5ltg2732gtijxq

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

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

iEYEABECAAYFAkjSpp8ACgkQGnR+RTDgudhNdQCfeq+5+AY0hCSlk+9zD7L8fK5J
ek4AoN5fbeL/CoIeBo0rh8K+BYqxIWvt
=wHT/
-----END PGP SIGNATURE-----

--nextPart4262707.L6DRbuuAgA--

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

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============0095567627==--