cvs: peardoc /fr/guide/newmaint getting-started.xml
| From: | Christophe Gesch� | Date: | Mon, 11 Jul 2005 07:55:29 +0000 |
| Subject: | cvs: peardoc /fr/guide/newmaint getting-started.xml | ||
| Groups: | php.pear.doc | ||
| Request: | Send a blank email to pear-doc+get-6500@lists.php.net to get a copy of this message | ||
moosh Mon Jul 11 03:55:29 2005 EDT
Modified files:
/peardoc/fr/guide/newmaint getting-started.xml
Log:
-sync to EN1.6
* 1.4 * Disabled the chapter "Hierarchy in PEAR" for now.
* 1.5 * Fixed a few mistakes spotted by Lorenzo Alberton.
* 1.6 * Incorporated feedback by Daniel Convissor.
http://cvs.php.net/diff.php/peardoc/fr/guide/newmaint/getting-started.xml?r1=1.3&r2=1.4&ty=u
Index: peardoc/fr/guide/newmaint/getting-started.xml
diff -u peardoc/fr/guide/newmaint/getting-started.xml:1.3
peardoc/fr/guide/newmaint/getting-started.xml:1.4
--- peardoc/fr/guide/newmaint/getting-started.xml:1.3 Thu Jun 16 14:53:29 2005
+++ peardoc/fr/guide/newmaint/getting-started.xml Mon Jul 11 03:55:25 2005
@@ -1,20 +1,21 @@
<?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.3 $ -->
-<!-- EN-Revision: 1.3 Maintainer: moosh Status: started -->
+<!-- $Revision: 1.4 $ -->
+<!-- EN-Revision: 1.6 Maintainer: moosh Status: started -->
<chapter id="newmaint.getting-started">
<chapterinfo>
<author>
<firstname>Martin</firstname>
<surname>Jansen</surname>
</author>
- <date>$Date: 2005/06/16 18:53:29 $</date>
+ <date>Date: 2004/06/17 08:30:32 </date>
</chapterinfo>
- <title>Démarrer avec la communauté</title>
+ <title>Démarrer dans la communauté</title>
<titleabbrev>Se lancer</titleabbrev>
<simpara>
- Once you have discovered, if your code fits into PEAR, you should get
- started with the PEAR community.
+ Afin de déterminer si votre code
+ peut sintégrer dans PEAR,
+ vous devriez vous lancer avec la communauté de PEAR.
In this chapter we will provide several ways, in which you can
establish a first contact with the other PEAR developers,
@@ -35,29 +36,32 @@
Nous proposons plusieurs mailing lists publiques.
- Celles-ci sont listées sur le
+ Celles-ci sont listées sur le
<ulink url="&url.pear.support;">site web de PEAR</ulink>.
Pour les premiers pas, la mailing list des developpeurs de
PEAR <emphasis><ulink
- url="&email.pear.dev;">&email.pear.dev;</ulink></emphasis>
+ url="mailto:&email.pear.dev;">&email.pear.dev;</ulink></emphasis>
est importante:
- This mailing list is the place where the
- maintainers get together to discuss various aspects of their
- packages and this list is also the place where new packages are
- discussed.
+ Cette mailing list est l'endroit où
+ sont rassemblés les mainteneurs
+ pour discuter des différents aspects de leurs packages
+ et cette liste est aussi l'endroit où
+ l'on discute des nouveaux packages.
+
(<ulink url="&url.pear.support;">instructions pour
s'inscrire</ulink>)
</para>
<para>
Si vous avez l'intention de commencer par maintenir des paquets de PEAR,
- on s'attend à ce que vous souscriviez à cette liste d'expédition.
+ on s'attend à ce que vous souscriviez
+ à cette liste d'expédition.
</para>
<note>
<simpara>
- Pendant vos premiers pas dans la communauté PEAR,
+ Pendant vos premiers pas dans la communauté PEAR,
you may stumble across the term <quote>pear-dev</quote>,
which describes the abbreviation for the developers
mailing list in PEAR's lingo.
@@ -84,13 +88,16 @@
<itemizedlist>
<listitem>
<para>
- In unsteady intervals, the PEAR Group publishes so called
- <ulink url="http://pear.php.net/group/">Administrative
- Documents</ulink>, in which decisions by the PEAR Group are
- described. You are expected to read those documents before
+ The <ulink url="&url.pear.group;">PEAR Group</ulink>
+ occasionally publishes so called
+ <ulink url="http://pear.php.net/group/">Administrative
Documents</ulink>,
+ which describe the Group's decisions.
+
+ You are expected to read those documents before
starting serious contributions to PEAR, because they contain
- important information about the inner workings of PEAR. The
- developers mailing list will be informed, when new documents are
+ important information about the inner workings of PEAR.
+
+ The developers mailing list will be informed, when new documents are
added, so you do not need to visit the site frequently.
</para>
</listitem>
@@ -101,9 +108,16 @@
valueable information as well.
</para>
</listitem>
+ <listitem>
+ <para>
+ The <link linkend="standards">Coding Standards</link> describe the
+ standards which PEAR code must adhere to.
+ </para>
+ </listitem>
</itemizedlist>
</sect1>
+ <!--
<sect1 id="newmaint.getting-started.hierarchy">
<title>The hierarchy in PEAR</title>
@@ -111,7 +125,7 @@
TBD
</simpara>
</sect1>
-
+-->
</chapter>
<!-- Keep this comment at the end of the file