[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-www
Subject:    Re: Repository structure for the websites
From:       Christoph Cullmann <cullmann () babylon2k ! de>
Date:       2005-03-02 20:45:57
Message-ID: 200503022146.01255 () cullmann
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 02 March 2005 16:00, Olaf Schmidt wrote:
> websites/www - http://www.kde.org
> websites/* - subproject sites (e.g. multimedia, usability, accessibility)
> websites/developer - http://developer.kde.org
> websites/bugs - http://bugs.kde.org
> websites/apps/* - application sites
> websites/international/* - localised sites
> websites/media - media directory to be used by most subsites
>
> This implies that we have a subdomain *.kde.org for every subsite and a
> redirect from the old location to the subdomain.
if we really want to get that consistent, I guess best way would be just give 
all apps/areas pages subdomains (or use the toplevel domains the already 
have, like konqueror.org and co)

than the simplest layout would be

www/sites/www
www/sites/developer
www/sites/bugs
www/sites/*

additionally a 

www/i18n/*

for all i18n subpages

and a 

www/media

for the media stuff shared by all pages

the areas/apps seperation is very fuzzy and not that useful I guess (I was one 
of the people wanting it, but now, it just seems to be redundant).

one important question is: what's up with any www mirror? they will break, and 
not sure if they want to use svn at all, as a svn checkout needs 2times as 
much space (not that www stuff would be that big, but who knows)
other question: does the www mirrors have any effect? are they used at all?

-- 
Christoph Cullmann
KDE Developer, kde.org Maintainance Team
http://www.babylon2k.de, cullmann@kde.org

[Attachment #5 (application/pgp-signature)]

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


[prev in list] [next in list] [prev in thread] [next in thread]