public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Svyatogor <svyatogor@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GLEP #10 -- Proposal for restructuring the CVS regarding documentation wrt internationalization proposal
Date: Tue, 5 Aug 2003 13:18:31 +0300	[thread overview]
Message-ID: <20030805131831.31f325d7.svyatogor@gentoo.org> (raw)
In-Reply-To: <20030804183108.GA6036@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]

I just want to clarify something. We are gonna have ${LANGUAGE}.gentoo.org -> www.gentoo.org/${LANGUAGE}  which will contain the localised version of existing www.gentoo.org + links to community pages. Did I get it right?

Another proposal, which has been discussed for a while is that community pages (or rather 1 page) should actually be maintained by Gentoo itself. Other words, $LANG.gentoo.org rather than being a simple translation of existing of main website will be a localised page (please note the diff. between translation and localisation). Though this page will have to comply with some standarts, authors will be more or less free to add the information, which they feel is important for their community.

Any ideas?

On Mon, 4 Aug 2003 20:31:08 +0200
Sven Vermeulen <swift@gentoo.org> wrote:

> Okay, the subject has too much characters, but I hope I get the attention of
> the people interested.
> 
> On http://www.gentoo.org/proj/en/glep/glep-0010.txt (and
> http://www.gentoo.org/proj/en/glep/glep-0010.html) you will find a proposal
> regarding a restructuration of the CVS layout and permissions for the
> Documentation and Website (i.e. only [gentoo]/xml/htdocs). 
> 
> In short: this proposal implements a new cvs structure and permissions so
> that we can safely start with the internationalization as discussed on
> http://bugs.gentoo.org/show_bug.cgi?id=23199
> 
> All feedback appreciated, especially from the infrastructure folks as it is
> mainly infrastructure related.
> 
> Wkr,
> 	Sven Vermeulen
> 
> PS Reply-To set to gentoo-dev@gentoo.org, please discuss everything in that
>   mailinglist (no need for crossposting).
> 
> -- 
>     Save some animals, eat a vegetarian.
> 


-- 
Let the Force be with us!
Sergey Kuleshov <svyatogor@gentoo.org>
Public Key: http://dev.gentoo.org/~sergey/gentoo-gpg

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-05 10:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 18:31 [gentoo-dev] GLEP #10 -- Proposal for restructuring the CVS regarding documentation wrt internationalization proposal Sven Vermeulen
2003-08-05 10:18 ` Svyatogor [this message]
2003-08-05 11:43   ` Sven Vermeulen
2003-08-05 11:50     ` FRLinux
2003-08-05 12:03       ` Svyatogor
2003-08-05 13:07         ` Sven Vermeulen
2003-08-12 13:05     ` Kurt Lieber
2003-08-12 13:20       ` Paul de Vrieze
2003-08-12 13:41       ` Sven Vermeulen
2003-08-12 15:56         ` Kurt Lieber
2003-08-05 13:31 ` Lisa Marie Seelye
2003-08-05 13:25   ` Svyatogor
2003-08-05 14:15   ` Paul de Vrieze
2003-08-05 15:21   ` Sven Vermeulen
2003-08-05 19:51     ` Paul de Vrieze
2003-08-06  8:06       ` Sven Vermeulen
2003-08-12 12:45 ` Kurt Lieber
2003-08-12 13:36   ` Sven Vermeulen
2003-08-12 13:43   ` Svyatogor
2003-08-12 21:56   ` Robin H. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030805131831.31f325d7.svyatogor@gentoo.org \
    --to=svyatogor@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox