Date: Sun, 10 Oct 1999 19:51:56 -0400 (EDT) From: Barrett Richardson <barrett@phoenix.aye.net> To: Michael Lucas <mwlucas@blackhelicopters.org> Cc: Chris Parry <laotzu@juniper.net>, blk@skynet.be, stable@FreeBSD.ORG Subject: Re: Roasting Newbies Message-ID: <Pine.BSF.4.01.9910101936500.18882-100000@phoenix.aye.net> In-Reply-To: <199910091303.JAA33525@blackhelicopters.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 9 Oct 1999, Michael Lucas wrote: > > But I'd rather intercept these before they reach a developer, and > point said newbie at a web page that says "This is how you submit a > NIC driver report." Make the page very detailed. Show said newbie > that they, too, can actually gather the necessary information to file > a useful and sensible PR. By the time said developer checks his mail, > I want him to see not only the trouble report, but the reply that > says, "Check out http://..../nic-trouble-report.html" > As an end user something I could make use of is a periodic posting at regular intervals of some basic info on where to find stuff like http://..../nic-trouble-report.html. What consists of a problem that should be presented in -hackers, -current, -stable .... etc. Maybe some links to stuff like Greg's tips on formatting e-mail, using -question effectively. A pointer on where to find information on how to collect useful information from a panic, stuff like that. Just kind of a mini FAQ or HOWTO that explains how to "go with the flow" when presenting problems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.01.9910101936500.18882-100000>