Structure of our websites (in CVS + on the servers)
Christoph Cullmann
cullmann at babylon2k.de
Fri Oct 11 08:22:43 UTC 2002
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
as Neil allready was much faster than I (thx ;) to answer many question, here
some statements from me:
1) Neil is right, acls are directory based in CVS www module
2) yeah, I want that *.kde.org is accessible through www.kde.org/apps/* or
www.kde.org/areas/* (apps in apps, areas like printing, multimedia, usability
in areas subdir of www), some links need to be fixed, but that needs to be
done anyway (for example, even atm multimedia.kde.org is accessible through
www.kde.org/multimedia, but if you use the last url, all links are borked (as
the use absolute links like /contact.php in relation to multimedia.kde.org),
that should be changed to relative links for all *.kde.org pages, as it is
just awful to find a page via google and just get it broken because you
entered in the wrong place.
3) it will break some links, for sure, but
a) the *.kde.org domains will stay, which is the place most people
remember
b) if we have cleaned up, moved all stuff on the same server (or at least
as if it is in one dir structure) and have cleanly separated the apps
in the apps subdir + areas in the area subdir we should be able to let
this structure live on for year, the current mess won't support that
long term planning ;)
4) as Rainer (which does and will help a lot both in planing + actually
implementing ;) mentioned, that is not a pet project of myself ;) On
kde-core-devel I asked if there is interest in new kde.org design +
structural cleanups some time ago, that was accepted and I will try to manage
this efforts to get the thing rolling on, which will not mean that I will
"kick" any existing admin/maintainer from his page, atm my job is to mail
around like a furry to all of them to request the movements of their cvs
dirs, to talk to them why do it, ... That is now fun work, just dumb writing
;)
Some notes again to the structural changes ;)
www/"appname" -> www/apps/"appname"
www/"areaname" -> www/areas/"areaname"
"areaname".kde.org cvs module -> www/areas/"areaname" (but that won't be that
easy, needs more work as *.kde.org modules are atm at ktown, www module not,
btw. why ? traffic ? mess ?)
As seen I want to collect all www.kde.org pages under www module (with right
directory acls), that will make life much easier to get structure into it,
later I would like to see that the translated pages for www.kde.de,
www.kde.il, ... would be moved to a seperate www-i18n module (like the
kde-i18n module) or into www-"isocode" modules, or at least consistent under
www/"isocode", as it is down by many big pages, too (or
www/international/"isocode")
The app people I allready written mails, waiting for answer, got the first ok
from kooka and the first "be possible" from koffice.
The area guys I will mail later after some apps have settled (btw. Neil, are
you the multimedia.kde.org maintainer, just found no note who is it :P ?)
cu
Christoph
P.S.
Will take a look at your design Neil, just after writing that mail ;) And
btw., think you the www/kde-ev should move to www/areas/kde-ev, as you seem
to maintain that page, or should we let it live where it is as the kde-ev is
integral part of kde project ?
- --
Christoph Cullmann
Kate/KDE developer
cullmann at kde.org
http://kate.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9popWyPjDGePm9UIRAqNrAJsFNacbohqngZ9QcBKvXfT+4dW1JQCgtSt8
9qlNjrNLbNvUO46b0GfiP/w=
=fmi9
-----END PGP SIGNATURE-----
More information about the kde-www
mailing list