www/software maintainer-tips.html po/maintainer...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     14/10/29 14:58:31

Modified files:
        software       : maintainer-tips.html 
Added files:
        software/po    : maintainer-tips.pot maintainer-tips.translist 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/software/maintainer-tips.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/software/po/maintainer-tips.pot?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/software/po/maintainer-tips.translist?cvsroot=www&rev=1.1

Patches:
Index: maintainer-tips.html
===================================================================
RCS file: /web/www/www/software/maintainer-tips.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- maintainer-tips.html        29 Oct 2014 14:51:12 -0000      1.2
+++ maintainer-tips.html        29 Oct 2014 14:58:30 -0000      1.3
@@ -2,7 +2,7 @@
 <!-- Parent-Version: 1.77 -->
 <title>Tips for new GNU maintainers
 - GNU Project - Free Software Foundation</title>
-<!--#include virtual="/server/gnun/initial-translations-list.html" -->
+ <!--#include virtual="/software/po/maintainer-tips.translist" -->
 <!--#include virtual="/server/banner.html" -->
 
 <h2>Tips for new GNU maintainers</h2>
@@ -198,7 +198,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/10/29 14:51:12 $
+$Date: 2014/10/29 14:58:30 $
 <!-- timestamp end -->
 </p>
 </div>

Index: po/maintainer-tips.pot
===================================================================
RCS file: po/maintainer-tips.pot
diff -N po/maintainer-tips.pot
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/maintainer-tips.pot      29 Oct 2014 14:58:30 -0000      1.1
@@ -0,0 +1,245 @@
+# LANGUAGE translation of http://www.gnu.org/software/maintainer-tips.html
+# Copyright (C) YEAR Free Software Foundation, Inc.
+# This file is distributed under the same license as the original article.
+# FIRST AUTHOR <address@hidden>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: maintainer-tips.html\n"
+"POT-Creation-Date: 2014-10-29 14:56+0000\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <address@hidden>\n"
+"Language-Team: LANGUAGE <address@hidden>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=CHARSET\n"
+"Content-Transfer-Encoding: ENCODING"
+
+#. type: Content of: <title>
+msgid "Tips for new GNU maintainers - GNU Project - Free Software Foundation"
+msgstr ""
+
+#. type: Content of: <h2>
+msgid "Tips for new GNU maintainers"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"If you are new to maintaining a GNU package, whether one that you have "
+"offered to GNU or an existing one that you have adopted, it can be "
+"overwhelming to know where to start.  The official email notice you received "
+"when you became a GNU maintainer has lots of details; this document is not a "
+"replacement for that email, but rather a complement, aiming to provide some "
+"tips on getting started."
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"Of course, what's listed here just skims the surface of GNU maintainership.  "
+"Please be sure to read the <a href=\"https://gnu.org/prep/maintain/\";>GNU "
+"Maintainers Guide</a> and the <a "
+"href=\"https://gnu.org/prep/standards/\";>GNU Coding Standards</a>.  Indeed, "
+"you should have read them already, but they are densely enough written that "
+"careful re-readings are useful.  In addition, a few experienced GNU "
+"contributors have volunteered to answer questions about GNU maintenance via "
+"<a href=\"mailto:address@hidden";>address@hidden</a> as well as <a "
+"href=\"mailto:address@hidden";>address@hidden</a>."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "First steps for new maintainers"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Update project information on Savannah.</b> Check under \"Update Public "
+"Info\" in the \"Main\" menu.  Here, you should set the project's full name "
+"and, if needed, write both a short and a long description for it (please "
+"also send those descriptions to address@hidden for use in the lists of "
+"<a href=\"/software/software.html#allgnupkgs\">all GNU packages</a>).  You "
+"should also set its development status to reflect the maturity of the code.  "
+"It is essential to do this if you have adopted a package, since it will be "
+"marked as \"Orphan\".  (<a "
+"href=\"/prep/maintain/html_node/Old-Versions.html\">About Savannah.</a>)"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Turn to the mailing lists.</b> If you have a new GNU package, you should "
+"set up at least one mailing list for the package via Savannah.  It is "
+"strongly recommended to have one called <i>address@hidden</i>; others "
+"can wait until traffic warrants.  If you have adopted an existing package, "
+"send an email introducing yourself.  Finally, whether lists are newly "
+"created or already existing, don't forget to subscribe yourself, as this is "
+"not automatically done.  (<a "
+"href=\"/prep/maintain/html_node/Mail.html\">About dealing with mail.</a>)"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Check for existing bug reports.</b> If you have adopted an existing "
+"package, be sure to look for existing bug reports.  These may be on any or "
+"all of a Savannah bug tracker, a mailing list (mbox archives are available "
+"via <a href=\"ftp://lists.gnu.org/\";>ftp</a> and <a "
+"href=\"rsync://lists.gnu.org/mbox/\">rsync</a>), or at the <a "
+"href=\"https://debbugs.gnu.org\";>GNU debbugs server</a>.  (<a "
+"href=\"/prep/maintain/html_node/Replying-to-Mail.html\">About replying to "
+"bug reports.</a>)"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Contact distro packagers.</b> If you have adopted an existing package and "
+"it is available in downstream distros, get in contact with the packagers.  "
+"It is likely that they have unresolved bug reports to be addressed, and "
+"perhaps even patches that should be applied.  (<a "
+"href=\"/distros/distros.html\">About distros.</a>)"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Use the software.</b> It should go without saying that if you have "
+"adopted a GNU package, you should use it to get a feel for its current "
+"status and to discover what might need to be fixed."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Pick some tasks and start hacking!</b> There's no substitute for spending "
+"time doing the actual work."
+msgstr ""
+
+#. type: Content of: <h3>
+msgid "General tips on maintaining GNU software"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Aim for a quick first release.</b> Whether your package is new or you've "
+"adopted an older one, your number one priority should be making a first "
+"release as soon as possible.  If you've adopted a package, it's sufficient "
+"to fix a few bugs and push that out.  In fact, just updating the "
+"infrastructure files (e.g., Autoconf/Automake, gnulib modules, etc.) is "
+"enough to justify a new release when you've first taken over a package.  If "
+"your package is new, don't be afraid to put out an early version that is not "
+"yet feature complete.  In any case, a release (with <a "
+"href=\"/prep/maintain/html_node/Announcements.html\">proper "
+"announcements</a>) will draw attention to your package in the form of "
+"potential users or even other developers.  It is the best way to let people "
+"know that an old package has been revived or that a new package exists at "
+"all.  (<a href=\"/prep/maintain/html_node/Distributions.html\">About making "
+"releases.</a>)"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Focus on fixing outstanding bugs first.</b> An excellent way to begin to "
+"learn a new codebase is to fix some outstanding bugs to get a feel for how "
+"the system works.  Besides, new features shouldn't be given much focus if "
+"notable problems already exist."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Don't try to rewrite the entire thing.</b> If you've adopted a package, "
+"we strongly recommend that you not set out to rewrite the whole program from "
+"scratch.  While always tempting, and an easy thing to start, completing it "
+"successfully requires a colossal effort, and experience has shown that it is "
+"an almost sure-fire way to become demotivated and lead to eventual "
+"(re-)stagnation of the project.  Instead, focus on incremental "
+"improvements.  Once you've become intimately familiar with the package, you "
+"will be in a better position to consider more radical changes."
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>You're in charge!</b> As a maintainer, you look after a package as part "
+"of the overall GNU project.  GNU depends on you to take care of <a "
+"href=\"/maintain/html_node/Legal-Matters.html\">legal matters</a>, make new "
+"releases, keep the <a href=\"/prep/maintain/html_node/Web-Pages.html\">web "
+"pages</a> updated, reply to bug reports and otherwise communicate with "
+"users, <a href=\"/prep/maintain/html_node/Clean-Ups.html\">handle patches "
+"appropriately</a>, and all else.  This is your privilege and your "
+"responsibility.  Please help us maintain an active and stable collection of "
+"software.  If you have questions or run into problems, do not hesitate to "
+"get in touch via <a "
+"href=\"mailto:address@hidden";>address@hidden</a>.  (<a "
+"href=\"/prep/maintain/html_node/Recruiting-Developers.html\">About "
+"recruiting developers.</a>)"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<b>Get involved.</b> GNU consists entirely of volunteers and your "
+"participation in the organization is what you make of it! As a maintainer, "
+"the communication received from us (read: pestering) will be low-volume.  "
+"Being active within GNU is a great way to increase your contact and exposure "
+"to other like-minded volunteers.  If you find an aspect of GNU in which you "
+"would like to be involved, there is almost certainly room for contribution.  "
+"(<a href=\"/help/help.html\">About helping GNU and free software.</a>)"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"To conclude with one final reiteration: the information and links above are "
+"just a sampling.  Please refer to and (re)read the full <a "
+"href=\"/prep/maintain/\">GNU Maintainer Information</a> and <a "
+"href=\"/prep/standards/\">GNU Coding Standards</a> documents for plenty "
+"more."
+msgstr ""
+
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
+#. type: Content of: <div>
+msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
+msgstr ""
+
+#. type: Content of: <div><div><p>
+msgid ""
+"Please send general FSF &amp; GNU inquiries to <a "
+"href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>.  There are also <a "
+"href=\"/contact/\">other ways to contact</a> the FSF.  Broken links and "
+"other corrections or suggestions can be sent to <a "
+"href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>."
+msgstr ""
+
+#.  TRANSLATORS: Ignore the original text in this paragraph,
+#.         replace it with the translation of these two:
+#
+#.         We work hard and do our best to provide accurate, good quality
+#.         translations.  However, we are not exempt from imperfection.
+#.         Please send your comments and general suggestions in this regard
+#.         to <a href="mailto:address@hidden";>
+#
+#.         &lt;address@hidden&gt;</a>.</p>
+#
+#.         <p>For information on coordinating and submitting translations of
+#.         our web pages, see <a
+#.         href="/server/standards/README.translations.html">Translations
+#.         README</a>. 
+#. type: Content of: <div><div><p>
+msgid ""
+"Please see the <a "
+"href=\"/server/standards/README.translations.html\">Translations README</a> "
+"for information on coordinating and submitting translations of this article."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid "Copyright &copy; 2014 Free Software Foundation, Inc."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"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>."
+msgstr ""
+
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
+#. type: Content of: <div><div>
+msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
+msgstr ""
+
+#.  timestamp start 
+#. type: Content of: <div><p>
+msgid "Updated:"
+msgstr ""

Index: po/maintainer-tips.translist
===================================================================
RCS file: po/maintainer-tips.translist
diff -N po/maintainer-tips.translist
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/maintainer-tips.translist        29 Oct 2014 14:58:31 -0000      1.1
@@ -0,0 +1,13 @@
+<!-- begin translist file -->
+<!--#set var="TRANSLATION_LIST"
+value='<div id="translations">
+<p>
+<span dir="ltr" class="original"><a lang="en" hreflang="en" 
href="/software/maintainer-tips.en.html">English</a>&nbsp;[en]</span> &nbsp;
+</p>
+</div>' -->
+<!--#if expr="$HTML_BODY = yes" -->
+<!-- Fallback for old position of translist; to be removed
+     when translists in all translations are included before banner.html. -->
+<!--#echo encoding="none" var="TRANSLATION_LIST" -->
+<!--#endif -->
+<!-- end translist file -->