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=\"/prep/maintain/\">GNU Maintainers " "Guide</a> and the <a href=\"/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 <mentors@gnu.org> as well as <maintainers@gnu.org>." msgstr "" #. type: Content of: <h3> msgid "First steps for new maintainers" msgstr "" #. type: Content of: <p> msgid "" "These tasks are listed in order of priority. The labels (<span " "class=\"all\">[All]</span>, <span class=\"new\">[New]</span>, and <span " "class=\"adopted\">[Adopted]</span>) indicate the category of packages each " "task mostly applies to." msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"all\">[All]</span> <b>Update project information on " "Savannah.</b> Go to your project page " "(<code>https://sv.gnu.org/projects/PKG</code>, where PKG is the name of your " "package), log in with your Savannah ID, and 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 " "<maintainers@gnu.org> 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”." msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"all\">[All]</span> <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 (“Select features” in the Main menu). It is strongly " "recommended to have one called <bug-PKG@gnu.org>; 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: <ol><li> msgid "" "<span class=\"new\">[New]</span> <b>Set up a repository for your source " "code</b> (“Select features” in the Main menu), and import " "whatever is available (look up the procedures under “Source Code " "Manager” in the Development Tools section). Experience has shown that " "self-hosting is unreliable. (<a " "href=\"/prep/maintain/html_node/Old-Versions.html#Old-Versions\">About " "back-up files</a>.)" msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"new\">[New]</span> <b>Upload your package to the GNU FTP " "site</b> if it is ready for public release. (<a " "href=\"/prep/maintain/html_node/Automated-FTP-Uploads.html\">About the " "upload procedure</a>.)" msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"new\">[New]</span> <b>Create a GNU home page</b>, to replace " "the <code>PKG.html</code> file that webmasters have placed in your web repo " "(keep the same name). If you want to make this quick and easy, use our " "standard <a " "href=\"/server/standards/boilerplate.html\">template</a>. Comment out the " "irrelevant parts, such as Downloading and Documentation if the project has " "barely started; you'll complete them later on. Also put any documentation " "you already have in a subdirectory called “manual”. (<a " "href=\"/prep/maintain/html_node/Web-Pages.html\">About web pages</a>.)" msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"adopted\">[Adopted]</span> <b>Check for existing bug " "reports</b> if you have adopted an existing package. These may be on any or " "all of a Savannah bug tracker, a <a href=\"https://lists.gnu.org/\">mailing " "list</a> (mbox archives can be downloaded by <a " "href=\"https://lists.gnu.org/archive/mbox/\">HTTPS</a>), or 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: <ol><li> msgid "" "<span class=\"adopted\">[Adopted]</span> <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. You may also like to get involved with the <a " "href=\"/software/guix/\">GNU Guix</a> package manager. (<a " "href=\"/distros/distros.html\">About distros</a>.)" msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"adopted\">[Adopted]</span> <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: <ol><li> msgid "" "<span class=\"all\">[All]</span> <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> This is an excellent way to " "start learning a new codebase, and get a feel for how the system works. " "Besides, new features shouldn't be given much focus if notable problems " "already exist. (<a href=\"/software/devel.html\">About resources for GNU " "developers</a>.)" 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=\"/prep/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 <maintainers@gnu.org>. (<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 this list 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 "" #. type: Content of: <h3> msgid "GNU Philosophy" msgstr "" #. type: Content of: <p> msgid "" "This also seems like an appropriate page on which to give some links to the " "basic ideas of GNU and free software:" msgstr "" #. type: Content of: <ul><li> msgid "<a href=\"/gnu/the-gnu-project.html\">The GNU Project</a>" msgstr "" #. type: Content of: <ul><li> msgid "" "<a href=\"/philosophy/free-sw.html\">What is free software?</a> (the free " "software definition)" msgstr "" #. type: Content of: <ul><li> msgid "" "<a href=\"/philosophy/categories.html\">Categories of free and nonfree " "software</a>" msgstr "" #. type: Content of: <ul><li> msgid "<a href=\"/philosophy/compromise.html\">Avoiding ruinous compromises</a>" msgstr "" #. type: Content of: <ul><li> msgid "" "<a href=\"/philosophy/words-to-avoid.html\">Words to avoid (or use with " "care) because they are loaded or confusing</a>" msgstr "" #. type: Content of: <ul><li> msgid "<a href=\"/gnu/linux-and-gnu.html\">Linux and the GNU System</a>" msgstr "" #. type: Content of: <ul><li> msgid "<a href=\"/gnu/gnu-linux-faq.html\">GNU/Linux FAQ</a>" msgstr "" #. type: Content of: <ul><li> msgid "" "<a href=\"/philosophy/open-source-misses-the-point.html\">Why Open Source " "misses the point of Free Software</a>" 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 & GNU inquiries to <a " "href=\"mailto:gnu@gnu.org\"><gnu@gnu.org></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:webmasters@gnu.org\"><webmasters@gnu.org></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:web-translators@gnu.org"> # #. <web-translators@gnu.org></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 © 2014, 2017, 2018, 2019 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/4.0/\">Creative Commons " "Attribution-NoDerivatives 4.0 International 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 ""

# LANGUAGE translation of https://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 , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: maintainer-tips.html\n" "POT-Creation-Date: 2019-11-23 13:25+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #. type: Content of: 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=\"/prep/maintain/\">GNU Maintainers " "Guide</a> and the <a href=\"/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 <mentors@gnu.org> as well as <maintainers@gnu.org>." msgstr "" #. type: Content of: <h3> msgid "First steps for new maintainers" msgstr "" #. type: Content of: <p> msgid "" "These tasks are listed in order of priority. The labels (<span " "class=\"all\">[All]</span>, <span class=\"new\">[New]</span>, and <span " "class=\"adopted\">[Adopted]</span>) indicate the category of packages each " "task mostly applies to." msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"all\">[All]</span> <b>Update project information on " "Savannah.</b> Go to your project page " "(<code>https://sv.gnu.org/projects/PKG</code>, where PKG is the name of your " "package), log in with your Savannah ID, and 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 " "<maintainers@gnu.org> 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”." msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"all\">[All]</span> <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 (“Select features” in the Main menu). It is strongly " "recommended to have one called <bug-PKG@gnu.org>; 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: <ol><li> msgid "" "<span class=\"new\">[New]</span> <b>Set up a repository for your source " "code</b> (“Select features” in the Main menu), and import " "whatever is available (look up the procedures under “Source Code " "Manager” in the Development Tools section). Experience has shown that " "self-hosting is unreliable. (<a " "href=\"/prep/maintain/html_node/Old-Versions.html#Old-Versions\">About " "back-up files</a>.)" msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"new\">[New]</span> <b>Upload your package to the GNU FTP " "site</b> if it is ready for public release. (<a " "href=\"/prep/maintain/html_node/Automated-FTP-Uploads.html\">About the " "upload procedure</a>.)" msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"new\">[New]</span> <b>Create a GNU home page</b>, to replace " "the <code>PKG.html</code> file that webmasters have placed in your web repo " "(keep the same name). If you want to make this quick and easy, use our " "standard <a " "href=\"/server/standards/boilerplate.html\">template</a>. Comment out the " "irrelevant parts, such as Downloading and Documentation if the project has " "barely started; you'll complete them later on. Also put any documentation " "you already have in a subdirectory called “manual”. (<a " "href=\"/prep/maintain/html_node/Web-Pages.html\">About web pages</a>.)" msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"adopted\">[Adopted]</span> <b>Check for existing bug " "reports</b> if you have adopted an existing package. These may be on any or " "all of a Savannah bug tracker, a <a href=\"https://lists.gnu.org/\">mailing " "list</a> (mbox archives can be downloaded by <a " "href=\"https://lists.gnu.org/archive/mbox/\">HTTPS</a>), or 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: <ol><li> msgid "" "<span class=\"adopted\">[Adopted]</span> <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. You may also like to get involved with the <a " "href=\"/software/guix/\">GNU Guix</a> package manager. (<a " "href=\"/distros/distros.html\">About distros</a>.)" msgstr "" #. type: Content of: <ol><li> msgid "" "<span class=\"adopted\">[Adopted]</span> <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: <ol><li> msgid "" "<span class=\"all\">[All]</span> <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> This is an excellent way to " "start learning a new codebase, and get a feel for how the system works. " "Besides, new features shouldn't be given much focus if notable problems " "already exist. (<a href=\"/software/devel.html\">About resources for GNU " "developers</a>.)" 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=\"/prep/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 <maintainers@gnu.org>. (<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 this list 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 "" #. type: Content of: <h3> msgid "GNU Philosophy" msgstr "" #. type: Content of: <p> msgid "" "This also seems like an appropriate page on which to give some links to the " "basic ideas of GNU and free software:" msgstr "" #. type: Content of: <ul><li> msgid "<a href=\"/gnu/the-gnu-project.html\">The GNU Project</a>" msgstr "" #. type: Content of: <ul><li> msgid "" "<a href=\"/philosophy/free-sw.html\">What is free software?</a> (the free " "software definition)" msgstr "" #. type: Content of: <ul><li> msgid "" "<a href=\"/philosophy/categories.html\">Categories of free and nonfree " "software</a>" msgstr "" #. type: Content of: <ul><li> msgid "<a href=\"/philosophy/compromise.html\">Avoiding ruinous compromises</a>" msgstr "" #. type: Content of: <ul><li> msgid "" "<a href=\"/philosophy/words-to-avoid.html\">Words to avoid (or use with " "care) because they are loaded or confusing</a>" msgstr "" #. type: Content of: <ul><li> msgid "<a href=\"/gnu/linux-and-gnu.html\">Linux and the GNU System</a>" msgstr "" #. type: Content of: <ul><li> msgid "<a href=\"/gnu/gnu-linux-faq.html\">GNU/Linux FAQ</a>" msgstr "" #. type: Content of: <ul><li> msgid "" "<a href=\"/philosophy/open-source-misses-the-point.html\">Why Open Source " "misses the point of Free Software</a>" 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 & GNU inquiries to <a " "href=\"mailto:gnu@gnu.org\"><gnu@gnu.org></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:webmasters@gnu.org\"><webmasters@gnu.org></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:web-translators@gnu.org"> # #. <web-translators@gnu.org></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 © 2014, 2017, 2018, 2019 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/4.0/\">Creative Commons " "Attribution-NoDerivatives 4.0 International 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 ""