public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Heinrich Wendel <lanius@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] User contributed documentation
Date: Sun, 20 Jul 2003 15:38:15 +0200	[thread overview]
Message-ID: <200307201538.15637.lanius@gentoo.org> (raw)

Hi,

I had a short discussion about this on irc with swift, but as he says this 
topic has never really been discussed, I want to post it here as well.

If you take a look at the "Documentatin, Tips & Tricks" section on 
forums.gentoo.org you can find a lot of usefull documentation about several 
parts of gentoo. I also submitted a doc (LTSP-Guide) before i became dev and 
this is now hosted by swift (http://dev.gentoo.org/~swift/), because there 
are no policies to bring this on the official gentoo page.
I propose to add a "User contributed documentation" - section to the gentoo 
docs page, where such things can be hosted, they would be somehow maintained 
by the authors.

mfg, Heinrich :)

--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-07-20 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 13:38 Heinrich Wendel [this message]
2003-07-21 21:49 ` [gentoo-dev] User contributed documentation Matthew Walker
2003-07-22  4:27   ` Sven Vermeulen

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=200307201538.15637.lanius@gentoo.org \
    --to=lanius@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