public inbox for gentoo-doc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jan Kundrát" <jkt@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Cc: Theo Chatzimichos <tampakrap@gentoo.org>, dberkholz@gentoo.org
Subject: Re: [gentoo-doc] Re: okupy, a Django rewrite of www.g.o
Date: Thu, 02 Jun 2011 13:47:09 +0200	[thread overview]
Message-ID: <4DE7783D.8060508@gentoo.org> (raw)
In-Reply-To: <BANLkTimu8t0cXHEEz72kS5DOR95Kuy1wug@mail.gmail.com>

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

On 06/02/11 12:29, Theo Chatzimichos wrote:
> Sure, I contacted Josh who showed much interest to my idea, and Infra
> to make sure they (we) are willing to replace gorg

Hi Theo, thanks for clarification and for your reply. Too bad Josh did
not pass the word along the GDP. Given how much stuff he does, I'm sure
he was just swamped with work.

> Gorg currently has two very important bugs open in bugzilla.

I went through the Bugzilla [1] before I sent that mail, hence this
question. Bug 336055 looks like an Apache problem (and is trivially
fixable), bug 342569 is a feature of how the Gentoo-specific XSLT
stylesheets work, and in no way Gorg-specific (and could be probably
RESO/INVALID immediately). Looks like the only real issue is bug 315487,
the compatibility with Ruby 1.9.

> We've faced a couple more recently.

Again, this is rather hard to evaluate without any evidence. I've been
running Gorg on a non-Gentoo web site for years, so I do agree that it
takes some effort to set up (like any other server application), but
without specific references to problems, it's hard to judge how much of
a troublemaker Gorg really is.

I do understand your desire not to use abandoned projects -- that's a
very reasonable stance.

> Nothing will change for GDP. The GuideXML will continue to exist, you
> will be able to edit XML files directly as usual. There will be only
> improvements here (like stats for translators, an editor, etc).

See, this is *exactly* why I wrote this mail. What are "statistics for
translators"? I'm a translator myself, and nobody asked me what could
help me. What translators indicated that they consider that an
improvement over current way with metadoc.xml/overview.xml/trads.rb?

I welcome the change to git, it's great that you're willing to undertake
it, but it will surely affect the way how GDP works.

Whether a WYSIWYG editor is an improvement (or would just cause troubles
for translators due to line noise in diffs) is debatable IMHO, but that
discussion has been already started and abandoned several times.

Cheers,
Jan

[1] http://bugs.gentoo.org/buglist.cgi?quicksearch=gorg&list_id=200467

-- 
Trojita, a fast e-mail client -- http://trojita.flaska.net/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2011-06-02 11:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 10:13 [gentoo-doc] okupy, a Django rewrite of www.g.o Jan Kundrát
2011-06-02 10:29 ` [gentoo-doc] " Theo Chatzimichos
2011-06-02 11:47   ` Jan Kundrát [this message]
2011-06-02 11:54     ` Theo Chatzimichos
2011-06-02 12:15       ` Jan Kundrát
2011-06-02 17:22         ` wireless
2011-06-02 18:35           ` Nils Larsson
2011-06-05 22:51           ` Jan Kundrát
2011-06-07  9:35     ` Joshua Saddler

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=4DE7783D.8060508@gentoo.org \
    --to=jkt@gentoo.org \
    --cc=dberkholz@gentoo.org \
    --cc=gentoo-doc@lists.gentoo.org \
    --cc=tampakrap@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