Hi Axel,
> > To me a distributed project management tool kind of eliminates the need
> > for multi-user tools, unless you are thinking of large non-technical
> > end-user populations, in which case the distributed criteria probably
> > ranks lower overall (although not necessarily in the minds of
> > developers :-).
>
> You hit the core of my thoughts about this whole topic: I'm looking
> for a tool which can serve both groups.
>
> Despite xen-tools being a commandline tool, I doubt that everyone who
> wants to report a bug wants to checkout and commit to a VCS repo, or
> even worse: fork it and make a pull request just to write a bug report.
As some have already noted in other places, bug/issue tracking should
be independent from any VCS. No end-user wants to have to deal with any
software-project's specific tools for this task. And no end-user wants
to have to sign up to Yet-Another-Bug-Tracking-System in order to
report a bug. In an ideal world where bugs can be distributed, your
above scenario could instead become the following:
* Packaged with each (Linux/BSD/whatever) system is the
Distributed Bug Reporting Tool, which is used for all packages.
* An end user has a problem with xen-tools and creates a bug in
their local bug database. At any time they can list their local
database to see what issues *they* currently have open.
* The bug system automatically 'pushes' the bug to
the already defined 'debian' remote (hub) bug database.
* The Debian package maintainer 'pulls' all bugs related to their
package into her local bug database, determines that the problem is
more than a packaging issue and 'pushes' the bug to yet another
'upstream' hub.
* This above step is repeated until the bug reaches the
right place, and each time a synchronisation occurs the status
and updates can slowly filter back to the original reporter.
Sounds straight-forward, right? Basically what we already do today with
email and a web browser, but with certain steps automated reducing the
hands-on effort. Probably I'm preaching to the choir here.
> OTOH you may be not so wrong: If I count that bugs can easily reported
> via the users' or developers' mailing list, a read-only web interface
> could suffice. The only thing then is that the developers (or those
> with VCS repo write access) have to take care that each such report is
> documented in the VCS/BTS. And that's a thing I'd be happy to avoid.
> :-)
Hopefully a simple mail-client bounce to the bug tracker email
interface would be sufficient...
Cheers,
Mark.
--
Mark Lawrence
_______________________________________________
dist-bugs mailing list
[email protected]
http://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs
