[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards README.webmastering.html
|
From: |
Therese Godefroy |
|
Subject: |
www/server/standards README.webmastering.html |
|
Date: |
Sun, 9 Sep 2018 06:34:28 -0400 (EDT) |
CVSROOT: /webcvs/www
Module name: www
Changes by: Therese Godefroy <th_g> 18/09/09 06:34:28
Modified files:
server/standards: README.webmastering.html
Log message:
Reorganize and proofread; move what is also useful for maintainers
to gnu-website-guidelines.html (RT #1318643).
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.201&r2=1.202
Patches:
Index: README.webmastering.html
===================================================================
RCS file: /webcvs/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.201
retrieving revision 1.202
diff -u -b -r1.201 -r1.202
--- README.webmastering.html 28 May 2018 15:23:24 -0000 1.201
+++ README.webmastering.html 9 Sep 2018 10:34:27 -0000 1.202
@@ -40,21 +40,22 @@
<li><a href="#webpages">Editing and creating web pages</a>
<ul>
<li><a href="#structure">Site structure and navigation</a></li>
- <li><a href="#templating">Page templating</a></li>
- <li><a href="#styling">Page styling</a></li>
- <li><a href="#orthography">Orthography</a></li>
- <li><a href="#addarticle">Adding new articles</a></li>
- <li><a href="#writeentry">Writing and reviewing items for
<code>/proprietary</code></a></li>
+ <li><a href="/server/standards/gnu-website-guidelines.html#templating">
+ Using our page template</a></li>
+ <li><a href="/server/standards/gnu-website-guidelines.html#styling">
+ Page styling</a></li>
+ <li><a href="#addarticle">Conversion of plain text to XHTML</a></li>
+ <li><a href="#writeentry">Writing and reviewing items for
+ <code>/proprietary</code></a></li>
<li><a href="#announcements">Making a new page visible</a></li>
<li><a href="#gnupackages">Web pages for official GNU software</a></li>
</ul></li>
<li><a href="#linking">Linking</a>
<ul>
- <li><a href="#pollinking">Linking policies</a></li>
- <li><a href="#distros">Links to free GNU/Linux distributions</a></li>
- <li><a href="#usergroups">Links to GNU & Free Software User
Groups</a></li>
<li><a href="#deadlink">Fixing dead links</a></li>
<li><a href="#addlink">Adding links</a></li>
+ <li><a href="#distros">Links to free GNU/Linux distributions</a></li>
+ <li><a href="#usergroups">Links to GNU & Free Software User
Groups</a></li>
</ul></li>
<li><a href="#mirrors">Mirrors</a>
<ul>
@@ -67,15 +68,13 @@
<li><a href="#thankgnu">ThankGNU/ThankCRM</a></li>
<li><a href="#image">Requests for permission to use an image</a></li>
</ul></li>
- <li><a href="#repo">Working with webmaster-related repositories</a>
- <ul>
- <li><a href="#cvs">Basic CVS commands</a></li>
- <li><a href="#scripts">Scripts</a></li>
- <li><a href="#symlinks">Symbolic links</a></li>
- <li><a href="#htaccess">.htaccess and redirections</a></li>
- <li><a href="#sysadmins">System administrators</a></li>
- </ul></li>
- <li><a href="#readme">More README pages</a></li>
+ <li><a href="#AddImageToGallery">Adding an image to the GNU Gallery</a></li>
+ <li><a href="/server/standards/gnu-website-guidelines.html#pollinking">
+ Appendix 1 - Linking Policies</a></li>
+ <li><a href="/server/standards/gnu-website-guidelines.html#repo">
+ Appendix 2 - Working with Web CVS Repositories</a></li>
+ <li><a href="/server/standards/gnu-website-guidelines.html#UsefulResources">
+ Useful Resources</a></li>
</ul>
<hr class="no-display" />
</div>
@@ -245,9 +244,9 @@
<li>If the message is about adding an image or a joke, be sure to get
the explicit ok for it to be released under a free
license—GPLv3-or-later and FDLv1.3-or-later is good. Then make a
-new page under <code>/graphics</code>, resp. <code>/fun</code>, and add it to
the
-index page. RMS' requirements for adding items to <code>/fun</code> are in
-<a href="/fun/README">/fun/README</a>.</li>
+new page under <code>/graphics</code>, resp. <code>/fun</code>, and add it
+to the index page. RMS' requirements for adding items to <code>/fun</code>
+are in <a href="/fun/README">/fun/README</a>.</li>
<li>If the message is about a mirror, see <a
href="#mirrors">mirror procedures and information</a>.</li>
@@ -260,7 +259,8 @@
ticket.</li>
<li>If the message needs to be dealt with by another group, such as
-web-translators, sysadmin, licensing or audio-video, move it to the
+<em>web-translators</em>, <em>sysadmin</em>, <em>licensing</em> or
+<address@hidden>, move it to the
corresponding queue or otherwise forward it. <a
href="#rtmisdirected">Specific directions for redirecting tickets</a>.</li>
</ul>
@@ -271,13 +271,13 @@
<p>You can attach two kinds of information to a ticket: correspondence and
comments.</p>
-<p><em>Correspondence</em> will be sent to the person who sent the initial
report. Add
-correspondence when you want to get more information about the report, give
-the requestor more information about the work being done, let them know
-it's finished, and so on.</p>
+<p><em>Correspondence</em> will be sent to the person who sent the initial
+report. Add correspondence when you want to get more information about the
+report, give the requestor more information about the work being done, let
+them know it's finished, and so on.</p>
-<p><em>Comments</em> are only seen by the ticket staff: the owner and people
listed
-as AdminCCs. You can use comments to make internal notes about ticket
+<p><em>Comments</em> are only seen by the ticket staff: the owner and people
+listed as AdminCCs. You can use comments to make internal notes about ticket
work. For instance, if you do some work on converting an essay of RMS's to
HTML, but didn't get a chance to finish yet, you could add a comment saying
that you're partially done, so other webmasters know not to work on it
@@ -289,8 +289,8 @@
<p>Unfortunately, the methods for adding either type of correspondence are
very similar, so it's easy to get them confused. Be careful.</p>
-<p>To add correspondence, use one of the “Reply” links on the
ticket page, or
-send mail to <address@hidden> with</p>
+<p>To add correspondence, use one of the “Reply” links on the
+ticket page, or send mail to <address@hidden> with</p>
<pre>
[gnu.org #1234]
@@ -298,8 +298,8 @@
<p>in the subject line, where 1234 is the ticket number.</p>
-<p>To add comments, use one of the “Comment” links on the ticket
page, or send
-mail to <address@hidden> with</p>
+<p>To add comments, use one of the “Comment” links on the ticket
+page, or send mail to <address@hidden> with</p>
<pre>
[gnu.org #1234]
@@ -323,8 +323,8 @@
<p>So, say for example that you wanted to ask RMS whether
a certain link on a page was permissible. You can do this by using
-one of the “Comment” links on the ticket page, and listing the
other
-party (in this case, <address@hidden>) in the CC field. You
+one of the “Comment” links on the ticket page, and listing the
+other party (in this case, <address@hidden>) in the CC field. You
could also do this by sending a mail with headers like this:</p>
<pre class="emph-box">
@@ -339,8 +339,8 @@
guaranteed to go into the ticket (also as comments). The latter is fine if
you're primarily doing work by email, however.</p>
-<p><em>Note that this won't work with other RT-handled addresses.</em> So, if
-you add <address@hidden> to the CC field of a comment on a
+<p><em>Note that this won't work with other RT-handled addresses.</em> So,
+if you add <address@hidden> to the CC field of a comment on a
ticket that already exists in webmasters, nothing will come to the
<em>campaigns</em> queue. In those situations, create a new ticket in the
queue whose attention you want to get, and use the “Refers
@@ -489,8 +489,17 @@
<h3 id="webpages">Editing and creating web pages</h3>
+<p>This section only contains information that is specifically aimed at
+webmasters. For general info, <span class="highlight">refer to the
+<a class="highlight" href="/server/standards/gnu-website-guidelines.html">GNU
+Website Guidelines</a>.</span></p>
+
+<p>To create a new page in the main part of gnu.org, please <a
+href="/server/standards/gnu-website-guidelines#templating">use the
+boilerplate</a>.</p>
+
-<h4 id="structure">Site structure and navigation</h4>
+<h4 id="structure">Site Structure and Navigation</h4>
<p>The site is divided up into directories by topic—there's a
directory for GNU Project information and history (“About GNU”
@@ -512,91 +521,21 @@
link back to their main page to allow people to get more information about
the topic at hand.</p>
-<p>Links should include a full path, if possible. For example, within
-a specific article in the <code>/proprietary</code> directory, link to
-<code>/proprietary/proprietary.html</code>, rather than just
-<code>proprietary.html</code>. This eases maintenance of the site as
-things get moved around.</p>
-
-
-<h4 id="templating">Page templating</h4>
-
-<p>All new pages in the main part of gnu.org should use a boilerplate
-that includes
-additional files by means of Apache SSIs. Please don't start out with
-an existing page to create a new one; use the <a
-href="//web.cvs.savannah.gnu.org/viewvc/*checkout*/www/server/standards/boilerplate.html?root=www&content-type=text%2Fplain">
-original source</a> of the boilerplate instead, and follow the instructions
-in it.</p>
-
-
-<h4 id="styling">Page styling</h4>
-
-<p>Generic styling for desktops and smartphones is provided by two CSS:
-<code>/reset.css</code> (from the <a
-href="//web.archive.org/web/20070930230754/http://developer.yahoo.com:80/yui/";>
-YUI library, version 2</a>), which normalizes the default rendering of all
-HTML elements by the various browsers, and <code>/layout.css</code>, which
-contains gnu.org-specific formatting.</p>
-
-<p>If some special styling is needed for a specific page, it should be added
-to the page itself in a <style> element, between the SSI directives
-that include <code>header.html</code> and <code>banner.html</code>. If the
-style applies to a single element, it should normally be added as an
attribute.</p>
-
-<p><em>Note about grids:</em> Very few pages currently use them. In the
-event you'd like to create one that does, good starting points may be
-found in <a
-href="//yuilibrary.com/yui/docs/cssgrids/">YUI version 3</a>, and <a
-href="//purecss.io/grids/">Pure Grids</a>. The components provided by
-these libraries are licensed under the modified (3-clause) BSD license.</p>
-
-<p>Mobile devices with very limited resources use <code>/mini.css</code>.
-This stylesheet is just the YUI (version 2) reset and base stylesheets,
as these
-devices typically have minimal need for various fonts and no need for
-fancy layouts.</p>
-
-<p>Printers use <code>/print.css</code>. Note that the header, navigation
-bars and footer (except copyright and license) are unprintable.</p>
-
-<p>Historical pages (unmaintained translations for the most part) refer
-to <code>/gnu.css</code>, which also loads the mobile CSS, as these pages are
-usually very basic, plain pages with little or no formatting.</p>
-
-<p>Some software manuals use a dedicated CSS, <code>/style.css</code>.</p>
-
-
-<h4 id="orthography">Orthography</h4>
-
-<p>English pages should follow the standard American spelling,
-hyphenation and punctuation conventions. However, these conventions are
-not always very specific, especially as regards hyphenation and quotes.
-For the sake of consistency, gnu.org adds its own rules:</p>
-
-<ul>
-<li>In ordinary text, HTML entities “&ldquo;...&rdquo;”
-and “&lsquo;...&rsquo;” are preferred over straight
-quotes ("..." and '...').</li>
-
-<li>“Nonfree” is preferred over “non-free”;
-likewise, “noncommercial” over “non-commercial.”</li>
-</ul>
-
-<h4 id="addarticle">Adding new articles</h4>
+<h4 id="addarticle">Conversion of plain text to XHTML</h4>
<p>Occasionally, RMS will mail an article, usually in plain text, to
webmasters and ask that they put it on the site. The plain text needs to be
-converted to XHTML and <a href="#templating">put into our standard
-boilerplate</a>. There are some things which you should look out for when
-doing the conversion:</p>
+converted to XHTML and <a
+href="/server/standards/gnu-website-guidelines#templating">put into our
+standard boilerplate</a>. There are a few things you should take care of
+while doing the conversion:</p>
<ul>
-<li>When they exist, preserve double spaces after sentence breaks.</li>
-<li>Replace any straight quotes with HTML entities (in ordinary text only,
-of course).</li>
-<li>Replace any instances of “non-free” with
-“nonfree.”</li>
+<li>Fix any obvious typos. If in doubt, contact the author.</li>
+<li>Follow the <a
+href="/server/standards/gnu-website-guidelines#orthography">spelling and
+punctuation guidelines</a>.</li>
<li>Add the author's name below the <h2> header.</li>
</ul>
@@ -605,7 +544,7 @@
<p>
If you plan to write or review an item for a page in <a
-href="/proprietary">/proprietary</a>, please refer to our <a
+href="/proprietary/proprietary.html">/proprietary/</a>, please refer to our <a
href="/server/standards/proprietary-guidelines.html">submission guidelines</a>.
</p>
@@ -651,200 +590,11 @@
<h3 id="linking">Linking</h3>
-<h4 id="pollinking">Linking policies</h4>
-
-<p>One of the most complex aspects of webmastering is following the linking
-guidelines; however, it's also a very crucial aspect of the job.</p>
-
-<p>We strive to ensure that all pages we promote—all pages which are
given
-links on our site—are friendly to the free software movement. Some
-pages will obviously not meet such standards; if the site flames the Free
-Software Foundation, or has no apparent relation to free software and
-surrounding issues, the link shouldn't be made. Beyond that, however,
-there are criteria used in determining whether or not it is appropriate to
-provide a link to a page from ours. They are listed below, in order of
-descending general importance.</p>
-
-<dl>
-<dt>What's the context of the link?</dt>
-
-<dd>
-<p>The link's purpose on our site will play a role in determining how
-strongly it should be judged against the other criteria. Pages
-hosting GNU projects will be held to the highest standards. Pages
-about other free software and given high promotion—for example,
-included in a newsfeed on the main page—are a close second.
-Links on the philosophy page may be given more leeway in talking
-about proprietary software; GNU/Linux user group pages should call
-the system GNU/Linux almost always but are hardly checked on other
-criteria. Always keep this in mind when deciding how to weigh each
-aspect of these policies.</p>
-</dd>
-
-<dt>Does the page promote proprietary software?</dt>
-
-<dd>
-<p>The big point made by the free software movement is that proprietary
-software presents an ethical dilemma: you cannot agree to such
-nonfree terms and treat those around you as you would like to be
-treated. When proprietary software is promoted, people get the
-impression that it is okay to use it, while we are trying to convince
-them otherwise. As such, we avoid offering such free advertising,
-either directly on our site or indirectly through links.</p>
-
-<p>What's tricky about this criteria is the “promotion” point:
there's
-a difference between mentioning proprietary software and making a
-sales pitch for it. Indeed, the GNU Project website mentions
-proprietary software throughout, but never gives people the impression
-that its use does not present ethical problems.</p>
-
-<p>There are two things to keep in mind when determining whether a
-reference to proprietary software promotes it, or simply mentions
-it. First, how much information does it offer about the software?
-Second, how much information is the reader likely to actually gain
-from this page?</p>
-
-<p>Different pages provide different amounts of information about
-proprietary software; the more it provides, the more of a problem
-it poses for us. For example, some pages may link to the primary
-site for a proprietary software program. Others may describe its
-functionality in detail. Even the product name given matters;
-there's a difference between “Windows” and
-“Microsoft Windows XP Home Edition.”</p>
-
-<p>If the page requires <a href="/philosophy/javascript-trap.html">nonfree,
-nontrivial JavaScript</a> and has serious failures with
-JavaScript disabled, the link shouldn't be made. Similarly, if the page
-has embedded Flash that plays an important role, so that a person would
-be missing something important if the videos do not play, the link
-should not be made.</p>
-
-<p>The subject of the reference will also play a role in determining
-how problematic a reference is. If the software is already very
-popular, it's unlikely that a basic mention of it will be news to
-the reader. Some examples of proprietary software which are common
-enough to be considered “well-known” are major operating systems
-(Windows, Mac OS, Sun OS, HP-UX) and primary common applications
-such as Office, Internet Explorer, Photoshop, Acrobat Reader, and
-Flash.</p>
-
-<p>GNU software project pages feel the full force of this policy.
-Proprietary software should only be mentioned when the software
-provides support for it, or to compare it against the features of
-well-known proprietary software. For example, the following
-text—and not much else—would be acceptable:</p>
-
-<blockquote><p>w3 is a web browser for GNU Emacs, similar to Internet Explorer.
-It can run on all platforms GNU Emacs runs on, including GNU/Linux,
-proprietary Unix systems, and Windows.</p></blockquote>
-
-<p>Links which appear in other areas, such as the testimonials or
-philosophy pages, as well as links to user groups may discuss such
-software in greater detail, but links and other methods of
-encouragement to “learn more” should still be avoided.</p>
-</dd>
-
-<dt>How does the page compare free software to open source?</dt>
-
-<dd>
-<p>Almost all pages which have links on our site should, at the very
-least, treat free software and open source equally. Failure to do
-so—whether it be by omitting free software or by implying that
-open source is superior—is usually unacceptable. GNU software
-project pages should have little mention of open source. The GNOME
-page used to provide a good example of a tactful way to do it:</p>
-
-<blockquote><p>GNOME is part of the GNU Project, and is free software
(sometimes
-referred to as open source software).</p></blockquote>
-
-<p>Any exceptions to this rule should be apparent from the context.
-For instance, user groups pages may talk in greater detail about
-open source; we state on the user groups page, “As with our links
-page, the FSF is not responsible for the contents of other websites,
-or how up-to-date their information is.”</p>
-</dd>
-
-<dt>How does the page treat the GNU Project?</dt>
-
-<dd>
-<p>Pages which we link to should treat the GNU Project well. The
-primary thing to look out for in this regard is whether the page
-calls the system GNU/Linux or just “Linux.” GNU software project
-and user group pages should almost never, if ever, fail to do this.
-Again, exceptions for other pages should be apparent from context.</p>
-
-<p>That said, certain parts of a page should not be considered against these
-criteria. For example, suppose we were to make a link to a page on a free
-software news site. Any advertisements or reader comments attached to the
-article would not be considered when determining whether it met or linking
-guidelines, since they're understood to be the opinion of their individual
-authors. Similarly, on user group pages, the contents of forums and Wiki
-pages should not hold weight in these regards.</p>
-
-<p>Finally, some sites are understood to always have exception with most of
-these guidelines. These sites are usually about issues which are
-important, but somewhat peripheral, to the free software movement. Several
-times we have linked to the Electronic Frontier Foundation's site, even
-though they encourage the use of Flash and talked exclusively about open
-source software. It's generally understood that since these pages are not
-primarily about free software, the policies do not hold full force for
-them.</p>
-
-<p>As a final explanation (coming from RMS):
-Even for making links from www.gnu.org, we do not <em>require</em> that
-people call the system GNU/Linux or use the term “free software”
-rather than “open source.” We do, however, require that they not
-promote any nonfree software.</p>
-
-<p>If all this seems complicated, that's because, unfortunately, it is. Don't
-worry; a knack for it comes with time and experience. You may mis-evaluate
-a few pages as you're learning to get a feel for what's acceptable and what
-isn't; please don't hesitate to get a second opinion from a more
-experienced webmaster, or someone in charge like the Chief Webmaster or
-RMS. New exceptions will always come up; keep an open mind to that
-possibility and be ready to handle them properly.</p>
-</dd>
-</dl>
-
-
-<h4 id="distros">Links to free GNU/Linux distributions</h4>
-
-<p>Suggestions for links to <a href="/distros/distros.html">GNU/Linux
-distributions</a> should be handled like this:</p>
-
-<ol>
-<li>The requestors should be the primary developers of the distro, not
-just users. If they are users, thank them and ask them to contact the
-developers in case they want to be listed.</li>
-
-<li>Briefly check that the distro is a <a
-href="/distros/common-distros.html">feasible candidate</a>: they should
-have a clear policy of only including free software, and it should be
-reasonably apparent how to get the sources and what packages are
-included. If these things are not present, talk to the requestor about
-it (politely).</li>
-
-<li>If there are no glaring problems, ask the requestors to request an
-endorsement from the dedicated mailing list <address@hidden>. They
-should include a description of their new distro, a link to their home
-page, and any other useful info. Our ticket should then be
-resolved.</li>
-
-<li>FYI: the gnu-linux-libre list will take over from there. In essence,
-they will review it in detail for meeting our criteria, and if all seems
-good, pass it on to the FSF licensing person for final approval.</li>
-</ol>
-
-<p>In any event, webmasters should <em>never</em> simply add new distros
-that are said to be free to <a href="/distros/free-distros.html">our
-list</a>. FSF licensing and RMS must explicitly approve any
-additions.</p>
-
-
-<h4 id="usergroups">Links to GNU & Free Software User Groups</h4>
-<p>Requests for links to GNU or Free Software Users Groups can be referred
-to the LibrePlanet website. Our ticket can then be resolved.</p>
+<p><span class="highlight">Before adding or replacing any links, please
+read our <a
+href="/server/standards/gnu-website-guidelines#pollinking">linking
+criteria</a>.</span></p>
<h4 id="deadlink">Fixing dead links</h4>
@@ -874,10 +624,11 @@
<ul>
<li>If the person requesting the link is a friend of the GNU Project,
-check the page against our <a href="#pollinking">linking criteria</a>,
-and if it passes, add the link as requested. If it doesn't, say so
-in your reply to the requestor, outlining in detail what the problem(s)
-are.</li>
+check the page against our <a
+href="/server/standards/gnu-website-guidelines#pollinking">linking
+criteria</a>, and if it passes, add the link as requested. If it doesn't,
+say so in your reply to the requestor, outlining in detail what the
+problem(s) are.</li>
<li>If the suggestion is coming from someone outside the GNU Project,
check the page against our linking criteria, and if it passes, forward
@@ -893,6 +644,46 @@
</ul>
+<h4 id="distros">Links to free GNU/Linux distributions</h4>
+
+<p>Suggestions for links to <a href="/distros/distros.html">GNU/Linux
+distributions</a> should be handled like this:</p>
+
+<ol>
+<li>The requestors should be the primary developers of the distro, not
+just users. If they are users, thank them and ask them to contact the
+developers in case they want to be listed.</li>
+
+<li>Briefly check that the distro is a <a
+href="/distros/common-distros.html">feasible candidate</a>: they should
+have a clear policy of only including free software, and it should be
+reasonably apparent how to get the sources and what packages are
+included. If these things are not present, talk to the requestor about
+it (politely).</li>
+
+<li>If there are no glaring problems, ask the requestors to request an
+endorsement from the dedicated mailing list
+<address@hidden>. They should include a description of
+their new distro, a link to their home page, and any other useful info. Our
+ticket should then be resolved.</li>
+
+<li>FYI: the gnu-linux-libre list will take over from there. In essence,
+they will review it in detail for meeting our criteria, and if all seems
+good, pass it on to the FSF licensing person for final approval.</li>
+</ol>
+
+<p>In any event, webmasters should <em>never</em> simply add new distros
+that are said to be free to <a href="/distros/free-distros.html">our
+list</a>. FSF licensing and RMS must explicitly approve any
+additions.</p>
+
+
+<h4 id="usergroups">Links to GNU & Free Software User Groups</h4>
+
+<p>Requests for links to GNU or Free Software Users Groups can be referred
+to the LibrePlanet website. Our ticket can then be resolved.</p>
+
+
<h3 id="mirrors">Mirrors</h3>
@@ -927,7 +718,7 @@
security risks for users. Checking the status of mirrors is therefore an
essential part of the process of adding/modifying mirrors.</p>
-<p>A <a href="//download.savannah.gnu.org/mirmon/allgnu/">mirmon page</a>
+<p>A <a href="//download.savannah.gnu.org/mirmon/allgnu/">Mirmon page</a>
tracker (maintained by Savannah) shows how up-to-date each mirror is. When
a mirror has gotten more than a few days out of date, it is necessary to
contact its maintainers and let them know about the problem so that they
@@ -937,8 +728,8 @@
<p>If a mirror needs to be removed, please check to see if it is referenced
on <code>/server/mirror.html</code> and remove that entry as well.</p>
-<p>The address <code>http(s?)://ftpmirror.gnu.org/PKG</code> (also maintained
by
-Savannah) multiplexes between the mirrors, trying to choose one that is
+<p>The address <code>http(s?)://ftpmirror.gnu.org/PKG</code> (also maintained
+by Savannah) multiplexes between the mirrors, trying to choose one that is
nearby and up to date.</p>
<h5>Mirror contact information</h5>
@@ -952,9 +743,9 @@
<h4 id="nongnu">Non-GNU mirrors</h4>
<p>When we get a request to add, change, or remove a non-GNU Savannah mirror,
-email <address@hidden> with the information. The reason to
-use -private is to avoid the contact address from becoming public. If the
-email address of a mirror admin is not involved or there are no other
+email <address@hidden> with the information. The
+reason to use -private is to avoid the contact address from becoming public.
+If the email address of a mirror admin is not involved or there are no other
privacy issues, it's better to use <address@hidden>.</p>
@@ -1014,245 +805,87 @@
incompatible with that license, move the ticket to the <em>licensing</em>
queue. Otherwise draw their attention to the license.</p>
-<p>If the web page where the image is located does not have a clear license and
-the request is a clear-cut yes or no, respond to the requestor
+<p>If the web page where the image is located does not have a clear license
+and the request is a clear-cut yes or no, respond to the requestor
directly and explain the decision with reference to GNU policy. For
more difficult cases, move the ticket to <em>licensing</em>.</p>
<p>When considering a request, err on the side of caution. If the use of
-an image isn't <a href="#pollinking">something we'd link to</a>, for example,
-then it isn't
-something we should give permission for. Feel free to discuss any
-requests on www-discuss before responding to them.</p>
-
-
-<h3 id="repo">Working with webmaster-related repositories</h3>
-
-
-<h4 id="cvs">Basic CVS commands</h4>
-
-<ul>
-<li>
-Before the initial checkout, set the environment variable
-<code>CVS_RSH=ssh</code>.
-</li>
-
-<li>
-<p>Check out the main www repository:</p>
-
-<pre class="emph-box">
-cvs -z3 -d:ext:<username>@cvs.savannah.gnu.org:/web/www co www
-</pre>
-
-<p>You will get a working directory, <code>www</code>, with the same
-structure as our main website.</p>
-</li>
-
-<li>
-<p>Check out the web repository of the fooproject:</p>
-
-<pre class="emph-box">
-cvs -z3 -d:ext:<username>@cvs.savannah.gnu.org:/web/fooproject co
fooproject
-</pre>
-
-<p>You will get a working directory, <code>fooproject</code> with the same
-structure as the <code>www/software/fooproject</code> subdirectory. Note,
-however, that the fooproject and www repositories are independent. The
-working directories can be anywhere in your filesystem.</p>
-
-<p><em>Please read <a href="#gnupackages">Web pages for official GNU
-software</a> before committing anything to the web repository of a
-software project.</em></p>
-</li>
-
-<li>
-<p>Add a file or directory:</p>
-
-<pre class="emph-box">
-cvs add foo
-</pre>
-</li>
-
-<li>
-<p>Update before you edit a file:</p>
-
-<pre class="emph-box">
-cvs update -P foo
-</pre>
-</li>
-
-<li>
-<p>Check the changes you are going to commit:</p>
-
-<pre class="emph-box">
-cvs diff -U2 foo
-</pre>
-</li>
-
-<li>
-<p>Perform the commit:</p>
-
-<pre class="emph-box">
-cvs commit foo
-</pre>
-
-<p>This will open a text editor where you should enter a log message. The
-commit will occur upon saving the message.</p>
-
-<p>Without being excessively verbose, log messages should describe
-as clearly as possible the nature of the commit, including any related
-ticket numbers from RT to allow future historians to understand why your
-changes were made.</p>
-
-<p>Whenever possible, changes to multiple files that share the same log
-message should be bundled in one commit. Do not bundle multiple unrelated
-changes in one commit.</p>
-
-<p>The changes (except to <a href="#symlinks">.symlinks files</a>) should
-be visible on www.gnu.org within minutes.</p>
-</li>
-</ul>
-
-<p>For further details on CVS, such as reverting to a previous version, or
-looking at the <code>diff</code> output of a particular change, see the <a
-href="//www.gnu.org/software/trans-coord/manual/cvs/">
-CVS documentation</a>.</p>
-
-
-<h4 id="scripts">Scripts</h4>
-
-<p>A <a href="/server/source/source.html">description of scripts and
-software</a> used on www.gnu.org is available. Please read it before
-writing any scripts, and also update it as needed.</p>
-
+an image isn't <a
+href="/server/standards/gnu-website-guidelines#pollinking">something
+we'd link to</a>, for example, then it isn't something we should give
+permission for. Feel free to discuss any requests on www-discuss before
+responding to them.</p>
-<h4 id="symlinks">Symbolic links</h4>
-<p>Since CVS is not able to handle symbolic links directly, a separate
-mechanism has been implemented to allow webmasters to maintain symbolic
-links, as follows. (Actual symbolic links are no longer created on
-www.gnu.org; mod_rewrite rules are used instead. But we'll
-keep this discussion talking about symlinks since it is easier to
-understand that way.)</p>
+<h4 id="add-image">Adding an image to the GNU Gallery</h4>
-<p>Being a symlink means that relative links from the linked page
-may break when the symlink jumps to a different directory.</p>
-
-<p>Special files, named <code>.symlinks</code>, when committed
-to the CVS tree, are interpreted as specifications to build
-symbolic links.
-Each symbolic link specification from the .symlinks file is honored,
-i.e., the symbolic link is created if it does not exist yet. If a
-symbolic link is found in the directory and is not listed in the
-.symlinks file, it is removed.</p>
-
-<p>The .symlinks files obey the <code>ln -s</code> format, as described
below:</p>
-
-<ul>
-<li>Lines starting with a sharp sign (“#”) are ignored.</li>
-
-<li>Lines that do not contain two strings separated by white space are silently
-ignored.</li>
-</ul>
-
-<p>Here is an example of a .symlinks file:</p>
-
-<pre class="emph-box">
-# Make a link named l.html to a target t.html.
-# Strictly equivalent to ln -s t.html l.html:
-t.html l.html
-</pre>
-
-<p>On each line the first file name must be a relative path name to an
-existing file. The second file name may not contain any slash; it is the
-name of the symbolic link to be created in the present directory. For
-instance, if a page named <code>DIR.html</code> exists in the
-<code>/DIR</code> directory, and <code>index.html</code> does not exist,
-<code>/DIR/.symlinks</code> should contain a line like this:</p>
-
-<pre class="emph-box">
-DIR.html index.html
-</pre>
-
-<p>The <code>ln -s</code> analogy accounts for only part of the story.
-The current method actually takes advantage of the flexibility of URL
-rewriting. Thus a single HTML entry in the .symlinks file defines links
-to all possible translations that follow our <a
-href="/server/fsf-html-style-sheet.html#NamingTranslations">naming
-conventions</a>. This makes it impossible to use
-symlinks to redirect to and from HTML files whose names look like
-translations, that is, <code>page.<var>LL</var>.html</code> or
-<code>page.<var>LL-CC</var>.html</code>, where LL and CC are two-letter
-codes. When you need such redirections, use the <a
-href="#htaccess">htaccess mechanism</a>.</p>
-
-<p>These days, the .symlinks handling happens on www.gnu.org
-via a cron job that runs twice an hour. Webmasters do not have
-access to it.</p>
-
-
-<h4 id="htaccess">.htaccess and redirections</h4>
-
-<p>To browsers, the symbolic links in the previous section are
-indistinguishable from the actual file. You may want an actual
-redirection in some cases. You can do this either in the top-level
-control file <code>.htaccess</code>, or by using something like this as the
-file to be redirected:</p>
-
-<p class="emph-box"><code>
-<meta http-equiv="refresh" content="0;
- url=http://www.gnu.org/target">
-</code></p>
-
-
-<h4 id="sysadmins">System administrators</h4>
-
-<p>The system administrators for GNU change from time to time. Please
-email the sysadmin list <address@hidden> rather than an individual,
-unless you have a specific reason to do so.</p>
-
-
-<h3 id="readme">More README pages</h3>
+<ol>
+<li>When someone offers an image to GNU, first find out from the author
+which license it is released under, and check that this is a suitable <a
+href="/licenses/license-list.html#OtherLicenses">free license</a>. If the
+new image is a derivative of another one, make sure its license is
+compatible with at least one of the license(s) the parent image was
+released under. If in doubt, ask on www-discuss.</li>
+
+<li>Check that rendering is adequate at the original size, using the
+browser's default font size, for at least one of the versions provided by
+the author. If not, create a new version for display.</li>
+
+<li>Try to compress any large PNG files (several hundred kB), for instance
+with OptiPNG.</li>
+
+<li>Install the image file(s) in the <code>/graphics/</code> directory, but
+do not install very large ones (2MB or more) unless absolutely necessary;
+instead, ask the author to upload them to a user-respecting hosting
+facility, e.g. <a
+href="https://goblinrefuge.com/";>Goblin Refuge</a>, <a
+href="https://framadrive.org/";>Framadrive</a>, <a
+href="https://archive.org/";>Internet Archive</a>, etc.</li>
+
+<li>Create a 80x80px thumbnail in the <code>/graphics/icons/</code>
+subdirectory; this can be done conveniently with <code>mogrify</code>. To
+create a thumbnail for <code>arantxa-glitch.jpg</code>, for example, you
+would run:
+
+<pre class="emph-box">mogrify -resize 80x80 -background white -gravity center \
+-extent 80x80 -format png -path icons arantxa-glitch.jpg \
+&& mv icons/arantxa-glitch.png icons/arantxa-glitch.80.png</pre></li>
+
+<li>Create a new web page in <code>/graphics/</code>, clearly stating the
+copyright and license(s) of the image. If this is a derivative work, provide
+a link (or at least a reference) to the image it is derived from.</li>
+
+<li>Choose one or several keywords which will be used to select the new page
+in the <a href="/graphics/graphics.html">main menu</a>. Currently we have
+the following keywords (check the selection form to know what each one
+covers):
+<p class="emph-box"><code><em>Themes:</em> gnuhead, gnu, tux, rms, emacs, fs,
+license, drm, surveillance.<br />
+<em>Types:</em> ascii, banner, button, icon, cartoon, plastic, logo, poster,
+svg, wallpaper.</code></p>
+Feel free to add more as needed, but don't forget to update the selection
+form if you do.</li>
+
+<li>Add entries for the new page in the <a href="/graphics/graphics.html">
+main menu</a>. The most convenient way to do this is to duplicate one of the
+entries, and replace the keywords, links, page title and author by those of
+the new page. This is what the <code>arantxa.html</code> entry looks like:
+
+<pre class="emph-box"> <!--#if expr="$THEME = /^(gnuhead|)$/
+ && $TYPE = /^(banner|logo|)$/" -->
+<tr><td><a href="/graphics/arantxa.html">
+ <img src="/graphics/icons/arantxa-glitch.80.png" alt="X"
/></a></td>
+ <td>GNU designs<br />
+ <small>by Arantxa
Serantes</small></td></tr><!--#endif
+-->
+</pre>
+
+Note that the entry starts and ends with SSI directives, and that there is
+a line break within the <code>endif</code> rather than after it, to avoid
+numerous blank lines in the HTML that is served to the user.</li>
+</ol>
-<ul>
- <li>
- The <a href="/server/fsf-html-style-sheet.html">FSF HTML Style
- Sheet</a>
- </li>
- <li>
- <a href="/accessibility/accessibility.html">GNU Accessibility
- Statement</a>
- </li>
- <li>
- Guide to
- <a href="/server/standards/README.translations.html">translating</a>
- GNU web pages into other languages
- </li>
- <li>
- Guidelines for
- <a href="/server/standards/README.editors.html">Web Page Creation</a>
- at www.gnu.org
- </li>
- <li>
- <a href="//savannah.gnu.org/maintenance/FrontPage/">Documentation for
- Savannah</a>, the SourceForge clone dedicated to the GNU Project.
- </li>
- <li>
- Here is the <a href="/server/tasks.html">help</a>
- we need with our <a href="/server/server.html">web server</a>
- </li>
- <li>
- <a
href="//cvs.savannah.gnu.org/viewvc/gnumaint/README?root=womb&view=markup">
- README</a> for the <code>/gnumaint</code> directory in the
<code>womb</code>
- Savannah group. (Those files are used by <a
- href="/prep/maintain/">GNU maintainer administrators</a> to update
- the <code>/*/allgnupkgs.html</code> files here in www.)
- </li>
- <li>
- <a href="/software/trans-coord/manual/gnun/html_node/Webmaster-Tips.html">
- Tips for webmasters</a> to make translators' job easier.
- </li>
-</ul>
</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
@@ -1299,7 +932,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2018/05/28 15:23:24 $
+$Date: 2018/09/09 10:34:27 $
<!-- timestamp end -->
</p>
</div>
- www/server/standards README.webmastering.html,
Therese Godefroy <=