sane-project-website/bugs.html

119 wiersze
3.9 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>SANE - Reporting Bugs</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="author" content="Henning Meier-Geinitz">
<meta name="keywords" content="sane, scanner, bug, reporting, feature
request, error, mistake, contact">
<meta name="description" content="Reporting bugs in SANE or the SANE website">
<link href="mailto:hmg-guest@users.alioth.debian.org" rev="made">
<link rel="icon" href="favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="favicon.ico" type="image/x-icon">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<center>
<a href="http://www.sane-project.org"><img src="images/sane.png"
alt="SANE" height="117" width="346" border="0"></a>
</center>
<center>
<h1><a
href="https://alioth.debian.org/tracker/?atid=410366&#38;group_id=30186&#38;func=browse"
target="_top">SANE - Reporting Bugs</a></h1>
</center>
<hr>
<p>
The <a
href="https://alioth.debian.org/tracker/?atid=410366&#38;group_id=30186&#38;func=browse"
target="_top">SANE bug tracker</a> can be used to report bugs or missing
features in sane-backends, sane-frontends or the web pages. Please be as
specific as possible and use an appropriate category. Add as much
information as possible to the report. Have a look at the list of
categories and groups to decide which one to use:
</p>
<h2>Categories</h2>
<ul>
<li>
<strong>None</strong>: If you don't know which category to chose, use
<em>None</em>. One of the SANE developers will select the right
category later.
</li>
<li>
<strong>backends (drivers)</strong>: All bugs concerning the
backends. E.g. if your scans have wrong colors. Please mention the
name of the backend and the manufacturer and name of the
scanner. Example: <em>gt68xx: Artec Ultima 2000 scans are completely
red</em>
</li>
<li>
<strong>scanimage</strong>, <strong>xscanimage</strong>, and
<strong>xcam</strong>: For bugs concerning one of these frontends. To
make sure if it's really a frontend problem, check if the bug happens
only with that frontend.
</li>
<li>
<strong>saned</strong>: Bugs concerning the SANE network scanning daemon
with SANE.
</li>
<li>
<strong>documentation</strong>: Bugs, missing information, spelling
mistakes in the manual pages, READMEs or other documentation coming
with SANE.
</li>
<li>
<strong>website</strong>: Wrong or missing information, spelling
mistakes, and dead links on the SANE website.
</li>
<li>
<strong>sanei</strong>, <strong>porting</strong>, and <strong>sane
standard</strong> are (almost) only relevant for
developers. <em>sanei</em> is used for bugs in the SANE internal
functions. <em>porting</em> is for bugs concerning compilation and
installation of SANE on various platforms. If something should be
changed in our API, <em>sane standard</em> should be used as category.
</li>
<li>
<strong>general</strong>: This category should be used for
bugs/feature requests concerning SANE as a whole.
</li>
</ul>
<h2>Groups</h2>
<ul>
<li>
<strong>None</strong>: Used for most bugs.
</li>
<li>
<strong>wishlist</strong>: If you submit a feature request and not a
bug, use this group.
</li>
<li>
<strong>security</strong>: Bugs that can affect the security of the
system. E.g. buffer overflows in saned or temporary file issues.
</li>
<li>
<strong>standard-compliance</strong>: If a backend or frontend fails
to comply with the SANE standard.
</li>
</ul>
<hr>
<p>
<a href="/">SANE homepage</a><br>
<a href="imprint.html">Contact</a>
</p>
<p>
<font size="-1">$Date$ $Author$</font>
</p>
</body>
</html>