@meitar has raised an important question, how does one know whether to post something to this docs list serve or to the issue queue? He's also raising the issue of lack of visibility regarding the list serve, which is <a href="http://drupal.org/node/263767">relevant to the propsed new block for doc pages and being discussed there</a>.<br>
<br>This is how I would break down the "When Listserve? When Issue Queue?" question.<br><br><b>Doc listserve</b>: <i>discuss</i> docs strategy, approach, overall problems, announcements for IRC Docs meetings or other Doc meetings like a docs sprint.<br>
<br><b>Issue queue</b> <br>*for non-documentation team members: <br> --file as "bug" something that is a mistake in the docs section of the d.o. handbook. (If the person is on the docs team, that person should just fix it; no need to post in the queue.) <br>
--Submit request to join the documentation team.<br><br>*for anyone:<br> --make any formal request to change the way the Drupal project deals with documentation (sometimes these are actually filed in the webmasters queue or the infrastructure queue)<br>
--submit support request when desiring help in writing a document.<br> --submit feature request for needed doc that doesn't exist -- but person submitting can't or doesn't want to write it. (If person was able to and wanted to, person could just add it without filing an issue).<br>
<br>There is overlap and some duplication in that the responses to a formal proposal made in the queue will certainly contain opinions about the overall approach and strategy of docs, which may previously have come up on the list serve. But when they came up on the list serve, it was part of brainstorming or general discussion, not in the context of a formal proposal, and so it's okay that they are repeated on the issue queue.<br>
<br>Another way to think of all this is that the list serve is for vetting and the queue is for action.<br><br>Do other people agree with this -- have better ways of describing this?<br><br>Shai<br><br>