www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/software devel.de.html po/devel.de-diff.html


From: GNUN
Subject: www/software devel.de.html po/devel.de-diff.html
Date: Fri, 23 Aug 2019 07:32:28 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     19/08/23 07:32:28

Modified files:
        software       : devel.de.html 
Added files:
        software/po    : devel.de-diff.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/software/devel.de.html?cvsroot=www&r1=1.49&r2=1.50
http://web.cvs.savannah.gnu.org/viewcvs/www/software/po/devel.de-diff.html?cvsroot=www&rev=1.1

Patches:
Index: devel.de.html
===================================================================
RCS file: /web/www/www/software/devel.de.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -b -r1.49 -r1.50
--- devel.de.html       3 Dec 2016 23:45:17 -0000       1.49
+++ devel.de.html       23 Aug 2019 11:32:26 -0000      1.50
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/software/devel.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/software/po/devel.de.po">
+ https://www.gnu.org/software/po/devel.de.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/software/devel.html"
+ --><!--#set var="DIFF_FILE" value="/software/po/devel.de-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2019-06-24" --><!--#set 
var="ENGLISH_PAGE" value="/software/devel.en.html" -->
 
 <!--#include virtual="/server/header.de.html" -->
 <!-- Parent-Version: 1.77 -->
@@ -8,6 +13,7 @@
 
 <!--#include virtual="/software/po/devel.translist" -->
 <!--#include virtual="/server/banner.de.html" -->
+<!--#include virtual="/server/outdated.de.html" -->
 <h2>Ressourcen für die Entwicklung</h2>
 
 <p>Diese Seite beschreibt viele der auf Rechnern des GNU-Projekts für die
@@ -312,7 +318,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Letzte Änderung:
 
-$Date: 2016/12/03 23:45:17 $
+$Date: 2019/08/23 11:32:26 $
 
 <!-- timestamp end -->
 </p>

Index: po/devel.de-diff.html
===================================================================
RCS file: po/devel.de-diff.html
diff -N po/devel.de-diff.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/devel.de-diff.html       23 Aug 2019 11:32:27 -0000      1.1
@@ -0,0 +1,295 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/software/devel.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+&lt;!--#include virtual="/server/header.html" --&gt;
+&lt;!-- Parent-Version: 1.77 --&gt;
+&lt;title&gt;GNU Development Resources
+- GNU Project - Free Software Foundation&lt;/title&gt;
+&lt;!--#include virtual="/software/po/devel.translist" --&gt;
+&lt;!--#include virtual="/server/banner.html" --&gt;
+&lt;h2&gt;GNU Development Resources&lt;/h2&gt;
+
+&lt;p&gt;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 &lt;a
+href="/prep/maintain/"&gt;Information for GNU Maintainers&lt;/a&gt; document, 
and
+also follow the &lt;a href="/prep/standards/"&gt;GNU Coding 
Standards&lt;/a&gt;.
+Also interesting to review may be the &lt;a
+href="/software/maintainer-tips.html"&gt;tips for GNU maintainers&lt;/a&gt; and
+&lt;a href="/help/evaluation.html#whatmeans"&gt;overview of what it means to
+be a GNU package&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;With the abundance of inexpensive computers that can run &lt;a
+href="/gnu/linux-and-gnu.html"&gt;GNU/Linux&lt;/a&gt;, 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.&lt;/p&gt;
+
+&lt;p&gt;For that reason, the Free Software Foundation strongly encourages GNU
+software projects to use the machines at &lt;code&gt;gnu.org&lt;/code&gt; 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.&lt;/p&gt;
+
+
+&lt;h3 id="CVS"&gt;Savannah and version control&lt;/h3&gt;
+
+&lt;p&gt;If you are developing an official GNU package, we strongly recommend
+using a public source control repository on &lt;a
+href="http://savannah.gnu.org/"&gt;Savannah&lt;/a&gt;, the GNU hosting server.
+To do this, first &lt;a
+href="https://savannah.gnu.org/account/register.php"&gt;create yourself an
+account&lt;/a&gt; and then &lt;a
+href="http://savannah.gnu.org/register/"&gt;register your GNU 
package&lt;/a&gt;.
+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.&lt;/p&gt;
+
+
+&lt;h3 id="MailLists"&gt;Mailing lists&lt;/h3&gt;
+
+&lt;p&gt;We operate mailing lists for GNU software packages as needed,
+including both hand-managed lists and automatically managed lists.&lt;/p&gt;
+
+&lt;p&gt;When a GNU package is registered on &lt;a
+href="http://savannah.gnu.org/"&gt;Savannah&lt;/a&gt;, a web interface allows
+developers to create and manage mailing lists dedicated to their
+package.&lt;/p&gt;
+
+&lt;p&gt;Each GNU package &lt;em&gt;name&lt;/em&gt; ought to have at least a 
bug-reporting
+list with the canonical name 
&lt;code&gt;bug-&lt;em&gt;name&lt;/em&gt;@gnu.org&lt;/code&gt;,
+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 address@hidden but we now encourage packages to set up their
+own individual lists.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;Mailing list archives for automatically-managed lists are available
+at &lt;a <span 
class="removed"><del><strong>href="http://lists.gnu.org/"&gt;lists.gnu.org&lt;/a&gt;
 (&lt;a
+href="rsync://lists.gnu.org/"&gt;mbox</strong></del></span> <span 
class="inserted"><ins><em>href="https://lists.gnu.org/"&gt;lists.gnu.org&lt;/a&gt;
 (mbox</em></ins></span> archives <span class="removed"><del><strong>available 
through rsync&lt;/a&gt;
+and</strong></del></span>
+<span class="inserted"><ins><em>can be downloaded by</em></ins></span> &lt;a 
<span 
class="removed"><del><strong>href="ftp://lists.gnu.org/"&gt;ftp&lt;/a&gt;),</strong></del></span>
+<span 
class="inserted"><ins><em>href="https://lists.gnu.org/archive/mbox/"&gt;HTTPS&lt;/a&gt;),</em></ins></span>
+as well as through the list
+manager. Archives for hand-maintained lists are generally kept in
+&lt;code&gt;/com/archive&lt;/code&gt; on the GNU machines.&lt;/p&gt;
+
+&lt;p&gt;When a mailing list becomes large enough to justify it, we can set up
+a &lt;code&gt;gnu.*&lt;/code&gt; newsgroup with a two-way link to the mailing
+list.&lt;/p&gt;
+
+
+&lt;h3 id="WebServer"&gt;Web pages&lt;/h3&gt;
+
+&lt;p&gt;The master GNU web server is &lt;a
+href="http://www.gnu.org/"&gt;http://www.gnu.org/&lt;/a&gt;.  We very strongly
+recommend that GNU packages use
+&lt;tt&gt;http://www.gnu.org/software/&lt;/tt&gt;&lt;i&gt;package&lt;/i&gt; as 
their primary
+home page.&lt;/p&gt;
+
+&lt;p&gt;Using Savannah, developers can create and maintain their own pages at
+that url via a CVS &ldquo;web repository&rdquo;, separate from the
+package's main source repository (which can use any supported version
+control system).  &lt;a href="/prep/maintain/maintain.html#Web-Pages"&gt;More
+information on maintaining GNU web pages&lt;/a&gt;.&lt;/p&gt;
+
+
+&lt;h3 id="FTP"&gt;FTP&lt;/h3&gt;
+
+&lt;p&gt;The primary ftp site for GNU software on &lt;a
+href="http://ftp.gnu.org/gnu"&gt;&lt;code&gt;http://ftp.gnu.org/&lt;/code&gt;&lt;/a&gt;,
+which is &lt;a href="/prep/ftp.html"&gt;mirrored worldwide&lt;/a&gt;.  We very
+strongly recommend that all GNU packages upload their releases here (in
+addition to any other location you find convenient).&lt;/p&gt;
+
+&lt;p&gt;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 &lt;a
+href="ftp://alpha.gnu.org/"&gt;&lt;code&gt;ftp://alpha.gnu.org/&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;The &lt;a
+href="/prep/maintain/maintain.html#Automated-FTP-Uploads"&gt;Information
+for GNU Maintainers&lt;/a&gt; document has complete details on the ftp upload
+process, which is the same for both servers.&lt;/p&gt;
+
+
+&lt;h3 id="LoginAccounts"&gt;Login accounts&lt;/h3&gt;
+
+&lt;p&gt;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.
+&lt;a href="README.accounts.html"&gt;Instructions for obtaining an account
+machines&lt;/a&gt; are written separately.&lt;/p&gt;
+
+&lt;p&gt;On the general login machine, the &lt;a 
href="/software/gsrc/"&gt;gsrc&lt;/a&gt;
+package developers maintain a hierarchy of the current GNU package
+releases (&lt;tt&gt;/gd/gnu/gnusys/live&lt;/tt&gt;), compiled from the original
+sources.  To use it, source 
&lt;tt&gt;/gd/gnu/gnusys/live/setup&lt;/tt&gt;.&lt;/p&gt;
+
+&lt;p&gt;You can also &lt;a
+href="http://www.fsf.org/about/systems/sending-mail-via-fencepost"&gt;use a
+GNU account for email&lt;/a&gt;.&lt;/p&gt;
+
+
+&lt;h3 id="Hydra"&gt;Hydra: Continuous builds and portability 
testing&lt;/h3&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;&lt;a href="http://nixos.org/hydra/"&gt;Hydra&lt;/a&gt; is a free 
continuous
+build tool based on the &lt;a href="http://nixos.org/nix/"&gt;Nix&lt;/a&gt; 
package
+manager.  Administrators of the &lt;a href="http://hydra.nixos.org/"&gt;Hydra
+instance at the Delft University of Technology&lt;/a&gt; have generously
+offered &lt;a href="http://hydra.nixos.org/project/gnu"&gt;slots for the GNU
+Project&lt;/a&gt;.  Projects on Hydra get re-built &lt;em&gt;at each 
commit&lt;/em&gt;
+or change in their dependencies, whichever comes first (dependencies
+&lt;em&gt;include&lt;/em&gt; the standard build environment being used, which
+itself contains recent released versions of GCC, GNU&nbsp;make,
+etc.)&lt;/p&gt;
+
+&lt;p&gt;Currently it can build software on GNU/Linux 
(&lt;tt&gt;i686&lt;/tt&gt; and
+&lt;tt&gt;x86_64&lt;/tt&gt;) 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
+&lt;code&gt;deb&lt;/code&gt;- and &lt;code&gt;RPM&lt;/code&gt;-based 
distributions.  Packages
+can be built against the latest versions of their dependencies; for
+instance, GnuTLS is built using GNU&nbsp;libtasn1 and GNU&nbsp;libgcrypt
+builds corresponding to their latest revision.&lt;/p&gt;
+
+&lt;p&gt;In addition to the &lt;a 
href="http://hydra.nixos.org/project/gnu"&gt;web
+interface&lt;/a&gt;, Hydra can send notifications by email when the build
+status of a project changes&mdash;e.g., from 
&lt;code&gt;SUCCEEDED&lt;/code&gt; to
+&lt;code&gt;FAILED&lt;/code&gt;.  When a build fails, its log and build tree 
are
+accessible from the web interface; the latter allows generated files
+(for example, &lt;code&gt;config.log&lt;/code&gt; or 
&lt;code&gt;testsuite.log&lt;/code&gt;) to
+be inspected, which provides debugging hints.&lt;/p&gt;
+
+&lt;p&gt;Any GNU software package can request a slot on Hydra.  Each package
+must provide its own &ldquo;build recipe&rdquo; written in the Nix
+language (a &lt;em&gt;Nix expression&lt;/em&gt;, in Nix parlance).  &lt;a
+href="http://git.savannah.gnu.org/cgit/hydra-recipes.git"&gt;Nix
+expressions for GNU projects&lt;/a&gt; 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 &lt;a
+href="http://git.savannah.gnu.org/cgit/hydra-recipes.git/tree/patch/release.nix"&gt;recipe
+for GNU&nbsp;Patch&lt;/a&gt;.  You are welcome to ask for guidance on &lt;a
+href="mailto:address@hidden"&gt;address@hidden&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;After constructing your build recipe, email &lt;a
+href="http://lists.gnu.org/mailman/listinfo/hydra-users"&gt;address@hidden&lt;/a&gt;
+and ask to be included in Hydra.  Also make sure to become a member of
+the &lt;a
+href="https://savannah.gnu.org/projects/hydra-recipes/"&gt;&lt;code&gt;hydra-recipes&lt;/code&gt;
+project at Savannah&lt;/a&gt;.  This will allow you to customize your
+project's build job directly.&lt;/p&gt;
+
+&lt;p&gt; For technical information about Hydra, please consult the &lt;a
+href="http://hydra.nixos.org/job/hydra/trunk/tarball/latest/download-by-type/doc/manual"&gt;
+manual of Hydra&lt;/a&gt; (&lt;a
+href="http://hydra.nixos.org/job/hydra/trunk/tarball/latest/download-by-type/doc-pdf/manual"&gt;PDF&lt;/a&gt;).
+For more details, please refer to the &lt;a
+href="http://hydra.nixos.org/job/nix/trunk/tarball/latest/download/1/nix/manual.html"&gt;Nix
+manual&lt;/a&gt;.&lt;/p&gt;
+
+
+&lt;h3 id="platform-testers"&gt;platform-testers: Manual portability 
testing&lt;/h3&gt;
+
+&lt;p&gt;Another useful option for pre-release testing is the &lt;a
+href="http://lists.gnu.org/mailman/listinfo/platform-testers"&gt;platform-testers
+mailing list&lt;/a&gt;.  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.)&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;So, if you have a pre-release, you can write to the mailing list,
+providing (1)&nbsp;the url to the tarball, (2)&nbsp;the planned date of
+the release, and (3)&nbsp;the email address to which build reports
+should be sent.  The builds and reports are made by hand by the
+volunteers on the list.&lt;/p&gt;
+
+&lt;/div&gt;&lt;!-- for id="content", starts in the include above --&gt;
+&lt;!--#include virtual="/server/footer.html" --&gt;
+&lt;div id="footer"&gt;
+&lt;div class="unprintable"&gt;
+
+&lt;p&gt;Please send general FSF &amp; GNU inquiries to
+&lt;a href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.
+There are also &lt;a href="/contact/"&gt;other ways to contact&lt;/a&gt;
+the FSF.  Broken links and other corrections or suggestions can be sent
+to &lt;a 
href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;&lt;!-- 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 &lt;a href="mailto:address@hidden"&gt;
+        &lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+
+        &lt;p&gt;For information on coordinating and submitting translations of
+        our web pages, see &lt;a
+        href="/server/standards/README.translations.html"&gt;Translations
+        README&lt;/a&gt;. --&gt;
+Please see the &lt;a
+href="/server/standards/README.translations.html"&gt;Translations
+README&lt;/a&gt; for information on coordinating and submitting translations
+of this article.&lt;/p&gt;
+&lt;/div&gt;
+
+&lt;!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND <span class="removed"><del><strong>3.0 
US.</strong></del></span> <span 
class="inserted"><ins><em>4.0.</em></ins></span>  Please do NOT change or 
remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. --&gt;
+
+&lt;p&gt;Copyright &copy; <span 
class="removed"><del><strong>2014</strong></del></span> <span 
class="inserted"><ins><em>2014, 2019</em></ins></span> Free Software 
Foundation, Inc.&lt;/p&gt;
+
+&lt;p&gt;This page is licensed under a &lt;a rel="license"
+<span 
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/"&gt;Creative</strong></del></span>
+<span 
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/"&gt;Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United 
States</strong></del></span> <span 
class="inserted"><ins><em>Attribution-NoDerivatives 4.0 
International</em></ins></span> License&lt;/a&gt;.&lt;/p&gt;
+
+&lt;!--#include virtual="/server/bottom-notes.html" --&gt;
+
+&lt;p class="unprintable"&gt;Updated:
+&lt;!-- timestamp start --&gt;
+$Date: 2019/08/23 11:32:27 $
+&lt;!-- timestamp end --&gt;
+&lt;/p&gt;
+&lt;/div&gt;
+&lt;/div&gt;
+&lt;/body&gt;
+&lt;/html&gt;
+</pre></body></html>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]