xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Gordan Bobic <gordan@bobich.net>
Cc: xen-users <xen-users@lists.xen.org>,
	xen-devel@lists.xen.org,
	Bartek Krawczyk <bbartlomiej.mail@gmail.com>
Subject: Re: [Xen-users] xen forum
Date: Thu, 23 May 2013 14:40:09 +0100	[thread overview]
Message-ID: <519E1C39.3030808@eu.citrix.com> (raw)
In-Reply-To: <ac5bc11f574742a24588fd3d2fa6640e@mail.shatteredsilicon.net>

On 22/05/13 17:44, Gordan Bobic wrote:
>
>> What we need is people who report / complain about bugs / deficiences
>> in a constructive way.
>
> More like nag about a problem enough to get somebody to pay attention
> and hope that the attention it gets isn't being added to the killfile.

This conversation is getting really negative, so I think we need to turn 
the direction a bit.

The developers want to be told about bugs so we can fix them; and we 
want users to have confidence in the software they're using.  Nobody is 
going to be added to a killfile for reporting a bug and asking about it 
a few times.

We've known for a while that important bugs sometimes get dropped, and 
we've already started working on solutions for it that fit with our 
existing workflow.  And obviously having a bugzilla that no one actually 
uses is much worse than just having no bugzilla at all. That needs to be 
sorted out.

As we've been looking at re-organizing the bug-reporting process, we've 
been mainly looking at how we can make it useful for developers, so that 
we can spend more time actually fixing bugs and writing new features.  
It seems maybe we've been focusing too much on that and not on the 
perspective of the users.

So thank you for bringing this up; hopefully we can come up with 
something that is the best for everyone.

  -George

  reply	other threads:[~2013-05-23 13:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 15:09 xen forum jacek burghardt
2013-05-19 15:16 ` Gordan Bobic
2013-05-19 16:36   ` Joseph Glanville
2013-05-19 17:04     ` Gordan Bobic
2013-05-21 14:29 ` Konrad Rzeszutek Wilk
2013-05-21 14:57   ` Gordan Bobic
2013-05-21 15:04     ` [Xen-users] " Ian Campbell
2013-05-22  6:18       ` Bartek Krawczyk
     [not found]       ` <CAFp_H4vqFyNN-ZPTo-C2rN6_j1DsXWWPugNM8du9Ssa+V1FHAQ@mail.gmail.com>
2013-05-22  6:55         ` Gordan Bobic
2013-05-22  9:53           ` Ian Campbell
2013-05-22  9:58             ` George Dunlap
2013-05-22 15:27               ` Gordan Bobic
2013-05-22 15:32                 ` George Dunlap
2013-05-22 15:52                   ` Gordan Bobic
2013-05-22 15:53                     ` Ian Campbell
2013-05-22 15:58                     ` George Dunlap
2013-05-22 20:54                     ` Gordan Bobic
2013-05-23 10:41                       ` George Dunlap
2013-05-23 12:04                         ` Ian Campbell
2013-05-23 13:08                           ` George Dunlap
2013-05-22 10:20           ` George Dunlap
2013-05-22 15:24             ` Gordan Bobic
2013-05-22 16:18               ` George Dunlap
2013-05-22 16:44                 ` Gordan Bobic
2013-05-23 13:40                   ` George Dunlap [this message]
2013-05-21 15:04   ` Ian Murray
2013-05-21 15:19     ` Ian Campbell
2013-05-21 16:00       ` Ian Murray
2013-05-21 16:15         ` Ian Campbell
2013-05-21 17:57           ` Ian
2013-05-21 16:31     ` Konrad Rzeszutek Wilk
2013-05-21 17:19       ` jacek burghardt
2013-05-21 18:03       ` Ian
2013-05-24 14:04       ` Konrad Rzeszutek Wilk
2013-05-24 19:37         ` Gordan Bobic
2013-05-24 21:36           ` Stefano Stabellini
2013-05-24 22:14             ` Gordan Bobic
2013-05-25 12:06               ` Konrad Rzeszutek Wilk
2013-05-28 16:00               ` George Dunlap
2013-05-25  3:07         ` Andrew Bobulsky
2013-05-28 13:49           ` Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=519E1C39.3030808@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=bbartlomiej.mail@gmail.com \
    --cc=gordan@bobich.net \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).