public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: R Hill <dirtyepic.sk@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Gentoo Classes, a possible new method of spreading information
Date: Fri, 07 Oct 2005 21:28:58 -0600	[thread overview]
Message-ID: <di7edr$otf$1@sea.gmane.org> (raw)
In-Reply-To: <46059ce10510071821n672699bdhcd8d875e7293bed3@mail.gmail.com>

Dan Meltzer wrote:
> Hello,
> 
> I am a frequenter of #gentoo-*, as many of you know :)
> 
> Tonight, hanging out in #gentoo, I observed a huge amount of incorrect
> information once again.. tonight about profiles, cascading and all
> that jazz, which to be honest is fairly undocumented.  I decided to
> give a miniclass on how it worked.  ferringb and antarus sat in, and
> it was just an off the cuff information/QA session.
> 
> 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.
> 
> Developer A decides to speak about a specific aspect of portage, the
> discussion is announced on lists and in gwn a week or so in advance. 
> The discussion could take place in a channel such as #gentoo-class,
> and logged.  The developer would cover it as he saw fit, and then have
> a Q/A period after.  The entire class is logged, and added to the
> website on a publically accessible page.  If the docs team thinks its
> a useful subject, they could translate into a more formal page, and
> use the logs for reference, if not, it would still be availible
> information to anyone wishing to read it.
> 
> My thoughts are this would be best suited to Gentoo-specific things,
> portage, gentoo's infrastructure, baselayout, anything else
> ideosynconatic (sp?).  But, I suppose it could be on anything if the
> developer so wished.
> 
> Ideas? thoughts? comments?
> 
> Lets hear em :)

I think quick-basics tutorials like this would be a great addition to 
GWN, but if the IRC Q&A format works then I say go for it.

--de.

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-10-08  3:33 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 ` R Hill [this message]
2005-10-07 23:02   ` [gentoo-dev] " Alec Warner
2005-10-08  7:23   ` Duncan
2005-10-08  8:00 ` [gentoo-dev] " Jan Kundrát
2005-10-08  9:34 ` 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='di7edr$otf$1@sea.gmane.org' \
    --to=dirtyepic.sk@gmail.com \
    --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