<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0">
<TITLE>Proposal - documentation subject matter experts</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Asterisk Friends,</FONT></SPAN></P>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">It was good to see some activity at the doc list. I agree that something needs to be done with the documentation. </FONT></SPAN></P>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">I would like to have some feedback abou</FONT><FONT SIZE=2 FACE="Arial">t the following idea:</FONT></SPAN></P>
<UL>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Identify people that would like to become a documentation subject matter expert. Some potential projects are: ZAP, SIP, H323, Dialplan, Fax, IAX, etc. They do not need to have the ability to code. Reading code to some extend would</FONT><FONT SIZE=2 FACE="Arial"> be great.</FONT></SPAN></P>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Create a modular manual that provides all the information that people need to know to get asterisk (based at subject) up and running. Take SIP as an example. I think that a good description of NATs and Firewalls could avoid a lot of question</FONT><FONT SIZE=2 FACE="Arial">s and would give a better understanding about how the channel needs to be configured. To be able to keep up with development is it required that</FONT> <FONT SIZE=2 FACE="Arial">‘</FONT><FONT SIZE=2 FACE="Arial">writers</FONT><FONT SIZE=2 FACE="Arial">’</FONT><FONT SIZE=2 FACE="Arial"> and developers</FONT> <FONT SIZE=2 FACE="Arial">‘</FONT><FONT SIZE=2 FACE="Arial">talk</FONT><FONT SIZE=2 FACE="Arial">’</FONT><FONT SIZE=2 FACE="Arial"> so that the new development can be put in the right documentation perspective</FONT><FONT SIZE=2 FACE="Arial">.</FONT><FONT SIZE=2 FACE="Arial"> It would be great if the developer would be willing to review the modifications that have been made to the documentation. This would improve the quality of the documentation.</FONT></SPAN></P>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Another advantage could be that the documentation could be</FONT> <FONT SIZE=2 FACE="Arial">‘</FONT><FONT SIZE=2 FACE="Arial">tested</FONT><FONT SIZE=2 FACE="Arial">’</FONT><FONT SIZE=2 FACE="Arial"> together</FONT><FONT SIZE=2 FACE="Arial"> with the software. This would again improve the quality of the documentation and could also encourage people to become an active tester of the software. This means that the whole project would benefit. </FONT></SPAN></P>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">I think that at a later stage needs to be discus</FONT><FONT SIZE=2 FACE="Arial">sed about the infrastructure that should be used. Let</FONT><FONT SIZE=2 FACE="Arial">’</FONT><FONT SIZE=2 FACE="Arial">s start to create content.</FONT></SPAN></P>
</UL>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">I don</FONT><FONT SIZE=2 FACE="Arial">’</FONT><FONT SIZE=2 FACE="Arial">t mind to step up for the SIP subject. </FONT></SPAN></P>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Looking forward to your comments,</FONT></SPAN></P>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Henk</FONT></SPAN></P>
<P ALIGN=LEFT><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial"> </FONT></SPAN></P>
<BR>
</BODY>
</HTML>