svn commit: samba-web r522 - in trunk/docs/FAQ: .

[deryck at samba.org]

Author: deryck
Date: 2005-01-26 18:49:32 +0000 (Wed, 26 Jan 2005)
New Revision: 522

WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-web&rev=522

Log:

Finish off the general FAQ I started.

I'll give this a day or so to wait for feedback,
then I'll link to it in the site-wide nav.

deryck


Modified:
   trunk/docs/FAQ/index.html


Changeset:
Modified: trunk/docs/FAQ/index.html
===================================================================
--- trunk/docs/FAQ/index.html	2005-01-26 17:03:23 UTC (rev 521)
+++ trunk/docs/FAQ/index.html	2005-01-26 18:49:32 UTC (rev 522)
@@ -7,25 +7,101 @@
 
 <h3>What is Samba?</h3>
 
+<p>Samba is a suite of programs that enables interoperability between Linux/Unix 
+servers and Windows clients.  See <a href="/samba/what_is_samba.html">What Is
+Samba?</a> for more.</p>
+
 <h3>What is the Samba Team?</h3>
 
+<p>If someone is on the Samba Team, this means they have commit rights to the
+Samba Subversion tree.  Samba Team members, then, are the ones who maintain
+Samba, develop new features, and apply patches from the larger Samba community,
+to name just a few areas of respoonsibility.</p>
+
 <h3>How do I contact a Samba Team member?</h3>
 
+<p>See the <a href="/samba/team/">Samba Team</a> page for a list of Team member
+emails and websites.  Most can be reached through the <a href="https://lists.samba.org/mailman/listinfo/samba-technical">samba-technical</a> mailing
+list or on <a href="/samba/irc.html">IRC</a>.</p>
+
 <h3>How can I get help with Samba?</h3>
 
+<p>The <a href="https://lists.samba.org/mailman/listinfo/samba">Samba mailing 
+list</a> would be your best bet.  If you are seeking someone who provides
+commercial support services for Samba, please see the <a href="/samba/support/">
+support providers lists</a>.</p>
+
 <h3>How can I keep up to date with Samba development?</h3>
 
+<p>For general information, such as release announcements, see 
+<a href="/http://news.samba.org/">http://news.samba.org/</a>.
+For more indepth info on the daily work of Samba development,
+it's best to subscribe to the <a href="https://lists.samba.org/mailman/listinfo/samba-technical">samba-technical</a> mailing list, or visit 
+#samba-technical on irc.freenode.net.  The obsessive-compulsive will follow
+both.</p>
+
+<h3>How can I get involved with Samba development?</h3>
+
+<p>The usual course is to become active on the mailing lists and/or
+IRC first.  Then, when you spot a bug or think of some cool feature you'd
+like to see Samba implement, work up a patch and submit it to the samba-technical
+mailing list.</p>
+
+<p>The really thorough contributor will also find the coresponding bug
+in <a href="https:bugzilla.samba.org/">Bugzilla</a> and attach the patch there.
+Be sure to mention you've done this when posting to the samba-technical mailing
+list.</p>
+
+<h3>Will you include my patch in the next release?</h3>
+
+<p>If the patch is a bug fix, and it can be incorporated without an adverse 
+affect on other functionality, then yes, it will likely be included.</p>
+
+<p>If the patch implements a new feature, then larger questions about usefulness 
+and maintainability also have to be addressed.  Generally, though, we try
+to include as much good work as we can.</p>
+
 <h3>Which Samba version should I run?</h3>
+The Samba 2.2 branch is no longer maintained.  It's EOL was October 1, 2004.</p>
 
+<p>Samba4 is a development branch that hasn't yet had an initial release.  If 
+you are a developer wanting to play with the bleeding-edge of the work done on 
+Samba, try <a href="http://websvn.samba.org/cgi-bin/viewcvs.cgi/branches/SAMBA_4_0/">Samba4</a>, 
+which you'll obviously have to build yourself.  You can also try 
+<a href="http://websvn.samba.org/cgi-bin/viewcvs.cgi/trunk/">Trunk</a> in the 
+Subversion source tree, if you want to experiement with upcoming 3.0.x 
+features.</p>
+
+<p>The current stable, production Samba server is the Samba 3.0 branch.  The
+most recent release is always the recommended version for production use.  
+See the <a href="/samba/history">release history</a> page for an overview
+of current and past releases.</p>
+
 <h3>How do I verify a tarball with the GnuPG signature?</h3>
 
-<h3>How can I get involved with Samba development?</h3>
+<p>Using GnuPG, simply download the Samba source distribution, the tarball 
+signature, and the Samba distribution public key.  Then run:</p>
 
-<h3>Will you include my patch for XYZ feature in the next release?</h3>
+<pre>
+$ gpg --import samba-pubkey.asc
+$ gunzip samba-<em>version</em>.tar.gz
+$ gpg --verify samba-<em>release</em>.tar.asc
+</pre>
 
+<p>Please notice, the signature is checked against the <em>uncompressed</em>
+tarball.</p>
+
 <h3>What should I do if I think I've found a security issue?</h3>
 
+<p>Please send mail to <a href="mailto:security at samba.org">security at samba.org</a>.
+Provide any relevant information you can, so that we can recreate your
+test and confirm your results.</p>
+
 <h3>What should I do if I think I've found a bug?</h3>
 
+<p>Please file a bug report at <a href="https://bugzilla.samba.org/">https://bugzilla.samba.org/</a>. 
+You could also send mail to the <a href="https://lists.samba.org/mailman/listinfo/samba-technical">samba-technical</a> mailing list providing any relevant info
+while mentioning you've filed a bug report.</p>
 
+
 <!--#include virtual="/samba/footer.html" -->