<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Michelle Cox skrev:<br>
<blockquote cite="mid000301c6fa20$bad497f0$0300a8c0@inspiron"
type="cite">
<blockquote type="cite">
<pre wrap="">But to start with, I think it
is better to work within a sandbox, and wait to formally publishing it
on Drupal.org until it is judged ready. Why? I don't know if anyone else
feels like me, but I think it is intimidating to publish something which
for a fact will be scrutinized by many critical people. I therefore tend
to withhold my work until I'm dam sure that I can stand for it. If more
people feel like me, it will have a restraining influence on a
collaborative effort such as writing a new customer oriented
documentation. But if we work on a collaborative document clearly marked
as a sandbox (or draft or pre-alpha or whatever), then I and probably
many more would feel much easier to contribute in an early stage of
witting, and thereby reducing the risk of duplicated effort and increase
the chance of constructive criticism. Am I talking through my hat?
</pre>
</blockquote>
<pre wrap=""><!---->
I'm doing the same thing with the new user docs I'm writing. They're on my
site until they're good enough for Drupal.org.
</pre>
</blockquote>
<br>
Good to hear that I'm not alone. :-) But for writing the client
documentation, I suggest following principles<br>
<ul>
<li>a collective document ownership (cf. <a
href="http://www.extremeprogramming.org/rules/collective.html">collective
code ownership</a> of XP),<br>
</li>
<li><a href="http://en.wikipedia.org/wiki/Collaborative_editing">collaborative
editing</a> through a <a
href="http://en.wikipedia.org/wiki/Collaborative_editing">wiki</a> or
a <a href="http://en.wikipedia.org/wiki/Collaborative_real-time_editor">collaborative
editor</a> and<br>
</li>
<li>an encouraging attitude towards editing others writing (see for
an example <a
href="http://en.wikipedia.org/w/index.php?title=Drupal&action=history">all
contributions</a> made to the single Wikipedia article about Drupal).<br>
</li>
</ul>
So instead of having several efforts scattering all around the web, I
hope we all together can pull in the direction of creating an
industrial strength documentation of how to maintain a Drupal site.<br>
<br>
<br>
<blockquote cite="mid000301c6fa20$bad497f0$0300a8c0@inspiron"
type="cite">
<blockquote type="cite">
<pre wrap="">From one thing to another, it could be argued that this discussion
should be held on the documentation mailing list instead of here. But I
think that is a less good idea, at least for now, since we are talking
about documentation for consultants' customers. If we move this
discussion to the documentation mailing list, I'm afraid we will miss
many valuable and well-informed opinions.
</pre>
</blockquote>
<pre wrap=""><!---->
If you aren't willing to move to the doc list, at least cross-post there.</pre>
</blockquote>
<br>
It is not that I am unwilling to post on the doc list. I just thought
it could be a point to be in a less hurry to move the discussion from
the consultants' mailing list, since we are talking about a
documentation geared to the demand of consultants' customers. Maybe I
am wrong. :-)<br>
<br>
Another idea: Should we setup a group at <a class="moz-txt-link-freetext" href="http://groups.drupal.org/">http://groups.drupal.org/</a> for
this purpose?<br>
<br>
<br>
<blockquote cite="mid000301c6fa20$bad497f0$0300a8c0@inspiron"
type="cite">
<pre wrap="">
There is currently a major effort underway to redo the handbook and it would
be nice to have the doc team involved in this effort.
</pre>
</blockquote>
I've registered myself to <a class="moz-txt-link-abbreviated" href="mailto:documentation@drupal.org">documentation@drupal.org</a>.<br>
<br>
<br>
Regards,<br>
Thomas<br>
</body>
</html>