[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www help/evaluation.html evaluation/evaluation....
From: |
Karl Berry |
Subject: |
www help/evaluation.html evaluation/evaluation.... |
Date: |
Thu, 16 Aug 2007 19:04:55 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Karl Berry <karl> 07/08/16 19:04:55
Modified files:
help : evaluation.html
Removed files:
evaluation : evaluation.html
Log message:
evaluation.html was moved to help/ long ago, remove obsolete version
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/help/evaluation.html?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/evaluation/evaluation.html?cvsroot=www&r1=1.14&r2=0
Patches:
Index: help/evaluation.html
===================================================================
RCS file: /web/www/www/help/evaluation.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- help/evaluation.html 19 Jun 2007 00:03:35 -0000 1.9
+++ help/evaluation.html 16 Aug 2007 19:04:44 -0000 1.10
@@ -241,13 +241,13 @@
<h3><a name="eval" id="eval">Helping evaluate software for GNU</a></h3>
-<p>We can always use additional volunteers to commit to helping evaluate
-the software we are offered through the procedures above. Timeliness is
-of the utmost importance in doing an evaluation. The main goal of doing
-the evaluations is not to be an expert in the field (a common
-misconception), but to get a general understanding of the program on the
-one hand, and how it meets certain very specific criteria on the other
-(we use a standard form to guide evaluations).</p>
+<p>From time to time, we can use additional volunteers to commit to
+helping evaluate the software we are offered through the procedures
+above. Timeliness is of the utmost importance in doing an evaluation.
+The main goal of doing the evaluations is not to be an expert in the
+field (a common misconception), but to get a general understanding of
+the program on the one hand, and how it meets certain very specific
+criteria on the other (we use a standard form to guide evaluations).</p>
<p>It is also not critical to be a systems expert. Many packages are
offered in a state that is too difficult to compile, let alone run.
@@ -317,7 +317,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2007/06/19 00:03:35 $ $Author: karl $
+$Date: 2007/08/16 19:04:44 $ $Author: karl $
<!-- timestamp end -->
</p>
</div>
Index: evaluation/evaluation.html
===================================================================
RCS file: evaluation/evaluation.html
diff -N evaluation/evaluation.html
--- evaluation/evaluation.html 20 Oct 2005 21:32:04 -0000 1.14
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,324 +0,0 @@
-<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
-<html><head>
-
-<title>GNU Software Evaluation Team - GNU Project - Free Software Foundation
(FSF)</title><link rev="made" href="mailto:address@hidden"></head>
-
-<body alink="#ff0000" bgcolor="#ffffff" link="#1f00ff" text="#000000"
vlink="#9900dd">
-<h3>GNU Software Evaluation Team</h3>
-<a href="/graphics/agnuhead.html"><img src="evaluation_files/gnu-head-sm.jpg"
alt=" [image of the Head of a GNU] " height="122" width="129"></a>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- Please UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
- <a href="/evaluation/evaluation.html">English</a>
-<!-- | A HREF="/boilerplate.LG.html" LANGUAGE /A -->
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<p>
-
-</p><h4>Table of Contents</h4>
-<ul>
- <li><a href="#whatmeans" name="TOCwhatmeans">What it means for a
- program to be GNU software</a>
- </li><li><a href="#evaluationoutline" name="TOCevaluationoutline">Outline
- for Evaluations</a>
- </li><li><a href="#skills" name="TOCskills">Skills that will help this team
-reach its goals</a>
-</li></ul>
-
-<p>
-</p><hr>
-<p>
-</p><h4><a href="#TOCwhatmeans" name="whatmeans">What it means for a
- program to be GNU software</a></h4>
-
-<p>Before understanding what "GNU Software" is, it is important to
-understand the goals of the GNU project, those goals can be found at:
-<a href="/gnu/thegnuproject.html">http://www.gnu.org/gnu/thegnuproject.html</a>
-</p>
-
-<p>Here's an explanation from RMS of what it means for a program to be
-GNU software:</p>
-
-<blockquote>
-
- <p>Calling a program GNU software means that its developers and
- the GNU project agree that "This program is part of the GNU
- project, released under the aegis of GNU"-and say so in the
- program.</p>
-
- <p>This means that we normally put the program on ftp.gnu.org
- (although we could instead refer to the developer's choice of ftp
- site) and that we put the official pages describing the program
- on the GNU web server. (It is ok to have more informal pages
- about secondary issues, such as discussion meant for people who
- want to help develop the package, on some other site.)</p>
-
- <p>It means that the developers agree to pay some attention to
- making the program work well with the rest of the GNU system-and
- conversely that the GNU project will encourage other GNU
- maintainers to pay some attention to making their programs fit in
- well with it.</p>
-
- <p>Just what it means to make programs work well together is
- mainly a practical matter that depends on what the program does.
- But there are a few general principles. Certain parts of the GNU
- coding standards directly affect the consistency of the whole
- system. These include the standards for configuring and building
- a program, and the standards for command-line options. It is
- important to make all GNU programs follow these standards, where
- they are applicable.</p>
-
- <p>Another important GNU standard is that GNU programs should
- come with documentation in Texinfo format. That is the GNU
- standard documentation format, and it can be converted
- automatically into various other formats.</p>
-
- <p>A GNU program should not recommend use of any non-free
- program, and it should not refer the user to any non-free
- documentation for free software. The need for free documentation
- to go with free software is now a major focus of the GNU project;
- to show that we are serious about the need for free
- documentation, we must not contradict our position by
- recommending use of documentation that isn't free.</p>
-
- <p>Occasionally there are issues of terminology which are
- important for the success of the GNU project as a whole. So we
- ask maintainers of GNU programs to follow them. For example, the
- documentation files and comments in the program should speak of
- Linux-based GNU systems or GNU/Linux systems, rather than calling
- the whole system "Linux", and should use the term "free software"
- rather than "open source".</p>
-
- <p>Deciding that a program is GNU software does not necessarily
- require transferring copyright to the FSF; that is a separate
- question. If you transfer the copyright to the FSF, the FSF will
- enforce the GPL for the program if someone violates it; if you
- keep the copyright, enforcement will be up to you.</p>
-</blockquote>
-<p>
-
-</p><hr>
-
-<p>
-</p><h4><a href="#TOCevaluationoutline" name="evaluationoutline">Outline
- for Evaluations</a></h4>
-<p>
-</p>
-
-<br>
-
-<pre>GNU Software Evaluation - Outline for Evaluations
--------------------------------------------------
-
-* General Information
-
-** Package name and version:
-
-** Author <email>:
-
-** Requested by:
-
-** Message-ID:
-
-** Should the authors(s) be contacted? (Y/N)
-
-** Was this package offered by the author to become a GNU program? (Y/N)
-
-** Homepage:
-
-** Source:
-
-** Description provided by author:
-
-** Evaluator:
-
-** Describe in your own words what job or jobs this program does:
-
-* Package specifics
-
-** Binaries available? (Y/N)
-
-** GNU/Linux support? (Y/N)
-
-** License: (specify type - any problems?)
-
-** Dependencies: (ok/problematic + notes)
-
-** Configuration:
- GNU standards compliant?
- It might or might not use Autoconf/Automake, but it should meet GNU
- Standards.
-
-** Compilation:
- GNU standards compliant?
- It might or might not use Autoconf/Automake, but it should meet GNU
- Standards.
-
-** Usability/interface: (ok/problematic + notes)
- This is a very important issue.
- (For a C++ library, one important issue is, can it be used from C?)
-
-** What language(s) is/are the package written in?
-
-
-** Code
-
-*** Clarity/maintenance: (ok/problematic + notes)
- Skim a few header files and a few source files. Can you
- understand each part, at least in the large, from the comments there?.
-
-*** Does it meet GNU Coding Standards?
- The GNU Coding Standards apply to all software packages. To be
- sure, there are some parts which may not apply for certain
- languages--the indentation recommended there is specially for C,
- for instance--but there are some parts that always apply. The
- configure, makefile, and command line specs are among the parts
- that always apply.
-
- If not, please itemize the specific aspects that don't meet them.
-
-
-** Performance: (ok/problematic + notes)
-
-** Documentation
-
-*** Does the package include a good introduction or tutorial manual?
-
-*** Does the package include a good reference manual?
- (The introduction or tutorial can be the reference manual as well,
- as long as it does both jobs well. We think it is good to do both
- jobs with one manual.)
-
-*** Is the main documentation written in Texinfo?
- (Ideally it would be, or at least be convertible into Texinfo.)
-
-** Does the program recommend or encourage the use of any non-free software?
-
-** Does it have certain capabilities that can only be used in
- conjunction with some non-free software package?
-
-
-* Evaluation summary
-
-** Does the program fit coherently within the GNU system?
-
-** Does the program meet necessary requirements for being a GNU package?
- If not, what changes can be feasibly implemented by the author in
- order for the program to be acceptable?
-
-
-** Are there any licensing issues that need to be resolved?
-
-** Is there a large overlap with some other GNU package?
- An overlap is when two programs have substantial functionality in
- common, but neither one entirely subsumes the other. (Such overlap
- is undesirable.)
-
-** Does the program have any gratuitous incompatibilities with other
- GNU packages?
-
- (For example, a program for searching files in a new way should
- support all the options of grep, except for those that don't make
- sense in this program, so as to attain maximum compatibility
- between the two programs. For such a program, any grep option
- which would make sense but is not supported is a gratuitous
- incompatibility.)
-
-
-* Notes and comments during the evaluation process:
-
-
-* Status: (open | working | hold | closed)
-
-** Activity Log:
-
-</email></pre>
-
-
-<p></p>
-
-<hr>
-
-<h4><a href="#TOCskills" name="skills">Skills that will help this team
-reach its goals</a></h4>
-
- <p>This team performs a technical and strategic function for the
- GNU Project, it helps determine what software fits into the GNU
- System.</p>
-
- <p>These are some of the skills that help to accomplish this
- task:</p>
-
- <ul>
- <li>Understanding and support for the goals of the GNU
- Project.</li>
-
- <li>Experience building and installing software, specially using
- GNU utilities like gcc, GNU make, etc.</li>
-
- <li>Experience developing software with various programming
- languages, preferably: C, Perl, Lisp, Scheme, Guile.</li>
-
- <li>Years of experience reading and modifying programs, and
- using a wide range of software, so that you have a feel for what
- is possible.</li>
-
- <li>An ability to recognize clear (understandable and
- maintainable) code or unclear code.</li>
-
- <li>An ability to recognize good or bad design in a
- program.</li>
-
- <li>An ability to recognize clear and natural user interfaces
- and APIs.</li>
-
- <li>GNU Evaluators should be very familiar with the GNU Coding
- Standards and the GNU Maintainers Guide.</li>
-
- <li>Understand the difference between the Free Software Movement
- and the Open Source Movement.</li>
- </ul>
-
-
-<hr>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
- <a href="/evaluation/evaluation.html">English</a>
-<!-- | A HREF="/boilerplate.LG.html" LANGUAGE /A -->
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<hr>
-
-<p>
-Return to <a href="/home.html">GNU's home page</a>.
-</p><p>
-
-Please send FSF & GNU inquiries & questions to
-
-<a href="mailto:address@hidden"><em>address@hidden</em></a>.
-There are also <a href="/home.html#ContactInfo">other ways to
-contact</a> the FSF.
-</p><p>
-
-Please send comments on these web pages to
-
-<a href="mailto:address@hidden"><em>address@hidden</em></a>,
-send other questions to
-<a href="mailto:address@hidden"><em>address@hidden</em></a>.
-</p><p>
-Copyright (C) 2001 Free Software Foundation, Inc.,
-59 Temple Place - Suite 330, Boston, MA 02111, USA
-</p><p>
-Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.
-</p><p>
-$Date: 2005/10/20 21:32:04 $ $Author: ppalazon $
-</p><hr>
-</body></html>
\ No newline at end of file
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- www help/evaluation.html evaluation/evaluation....,
Karl Berry <=