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

List:       kde-core-devel
Subject:    Re: Questions about root of the SVN trunk/
From:       "Nicolas Ternisien" <nicolas.ternisien () gmail ! com>
Date:       2008-02-26 22:54:35
Message-ID: ccba71b50802261454o63e29144h155b5b1046af802b () mail ! gmail ! com
[Download RAW message or body]

I think we are still not at a moment of the discussion where we can
say those SVN layout modifications are useless, because those folders
are websites, and the trunk/ folder contains a www/ folder for this.

bugs.kde.org is a separate website as l10n.kde.org is, and however,
l10n.kde.org is stored in /trunk/www/areas/. It is just a question of
uniformity.

I think it could be useful because the first time someone navigate
into the SVN, it will help him if there are not thousands folders in
the root one.

On Tue, Feb 26, 2008 at 4:50 PM, Matt Rogers <mattr@kde.org> wrote:
> On Tue, Feb 26, 2008 at 9:04 AM, Nicolas Ternisien
>
> <nicolas.ternisien@gmail.com> wrote:
>
> > Hi,
>  >
>  >  Here is the next step of the KDE SVN trunk/ cleanup :
>  >
>  >  Would you agree to move the following Web folders to trunk/www/ :
>  >
>  >  dot.kde.org/
>  >  (webmaster : admin@kdenews.org)
>  >  -> Could go to trunk/www/ directly
>  >
>  >  kdewiki/
>  >  (webmaster : luci2007@ground.cz)
>  >  -> Could go to trunk/www/sites/
>  >
>  >  bugs/
>  >  (webmaster : webmaster@kde.org)
>  >  -> Could go to trunk/www/sites/
>  >
>  >  Of course, for each of, we will need the approval of the webmaster,
>  >  who will have to do a svn switch when the move will be done. Those
>  >  webmasters are CC'ed
>  >
>
>  Except that webmaster@kde.org doesn't maintain bugs.kde.org. sysadmin
>  does. And bugs.kde.org is more of a seperate project than the rest of
>  the KDE web sites. IMHO, the last point justifies it staying where
>  it's currently at.
>
>  I personally don't see the point of doing anymore cleanups after
>  what's already been done because now it turns into a debate about who
>  likes which layout for our repository best.
>  --
>  Matt
>
[prev in list] [next in list] [prev in thread] [next in thread]