public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: FRLinux <frlinux@frlinux.net>
To: gentoo-dev ML <gentoo-dev@gentoo.org>
Cc: Arachne <arachne@gentoo.org>,
	gentoo-user-fr ML <gentoo-user-fr@gentoo.org>
Subject: [gentoo-dev] Re: Internationalisation of gentoo.org (part II)
Date: 07 Jul 2003 20:51:00 +0100	[thread overview]
Message-ID: <1057607460.14526.13.camel@localhost> (raw)
In-Reply-To: <1056656926.11561.40.camel@localhost>

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

Hello, now that we agreed that having an <isocode>.gentoo.org with a
project page per country was the ideal solution, i'm referring to the
discussion on the bug (23199) where liquidx and swift agreed we should
get that implemented, so i'm turning back to mister seemant to get the
next step in this operation, should someone write a page and make sure
anyone is happy about it ? How do we get that done quickly ?

There is obviously the license thing as well concerning documentation,
which is currently handled by pauldv, klieber and zhen. As pauldv
mentionned to me via IRC, we didn't take any further action, so i'd like
to move on this topic too.

Steph

On Thu, 2003-06-26 at 20:48, FRLinux wrote:
> Hello,
> 
> Following today's discussion on -dev with seemant, klieber and others,
> it has been suggested that i send an email summing up what could be good
> in terms of getting an international touch on gentoo.org, so here i am.
> 
> Whilst the ideal situation would be to have an i18n site in all
> maintained languages from doc, i've been told it would be impossible for
> now for several reasons including time constraints and priorities.
> 
> So it seems that we should move to a single local <country> page summing
> up links to 'regional' websites and projects. It has also been
> mentionned that the coordinator of the translators team could be the
> right candidate to ensure CVS access to such a page which would be
> maintained by the translation team (one or several people). This is a
> good beginning to show users that we care for them and such local
> projects exist.
> 
> Seemant mentionned that no time can currently be allocated to the i18n
> aspect of gentoo.org as more important issues are being dealt with. We
> should however get more feedback and action in roughly a weeks time.
> 
> Some other translators such as Sergey (svyatogor), Sven (swift) and Bass
> (José) have already shown their interest in such an initiative. I filled
> in a bug last saturday here :
> http://bugs.gentoo.org/show_bug.cgi?id=23199
> 
> Hoping that sums it up and more people are interested in the idea, this
> is now open for suggestions.
> 
> Steph
-- 
Mail sent on Gentoo 1.4rc3 k2421 AMD 2600+
http://frlinux.net - frlinux@frlinux.net
http://gentoofr.org - Portail Francais sur Gentoo Linux



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-07-07 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26 19:48 [gentoo-dev] Internationalisation of gentoo.org (part II) FRLinux
2003-07-07 19:51 ` FRLinux [this message]

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=1057607460.14526.13.camel@localhost \
    --to=frlinux@frlinux.net \
    --cc=arachne@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-user-fr@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