Index: branches/PublicaMundi_David-devel/docs/contribute/code.rst =================================================================== --- branches/PublicaMundi_David-devel/docs/contribute/code.rst (revision 679) +++ branches/PublicaMundi_David-devel/docs/contribute/code.rst (revision 696) @@ -13,16 +13,18 @@ Submit new code --------------------------- +--------------- For new comers -************************* +************** New source code or existing source code corrections (patches) should -be submitted using the ZOO-Project bug tracking system (`ZOO-Trac `__ ). +be submitted using the ZOO-Project bug tracking system (`ZOO-Trac +`__ ). -Create a new ticket in order to describe your code or patch and attach -it to the ticket (attach all the needed files needed to use your code -or patch). It will then be checked and discussed with the developers, -and can potentially be integrated and merged with the trunk. +Create a `new ticket `__ in +order to describe your code or patch and attach it to the ticket +(attach all the files required to use your code or patch). It will +then be checked and discussed with the developers, and can potentially +be integrated and merged with the trunk. For registered developers Index: branches/PublicaMundi_David-devel/docs/contribute/dev.rst =================================================================== --- branches/PublicaMundi_David-devel/docs/contribute/dev.rst (revision 679) +++ branches/PublicaMundi_David-devel/docs/contribute/dev.rst (revision 696) @@ -9,5 +9,5 @@ ----------------------------- -Permission for SVN commit access shall be provided to new developers only if accepted by the ZOO-Project Project Steering Committee. A proposal should be written to the PSC for new committers and voted. +Permission for SVN commit access shall be provided to new developers only if accepted by the ZOO-Project Project Steering Committee. A proposal should be written to the PSC for new committers and voted. Removal of SVN commit access should be handled by the same process. @@ -24,9 +24,10 @@ ------------------ -A list of all project committers will be kept in the main zoo-project directory (called COMMITTERS) listing for each SVN committer: +A list of all project committers will be kept in the main zoo-project directory (called `COMMITTERS `__) listing for each SVN committer: * Userid: the id that will appear in the SVN logs for this person. * Full name: the users actual name. * Email address: A current email address at which the committer can be reached. It may be altered in normal ways to make it harder to auto-harvest. + SVN Administrator Index: branches/PublicaMundi_David-devel/docs/contribute/doc.rst =================================================================== --- branches/PublicaMundi_David-devel/docs/contribute/doc.rst (revision 679) +++ branches/PublicaMundi_David-devel/docs/contribute/doc.rst (revision 696) @@ -28,6 +28,11 @@ ........................................ -The current structure of the ZOO Project documentation process is for developers with :ref:`SVN ` commit access to maintain their documents in reStructuredText format, and therefore all documents live in the /docs directory in SVN. The `Sphinx `__ documentation generator is used to convert the reStructuredText files to html, and the live -website is then updated on an hourly basis. +The current structure of the ZOO Project documentation process is for +developers with :ref:`SVN ` commit access to maintain their +documents in reStructuredText format, and therefore all documents live +in the /docs directory in SVN. The `Sphinx +`__ documentation generator is used to +convert the reStructuredText files to html, and the live website is +then updated on an hourly basis. @@ -49,9 +54,9 @@ :: - sudo easy_install Sphinx + sudo easy_install Sphinx==1.3.1 .. note:: - Make sure you install Sphinx 1.0 or more recent. See note above. + Make sure you install Sphinx 1.3.1 or more recent. * Checkout the /docs directory from SVN, such as: @@ -88,9 +93,9 @@ :: - sudo easy_install Sphinx + sudo easy_install-2.7 Sphinx==1.3.1 .. note:: - Make sure you install Sphinx 1.0 or more recent. See note above. + Make sure you install Sphinx 1.3.1 or more recent. * Install `MacTex `__ if you want to build pdfs @@ -127,5 +132,5 @@ :: - easy_install Sphinx + easy_install Sphinx==1.3.1 ...you should see message: "Finished processing dependencies for Sphinx" @@ -133,5 +138,5 @@ .. note:: - Make sure you install Sphinx 1.0 or more recent. See note above. + Make sure you install Sphinx 1.3.1 or more recent. See note above. * Install `MiKTeX `__ if you want to build pdfs Index: branches/PublicaMundi_David-devel/docs/contribute/howto.rst =================================================================== --- branches/PublicaMundi_David-devel/docs/contribute/howto.rst (revision 679) +++ branches/PublicaMundi_David-devel/docs/contribute/howto.rst (revision 696) @@ -1,4 +1,4 @@ How to contribute ? -================== +=================== Please consider the following simple rules if you would like to contribute to the `ZOO-Project `__ open source software. @@ -37,7 +37,7 @@ .. csv-table:: - Name,Description,Address - zoo-discuss,General mailing list for ZOO-Project users and developers,zoo-discuss@lists.osgeo.org - zoo-psc,Project Steering Committe mailing list,zoo-psc@lists.osgeo.org + Name,Description + `zoo-discuss `__,General mailing list for ZOO-Project users and developers + `zoo-psc `__,Project Steering Committe mailing list Index: branches/PublicaMundi_David-devel/docs/contribute/translate.rst =================================================================== --- branches/PublicaMundi_David-devel/docs/contribute/translate.rst (revision 679) +++ branches/PublicaMundi_David-devel/docs/contribute/translate.rst (revision 696) @@ -23,5 +23,5 @@ for i in Title Abstract; do - grep $i $j | sed "s:$i = :_(\":g;s:$:\"):g" ; + grep $i $j | sed "s:$i = :_ss(\":g;s:$:\"):g" ; done; done > locale/.cache/my_service_string_to_translate.c @@ -33,5 +33,5 @@ #!/bin/bash - xgettext service.c locale/.cache/my_service_string_to_translate.c -o message.po -p locale/po/ -k_ + xgettext service.c locale/.cache/my_service_string_to_translate.c -o message.po -p locale/po/ -k_ss Once 'messages.po' is created, use the following command to create the po file for the targeted language for translation. We will use the French language here as an example : @@ -45,7 +45,7 @@ Edit the zoo_fr_FR.po file with your favorite text editor or using one of the following tools : - * [http://www.poedit.net/ poedit] - * [http://translate.sourceforge.net/wiki/virtaal/index virtaal] - * [https://www.transifex.net/projects/p/grass6/c/grass64/ transifex] + * `poedit `__ + * `virtaal `__ + * `transifex `__ Once the zoo_fr_FR.po file is completed, you can generate and install the corresponding *mo* file using the following command : @@ -61,9 +61,9 @@ example, such a request: -[http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS] +http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS would become the following: -[http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS&language=fr-FR] +http://youserver/cgi-bin/zoo_loader.cgi?request=GetCapabilities&service=WPS&language=fr-FR The following command may also be useful in order to pull all the translations already available for a specific language.