cvs: pearweb /doc pearfaq.xml

alexmerz Wed Aug 15 21:18:21 2001 EDT Modified files: /pearweb/doc pearfaq.xml Log: add answers

Index: pearweb/doc/pearfaq.xml diff -u pearweb/doc/pearfaq.xml:1.1 pearweb/doc/pearfaq.xml:1.2 --- pearweb/doc/pearfaq.xml:1.1 Tue Aug 14 04:42:03 2001 +++ pearweb/doc/pearfaq.xml Wed Aug 15 21:18:21 2001 @@ -1,187 +1,221 @@ -<?xml version='1.0' encoding='ISO-8859-1' ?> -<!-- $Id: pearfaq.xml,v 1.1 2001/08/14 08:42:03 ssb Exp $ --> -<!DOCTYPE book PUBLIC "-//Norman Walsh//DTD DocBk XML V1.7//EN" - "./dbxml/docbookx.dtd"> - -<book> - -<article class="faq"> -<artheader> - <title>PEAR-Developer FAQ</title> - <date>$Date: 2001/08/14 08:42:03 $</date> -</artheader> - -<qandaset> - <qandaentry> - <question> - <para> - How to become a PEAR contributer? - </para> - </question> - <answer> - <para> - ( by Author ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para> - How to contribute patches - </para> - </question> - <answer> - <para> - ( by Author ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - How to contribute patches for - <trademark>Outlook Express</trademark> users - </para> - </question> - <answer> - <para> - ( by Author ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - I want to contribute, in what areas could I do it? - </para> - </question> - <answer> - <para> - ( by Author ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - Why is PEAR seperated into pear/ and php4/pear/? - </para> - </question> - <answer> - <para> - ( by Author ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - Why differs the directory structure of pear/ and php4/pear/? - </para> - </question> - <answer> - <para> - ( by Author ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - Why a flat directory structure instead of a deep? - </para> - </question> - <answer> - <para> - ( by Author ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - Can I commit experimental/ unstable stuff? - </para> - </question> - <answer> - <para> - ( by Alexander Merz ) - </para> - <para> - Yes. But make sure, that you mark up the experimental/ unstable - status of the project in the documention. - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - Are different packages with similar features allowed? - </para> - </question> - <answer> - <para> - ( by Author ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - How should I write the documentation? - </para> - </question> - <answer> - <para> - ( by Author ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - What is the difference between a package, a class and a file? - </para> - </question> - <answer> - <para> - ( by Stig Sæther Bakken ) - </para> - <para> - the ANSWER is 42 - </para> - </answer> - </qandaentry> -</qandaset> - -</article> - -</book> \ No newline at end of file +<?xml version='1.0' encoding='ISO-8859-1' ?> +<!-- $Id: pearfaq.xml,v 1.2 2001/08/16 01:18:21 alexmerz Exp $ --> +<!DOCTYPE book PUBLIC "-//Norman Walsh//DTD DocBk XML V1.7//EN" + "./dbxml/docbookx.dtd"> + +<book> + +<article class="faq"> +<artheader> + <title>PEAR-Developer FAQ</title> + <date>$Date: 2001/08/16 01:18:21 $</date> +</artheader> + +<qandaset> + <qandaentry> + <question> + <para> + How to become a PEAR contributer? + </para> + </question> + <answer> + <para> + ( by Author ) + </para> + <para> + the ANSWER is 42 + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + How to contribute patches + </para> + </question> + <answer> + <para> + ( by Author ) + </para> + <para> + the ANSWER is 42 + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + How to contribute patches for + <trademark>Outlook Express</trademark> users + </para> + </question> + <answer> + <para> + ( by Author ) + </para> + <para> + the ANSWER is 42 + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + I want to contribute, in what areas could I do it? + </para> + </question> + <answer> + <para> + ( by Alexander Merz ) + </para> + <para> + The general directory for new PEAR-classes and moduls is + pear/ in the CVS-repository. The name of the directory of the + new class is build from the class name and the package name. + If you wrote a class called bar as a part of the package foo, + the name of the directory is foo_bar. So the resulting path + is pear/foo_bar. + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + Why is PEAR seperated into pear/ and php4/pear/? + </para> + </question> + <answer> + <para> + ( by Author ) + </para> + <para> + the ANSWER is 42 + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + Why differs the directory structure of pear/ and php4/pear/? + </para> + </question> + <answer> + <para> + ( by Author ) + </para> + <para> + the ANSWER is 42 + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + Why a flat directory structure instead of a deep? + </para> + </question> + <answer> + <para> + ( by Author ) + </para> + <para> + the ANSWER is 42 + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + Can I commit experimental/ unstable stuff? + </para> + </question> + <answer> + <para> + ( by Alexander Merz ) + </para> + <para> + Yes. But make sure, that you mark up the experimental/ unstable + status of the project in the documention. The best place to do + this is in the package.xml in the &lt;status&gt;-tag. + The values for this tag are + <simplelist> + <member> + <parameter>alpha</parameter> - first stages of + development, all things could change ( API, behavoir) + without advice, a lot of bugs are normal + </member> + <member> + <parameter>beta</parameter> - stable API, usable + software, bugs are possible + </member> + <member> + <parameter>devel</parameter> - a release intented for + developers from outside the core developers of the + class who want from other developers to test, give + feedback. + </member> + <member> + <parameter>stable</parameter> - the software was tested, + the API fixed, the documention wrote and is the + recommended release for users and production + enviroments. + </member> + <member> + <parameter>cvs</parameter> - a cvs snapshot from a + certain date + </simplelist> + ( list by Tomas V.V. Cox ) + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + Are different packages with similar features allowed? + </para> + </question> + <answer> + <para> + ( by Author ) + </para> + <para> + the ANSWER is 42 + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + How should I write the documentation? + </para> + </question> + <answer> + <para> + ( by Author ) + </para> + <para> + the ANSWER is 42 + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + What is the difference between a package, a class and a file? + </para> + </question> + <answer> + <para> + ( by Stig Sæther Bakken ) + </para> + <para> + the ANSWER is 42 + </para> + </answer> + </qandaentry> +</qandaset> + +</article> + +</book>