Point to new issue tracker location and update instructions

merge-requests/1/head
Olaf Meeuwissen 2018-03-20 21:47:09 +09:00
rodzic c9388479eb
commit e62ede1316
2 zmienionych plików z 26 dodań i 65 usunięć

Wyświetl plik

@ -20,86 +20,48 @@
</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>
<h1>SANE - Reporting Bugs</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:
Issues can be used to report bugs or missing features in any of the SANE
Project's components. Please be as specific as possible and add as much
information as possible. Issues can be submitted for
<a href="https://gitlab.com/sane-project/backends/issues/new">sane-backends</a>,
<a href="https://gitlab.com/sane-project/frontends/issues/new">sane-frontends</a>,
and the <a href="https://gitlab.com/sane-project/website/issues/new">website</a>.
Use labels where appropriate. Labels for all backends and frontends are
available (for the component that provides them) as well as more generic
labels. The sane-backends components also has labels to indicate the type
of connection.
</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.
If you are not sure which label(s) to select, simply don't select any.
The SANE project members will add them where appropriate.
</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>
For security related issues, tick the checkbox to mark the issue as
confidential in addition to adding the security label.
</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.
Use attachments for images, screenshots, debug logs and otherwise lengthy
command-line output.
</li>
<li>
<strong>saned</strong>: Bugs concerning the SANE network scanning daemon
with SANE.
If you attach a patch, please also add a patch label.
</li>
<li>
<strong>documentation</strong>: Bugs, missing information, spelling
mistakes in the manual pages, READMEs or other documentation coming
with SANE.
<a href="https://gitlab.com/help/user/search/index.md">Search</a> for similar
issues before reporting a new one. Comment on the existing issue instead or
mention it in the issue you are about to submit.
</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.
Use <a href="https://gitlab.com/help/user/markdown.md">GitLab Flavored
Markdown</a> to make commands tried and their output readable.
</li>
</ul>

Wyświetl plik

@ -24,10 +24,9 @@
<hr>
<p>
If you find any bugs (e.g. spelling errors, missing/wrong links) on this website, please use
<a href="https://alioth.debian.org/tracker/?atid=410366&#38;group_id=30186&#38;func=browse"
target="_top">our bug tracking system</a> with the category "website". For more details, see
<a href="bugs.html">our page about bug-reporting</a>.
If you find any bugs (e.g. spelling errors, missing/wrong/broken links) on this website,
please <a href="https://gitlab.com/sane-project/website/issues/new">submit an issue</a>.
For details, see <a href="bugs.html">our page about submitting issues</a>.
</p>
<p>