CVSROOT: /web/www
Module name: www
Changes by: Yavor Doganov <yavor> 11/12/14 09:26:43
Modified files:
help : evaluation.fr.html
philosophy : public-domain-manifesto.fr.html
philosophy/po : public-domain-manifesto.fr.po
Added files:
help/po : evaluation.fr-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/help/evaluation.fr.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/help/po/evaluation.fr-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/public-domain-manifesto.fr.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/public-domain-manifesto.fr.po?cvsroot=www&r1=1.4&r2=1.5
Patches:
Index: help/evaluation.fr.html
===================================================================
RCS file: /web/www/www/help/evaluation.fr.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- help/evaluation.fr.html 14 Dec 2011 01:25:47 -0000 1.3
+++ help/evaluation.fr.html 14 Dec 2011 09:26:20 -0000 1.4
@@ -282,7 +282,7 @@
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
<b>Notes de traduction</b><ol>
-<li id="TransNote1">Traduction possible : chef enGNUyant.
+<li id="TransNote1">Traduction possible : chef enGNUyant.</li>
<li id="TransNote2">Le questionnaire n'a pas été traduit car il doit être
rempli en anglais.</li></ol></div>
</div>
@@ -322,7 +322,7 @@
<p><!-- timestamp start -->
Dernière mise à jour :
-$Date: 2011/12/14 01:25:47 $
+$Date: 2011/12/14 09:26:20 $
<!-- timestamp end -->
</p>
Index: philosophy/public-domain-manifesto.fr.html
===================================================================
RCS file: /web/www/www/philosophy/public-domain-manifesto.fr.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- philosophy/public-domain-manifesto.fr.html 9 Dec 2011 17:26:48 -0000
1.2
+++ philosophy/public-domain-manifesto.fr.html 14 Dec 2011 09:26:31 -0000
1.3
@@ -6,22 +6,17 @@
<link rel="canonical"
href="http://www.fsf.org/blogs/rms/public-domain-manifesto"; />
<!--#include virtual="/server/banner.fr.html" -->
-<!--#set var="PO_FILE"
- value='<a
href="http://www.gnu.org/philosophy/po/public-domain-manifesto.fr.po";>
- http://www.gnu.org/philosophy/po/public-domain-manifesto.fr.po</a>' -->
- <!--#set var="ORIGINAL_FILE" value="/philosophy/public-domain-manifesto.html"
-->
- <!--#set var="DIFF_FILE" value="" -->
- <!--#include virtual="/server/outdated.fr.html" -->
<!--#include virtual="/philosophy/po/public-domain-manifesto.translist" -->
<h2>Pourquoi je ne signerai pas le manifeste pour le domaine public</h2>
-<p>by <a href="http://www.stallman.org/";>Richard M. Stallman</a></p>
+<p>par <a href="http://www.stallman.org/";>Richard M. Stallman</a></p>
-<p>The Public Domain Manifesto (<a
-href="http://www.publicdomainmanifesto.org/node/8";>http://www.publicdomainmanifesto.org/node/8</a>)
-has its heart in the right place as it objects to some of the unjust
-extensions of copyright power, so I wish I could support it. However, it
-falls far short of what is needed.</p>
+<p>Le <a href="http://www.publicdomainmanifesto.org/node/8";;>manifeste pour le
+domaine public</a> (traduit en français <a
+href="http://publicdomainmanifesto.org/french";>ici</a>) a le cœur à la
+bonne place puisqu'il s'oppose à certaines des extensions illégitimes du
+pouvoir du copyright, aussi j'aurais souhaité pouvoir le soutenir. Cependant
+il n'est pas, de loin, à la hauteur de ce qui serait nécessaire.</p>
<p>Quelques-unes de ses insuffisances concernent les hypothèses implicites. Le
manifeste emploie fréquemment des <a
@@ -77,12 +72,14 @@
travail du domaine public. Concrètement, il légitimise la plupart des DRM
utilisés en pratique, en les soustrayant à la critique.</p>
-<p>I've saved the biggest omission for last. General Recommendation 9 calls
-for allowing “personal copying” of copyrighted works. Since it
-omits the issue of the freedom to share copies of published works with
-others, it fails to address the nastiest aspect of copyright: the vicious <a
-href="http://www.fsf.org/blogs/community/war-on-sharing-riaa-lawsuits";>War
-on Sharing</a> that the entertainment companies are now waging.</p>
+<p>J'ai gardé pour la fin l'omission la plus grave. La recommandation
générale
+9 revendique la permission de « copie privée » pour les travaux
+sous copyright. Elle omet la question du libre partage des copies de travaux
+publiés, donc ne s'intéresse pas à la manifestation la plus néfaste du
+copyright : la sauvage <a
+href="http://www.fsf.org/blogs/community/war-on-sharing-riaa-lawsuits";>guerre
+contre le partage</a> que l'industrie du divertissement est actuellement en
+train de mener.</p>
<p>Les revendications et les recommandations du manifeste pour le domaine
public constitueraient un pas en avant. Il pourrait avoir du bon s'il
@@ -95,11 +92,12 @@
avons à l'intérieur de la prison dorée du domaine public, mais abandonne
l'autre, la liberté hors des murs. Ce n'est pas suffisant.</p>
-<p>I ask the authors of the Public Domain Manifesto, and the public, to please
-join me in demanding the freedom to noncommercially share copies of all
-published works. Also please join <a
-href="http://defectivebydesign.org";>DefectiveByDesign.org</a> and help our
-fight against DRM wherever it may be found.</p>
+<p>Je demande aux auteurs du manifeste pour le domaine public, et au public, de
+bien vouloir me rejoindre pour exiger la liberté de partager, de manière
+non-commerciale, des copies de tous les travaux publiés. De plus, je les
+invite à rejoindre <a href="http://defectivebydesign.org";><acronym
+title="défectueux par construction">DefectiveByDesign.org</acronym></a> pour
+nous aider dans notre combat contre les DRM, où qu'ils se manifestent.</p>
<div style="font-size: small;">
@@ -128,24 +126,25 @@
<p>Copyright © 2010 Richard Stallman</p>
-<p>This work is licensed under the Creative Commons Attribution-No Derivative
-Works 3.0 United States License. To view a copy of this license, visit <a
-href="http://creativecommons.org/licenses/by-nd/3.0/us/";>http://creativecommons.org/licenses/by-nd/3.0/us/</a>
-or send a letter to Creative Commons, 171 Second Street, Suite 300, San
-Francisco, California, 94105, USA.</p>
+<p>Ce travail est sous licence « Creative Commons Attribution-No
+Derivative Works 3.0 » aux Etats-Unis. Une copie de cette licence est
+disponible sur la page web <a
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.fr";>http://creativecommons.org/licenses/by-nd/3.0/us/deed.fr</a>.
+Vous pouvez aussi écrire à Creative Commons, 171 Second Street, Suite 300,
+San Francisco, California, 94105, USA.</p>
<div class="translators-credits">
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
Traduction : Thérèse Godefroy<br />Révision : <a
-href="mailto:trad-gnu@april.org";;>trad-gnu@april.org</div>
+href="mailto:trad-gnu@april.org";>trad-gnu@april.org</a></div>
<p><!-- timestamp start -->
Dernière mise à jour :
-$Date: 2011/12/09 17:26:48 $
+$Date: 2011/12/14 09:26:31 $
<!-- timestamp end -->
</p>
Index: philosophy/po/public-domain-manifesto.fr.po
===================================================================
RCS file: /web/www/www/philosophy/po/public-domain-manifesto.fr.po,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- philosophy/po/public-domain-manifesto.fr.po 13 Dec 2011 21:11:19 -0000
1.4
+++ philosophy/po/public-domain-manifesto.fr.po 14 Dec 2011 09:26:36 -0000
1.5
@@ -14,7 +14,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"Outdated-Since: 2011-09-20 12:30-0300\n"
"Language: fr\n"
# type: Content of: <h2>
Index: help/po/evaluation.fr-en.html
===================================================================
RCS file: help/po/evaluation.fr-en.html
diff -N help/po/evaluation.fr-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ help/po/evaluation.fr-en.html 14 Dec 2011 09:26:27 -0000 1.1
@@ -0,0 +1,331 @@
+<!--#include virtual="/server/header.html" -->
+<title>GNU Software Evaluation
+- GNU Project - Free Software Foundation (FSF)</title>
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/help/po/evaluation.translist" -->
+<h2>GNU Software Evaluation</h2>
+
+<h3 id="submit">Offering software to GNU</h3>
+
+<p>If you have written software which you would like to offer to the GNU
+Project, thank you very much! This page includes a questionnaire for
+submitting your package, so that we can get the information needed and
+evaluate it as quickly as possible.</p>
+
+<p>Please take your time filling out the questionnaire. We've written
+it as preformatted text so you can copy to your system and fill it out
+at your convenience. When you're done, please email it to <a
+href="mailto:[email protected]";><[email protected]></a>
+(as plain text).</p>
+
+<p>If you can't answer all the questions, or if the program does not
+perfectly fulfill every item mentioned, don't worry, that does
+<em>not</em> mean we will blindly reject it. It's common for a program
+to be evaluated when it's not quite ready. If the program is basically
+good, but certain things are missing, we'll just point out what needs to
+be added. We can also evaluate a program at an early stage of
+development; in that case, we may want to judge your ability to complete
+the program based on other projects you have already done.</p>
+
+<p>GNU is not simply a collection of useful programs. We started the
+GNU Project with a specific overall goal: to create a free software
+operating system, the GNU System. To keep the GNU system technically
+coherent, we make sure that the parts fit well together. So the
+evaluators judge programs based on how well they fit into the GNU
+system, both technically and philosophically, as well as on their
+quality, usability, and the other characteristics you would expect.
+Based on the evaluators' report, Richard Stallman (the Chief GNUisance)
+makes the final decision on whether to accept the contribution.</p>
+
+<p>Thus, becoming a GNU maintainer is a somewhat formal process, since
+affiliating with the GNU project as a maintainer means you must agree to
+work (within the confines of the maintenance) with the GNU project's
+mission for software freedom.</p>
+
+<p>So, in addition to the questionnaire, please read the GNU policies in
+the <a href="/prep/maintain_toc.html">Information for Maintainers of GNU
+Software</a> as well as the <a href="/prep/standards_toc.html">GNU
+Coding Standards</a>. A <a href="#whatmeans">summary of the major
+policies</a> given below, but please also look through the full
+documents.</p>
+
+<p>If you don't wish to fill out the questionnaire and/or meet the
+requirements for official GNU packages, we still encourage you to submit
+it to the <a href="http://directory.fsf.org";>Free Software
+Directory</a>. We want the Directory to cover all released free
+software packages.</p>
+
+<p>Thanks again for your interest in GNU.</p>
+
+
+<h3 id="whatmeans">What it means for a program to be a GNU package</h3>
+
+<p>Here's the explanation, from rms, of what it means for a program to
+be a GNU package, which also explains at a general level the
+responsibilities of a GNU maintainer.</p>
+
+<p>Making a program GNU software means that its developers and the GNU
+project agree that “This program is part of the GNU project,
+released under the aegis of GNU”—and say so in the
+program.
+</p>
+
+<p>This means that you normally put the program on
+<code>ftp.gnu.org</code>.</p>
+
+<p>This means that the official site for the program should be on
+<code>www.gnu.org</code>, specifically in
+<code>/software/PROGRAMNAME</code>. Whenever you give out the URL for
+the package home page, you would give this address. It is ok to use
+another site for secondary topics, such as pages meant for people
+helping develop the package, and for running data bases. (We can make
+an exception and put the web pages somewhere else if there is a really
+pressing reason.)</p>
+
+<p>It means that the developers agree to pay attention to making the
+program work well with the rest of the GNU system—and conversely
+that the GNU project will encourage other GNU maintainers to pay
+attention to making their programs fit in well with it.</p>
+
+<p>Just what it means to make programs work well together is mainly a
+practical matter that depends on what the program does. But there are
+a few general principles. Certain parts of the GNU coding standards
+directly affect the consistency of the whole system. These include
+the standards for configuring and building a program, and the
+standards for command-line options. It is important to make all GNU
+programs follow these standards, where they are applicable.</p>
+
+<p>Another important GNU standard is that GNU programs should come with
+documentation in Texinfo format. That is the GNU standard documentation
+format, and it can be converted automatically into various other
+formats. You can use DocBook or any other suitable format for the
+documentation sources, as long as converting it automatically into
+Texinfo gives good results.</p>
+
+<p>If a GNU program wants to be extensible, it should use
+<a href="/software/guile/guile.html">GUILE</a> as the programming
+language for extensibility—that is the GNU standard
+extensibility package. For some programs there's a reason to do
+things differently, but please use GUILE if that is feasible.</p>
+
+<p>A GNU program should use the latest version of the license that the
+GNU Project recommends—not just any free software license. For
+most packages, this means using the GNU GPL.</p>
+
+<p>A GNU program should not recommend use of any non-free program, and
+it should not refer the user to any non-free documentation for free
+software. The <a href="/philosophy/free-doc.html">campaign for free
+documentation</a> to go with free software is a major focus of the GNU
+project; to show that we are serious about it, we must not undermine
+our position by recommending documentation that isn't free.</p>
+
+<p>Occasionally there are issues of terminology which are important
+for the success of the GNU project as a whole. So we expect
+maintainers of GNU programs to follow them. For example, the
+documentation files and comments in the program should speak of
+GNU/Linux systems, rather than calling the whole system
+“Linux”, and should use the term “free
+software” rather than “open source”. Since a GNU
+program is released under the auspices of GNU, it should not say
+anything that contradicts the GNU Project's views.</p>
+
+<p>For a program to be GNU software does not require transferring
+copyright to the FSF; that is a separate question. If you transfer
+the copyright to the FSF, the FSF will enforce the GPL for the program
+if someone violates it; if you keep the copyright, enforcement will be
+up to you.</p>
+
+<p>As the GNU maintainer of the package, please make sure to stay in
+touch with the GNU Project. If we come across a problem relating to
+the package, we need to tell you about it, and to discuss with you how
+to solve it. Sometimes we will need to ask you to work with other
+maintainers to solve a problem that involves using multiple packages
+together. This probably will happen less than once a year, but please
+make sure we can contact you in case it does happen.</p>
+
+<p>Finally, if you decide to step down as maintainer at any time, please
+<a href="/prep/maintain/html_node/Stepping-Down.html">inform
+us</a>.</p>
+
+
+<h3 id="questionnaire">Questionnaire for offering software to GNU</h3>
+
+<pre>
+* General Information
+** Do you agree to follow GNU policies?
+ If your program is accepted to be part of the GNU system, it means
+ that you become a GNU maintainer, which in turn means that you will
+ need to follow GNU policies in regards to that GNU program.
+ (Summarized above, see maintainers document for full descriptions.)
+
+** Package name and version:
+
+** Author Full Name <Email>:
+
+** URL to package home page (if any):
+
+** URL to source tarball:
+ Please make a release tarball for purposes of evaluation, whether
+ or not you publicly release it. If you don't have
+ anywhere to upload it, send it as an attachment.
+
+** Brief description of the package:
+
+
+* Code
+** Dependencies:
+ Please list the package's dependencies (source language, libraries, etc.).
+
+** Configuration, building, installation:
+ It might or might not use Autoconf/Automake, but it must meet GNU
+ standards. Even packages that do not require compilation
+ must follow these standards, so installers have a uniform way to
+ define target directories, etc. Please see:
+ http://www.gnu.org/prep/standards/html_node/Configuration.html
+ http://www.gnu.org/prep/standards/html_node/Makefile-Conventions.html
+
+** Documentation:
+ We require using Texinfo (http://www.gnu.org/software/texinfo/)
+ for documentation, and writing both reference and tutorial
+ information in the same manual. Please see
+ http://www.gnu.org/prep/standards/html_node/GNU-Manuals.html
+
+** Internationalization:
+ If your package has any user-visible strings, please make them
+ translatable to other languages using GNU Gettext:
+ http://www.gnu.org/software/gettext/
+
+
+* Licensing:
+ Both the software itself *and all dependencies* (third-party
+ libraries, etc.) must be free software in order to be included in
+ GNU. In general, official GNU software should be released under the
+ GNU GPL version 3 or any later version, and GNU documentation should
+ be released under the GNU FDL version 1.3 or any later version.
+
+ Please see http://www.gnu.org/philosophy/license-list.html for a
+ practical guide to which licenses are free (for GNU's purposes) and
+ which are not. Please give specific url's to any licenses involved
+ that are not listed on that page.
+
+
+* Similar free software projects:
+ Please explain what motivated you to write your package, and search
+ at least the Free Software Directory (http://www.gnu.org/directory/)
+ for projects similar to yours. If any exist, please also explain
+ what the principal differences are.
+
+* Any other information, comments, or questions:
+
+</pre>
+
+<p>Again, please email the questionnaire to <a
+href="mailto:[email protected]";><[email protected]></a>
+when it is done.</p>
+
+
+<!-- [too many volunteers is counterproductive for this task]
+<h3 id="eval">Helping evaluate software for GNU</h3>
+
+<p>From time to time (but not at the moment), we can use additional
+volunteers to commit to helping evaluate the software we are offered
+through the procedures above. Timeliness is of the utmost importance in
+doing an evaluation. The main goal of doing the evaluations is not to
+be an expert in the field (a common misconception), but to get a general
+understanding of the program on the one hand, and how it meets certain
+very specific criteria on the other (we use a standard form to guide
+evaluations).</p>
+
+<p>It is also not critical to be a systems expert. Many packages are
+offered in a state that is too difficult to compile, let alone run.
+This does not mean the evaluation cannot be completed! Considering the
+overall goal of the package, plus looking at the source code, is nearly
+always enough to do a useful evaluation. In general, it is neither
+necessary nor desirable to examine the minutiae of a given program; this
+tends to stall the evaluation endlessly.</p>
+
+<p>Doing evaluations is generally a very educational experience.
+Evaluators often learn about (usually) interesting projects which would
+never otherwise cross their path, as well gaining familiarity with GNU
+guidelines and Free Software in general. It helps the GNU
+Project and the Free Software Foundation as well.</p>
+
+<p>If you are interested in helping with this task for GNU, please email
+<a href="mailto:[email protected]";><[email protected]></a>,
+which will reach the coordinators of the group of volunteers that does
+evaluations.</p>
+-->
+
+<h3>Other ways to help the GNU Project</h3>
+
+<p>There are <a href="/help/help.html">many other ways</a> of helping
+GNU, both technical and non-technical.</p>
+
+<!-- If needed, change the copyright block at the bottom. In general,
+ all pages on the GNU web server should have the section about
+ verbatim copying. Please do NOT remove this without talking
+ with the webmasters first.
+ Please make sure the copyright date is consistent with the document
+ and that it is like this: "2001, 2002", not this: "2001-2002". -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:[email protected]";><[email protected]></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:[email protected]";><[email protected]></a>.</p>
+
+<p>Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+
+<p>Copyright © 2011 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.
+</p>
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2011/12/14 09:26:27 $
+<!-- timestamp end -->
+</p>
+</div>
+
+<!-- <div id="translations"> -->
+<!-- <h4>Translations of this page</h4> -->
+<!-- -->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text.
-->
+<!-- If you add a new language here, please -->
+<!-- advise [email protected] and add it to -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, you also have to add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
+<!-- -->
+<!-- See also '(web-trans)Capitalization': -->
+<!--
http://gnu.org/software/trans-coord/manual/web-trans/html_node/Capitalization.html
-->
+<!-- -->
+<!-- -->
+<!-- <ul class="translations-list"> -->
+<!-- German -->
+<!-- <li><a href="/help/evaluation.de.html">Deutsch</a> [de]</li> -->
+<!-- English -->
+<!-- <li><a href="/help/evaluation.html">English</a> [en]</li> -->
+<!-- </ul> -->
+<!-- </div> -->
+</div>
+</body>
+</html>
