[debian-edu-commits] [Debian Wiki] Update of "DebianEdu/HowTo/ReportBugsInBugzilla-es" by WolfgangSchweer

[Debian Wiki]

Dear wiki user,

You have subscribed to a wiki page "Debian Wiki" for change notification.

The page "DebianEdu/HowTo/ReportBugsInBugzilla-es" has been deleted by WolfgangSchweer:

https://wiki.debian.org/DebianEdu/HowTo/ReportBugsInBugzilla-es?action=diff&rev1=1&rev2=2

Comment:
skolelinux bugzilla is gone (has been unused since years)

- = Report bugs in Bugzilla =
  
- (Translated to english from german in Google translator, should be proof read and translated to spanish)
- 
- == Instructions Report: Errors and Opportunities ==
- 
- Like most free software projects, has Debian-Edu/Skolelinux a bug tracking system (in short: BTS). This is a Bugzilla system in version 2.16.4 (Stand 12-2005).
- 
- Free software is free for the most part - but never in vain. By using free software, you are already involved in the development process. Get involved in now so actively in the improvement of Skolelinux by adding errors and desires that stand you in our [[http://bugs.skolelinux.no/|central reporting]] system! We promise you: the knowledge that can earn you the process of transfer to almost all other free software projects? You can also install the Debian package 'bugzilla' on your school server to centrally manage internal network problems.
- 
-   * The address for the Bugzilla from Skolelinux http://bugs.skolelinux.no reads 
- 
- To help you make a start as easily as possible, we will show you the following first steps.
- 
-   * If you prefer to start with dry runs, assists you with the [[http://landfill.bugzilla.org/ |test server of Bugzilla]]. Here you can take first steps. 
- 
- == 1. Bugzilla Account ==
- 
- Open the [[http://bugs.skolelinux.no/createaccount.cgi|New Account]] to create your own Bugzilla account:
- 
- {{http://wiki.skolelinux.de/AnleitungBugzilla?action=AttachFile&do=get&target=slx-bugzilla1.png}}
- 
- 
- Please pay attention initially on a yellow background baseboard, you will see on all Bugzillaseiten. All the use cases presented here (1-4) are marked with red numbers for your information.
- 
- If you do not have an account (the registration and participation is of course free), you enter a valid email address in the first field.  If you wish to be displayed with your error messages even your real name, enter this (or alias) in the second field.
- 
- Now observe your inbox (mailbox). You will receive a confirmation message with further instructions regarding your password.
- 
- == 2. Sign in (Login) ==
- 
- {{http://wiki.skolelinux.de/AnleitungBugzilla?action=AttachFile&do=get&target=slx-bugzilla2.png}}
- 
- 
- To sign up simply enter the email address with which you have registered. The password should be known only to you.
- 
- == 3. Search for existing error messages ==
- 
- This step should always be run before you enter a new bug supposedly a second time.
- 
- {{http://wiki.skolelinux.de/AnleitungBugzilla?action=AttachFile&do=get&target=slx-bugzilla5.png}}
- 
- You should begin this process quite generous in the selection of categories to be searched. There probably is enough for the time being to seek a major keyword in the summary or comment too.
- 
- == 4. Own mistakes or wish to sign ==
- 
- When you have ensured that the error or wish that you want to submit, is a new following, now the fourth step. After clicking on New '(4) takes you to this page:
- 
- {{http://wiki.skolelinux.de/AnleitungBugzilla?action=AttachFile&do=get&target=slx-bugzilla3.png}}
- 
- Select a component "Skolelinux" if it is the software.
- 
- Now, please specify as many as possible into English.
- 
- {{http://wiki.skolelinux.de/AnleitungBugzilla?action=AttachFile&do=get&target=slx-bugzilla4.png}}
- 
- "Severity: Enhancement" (seriously: Improvement) denotes a request or suggestion for improvement. If you have made all the necessary inputs, confirm the data with the help of '''Commit''' (This example is a hypothetical case, Klaber Unfortunately there / not yet).
- 
- 
- '''Congratulations:''' you are now officially one of the active supporters of Skolelinux. The error detector keeps you up to date, the reporting system, if
- 
-   * Comments are attached to your entry;
-   * the problem is resolved or
-   * Your wish is granted;
-   * Be discovered duplicates of your message and marked as such; 
- 
- The allocation of [[http://bugs.skolelinux.no/describecomponents.cgi?product=Skolelinux|components]] is not always clear. You still have no fear of making mistakes (of which lives in Bugzilla!), All allocations are dynamic and can be corrected later. Only the summary, title (Summary) and the description and more comments will remain static in the database.
- 
- == Useful links ==
- 
-     * [[http://bugs.skolelinux.no/buglist.cgi?order=bugs.bug_id | List of all bugs]] in Bugzilla from Skolelinux / Debian-Edu
-     * [[http://bugs.skolelinux.no/reports.cgi?product=Skolelinux&output=show_chart&datasets=NEW%3A&datasets=ASSIGNED%3A&datasets=REOPENED%3A&datasets=UNCONFIRMED%3A&links=1&banner=1&quip=0|Statistics]] (see chart) Open error
-     * [[http://bugs.skolelinux.no/reports.cgi?product=Skolelinux&output=most_doomed&links=1&banner=1&quip=0|Bug Charts]]
-     * [[http://bugs.skolelinux.no/reports.cgi?product=Skolelinux&output=show_chart&datasets=NEW%3A&datasets=FIXED%3A&links=1&banner=1&quip=0|New and fixed bugs]] (graph)
-