qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Markus Armbruster <armbru@redhat.com>,
	Programmingkid <programmingkidx@gmail.com>,
	Peter Crosthwaite <crosthwaitepeter@gmail.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] feature idea: allow user to run custom scripts
Date: Fri, 2 Oct 2015 13:20:31 +0200	[thread overview]
Message-ID: <20151002112031.GC4373@noname.redhat.com> (raw)
In-Reply-To: <560D0C9A.1020300@redhat.com>

Am 01.10.2015 um 12:36 hat Paolo Bonzini geschrieben:
> 
> 
> On 30/09/2015 16:23, Programmingkid wrote:
> >> We clearly don't have the
> >> active maintainer and review capacity to do anything serious with
> >> "ui/" (MAINTAINERS lists everything except SPICE as Odd Fixes).
> > 
> > This could be changed. 
> 
> Sure it could.  Who's going to do the work?

I think he's talking about himself.

> >> This is why I tend to agree with Markus' opinion here: we should
> >> provide enough graphical UI to make raw QEMU minimally usable,
> >> and leave further user-friendliness to other projects which have
> >> more direct interest in that.
> >>
> >> If we had more regular contributors who were actively interested
> >> in improving our UI layer my opinion might be different.
> > 
> > It is really hard for more contributors to come when the maintainers
> > keep discouraging them. 
> 
> Submitting patches is never discouraged.  Endless email threads are.

To be fair, I can see how it is discouraging when you post patches and
they either get ignored or people start arguing that you are
implementing something that you shouldn't be implementing because doing
GUI work is bad. The latter is what causes endless email threads.

And you can already see the result: Instead of patches, we now only get
the question whether patches improving the UI would be acceptable at all
(and worse, people even answer no).

Why don't we just let him maintain the OS X GUI and accept the patches,
even if they aren't perfect and even if they mean committing the crime
of improving user friendliness?  It's one of those neglected areas in
our code base and we should be glad that someone is interested in
keeping it working and improving it.

Kevin

  reply	other threads:[~2015-10-02 11:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-27  3:39 [Qemu-devel] feature idea: allow user to run custom scripts Programmingkid
2015-09-27 10:13 ` Peter Maydell
2015-09-27 18:53   ` Peter Crosthwaite
2015-09-28  1:49     ` Programmingkid
2015-09-28  2:30       ` Michael Roth
2015-09-28  3:10         ` Programmingkid
2015-09-28  7:29           ` Markus Armbruster
2015-09-28 19:43             ` Programmingkid
2015-09-28 19:44               ` Peter Maydell
2015-09-28 19:48                 ` Programmingkid
2015-09-29 13:11                 ` Dr. David Alan Gilbert
2015-09-29 13:17                   ` Programmingkid
2015-09-29 13:23                     ` Dr. David Alan Gilbert
2015-09-30  5:01                       ` Paolo Bonzini
2015-09-29 13:24                   ` Peter Maydell
2015-09-29 13:31                     ` Dr. David Alan Gilbert
2015-09-30  7:48                       ` Markus Armbruster
2015-09-30  8:14                         ` Dr. David Alan Gilbert
2015-09-30 10:53                           ` Peter Maydell
2015-09-30 14:23                             ` Programmingkid
2015-10-01 10:36                               ` Paolo Bonzini
2015-10-02 11:20                                 ` Kevin Wolf [this message]
2015-10-01  7:06                             ` Markus Armbruster
2015-10-02 12:33                             ` Daniel P. Berrange
2015-10-02 13:28                               ` Programmingkid
2015-10-01  6:55                           ` Markus Armbruster
2015-10-01  8:01                             ` Dr. David Alan Gilbert
2015-10-02 12:30                         ` Daniel P. Berrange
2015-10-02 13:33                           ` Dr. David Alan Gilbert
2015-10-02 14:28                             ` Daniel P. Berrange
2015-10-02 14:37                               ` Programmingkid
2015-10-02 16:21                                 ` Eric Blake
2015-10-02 17:57                                   ` Programmingkid

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=20151002112031.GC4373@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=crosthwaitepeter@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.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).