From: Kurt Lieber <klieber@gentoo.org>
To: gentoo-dev@gentoo.org
Cc: robbat2@gentoo.org
Subject: Re: [gentoo-dev] GLEP #10 -- Proposal for restructuring the CVS regarding documentation wrt internationalization proposal
Date: Tue, 12 Aug 2003 08:45:17 -0400 [thread overview]
Message-ID: <20030812124513.GD4094@mail.lieber.org> (raw)
In-Reply-To: <20030804183108.GA6036@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2643 bytes --]
On Mon, Aug 04, 2003 at 08:31:08PM +0200 or thereabouts, Sven Vermeulen wrote:
> http://www.gentoo.org/proj/en/glep/glep-0010.html
> All feedback appreciated, especially from the infrastructure folks as it is
> mainly infrastructure related.
OK, so I finally had a chance to review and think about this GLEP. Below
are some questions/comments that I have.
1) I'd like Robin (robbat2) to comment on this since the primary reason for
the GLEP seems to be better control over CVS permissions. I know Robin has
some ideas on how he wants to change CVS permissions, so his feedback here
is important. (cc'd on this email)
2) One thing that isn't clear in the GLEP. Is
http://www.gentoo.org/${LANGUAGE} an *exact* copy of
http://www.gentoo.org/en/? Or are the internationalization teams allowed
to change things? For the most part, I would like to ensure that we have
one, consistent web site, so I'd like to see translations happening, but
not alternate content per se.
You touch a bit upon this in the "Internationalized Website" but I'm still
not clear on how it works, so some clarification would be appreciated.
3) Regarding permissions, I don't really like the idea of the entire docs
team having commit access to /en/main/. I realize that's the case now
because of where docs.xml resides, but if we're going to restructure things
then I'd like to change that. Ideally, I would like members of cvsdoc to
have commit access to /en/docs/ and the cvsweb group to have commit access
to /en/main/. cvswebdoc is a nasty hack of a solution created because of
our current structure. I'd like to see it killed off as part of this
restructure.
4) How do /en/proj/* pages get translated?
5) One significant problem we have with the GWN is translation teams not
keeping things up to date. This may be outside of the scope of this GLEP,
but I'd sure like to see a defined policy that states what is expected of
the translation teams and at what point a language will be "killed off"
from the web site for falling behind. We *do not* want to have
/<language>/doc/gentoo-x86-install.xml handing out the wrong information.
If we can't keep a language up to date, it should be removed entirely imo.
6) Backwards compatibility needs to be maintained. Think of all the
external links to http://www.gentoo.org/doc/en/gentoo-x86-install.xml on
other sites. We can't simply cause all of them to break. We can do some
fancy footwork with mod_rewrite to facilitate this, but the GLEP needs to
be updated to reflect the fact that we *will* make a best effort to
maintain backwards compatibility.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-12 12:45 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
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 [this message]
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=20030812124513.GD4094@mail.lieber.org \
--to=klieber@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=robbat2@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