[Tickets #9450] Re: "capture" compatibility issues - make it easy for submitters
bugs at horde.org
bugs at horde.org
Tue Dec 14 23:29:41 UTC 2010
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/9450
------------------------------------------------------------------------------
Ticket | 9450
Updated By | Michael Rubinsky <mrubinsk at horde.org>
Summary | "capture" compatibility issues - make it easy for
| submitters
Queue | Horde Groupware
Version | 1.2.8
Type | Enhancement
-State | New
+State | Rejected
-Priority | 2. Medium
+Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
Michael Rubinsky <mrubinsk at horde.org> (2010-12-14 18:29) wrote:
> Hello,
>
> Just a suggestion.
> Not wanting to add complexity (which should be reduced) to the bug
> report system.
> But ...
>
> 1) To make it easier to reports bugs;
> Use as little mandatory questions, and choice procedures as possible.
> Some kind hearted folk who are taking the time to talk to you, may
> get fed up with ancilliary comms and leave - then you learn Nothing
> new from them.
>
> 2) No harm in capturing additional information - if the submitter is
> capable, knowledgeable enough or willing to provide it.
> Useful information to help understand the "context" of a problem
> might include ;
> - is your Horde program being used within a site management system
> such as cPanel or Fantastico?
> - is horde on your own in-house network, or at your isp.
> - feel free to tell us more about how you are accessing Horde online?
While these are good communication practices, this *is* a bug tracking
system for Horde code. Information such as this may be useful, but not
in the context of a bug/issue tracker. i.e., if your horde install is
run by your isp, then you shouldn't be reporting a bug to horde.
More information about the bugs
mailing list