public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jan Kundrát" <jkt@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo Classes, a possible new method of spreading information
Date: Sat, 8 Oct 2005 10:00:58 +0200	[thread overview]
Message-ID: <200510081001.07687.jkt@gentoo.org> (raw)
In-Reply-To: <46059ce10510071821n672699bdhcd8d875e7293bed3@mail.gmail.com>

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

On Saturday 08 of October 2005 03:21 Dan Meltzer wrote:
> Okay, so that worked, but then I got to thinking, why not do these
> fairly regularly?  I do not profess to know enough to hold them about
> a large amount of topics, but I think this could surely supplant the
> current documentation process.  Here is basic rundown and example.

Hm, I don't like that. What's wrong with writing normal documentation and 
giving links to the users? IMHO it has a lot of advantages - it can be 
translated (and it is, in most cases), easily updated and is available for a 
wider range of users (I wouldn't read IRC log of 30 minutes lecture, but I'd 
read the doc).

Of course feel free to make a class before making "real doc", but IMHO it 
won't help the GDP people if you just give them IRC log.

Cheers,
-jkt

-- 
cd /local/pub && more beer > /dev/mouth

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

  parent reply	other threads:[~2005-10-08  8:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-08  1:21 [gentoo-dev] Gentoo Classes, a possible new method of spreading information Dan Meltzer
2005-10-08  3:28 ` [gentoo-dev] " R Hill
2005-10-07 23:02   ` Alec Warner
2005-10-08  7:23   ` Duncan
2005-10-08  8:00 ` Jan Kundrát [this message]
2005-10-08  9:34 ` [gentoo-dev] " Simon Stelling
2005-10-08  9:46   ` Simon Stelling
2005-10-08 17:36   ` Tres Melton
2005-10-10 16:48     ` 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=200510081001.07687.jkt@gentoo.org \
    --to=jkt@gentoo.org \
    --cc=gentoo-dev@lists.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