mirror of
https://github.com/GnoConsortium/gno.git
synced 2024-09-27 12:55:35 +00:00
bugs.html, index.html, Makefile:
- added interface to bug reporting system related.html: - added reference to the "Cathedral and the Bazaar" paper. - added link to Byte Works' page.
This commit is contained in:
parent
923ca66cd6
commit
95aaac5172
@ -7,7 +7,7 @@
|
||||
#
|
||||
# Devin Reade, 1997.
|
||||
#
|
||||
# $Id: Makefile,v 1.8 1998/02/19 03:03:48 gdr-ftp Exp $
|
||||
# $Id: Makefile,v 1.9 1998/03/15 00:36:33 gdr-ftp Exp $
|
||||
#
|
||||
|
||||
# Set this to 'true' (without the quotes) for local links (used
|
||||
@ -118,6 +118,7 @@ h: $(HTML) \
|
||||
$(HTMLD)/manindex.html \
|
||||
$(HTMLD)/related.html \
|
||||
$(HTMLD)/oldrefs.html \
|
||||
$(HTMLD)/bugs.html \
|
||||
$(HTMLD)/unaval.html top.html cleanhtml
|
||||
bib: intro.bbl
|
||||
|
||||
@ -186,6 +187,13 @@ $(HTMLD)/related.html: related.html
|
||||
-e 's,%%TITLE%%,GNO-Related Web Pages,;' > $@
|
||||
$(HTMLD)/related.html: head.html tail.html
|
||||
|
||||
$(HTMLD)/bugs.html: bugs.html
|
||||
@echo "making $@"; \
|
||||
[ -d $(HTMLD) ] || mkdir -p $(HTMLD); \
|
||||
cat head.html $< tail.html | $(REPLACE) \
|
||||
-e 's,%%TITLE%%,GNO Bug Reports,;' > $@
|
||||
$(HTMLD)/bugs.html: head.html tail.html
|
||||
|
||||
$(HTMLD)/oldrefs.html: oldrefs.html
|
||||
@echo "making $@"; \
|
||||
[ -d $(HTMLD) ] || mkdir -p $(HTMLD); \
|
||||
|
105
doc/refs/bugs.html
Normal file
105
doc/refs/bugs.html
Normal file
@ -0,0 +1,105 @@
|
||||
<H1>GNO Bug Reports</H1>
|
||||
<hr>
|
||||
|
||||
A critical part of GNO development is user feedback. What works
|
||||
well? What needs improvement? What is broken?
|
||||
By telling GNO developers this information, you are <em>much</em>
|
||||
more likely to see improvements.
|
||||
<p>
|
||||
|
||||
The traditional method of sending in bug reports is to email the
|
||||
developer. While this mechanism is simple, it has a few drawbacks:
|
||||
<ul>
|
||||
<li>Sometimes the original author has moved or is otherwise no longer around,
|
||||
making it impossible (or at least difficult) to submit bug reports.
|
||||
<li>Only the author sees the report. Consequently nobody else knows of
|
||||
the problem, which can result in unnecessary frusteration and
|
||||
wasted time for other users.
|
||||
</ul>
|
||||
|
||||
The GNO Consortium now provides a common bug reporting and tracking system.
|
||||
While it is primarily intended for bug reports on the GNO base distribution,
|
||||
reports are also welcome on programs that are not part of the base
|
||||
distribution (but that still run under GNO). This system is accessible
|
||||
both though the web and through email.
|
||||
|
||||
<hr>
|
||||
<H3>Bug Reports -- Web Access</H3>
|
||||
|
||||
The recommended way to submit GNO bug reports is to use the web-based
|
||||
bug reporting package. There are two ways to access this system:
|
||||
<ul>
|
||||
<li><A HREF="http://www.gno.org/cgi-bin/gnobugs">Guest Access</A>.
|
||||
This will allow you to submit, update, and view problem
|
||||
reports, but not perform any other operations.
|
||||
<li><A HREF="http://www.gno.org/cgi-bin/secure/gnobugs">Developer Access</A>.
|
||||
This allows full access to the problem report system, but
|
||||
is restricted to a small number of "core" developers.
|
||||
If you feel you should have developer access, you should send
|
||||
email to
|
||||
<A HREF="mailto:gno-bugs-admin@trenco.gno.org">
|
||||
gno-bugs-admin@trenco.gno.org</A>.
|
||||
Please do not feel insulted if you are not granted access.
|
||||
</ul>
|
||||
Note that this reporting system is accessible from Lynx, but is more
|
||||
readable using a graphical browser. This is unfortunate, but fixing
|
||||
this problem will require modifications to the bug tracking software
|
||||
itself. This will be addressed when time permits.
|
||||
|
||||
<hr>
|
||||
<H3>Bug Reports -- Email Access</H3>
|
||||
|
||||
If you prefer to send your bug reports via regular email, you can
|
||||
send them to
|
||||
<A HREF="mailto:gno-bugs@trenco.gno.org">gno-bugs@trenco.gno.org</A>.
|
||||
If you do this method, please ensure that your subject line contains
|
||||
a concise description of the problem, such as
|
||||
<pre>
|
||||
open(2) doesn't set errno
|
||||
or
|
||||
rm broken for HFS volumes
|
||||
</pre>
|
||||
<p>
|
||||
|
||||
When sending your bug reports in email, please also include the following
|
||||
information, in addition to your informative subject line:
|
||||
<ul>
|
||||
<li>With which distribution did you observe the problem? It should be
|
||||
one of the following:
|
||||
<ul>
|
||||
<li> the base 2.0.4 distribution
|
||||
<li> the v2.0.4 kernel with v2.0.6 libraries
|
||||
<li> beta 2.0.6
|
||||
</ul>
|
||||
<li>Which component is affected? It should be one of the following:
|
||||
<ul>
|
||||
<li>Documentation
|
||||
<li>Utilities
|
||||
<li>The GNO Shell
|
||||
<li>The Kernel
|
||||
<li>Libraries and Header Files
|
||||
<li>other
|
||||
</ul>
|
||||
<li>If you are reporting a problem with a utility or library routine,
|
||||
include the name of the utility (or routine). If it's available,
|
||||
also quote the version. This is often given as an rVersion
|
||||
resource on programs and libraries.
|
||||
<li>Give a clear description of the problem. If possible, include
|
||||
precise instructions on how to reproduce the problem.
|
||||
<li>If your problem is with a library routine, give a <em>short</em>
|
||||
program which exhibits the problem.
|
||||
<li>If your program is longer
|
||||
than one hundred or so, then you can upload the program to
|
||||
<b>ftp://ftp.gno.org/incoming</b>, preferably as a NuFX (Shrinkit)
|
||||
archive. Please include a brief description with your upload.
|
||||
The description can either be included in the NuFX archive or
|
||||
uploaded as a separate text file.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
Note that bug reports to the above address will go straight into
|
||||
the reporting system. If your bug report contains proprietary information,
|
||||
you should send it to
|
||||
<A HREF="mailto:gno-bugs-admin@trenco.gno.org">
|
||||
gno-bugs-admin@trenco.gno.org</A>
|
||||
<p>
|
@ -22,6 +22,7 @@ It consists of the following sections:
|
||||
<li><A HREF="%%HTML_ROOT%%/faqindex.html">Frequently Asked Questions</A>
|
||||
<li><A HREF="%%HTML_ROOT%%/refs.html">Reference Manuals</A>
|
||||
<li><A HREF="%%HTML_ROOT%%/manindex.html">Manual Pages</A>
|
||||
<li><A HREF="%%HTML_ROOT%%/bugs.html">Bug Reports</A>
|
||||
<li><A HREF="%%HTML_ROOT%%/related.html">GNO-Related Web Links</A>
|
||||
<li><A HREF="%%HTML_ROOT%%/oldrefs.html">Old Documentation (August 1996 Revision for GNO v2.0.4)</A>
|
||||
</ol>
|
||||
|
@ -10,6 +10,8 @@ and programmers.
|
||||
and from where they can be obtained.
|
||||
<li><A HREF="http://www.hypermall.com/companies/procyon">
|
||||
Procyon Enterprises Inc</A>
|
||||
<li><A HREF="http://www.hypermall.com/byteworks">The Byte Works</A>,
|
||||
creators of ORCA/C, ORCA/M, and other programming tools.
|
||||
<li>Soenke Behrens' <A HREF="http://www.arrowweb.com/sbehrens/obugs.htm">
|
||||
ORCA/C Bug List</A>
|
||||
<li>Leslie Barstow's
|
||||
@ -27,9 +29,20 @@ and programmers.
|
||||
</ul>
|
||||
<p>
|
||||
|
||||
The following links have a less direct relevence to GNO, but may still
|
||||
The following links have a less direct relevance to GNO, but may still
|
||||
be useful:
|
||||
<ul>
|
||||
<li><A HREF="http://earthspace.net/~esr/writings/cathedral-paper.html">
|
||||
The Cathedral and the Bazaar</A>
|
||||
by Eric S. Raymond.
|
||||
This paper discusses differences between two software engineering
|
||||
strategies: The traditional development / testing / release
|
||||
cycle and the high turn-around cycle typified by Linux and
|
||||
one of the author's own projects, <b>fetchmail</b>.
|
||||
This paper is valuable as "food for thought" for anyone
|
||||
considering working on GNO or any other large projects for the
|
||||
Apple II.<p>
|
||||
|
||||
<li>The <A HREF="http://www.pathname.com/fhs">File System Hierarchy</A>
|
||||
"standard". This is not a true standard in the ANSI/ISO
|
||||
sense, but still contains a lot of useful information.
|
||||
|
Loading…
Reference in New Issue
Block a user