Re: FreeBSD-newbies group is a compromise community.

From: clayton rollins (crollins666_at_hotmail.com)
Date: 03/25/04

  • Next message: Nikolas Britton: "Re: SV: CPU Clock Freq" 
    To: freebsd-newbies@freebsd.org
Date: Thu, 25 Mar 2004 09:36:11 +0000

    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

    _______________________________________________
    freebsd-newbies@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
    To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org"

  • Next message: Nikolas Britton: "Re: SV: CPU Clock Freq"

    Relevant Pages

    • Re: The List Problem: a pons asinorus for Cantorists
      ... Because I introduced it, to facilitate the exposition, ... is considered as a postulated infinite list. ... List members are subsequent relative to previous list ... cardinals, lists, etc.. ...
      (sci.math)
    • Re: [Full-Disclosure] Re: [Fwd: [TH-research] Modified Bagle]
      ... this has nothing to do with these lists Nick ... Since we were attacked, I will now forward my reply to TH-Research, I ... OKAY now - mandatory reading to list members. ...
      (Full-Disclosure)
    • Re: [SLE] cut n paste
      ... the lists, but annoying for replying to private email. ... personal preference of list members is that people need to setup ... Matthew Stringer wrote:" ...
      (SuSE)
    • Re: Delist this person: From: petsupermarket
      ... addresses into the "From:" headers of list email. ... an RFE;-) My thinking is that unless you are running lists yourself ... If people agree that putting list members' real email addresses into ...
      (Fedora)
    • Re: [SLE] Hitting reply-all to the list
      ... Have you looked in your general and/or folder specific settings for list ... most lists ban CC'ing of list members as part of their ... Check the headers for your unsubscription address ...
      (SuSE)