[documentation] Add disclaimer to all handbook pages

[Steven Peck]

On Thu, Jun 5, 2008 at 3:01 AM, Nathaniel Catchpole
<catch56 at googlemail.com> wrote:
> Whilst thinking about the contributors block and last updated info, it
> occurred to me we don't have a disclaimer displayed for all handbook pages.
> I think it'd make sense to have something displayed on all pages to make it
> clear that it's community contributed documentation etc. - might be worth
> putting in the contributors block. "All documentation is contributed by
> volunteers and may not have been checked for accuracy" something like that.
>
> For example, code snippets probably need this more than most.
>
> http://drupal.org/handbook/customization/snippets - has a disclaimer
> http://drupal.org/node/45471 - (theme snippets parent) has a disclaimer
> http://drupal.org/node/35728 - an actual code snippet, doesn't have a
> disclaimer. Unless I find the snippet via the handbook hierarchy (and IMO
> more people will find it from incoming links, irc, google and drupal.org
> search than clicking through), I won't see the disclaimer.
>
> If the block happens, then it's just an extra sentence to add, but it'd need
> to be carefully worded - since equally we don't want to give the idea that
> there's official, non-volunteer documentation hiding somewhere.
>
> Nat
>
>
Historically the text is there because there was concern that anything
in the handbook would be seen as 'OFFICIAL' and 'SAFE' which it is not
official or safe.  It's there because people contributed it.  It's not
that it's unsafe or unofficial it's that it's just something someone
contributed and solved there problem.

I don't really see a need to go overboard in yet more
warnings/disclaimers.  While we have unpublished unsafe, exploitable
code as people came across it we do not have a formal review policy
because there is not have enough knowledgeable people for such.  (plus
that would upset the people who believe that filters are inherently
evil and I'd get more email :)

I'd rather see a more generic testing and approach page for how/when
to use snippets or bits and pieces as opposed to writing a module.  Of
course, things like that are very hard to write for the diverse skill
levels and audiences we have.

Also, on all the pages, we have the CC license block.  I have to catch
up on the block text issue in the queue this weekend when I am not on
call.

Steven Peck
http://www.blkmtn.org