# LANGUAGE translation of https://www.gnu.org/software/devel.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: devel.html\n" "POT-Creation-Date: 2024-11-06 10:27+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=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. type: Content of: msgid "GNU Development Resources - GNU Project - Free Software Foundation" msgstr "" #. type: Content of: <div><h2> msgid "GNU Development Resources" msgstr "" #. type: Content of: <div><p> msgid "" "This page describes many of the development resources available for GNU " "developers on GNU Project machines. For full details of the privileges and " "responsibilities of GNU maintainers, please see the <a " "href=\"/prep/maintain/\">Information for GNU Maintainers</a> document, and " "also follow the <a href=\"/prep/standards/\">GNU Coding Standards</a>. Also " "interesting to review may be the <a " "href=\"/software/maintainer-tips.html\">tips for GNU maintainers</a> and <a " "href=\"/help/evaluation.html#whatmeans\">overview of what it means to be a " "GNU package</a>." msgstr "" #. type: Content of: <div><p> msgid "" "With the abundance of inexpensive computers that can run <a " "href=\"/gnu/linux-and-gnu.html\">GNU/Linux</a>, as well as the greater " "availability of Internet access, many GNU volunteers today have all the " "computer facilities they need. However, there are still advantages to having " "central computers where GNU volunteers can work together without having to " "make their own machines accessible to others." msgstr "" #. type: Content of: <div><p> msgid "" "For that reason, the Free Software Foundation strongly encourages GNU " "software projects to use the machines at <code>gnu.org</code> as a home " "base. Using these machines also benefits the GNU Project indirectly, by " "increasing public awareness of GNU, and spreading the idea of working " "together for the benefit of everyone." msgstr "" #. type: Content of: <div><h3> msgid "Savannah and version control" msgstr "" #. type: Content of: <div><p> msgid "" "If you are developing an official GNU package, we strongly recommend using a " "public source control repository on <a " "href=\"https://savannah.gnu.org/\">Savannah</a>, the GNU hosting server. To " "do this, first <a " "href=\"https://savannah.gnu.org/account/register.php\">create yourself an " "account</a> and then register your GNU package. After it is created, you " "will be able to choose a version control system, create web pages for your " "package, manage permissions for contributors to the pages, and many other " "features." msgstr "" #. type: Content of: <div><h3> msgid "Mailing lists" msgstr "" #. type: Content of: <div><p> msgid "" "We operate mailing lists for GNU software packages as needed, including both " "hand-managed lists and automatically managed lists." msgstr "" #. type: Content of: <div><p> msgid "" "When a GNU package is registered on Savannah, a web interface allows " "developers to create and manage mailing lists dedicated to their package." msgstr "" #. type: Content of: <div><p> msgid "" "Each GNU package <em>name</em> ought to have at least a bug-reporting list " "with the canonical name <code>bug-<var>pkgname</var>@gnu.org</code>, plus " "any aliases that may be useful. Using Savannah, you can create lists for " "your package with names like this. Some packages share the list " "bug-gnu-utils@gnu.org but we now encourage packages to set up their own " "individual lists." msgstr "" #. type: Content of: <div><p> msgid "" "Packages can have other lists for announcements, asking for help, posting " "source code, for discussion among users, or whatever the package maintainer " "finds to be useful." msgstr "" #. type: Content of: <div><p> msgid "" "Mailing list archives for automatically-managed lists are available at <a " "href=\"https://lists.gnu.org/\">lists.gnu.org</a> (mbox archives can be " "downloaded by <a href=\"https://lists.gnu.org/archive/mbox/\">HTTPS</a>), as " "well as through the list manager. Archives for hand-maintained lists are " "generally kept in <code>/com/archive</code> on the GNU machines." msgstr "" #. type: Content of: <div><p> msgid "" "When a mailing list becomes large enough to justify it, we can set up a " "<code>gnu.*</code> newsgroup with a two-way link to the mailing list." msgstr "" #. type: Content of: <div><h3> msgid "Web pages" msgstr "" #. type: Content of: <div><p> msgid "" "The master GNU web server is <a href=\"/home.html\">www.gnu.org</a>. We " "very strongly recommend that GNU packages use " "<code>https://www.gnu.org/software/<var>pkgname</var></code> as their " "primary home page." msgstr "" #. type: Content of: <div><p> msgid "" "Using Savannah, developers can create and maintain their own pages at that " "url via a CVS “web repository,” separate from the package's main " "source repository (which can use any supported version control system). <a " "href=\"/prep/maintain/maintain.html#Web-Pages\">More information on " "maintaining GNU web pages</a>." msgstr "" #. type: Content of: <div><h3> msgid "FTP" msgstr "" #. type: Content of: <div><p> msgid "" "The primary ftp site for GNU software on <a " "href=\"https://ftp.gnu.org/gnu\"><code>https://ftp.gnu.org/gnu</code></a>, " "which is <a href=\"/prep/ftp.html\">mirrored worldwide</a>. We very " "strongly recommend that all GNU packages upload their releases here (in " "addition to any other location you find convenient)." msgstr "" #. type: Content of: <div><p> msgid "" "We use a different server for test releases, so that people won't install " "them thinking they are ready for prime time. This server is <a " "href=\"https://alpha.gnu.org/gnu\"><code>https://alpha.gnu.org/gnu</code></a>." msgstr "" #. type: Content of: <div><p> msgid "" "The <a " "href=\"/prep/maintain/maintain.html#Automated-FTP-Uploads\">Information for " "GNU Maintainers</a> document has complete details on the ftp upload process, " "which is the same for both servers." msgstr "" #. type: Content of: <div><h3> msgid "Login accounts" msgstr "" #. type: Content of: <div><p> msgid "" "We provide shell login access to GNU machines to people who need them for " "work on GNU software. Having a login account is both a privilege and a " "responsibility, and they should be used only for your work on GNU. <a " "href=\"/software/README.accounts.html\">Instructions for obtaining an " "account machines</a> are written separately." msgstr "" #. type: Content of: <div><p> msgid "" "On the general login machine, the <a href=\"/software/gsrc/\">gsrc</a> " "package developers maintain a hierarchy of the current GNU package releases " "(<code>/gd/gnu/gnusys/live</code>), compiled from the original sources. To " "use it, source <code>/gd/gnu/gnusys/live/setup</code>." msgstr "" #. type: Content of: <div><p> msgid "" "You can also <a " "href=\"https://www.fsf.org/about/systems/sending-mail-via-fencepost\">use a " "GNU account for email</a>." msgstr "" #. type: Content of: <div><h3> msgid "Hydra: Continuous builds and portability testing" msgstr "" #. type: Content of: <div><p> msgid "" "Continuous build tools (often referred to as continuous integration tools) " "allow programming errors to be spotted soon after they are introduced in a " "software project, which is particularly useful for cooperatively developed " "software." msgstr "" #. type: Content of: <div><p> msgid "" "<a href=\"https://gothub.projectsegfau.lt/NixOS/hydra/\"> Hydra</a> is a " "free continuous build tool based on the <a " "href=\"https://nixos.org/\">Nix</a> package manager. Administrators of the " "<a href=\"https://hydra.nixos.org/\">Hydra instance at the Delft University " "of Technology</a> have generously offered <a " "href=\"https://hydra.nixos.org/project/gnu\">slots for the GNU Project</a>. " "Projects on Hydra get re-built <em>at each commit</em> or change in their " "dependencies, whichever comes first (dependencies <em>include</em> the " "standard build environment being used, which itself contains recent released " "versions of GCC, GNU make, etc.)" msgstr "" #. type: Content of: <div><p> msgid "" "Currently it can build software on GNU/Linux (<code>i686</code> and " "<code>x86_64</code>) as well as FreeBSD, Darwin, Solaris, and Cygwin, and " "can cross-build for GNU/Hurd, GNU/Linux on other architectures, and MinGW. " "It can provide code coverage reports produced using LCOV. In addition to " "source tarballs and Nix packages, it can build packages for " "<code>deb</code>- and <code>RPM</code>-based distributions. Packages can be " "built against the latest versions of their dependencies; for instance, " "GnuTLS is built using GNU libtasn1 and GNU libgcrypt builds " "corresponding to their latest revision." msgstr "" #. type: Content of: <div><p> msgid "" "In addition to the <a href=\"https://hydra.nixos.org/project/gnu\">web " "interface</a>, Hydra can send notifications by email when the build status " "of a project changes—e.g., from <code>SUCCEEDED</code> to " "<code>FAILED</code>. When a build fails, its log and build tree are " "accessible from the web interface; the latter allows generated files (for " "example, <code>config.log</code> or <code>testsuite.log</code>) to be " "inspected, which provides debugging hints." msgstr "" #. type: Content of: <div><p> msgid "" "Any GNU software package can request a slot on Hydra. Each package must " "provide its own “build recipe” written in the Nix language (a " "<em>Nix expression</em>, in Nix parlance). <a " "href=\"https://git.savannah.gnu.org/cgit/hydra-recipes.git\">Nix expressions " "for GNU projects</a> are available via Git. For simple projects using " "standard GNU build tools such as Automake and Autoconf, the recipe is " "usually fairly simple. For example, see the <a " "href=\"https://git.savannah.gnu.org/cgit/hydra-recipes.git/tree/patch/release.nix\">recipe " "for GNU Patch</a>. You are welcome to ask for guidance on <<a " "href=\"mailto:hydra-users@gnu.org\">hydra-users@gnu.org</a>>." msgstr "" #. type: Content of: <div><p> msgid "" "After constructing your build recipe, email <a " "href=\"https://lists.gnu.org/mailman/listinfo/hydra-users\">hydra-users@gnu.org</a> " "and ask to be included in Hydra. Also make sure to become a member of the " "<a " "href=\"https://savannah.gnu.org/projects/hydra-recipes/\"><code>hydra-recipes</code> " "project at Savannah</a>. This will allow you to customize your project's " "build job directly." msgstr "" #. type: Content of: <div><p> msgid "" "For technical information about Hydra, please consult the <a " "href=\"https://hydra.nixos.org/job/hydra/master/manual/latest/download-by-type/doc/manual\"> " "manual of Hydra</a>. For more details, please refer to the <a " "href=\"https://hydra.nixos.org/job/nix/trunk/tarball/latest/download/1/nix/manual.html\">Nix " "manual</a>." msgstr "" #. type: Content of: <div><h3> msgid "platform-testers: Manual portability testing" msgstr "" #. type: Content of: <div><p> msgid "" "Another useful option for pre-release testing is the <a " "href=\"https://lists.gnu.org/mailman/listinfo/platform-testers\">platform-testers " "mailing list</a>. Time permitting, the people on this list build " "pre-releases on a wide variety of platforms upon request. (Volunteers to " "handle testing requests are needed! Just subscribe to the list and start " "participating.)" msgstr "" #. type: Content of: <div><p> msgid "" "In contrast to the Hydra tool described above, the platform-testers list " "works essentially by hand, so each method has its advantages and " "disadvantages. Also, the platform-testers crew has access to a wider " "variety of platforms and compilers than the Hydra setup." msgstr "" #. type: Content of: <div><p> msgid "" "So, if you have a pre-release, you can write to the mailing list, providing " "(1) the url to the tarball, (2) the planned date of the release, " "and (3) the email address to which build reports should be sent. The " "builds and reports are made by hand by the volunteers on the list." 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 contributing 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 contributing translations of this " "article." msgstr "" #. type: Content of: <div><p> msgid "" "Copyright © 2000-2002, 2007, 2009-2012, 2014, 2022, 2024 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 ""