[Top][All Lists]

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

gnustandards maintain.texi

From: John Darrington
Subject: gnustandards maintain.texi
Date: Mon, 27 Nov 2017 01:05:31 -0500 (EST)

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     John Darrington <jmd>   17/11/27 01:05:31

Modified files:
        .              : maintain.texi 

Log message:
        maintain.tex: Patch on behalf of rms


Index: maintain.texi
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.264
retrieving revision 1.265
diff -u -b -r1.264 -r1.265
--- maintain.texi       16 Oct 2017 18:25:37 -0000      1.264
+++ maintain.texi       27 Nov 2017 06:05:31 -0000      1.265
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate October 16, 2017
address@hidden lastupdate November 7, 2017
 @c %**end of header
 @dircategory GNU organization
@@ -24,7 +24,8 @@
 Copyright @copyright{} 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999,
 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009,
-2010, 2011, 2012, 2013, 2014, 2015, 2016 Free Software Foundation, Inc.
+2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 Free Software Foundation,
 Permission is granted to copy, distribute and/or modify this document
 under the terms of the GNU Free Documentation License, Version 1.3 or
@@ -90,6 +91,9 @@
 In addition to this document, please read and follow the GNU Coding
 Standards (@pxref{Top, , Contents, standards, GNU Coding Standards}).
+You may also usefully check the ``Tips for new GNU maintainers''
+(@url{}), a list of the
+most important things you will need to do as a new maintainer.
 @cindex @code{} email address
 @cindex Savannah repository for @code{gnustandards}
@@ -2066,16 +2070,27 @@
 @chapter Web Pages
 @cindex web pages
-Please write web pages about your package, and install them on
address@hidden  They should follow our usual standards for web
-pages (see @url{}).
-The overall goals are to support a wide variety of browsers, to focus
-on information rather than flashy eye candy, and to keep the site
-simple and uniform.
+As soon as a new package is dubbed GNU, its home page
+is listed on
address@hidden://} and
address@hidden://}.  To avoid broken links,
+the webmasters create a temporary home page as follows:
-We encourage you to use the standard @code{} template as
-the basis for your pages:
address@hidden @bullet
+If there is a Savannah project for this package (@pxref{Hosting for
+Web Pages}), the temporary home page redirects to the project's main
+page, @indicateurl{{package}},
+where a short description should be available.
+Otherwise, the webmasters make a simple home page containing the short
+description provided with the original submission of the package to GNU.
address@hidden itemize
+This temporary home page ought to be replaced with the real one as soon
+as possible.
 Some GNU packages have just simple web pages, but the more information
 you provide, the better.  So please write as much as you usefully can,
@@ -2084,6 +2099,19 @@
 set them up on whatever site is convenient for you, and make the pages
 on @code{} link to that site.
+Your web pages should follow our usual standards (see
address@hidden://}). The
+overall goals are to support a wide variety of browsers, to focus on
+information rather than visual adornments, and to keep
+consistent on certain important points.
+We encourage you to use the standard @code{} template as
+the basis for your pages:
+This template changes slightly from time to time for various reasons. If
+a change affects existing web pages, the webmasters will inform you;
+then you can make the change or they can.
 Please follow the best practices of accessibility in your web pages
 (see @url{}).
@@ -2113,6 +2141,10 @@
 instance, you can mail them pages to install, if necessary.  But that
 is more work for them, so please use Savannah if you can.
+Please note that the GNU webmasters may fix technical details in your
+web pages (HTML, CSS, obvious typos, broken links in the footer, etc.)
+and inform you of the change afterwards.
 If you use Savannah, you can use a special file named @file{.symlinks}
 in order to create symbolic links, which are not supported in CVS.
 For details, see

reply via email to

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