#12041 closed defect (worksforme)
don't explain where the user isn't filing bugs to, but where to file bugs agaist trac
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
The page http://trac.edgewall.org/wiki/NewTicket explains (overly) long and broad where the user isn't filing bugs against instead of explaining what possibilites exist to file bugs. I'd say that a shorter version in the form of
Here is the issue tracker for the trac development wiki
Here is the issue tracker for trac software
is completely sufficient for the first lines. Extended explanation what a bug tracker is and what not should go in the section below.
Attachments (0)
Change History (8)
comment:1 by , 9 years ago
follow-up: 3 comment:2 by , 9 years ago
After reading through really everything on the page I still don't know where to report against the trac software…
comment:3 by , 9 years ago
| Milestone: | → unscheduled |
|---|
Replying to anonymous:
After reading through really everything on the page I still don't know where to report against the trac software…
And yet you managed to create this ticket, reporting an issue against Trac.
comment:4 by , 9 years ago
I thought this is the tracker for the "Trac instance used to manage the development of the Trac project itself"? I don't get it, giving up…
comment:5 by , 9 years ago
| Milestone: | unscheduled |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
Replying to krichter@…:
Here is the issue tracker for the trac development wiki
Here is the issue tracker for trac software
That depends what you mean by trac development wiki and trac software. If you are running your own instance of Trac and have discovered a defect or enhancement that you would like to have fixed, this is the place to report it. If you are navigating around this trac site (trac.edgewall.org) and discover some sort of defect or enhancement you would like (e.g. #12042), it should also be reported here. If you have a question or documentation issue, it's best to ask on the MailingList first.
If you wish to file a bug report in some other software that simply uses Trac to manage their software development, you need to find the Trac instance for that software and report it there. It could be something like trac.xyz-software.com. We frequently receive reports about software that have nothing to do with Trac.
But since you are giving up and I honestly can't understand why you are so troubled, I'll close this ticket.
comment:6 by , 9 years ago
Ahhh! Thanks for the clarification (in reply of my demotivating comment)! The description on NewTicket sounds like you're seperating the wiki on trac.edgewall.org from issue about the trac software and I was missing the reference to the issue tracker about the trac software.
Do you mind changing
You are about to file a ticket against the Trac instance used to manage the development of the Trac project itself.
to
You are about to file a ticket against the Trac instance used to manage the development of the Trac project itself or the Trac software.
comment:7 by , 9 years ago
I understand the point you were confused about. Let me give some thought to the rewording before making the change.
comment:8 by , 9 years ago
I made a minor reword in NewTicket@21. You can see from history of the page, in particular the edits in NewTicket@15 and NewTicket@17, that we could spend forever rewording the notice and it's not going to be clear to everyone. I expect that only a few users read the notice anyway, so I'm not going to fret much more over the wording.
It shouldn't be necessary to read the complete set of boilerplate to file a bug.