[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards README.webmastering.html
From: |
Dora Scilipoti |
Subject: |
www/server/standards README.webmastering.html |
Date: |
Thu, 01 Jan 2015 10:26:00 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Dora Scilipoti <dora> 15/01/01 10:26:00
Modified files:
server/standards: README.webmastering.html
Log message:
Validate, restructure and link to Thank GNU section. Delete old method
for audio-video, explain current procedures. Other validation fixes.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.173&r2=1.174
Patches:
Index: README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.173
retrieving revision 1.174
diff -u -b -r1.173 -r1.174
--- README.webmastering.html 18 Oct 2014 20:52:05 -0000 1.173
+++ README.webmastering.html 1 Jan 2015 10:26:00 -0000 1.174
@@ -25,6 +25,7 @@
<a href="#announcements">Announcements</a> -
<a href="#pollinking">Linking policies</a> -
<a href="#mirrors">Mirrors</a> -
+<a href="#thankgnu">Thank GNU</a> -
<a href="#commonreq">Handling common requests</a> -
<a href="#repo">Working with our repositories</a> -
<a href="#readme">More README pages</a>.
@@ -186,30 +187,8 @@
maintain, go ahead and fix it, using ‘Reply’ to tell the
submitter what you did, and then ‘Resolve’ it.</li>
-<li id="thankgnu">If the message is a ThankGNU or a ThankCRM:
- <ul>
- <li>For a corporation, confirm with www-discuss first (they can end
- up on separate pages).</li>
- <li>If any of the donors are already on the list, then mention that
- in an RT comment. The script sending out the messages has bugs. The
- occasional case of a person donating the same amount twice is
- handled by FSF staff.</li>
- <li>For an individual, add it to the
- appropriate <tt>/thankgnus/YYYYsupporters.html</tt> file in the
- correct place with a commit message such as "Add John Doe to YYYY >=
- 500$ ThankGNU list (RT #1234)" and comment the ticket with something
- simple like "Done".</li>
- <li>Finally, move the ticket into the 'campaigns' queue.</li>
- <li>Things to watch out for:</li>
- <ul>
- <li>Do not quote the dollar amount in the commit message or
- anywhere else, just the name, ticket number and category.</li>
- <li>Do not ‘Reply’ to sysadmin on these messages; they
- are automatically generated.</li>
- <li>Do not post a ThankGNU for Google Matching Gifts.</li>
- </ul>
- </ul>
-</li>
+<li>If the message is a ThankGNU or a ThankCRM see the
+<a href="#thankgnu">Thank GNU procedure</a>.</li>
<li>If the message is about making a link on one of our pages, see
<a href="#pollinking">linking procedures and information</a>.</li>
@@ -235,7 +214,6 @@
sysadmin or licensing, move it to the corresponding queue or otherwise
forward it. <a href="#rtmisdirected">Specific directions for
redirecting tickets</a>.</li>
-
</ul>
<h4>RT - correspondence vs. comments</h4>
@@ -311,7 +289,7 @@
you're primarily doing work by e-mail, however.</p>
<p>Note that this won't work with other RT-handled addresses. So, if
-you add <address@hidden&rt; to the CC field of a comment on a
+you add <address@hidden> to the CC field of a comment on a
ticket that already exists in webmasters, nothing will come to the
campaigns queue. In those situations, create a new ticket in the
queue whose attention you want to get, and using the “Refers
@@ -822,6 +800,38 @@
informed. This requires hand-assembling a list of addresses from the
<tt>FTP.contacts</tt> file based on the current mirror list.</p>
+<h3 id="thankgnu">Thank GNU</h3>
+
+<ul>
+ <li>For a corporation, confirm with www-discuss first (they can end
+ up on separate pages).</li>
+
+ <li>If any of the donors are already on the list, then mention that
+ in an RT comment. The script sending out the messages has bugs. The
+ occasional case of a person donating the same amount twice is
+ handled by FSF staff.</li>
+
+ <li>For an individual, add it to the
+ appropriate <tt>/thankgnus/YYYYsupporters.html</tt> file in the
+ correct place with a commit message such as "Add John Doe to YYYY >=
+ 500$ ThankGNU list (RT #1234)" and comment the ticket with something
+ simple like "Done".</li>
+
+ <li>Finally, move the ticket into the 'campaigns' queue.</li>
+</ul>
+
+<p>Things to watch out for:</p>
+
+<ul>
+ <li>Do not quote the dollar amount in the commit message or
+ anywhere else, just the name, ticket number and category.</li>
+
+ <li>Do not ‘Reply’ to sysadmin on these messages; they
+ are automatically generated.</li>
+
+ <li>Do not post a ThankGNU for Google Matching Gifts.</li>
+</ul>
+
<h3 id="commonreq">Handling common requests</h3>
@@ -1002,6 +1012,8 @@
<h3 id="repo">Working with webmaster-related repositories</h3>
+<ul>
+<li>
<p><i>Main www repository:</i>To make an initial checkout, set the
environment variable CVS_RSH=ssh, and run</p>
@@ -1025,59 +1037,26 @@
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
+<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>
+</li>
+<li>
<p><i>audio-video repository:</i> Use <tt>audio-video</tt> instead of
<tt>www</tt> and you will get the repository corresponding to <a
href="http://audio-video.gnu.org">audio-video.gnu.org</a>. Discuss
any changes to audio-video with address@hidden</p>
-<p><strong>Note</strong>: all materials in the current audio-video
-repository will eventually be migrated to <a
-href="http://audio-video-dev.gnu.org">audio-video-dev.gnu.org</a>. To
-post a file in this new website, first you need to be added as a user
-with admin permissions; talk to the Chief-Webmaster for this. Then
-follow these steps:</p>
-
-<ul>
- <li><p>Upload the file to a dedicated directory in your home in Fencepost:
-<tt> rsync -avz --progress your-media-file
<username>@fencepost.gnu.org:~/your-dedicated-dir/</tt>
- Add also a text file named <tt>your-media-file.txt</tt> with a short
- description, for example:</p>
-
- <pre>
- Title: Free Software in Ethics and in Practice
- Location: Manchester, UK
- Date: 2008
- In this ninety-minutes speech Richard Stallman talks about the goals
- and philosophy of the Free Software movement, and the status and
- history of the GNU operating system.
- </pre>
-
- <p>You can find descriptions of RMS' speeches in the
- <a href="http://www.fsf.org/events/rms-speeches.html">FSF website</a>.</p>
- </li>
-
- <li> <p>Login to your Fencepost account and, from there, copy the file
-you just uploaded onto the audio-video-dev machine under
-/var/www/audio-incoming or /var/www/video-incoming as appropriate:
-<tt>rsync -avz your-video-file
<username>@audio-video-dev:/var/www/video-incoming/</tt></p>
- </li>
-
- <li><p>Login to the <a
-href="http://audio-video-dev.gnu.org">audio-video-dev.gnu.org</a> website.
-Enter the Admin interface. Whether you want to submit a video or an audio
-file, go to Videos > Submit a Video > enter URL:
-<tt>http://audio-video-dev.gnu.org/static-video/your-video-file.ogv</tt>.
-Replace <tt>static-video</tt> with <tt>static-audio</tt> if you are
-submitting an audio file.</p>
- </li>
-
- <li>Add a thumbnail, add and edit descriptions as needed.</li>
-</ul>
+<p>The task of adding material to this repository is currently being handled
by
+the <a href="https://savannah.gnu.org/projects/audio-video/">GNU and FSF
+audio and video group in Savannah</a>, so when we get a request to add a
+video or audio file, we should either submit a new task there or forward
+the request to their mailing list at
+<a href="mailto:address@hidden"><address@hidden></a>.</p>
+</li>
+<li>
<p><i>Other packages:</i> Many software packages have their own projects
on Savannah and hence their own web repository corresponding to their
www/software/fooproject directory. If the maintainer needs your help
@@ -1089,6 +1068,8 @@
<p>Do not edit the web pages for software projects unless the maintainer
says ok. At the very least, inform them if you make a change.</p>
+</li>
+</ul>
<h4 id="scripts">Scripts</h4>
@@ -1269,7 +1250,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2014/10/18 20:52:05 $
+$Date: 2015/01/01 10:26:00 $
<!-- timestamp end -->
</p>
</div>
- www/server/standards README.webmastering.html,
Dora Scilipoti <=
- www/server/standards README.webmastering.html, Dora Scilipoti, 2015/01/01
- www/server/standards README.webmastering.html, Dora Scilipoti, 2015/01/03
- www/server/standards README.webmastering.html, Quentin Pradet, 2015/01/06
- www/server/standards README.webmastering.html, Dora Scilipoti, 2015/01/17
- www/server/standards README.webmastering.html, Quentin Pradet, 2015/01/26
- www/server/standards README.webmastering.html, Quentin Pradet, 2015/01/27