Re: [PHP] PHP RFC # 0001 --- List Etiquette - PHP

This is a discussion on Re: [PHP] PHP RFC # 0001 --- List Etiquette - PHP ; On Nov 28, 2007 10:56 AM, Jay Blanchard <jblanchard@pocket.com> wrote: > [snip] > So the summary of my proposal is as follows: > > 1.) An issue has been identified with the list whereby > improper archival will likely lead ...

+ Reply to Thread
Results 1 to 3 of 3

Re: [PHP] PHP RFC # 0001 --- List Etiquette

  1. Default Re: [PHP] PHP RFC # 0001 --- List Etiquette

    On Nov 28, 2007 10:56 AM, Jay Blanchard <jblanchard@pocket.com> wrote:
    > [snip]
    > So the summary of my proposal is as follows:
    >
    > 1.) An issue has been identified with the list whereby
    > improper archival will likely lead to repeat questions and unnecessary
    > traffic to the list.
    > 2.) I propose that we discontinue the act of subject
    > modification to indicate a change in status of the issue (SOLVED,
    > ALSO, ANOTHER PROBLEM, etc.) unless a completely different problem is
    > reached or question is asked. This will allow a step-by-step document
    > (of sorts) to be created and made "searchable" on the web.
    > [/snip]
    >
    > This has been the expected behavior (adding [SOLVED]) for a long time
    > though it does not occur as often as it should. It has been in the
    > NEWBIE GUIDE for a long time and has been a de-facto standard on IT or
    > computer related mailing lists like this for years.
    >



    Jay,

    See how simple it was to remove the [SOLVED] tag and maintain the
    track of the discussion?

    I'm aware that the NEWBIE GUIDE has that entry. For those not aware:

    9. It's always a good idea to post back to the list once you've solved
    your problem. People usually add [SOLVED] to the subject line of their
    email when posting solutions. By posting your solution you're helping
    the next person with the same question. [contribued by Chris W Parker]

    However, doing this defeats the purpose of a mailing list archive,
    and prompts unnecessary repetition of help requests for an issue that
    may have been "discussed to death" just five days prior. Again, the
    [SOLVED] tag is great on a forum, where you can quickly scan for that
    topic that you know has a solution. However, on a mailing list it
    only serves to create confusion, separation of problem and solution,
    and exasperation on behalf of the searcher when viewing the issue on a
    search engine or in the archives.

    If we expect people to first attempt to help themselves, we should
    not knowingly contribute to their inevitable failure.

    --
    Daniel P. Brown
    [office] (570-) 587-7080 Ext. 272
    [mobile] (570-) 766-8107

    If at first you don't succeed, stick to what you know best so that you
    can make enough money to pay someone else to do it for you.

  2. Default RE: [PHP] PHP RFC # 0001 --- List Etiquette

    [snip]
    However, doing this defeats the purpose of a mailing list archive,
    and prompts unnecessary repetition of help requests for an issue that
    may have been "discussed to death" just five days prior. Again, the
    [SOLVED] tag is great on a forum, where you can quickly scan for that
    topic that you know has a solution. However, on a mailing list it
    only serves to create confusion, separation of problem and solution,
    and exasperation on behalf of the searcher when viewing the issue on a
    search engine or in the archives.
    [/snip]

    I just wanted to point out that putting SOLVED on a mailing list subject
    line has been SOP since the dawn of mailing lists on ARPANet

  3. Default Re: [PHP] PHP RFC # 0001 --- List Etiquette

    On Nov 28, 2007 11:16 AM, Jay Blanchard <jblanchard@pocket.com> wrote:
    > [snip]
    > However, doing this defeats the purpose of a mailing list archive,
    > and prompts unnecessary repetition of help requests for an issue that
    > may have been "discussed to death" just five days prior. Again, the
    > [SOLVED] tag is great on a forum, where you can quickly scan for that
    > topic that you know has a solution. However, on a mailing list it
    > only serves to create confusion, separation of problem and solution,
    > and exasperation on behalf of the searcher when viewing the issue on a
    > search engine or in the archives.
    > [/snip]
    >
    > I just wanted to point out that putting SOLVED on a mailing list subject
    > line has been SOP since the dawn of mailing lists on ARPANet
    >


    Yeah, I know, and I certainly hope you realize I'm not shooting
    you down on that either. Even in the list itself it makes some sense,
    as we can see that the issue has been solved. However, due to the
    threading of the message it still separates it, so even a user who may
    have been away for a few days may not notice that the issue was
    resolved, and may respond to a defunct thread.

    --
    Daniel P. Brown
    [office] (570-) 587-7080 Ext. 272
    [mobile] (570-) 766-8107

    If at first you don't succeed, stick to what you know best so that you
    can make enough money to pay someone else to do it for you.

+ Reply to Thread