public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@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 16:15:41 +0200	[thread overview]
Message-ID: <200308051615.52068.pauldv@gentoo.org> (raw)
In-Reply-To: <1060090287.1449.17.camel@lisa.thedoh.com>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1196 bytes --]

On Tuesday 05 August 2003 15:31, Lisa Marie Seelye wrote:
> On Mon, 2003-08-04 at 14:31, Sven Vermeulen wrote:
> > All feedback appreciated, especially from the infrastructure folks as it
> > is mainly infrastructure related.
>
> I've been pondering this for a while.
>
> What I came up with was a directory structure that would look something
> like this:
>
> /$herd/$subproject/$lang/document.xml
>

Let me explain it once again. A herd is a group of ebuilds. Nothing more, 
nothing less. Such a group of ebuilds has maintainers, and an owner project. 
That project can have webpages, a herd cannot. A project can have multiple 
herds. By definition all people inside any of the herds of a project are part 
of the project in some way. (There can be additional people in the project 
though). The project has/will get a root under which it can have its own 
pages (in gentoo style), in an ordering that is basically free to the 
project. Although there will probably have to be some kind of "official" 
project page that uses a predefined setup (or even a new dtd)

Paul

-- 
Paul de Vrieze
Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.cs.kun.nl/~pauldv

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

  parent reply	other threads:[~2003-08-05 14:15 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 [this message]
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=200308051615.52068.pauldv@gentoo.org \
    --to=pauldv@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