Date: Thu, 25 Mar 2004 09:36:11 +0000 From: "clayton rollins" <crollins666@hotmail.com> To: freebsd-newbies@freebsd.org Subject: Re: FreeBSD-newbies group is a compromise community. Message-ID: <Sea1-F132hcRA23ZeZF0000b87a@hotmail.com>
next in thread | raw e-mail | index | archive | help
Hi List, Sorry, the thread has become so fragmented at this point, I can't really find a good last message to send a reply to. Nor can I really find a good way to integrate the past comments. This message is intended as a general reply to all the previously mentioned points in this thread. To state my main point firstly, the problem, as I see it, is not a matter of people asking technical questions, but a matter of people answering questions here. This is a problem (again, IMHO) because more authoritative and knowlegable voices are not generally present here. I would then propose that, in cases of technical replies, that a minimal rule of CC'ing the -questions list be imposed. (With the more knowledgeable members of this list forwarding to questions when another newbie forgets.) While this uses far more bandwidth, it reduces the constraints presently on this list and allows for more colorful replies than "send this to -questions." I have, personally, tried to follow such a path when I do actually attempt to answer a question. For me, a good guideline for a -newbies question has been: if the question is clear and I feel I can contribute something: Reply and CC to -questions If it's a FAQ or covered in the documentation: Give a link to the doc.s and let the sender know the proper list is -questions. If the question is unclear: Notify the user of the proper list and point out any problems with the question. While I know that many list members already follow personal rules, I would like to have solid guidelines and have them reflected in the charter. As a secondary point, I would also like to get, at least, a general agreement on what we should consider a technical reply. I would propose the simple criteria of whether or not the reply is advice. (example: it should be alright to point a user to a document, but not to say that a user should follow the steps in a document to solve a specific problem.) I would like to see these issues specified, again, at least by general agreement, then to ask our fellows on -questions to agree to some level of integration, then to document the new arrangement and/or begin operating under such rules. While I, personally, have no problem using the current system, I have replied to others to post to -questions quite often, and not seen the message to -questions. I can't help but feel that some of those people gave up on freebsd, rather than take the time to send yet another message. Other than creating an -install list, allowing for a link between the two lists seems the only reasonable method for addressing this issue. I know this thread is somewhat dead, but I finally had a free minute to reply to this. questions/comments welcome. Regards, Clayton Rollins PS. Recently a list member wanted to share the advice they had recieved. While I agree that this is a bad idea, I would encourage people in such a situation to rephrase the message as "what worked for me" and/or "documents I found useful." I'd also think it would be appropriate to CC -questions for technical-type stuff (for archiving and possibly some correction by the -questions members :) ). _________________________________________________________________ All the action. All the drama. Get NCAA hoops coverage at MSN Sports by ESPN. http://msn.espn.go.com/index.html?partnersite=espn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Sea1-F132hcRA23ZeZF0000b87a>