cvs: peardoc /ru/contributing howto.xml

kvn Mon Jan 28 13:08:53 2002 EDT Modified files: /peardoc/ru/contributing howto.xml Log: Finished Index: peardoc/ru/contributing/howto.xml diff -u peardoc/ru/contributing/howto.xml:1.1 peardoc/ru/contributing/howto.xml:1.2 --- peardoc/ru/contributing/howto.xml:1.1 Tue Jan 15 08:50:15 2002 +++ peardoc/ru/contributing/howto.xml Mon Jan 28 13:08:53 2002 @@ -1,49 +1,51 @@ <?xml encoding="iso-8859-1"?> -<!-- $Revision: 1.1 $ --> +<!-- $Revision: 1.2 $ --> <chapter id="contributing-howto"> - <title>How to contribute to PEAR</title> + <title>ëÁË ÓÏÄÅÊÓÔ×Ï×ÁÔØ Ó PEAR</title> <simpara> - This chapter describes how to contribute to the PEAR project. + üÔÏÔ ÒÁÚÄÅÌ ÒÁÓËÁÚÙ×ÁÅÔ, ËÁË ÓÏÄÅÊÓÔ×Ï×ÁÔØ Ó ÐÒÏÅËÔÏÍ PEAR. </simpara> <sect1 id="contributing-introduction"> - <title>Introduction</title> + <title>÷ÓÔÕÐÌÅÎÉÅ</title> - <para>Since PEAR is an open-source project, everybody is - welcomed to contribute to it.</para> + <para>ôÁË ËÁË PEAR - ÜÔÏ ÐÒÏÅËÔ Ó ÏÔËÒÙÔÙÍ ÉÓÈÏÄÎÙÍ ËÏÄÏÍ, ËÁÖÄÙÊ ÍÏÖÅÔ + ÓÏÄÅÊÓÔ×Ï×ÁÔØ Ó ÎÉÍ.</para> - <para>In order to keep the whole project well organized and - to create a clear structure, we have decided to set up some - common rules, everybody has to stick to when he want's to - contribute to PEAR.</para> + <para> + þÔÏÂÙ ÓÏÈÒÁÎÉÔØ ×ÅÓØ ÐÒÏÅËÔ ÈÏÒÏÛÏ ÏÒÇÁÎÉÚÏ×ÁÎÎÙÍ É ÓÔÒÕËÔÕÒÉÒÏ×ÁÎÎÙÍ, + ÍÙ ÒÅÛÉÌÉ ÕÓÔÁÎÏ×ÉÔØ ÎÅÓËÏÌØËÏ ÏÓÎÏ×ÎÙÈ ÐÒÁ×ÉÌ, + É ËÁÖÄÙÊ, ËÔÏ ÏËÁÚÙ×ÁÅÔ ÓÏÄÅÊÓÔ×ÉÅ PEAR, ÄÏÌÖÅÎ ÉÚ ÐÒÉÄÅÒÖÉ×ÁÔØÓÑ. + </para> </sect1> <sect1 id="contributing-requirements"> - <title>Requirements</title> + <title>ôÒÅÂÏ×ÁÎÉÑ</title> - <para>If you have written something, that you think should - belong to PEAR, you have to pay attention to the following - points:</para> + <para>åÓÌÉ ×Ù ÞÔÏ-ÔÏ ÎÁÐÉÓÁÌÉ, É ÄÕÍÁÅÔÅ, ÞÔÏ ÜÔÏ ÄÏÌÖÎÏ ÂÙÔØ × PEAR, + ×Ù ÄÏÌÖÎÙ ÏÂÒÁÔÉÔØ ×ÎÉÍÁÎÉÅ ÎÁ ÔÁËÉÅ ×ÅÝÉ: + </para> <para> <itemizedlist> <listitem> - <simpara>Your code has to be compliant to the <ulink url=" - standards.php">PEAR coding standards</ulink>. This is - necessary because PEAR has the aim to provide well suited - and standards compliant source code.</simpara> + <simpara> + ÷ÁÛ ËÏÄ ÄÏÌÖÅÎ ÂÙÔØ ÓÏ×ÍÅÓÔÉÍÙÍ ÓÏ <ulink url=" + standards.php">ÓÔÁÎÄÁÒÔÁÍÉ ËÏÄÉÒÏ×ÁÎÉÑ PEAR</ulink>. + üÔÏ ÎÅÏÂÈÏÄÉÍÏ, ÐÏÔÏÍÕ ÞÔÏ ÃÅÌØ PEAR - ÜÔÏ ÐÒÅÄÌÏÉÔØ + ÈÏÒÏÛÏ ÓÏ×ÍÅÓÔÉÍÙÊ É ÓÔÁÎÄÁÒÔÎÙÊ ÉÓÈÏÄÎÙÊ ËÏÄ. + </simpara> </listitem> <listitem> - <simpara>You are willing and able to maintain your code and to fix - upcoming bugs in your code once you have commited it to the PEAR - project. + <simpara>ëÁË ÔÏÌØËÏ ×Ù ÞÔÏ-ÔÏ ÄÏÂÁ×ÉÌÉ × PEAR, ×Ù ÄÏÌÖÎÙ ÂÙÔØ × ÓÏÓÔÏÑÎÉÉ ÕÐÒÁ×ÌÑÔØ ×ÁÛÉÍ ËÏÄÏÍ É ÉÓÐÒÁ×ÌÑÔØ + ÐÏÑ×ÌÑÀÝÉÅÓÑ ÏÛÉÂËÉ. </simpara> </listitem> <listitem> - <simpara>You are willing document your code in an appropriate - way. The prefered way of documentation is Docbook XML.</simpara> + <simpara>÷Ù ÄÏÌÖÎÙ ÄÏËÕÍÅÎÔÉÒÏ×ÁÔØ ×ÁÛ ËÏÄ ÎÁÄÌÅÖ×ÝÉÍ ÐÕÔÅÍ. îÁÉÌÕÞÛÉÊ ÄÌÑ ÜÔÏÇÏ ÐÕÔØ - ÜÔÏ Docbook XML. + </simpara> </listitem> </itemizedlist> @@ -53,39 +55,45 @@ </sect1> <sect1 id="contributing-introducing"> - <title>Introducing your code</title> + <title>ðÒÅÄÓÔÁ×ÌÅÎÉÅ ×ÁÛÅÇÏ ËÏÄÁ ÎÁ ÒÁÓÓÍÏÔÒÅÎÉÅ</title> - <para>Once you can verify that all the requirements listed - above are ok for you, you can tell us about your plan.</para> + <para> + ëÁË ÔÏÌØËÏ ×Ù ÐÒÏ×ÅÒÉÌÉ, ÞÔÏ ×ÓÅ ÔÒÅÂÏ×ÁÎÉÑ, ÏÐÉÓÁÎÎÙÅ ×ÙÛÅ, + ×ÙÐÏÌÎÑÀÔÓÑ ×ÁÍÉ, ×Ù ÍÏÖÅÔÅ ÒÁÓÓËÁÚÁÔØ ÎÁÍ Ï ×ÁÛÉÈ ÐÌÁÎÁÈ. + </para> - <para>The best way to do so is to tell the people on the <ulink - url="mailto:&email.pear.dev">PEAR developers mailinglist</ulink> - about your code. You should present us the following information:</para> + <para>ìÕÞÛÉÊ ÓÐÏÓÏ ÜÔÏ ÓÄÅÌÁÔØ - ÜÔÏ ÒÁÓËÁÚÁÔØ ÌÀÄÑÍ × <ulink + url="mailto:&email.pear.dev">ÒÁÓÓÙÌËÅ PEAR ÒÁÚÒÁÂÏÔÞÉËÏ×</ulink> + Ï ×ÁÛÅÍ ËÏÄÅ. ÷Ù ÄÏÌÖÎÙ ÐÒÅÄÓÔÁ×ÉÔØ ÓÌÅÄÕÀÝÕÀ ÉÎÆÏÒÍÁÃÉÀ: + </para> <para> <itemizedlist> <listitem> - <simpara>What does your code do? (should be as verbose as - possible)</simpara> + <simpara>þÔÏ ÄÅÌÁÅÔ ×ÁÛ ËÏÄ/ÐÒÏÇÒÁÍÍÁ? (ÐÏ ×ÏÚÍÏÖÎÏÓÔÉ ÄÅÔÁÌØÎÅÅ)</simpara> </listitem> <listitem> - <simpara>Where can we have a look at the code (best thing - is to tell us an URL where we can view the source)?</simpara> + <simpara> + çÄÅ ÍÙ ÍÏÖÅÍ ÐÏÓÍÏÔÒÅÔØ ÉÓÈÏÄÎÙÊ ËÏÄ (ÌÕÞÛÉÊ ×ÁÒÉÁÎÔ ÄÌÑ ÜÔÏÇÏ + , ÓËÁÚÁÔØ ÎÁÍ URL, ÇÄÅ ÍÙ ÍÏÖÅÍ ÐÏÓÍÏÔÒÅÔØ ÉÓÈÏÄÎÉËÉ) + </simpara> </listitem> <listitem> - <simpara>What requirements/dependencies does your code have?</simpara> + <simpara>ëÁËÉÅ ÓÉÓÔÅÍÎÙÅ ÔÒÅÂÏ×ÁÎÉÑ/ÚÁ×ÉÓÉÍÏÓÔÉ ÉÍÅÅÔ ×ÁÛ ËÏÄ?</simpara> </listitem> </itemizedlist> </para> - <para>We will then (hopefully) start discussing about your code and - we'll decide, if we accept your contribution or not. (Don't be - afraid, that your code will not be taken, although it is good: If it - is well developed and we think it can be useful for some people out - there, we will take it for sure.)</para> + <para> + íÙ ÎÁÞÎÅÍ (ÏÂÎÁÄÅÖÉ×ÁÀÝÅ) ÄÉÓËÕÓÓÉÀ Ï ×ÁÛÅÍ ËÏÄÅ, É ÒÅÛÉÍ: + ÅÓÌÉ ÍÙ ÏÄÏÂÒÑÅÍ ÌÉ ÍÙ ×ÁÛÅ ÓÏÄÅÊÓÔ×ÉÅ ÉÌÉ ÎÅÔ. + (îÅ ÂÏÊÔÅÓØ, ×ÁÛ ËÏÄ ÎÅ ÂÕÄÅÔ ÔÒÏÎÕÔ, ÎÅÓÍÏÔÒÑ ÎÁ ÔÏ, ÞÔÏ ÏÎ ÈÏÒÏÛ: + åÓÌÉ ÏÎ ÈÏÒÏÛÏ ÒÁÚÒÁÂÏÔÁÎ É ÍÙ ÄÕÍÁÅÍ, ÞÔÏ ÍÏÖÅÔ ÂÙÔØ ÎÅÏÂÈÏÄÉÍ ÎÅËÏÔÏÒÙÍ + ÌÀÄÑÍ, ÍÙ ×ÏÚØÍÅÍ ÅÇÏ ÏÂÑÚÁÔÅÌØÎÏ.) + </para> </sect1> </chapter>