Date: Thu, 10 Dec 1998 12:15:06 +1030 From: Greg Lehey <grog@lemis.com> To: Mike Smith <mike@smith.net.au>, van.woerkom@netcologne.de Cc: eivind@yes.no, imp@village.org, archie@whistle.com, rnordier@nordier.com, vanmaren@fast.cs.utah.edu, committers@FreeBSD.ORG Subject: Re: problem reports Message-ID: <19981210121506.H12688@freebie.lemis.com> In-Reply-To: <199812100114.RAA01641@dingo.cdrom.com>; from Mike Smith on Wed, Dec 09, 1998 at 05:14:23PM -0800 References: <199812100022.BAA77651@oranje.my.domain> <199812100114.RAA01641@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 9 December 1998 at 17:14:23 -0800, Mike Smith wrote: >>> Teams, and cycle between the members (to reduce volume). >> >> It would be nice way for me and possibly for others to learn more >> about FreeBSD hacking, if a senior team member could have a first >> look at those bugs, give hints on how to fix them to volunteers >> and later reviews the solution attempts. >> Some kind of master/apprentice thing. > > This typically degenerates into the "tutor" doing all the work, with > the "pupil" not actually getting much out of it. If it's done incorrectly, yes. It can also be done correctly. > A better way is for the pupil to find a bug report that sounds > interesting and not too scary, and spend some time learning about > the subsystem(s) involved, eventually getting to understand the bug > in that context. While doing that, asking questions of the tutor > places less load on the tutor and gives the pupil more "real" > exposure. That's a correct way. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981210121506.H12688>