1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Teamwork</title><meta name="generator" content="DocBook XSL Stylesheets V1.40"><link rel="home" href="index.html" title="The GNOME Handbook of Writing Software Documentation"><link rel="up" href="index.html" title="The GNOME Handbook of Writing Software Documentation"><link rel="previous" href="indexs12.html" title="Basics of Documentation Style"><link rel="next" href="indexs14.html" title="Finishing A Document"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Teamwork</th></tr><tr><td width="20%" align="left"><a href="indexs12.html">Prev</a>�</td><th width="60%" align="center">�</th><td width="20%" align="right">�<a href="indexs14.html">Next</a></td></tr></table><hr></div><div class="sect1"><a name="teamwork"></a><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="teamwork"></a>Teamwork</h2></div></div><div class="sect2"><a name="teamworkgdp"></a><div class="titlepage"><div><h3 class="title"><a name="teamworkgdp"></a>Working With The GDP Team</h3></div></div><p>
2        The GDP team is a valuable resource for any documentation
3        author.  GDP members can answer most questions documentation
4        authors have during the course of their work. It is also
5        important to make sure you are not duplicating work of other
6        GDP members by visiting the <i>GDP Documentation
7        Status Table</i> (<a href="http://www.gnome.org/gdp/doctable/" target="_top">http://www.gnome.org/gdp/doctable/</a>) and
8        assigning a documentation item to yourself.  This table also
9        provides a forum for making suggestions and announcements for
10        each documentation item.  The best way to get in touch with
11        GDP members is on the #docs IRC channel at irc.gnome.org or
12        else by emailing the <a href="http://mail.gnome.org/mailman/listinfo/gnome-doc-list/" target="_top">
13        <i>gnome-doc-list mailing list</i></a>.
14      </p><p>
15        After an author has finished a document (or even a draft
16        version of the document), it is a good idea to ask a member of
17        the GDP team to read the document, checking it for grammar,
18        proper DocBook markup, and clarity.  One may typically find
19        another author to do this by either asking on the #docs IRC
20        channel at irc.gnome.org or by emailing the <a href="http://mail.gnome.org/mailman/listinfo/gnome-doc-list/" target="_top">
21        <i>gnome-doc-list mailing list</i></a>.
22      </p></div><div class="sect2"><a name="teamworkdevelopers"></a><div class="titlepage"><div><h3 class="title"><a name="teamworkdevelopers"></a>Working With Developers</h3></div></div><p>
23        Writing documentation typically involves a certain amount of
24        interaction with the developers of GNOME or the application
25        which is being documented.  Often a document author will need
26        to ask the developer technical questions during the course of
27        writing a document. After the document is finished, it is good
28        idea to ask the developer to read the document to make sure it
29        is technically correct.  The documentation author should also
30        make sure that the application author correctly binds and
31        packages the documentation with the application.
32      </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a href="indexs12.html">Prev</a>�</td><td width="20%" align="center"><a href="index.html">Home</a></td><td width="40%" align="right">�<a href="indexs14.html">Next</a></td></tr><tr><td width="40%" align="left">Basics of Documentation Style�</td><td width="20%" align="center"><a href="index.html">Up</a></td><td width="40%" align="right">�Finishing A Document</td></tr></table></div></body></html>
33