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

List:       kde-i18n-doc
Subject:    Re: l10n web site
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2006-02-03 12:29:44
Message-ID: 200602031329.44905.nicolasg () snafu ! de
[Download RAW message or body]

On Thursday 02 February 2006 00:25, Nicolas Ternisien wrote:
> In fact, I don't know if your current account (and existing
> translators account) can commit something in the dedicated l10n
> website folder, I think we need the advices of a SVN admin for this.
>
> Of course, existing SVN accounts will not have to be recreated,
> specifical rights will only be added if needed

The file
trunk/KDE/kde-common/svn/hooks/svnacl.cfg
defines where which account has or has not writing priviledges.

>
> Nicolas

Have a nice day!

>
> PS: Happy to see you like the new l10n layout ;-)
>
> 2006/2/1, Spiros Georgaras <sngeorgaras@otenet.gr>:
> > On Wednesday 01 February 2006 23:44 Claudiu Costin wrote:
> > > There's too much security risk because a whole website is involved.
> > > Personally, I would give any team PHP access if cannot demonstrate good
> > > and security aware coding practices. In fact very sub-site on
> > > i18n.kde.org is create by default with "php_flag engine off". In the
> > > past I saw abuses: i.e. some started to learn PHP on i18n.kde.org or
> > > subvert security using PHP.
> >
> > Yes, I see what you mean...
> > What about those of us who already have a KDE SVN account? Do we have to
> > apply for a new one (dedicated to the web area of  l10n.kde.org)? Or will
> > there be some restrictions applied for the existing accounts just for the
> > web area of l10n.kde.org?
> >
> > BTW, I am happy to say I have already started adapting the existing Greek
> > i18n site to the new look and feel :) Do we have an estimate on when
> > l10n.kde.org will be 'up' for use by the teams?
> >
> > Kind regards
> >   Spiros

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

Configure | About | News | Add a list | Sponsored by KoreLogic