public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Gentoo Classes, a possible new method of spreading information
Date: Sat, 08 Oct 2005 00:23:04 -0700	[thread overview]
Message-ID: <pan.2005.10.08.07.23.03.792533@cox.net> (raw)
In-Reply-To: di7edr$otf$1@sea.gmane.org

R Hill posted <di7edr$otf$1@sea.gmane.org>, excerpted below,  on Fri, 07
Oct 2005 21:28:58 -0600:

> Dan Meltzer wrote:
>> 
>> 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? []
>> 
>> 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, [but it could be on
>> anything a dev wished].
> 
> 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.

What about asking in GWN for classes the users would like?  Start a
question submission que, then have the GWN editors select the common ones
they like and ask appropriate devs if they want to do a presentation.

Depending on interest, a few weeks after the original request for class
requests, they could start, once a week or once a month.  Announce the
subject a week ahead, then if a dev wants to have the original class in
IRC, do so, or he can just create a presentation to be featured in GWN. 
If it's originally on IRC, the (cleaned up/edited) log could be  featured
in GWN that way as well.

In either case, the initial class/tutorial would be mostly
non-interactive, as presented in the GWN writeup.  However, when
presented, an announcement would be made as to a date/time for a Q/A
session on IRC, a few days later.  Questions could be submitted thru a
link (email or whatever) for a couple days after the GWN presentation as
well, with selected submissions covered in the IRC session as well.  Then
the IRC session would be posted the following week.  (Thus, original
tutorial/presentation one week, a couple days for Q submissions b4 the
scheduled IRC Q/A session (and a day or two to go over them, if desired,
depending on how the scheduling and deadlines are worked out), then a
couple days to clean the log from it up and address any other submitted
questions if desired, for the GWN followup coverage a week after the
initial presentation.)

This would cover the timing issue of a scheduled IRC session, plus have
the advantage of multi-format, for those who don't do IRC, plus give folks
a couple days to come up with questions after the original presentation. 
The initial presentation probably wouldn't need IRC's interactivity
anyway, but it would preserve that element in the QA session.  Coverage
would be far wider as well, given the GWN coverage in all its forms (LWN
coverage, Gentoo site front page billing, the mailing list, in addition to
any proposed "class" site).

Subject known ahead, original lecture, Q/A and interactive lab session
a few days later, review and followup a few days after that at the next
lecture period, similar to a Uni class with a weekly lecture and separate
lab, except that it would bypass the scheduling difficulties of an global
internet-wide "university".

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-10-08  7:27 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 [this message]
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=pan.2005.10.08.07.23.03.792533@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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