From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: An organizational suggestion
Date: Tue, 3 Jun 2008 15:26:17 +0100 [thread overview]
Message-ID: <20080603142617.GA32331@shareable.org> (raw)
In-Reply-To: <484540A0.6040907@siemens.com>
Jan Kiszka wrote:
> I think we don't need this agreement-in-advance if the people who
> finally decide about commits are neutral due to their affiliation or
> have proven to be neutral despite of it, both politically as well as
> technically - someone being deeply involved in one of both approaches
> /may/ look biased at things, naturally.
As a user (not really a contributor), it looks like vague neutrality
is what we have now. E.g. the command-line and (proposed) config file
are really messy, it looks like people try to do 'just technical'
patches to those because they might be accepted, rather than a
coherent design. That's just an example, but a visible one.
But I'm probably not seeing a lot that goes on off-list.
I think the project would benefit from some more vision for it's next
step, so that _potential_ contributors (like me) have an idea what
it's worth looking it, and how best to ensure contributions are useful.
Right now, there are several bugs, improvements (if you agree :-) and
documentation I'm curious to look at, but I'm not going to waste my
time if I think it won't be used. Writing notes on a disorganised
wiki does not count as worth my time.
I think encouraging more subsystem maintainers would be good. I have
a problem with USB tablet at the moment - Windows Server 2003's driver
doesn't work with it - and no idea who to send to. Bugs like that
reported to the list often don't get a response, but I'm sure someone
cares. Assuming so, it suggests they might like to be a contact -
even if it's as specific as "USB tablet: <person>" so they don't have
to deal with much, just occasional rare feedback.
-- Jamie
next prev parent reply other threads:[~2008-06-03 14:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 5:42 [Qemu-devel] An organizational suggestion Balazs Attila-Mihaly (Cd-MaN)
2008-06-03 9:27 ` Ian Jackson
2008-06-03 10:00 ` Jamie Lokier
2008-06-03 10:19 ` Ian Jackson
2008-06-03 11:03 ` Jamie Lokier
2008-06-03 12:32 ` Ian Jackson
2008-06-03 13:01 ` [Qemu-devel] " Jan Kiszka
2008-06-03 14:26 ` Jamie Lokier [this message]
2008-06-03 22:24 ` [Qemu-devel] " Anthony Liguori
2008-06-03 13:45 ` Johannes Schindelin
2008-06-03 14:02 ` Ian Jackson
2008-06-03 14:35 ` Paul Brook
2008-06-03 14:41 ` Jamie Lokier
2008-06-03 14:55 ` Paul Brook
2008-06-03 15:14 ` Jamie Lokier
2008-06-03 14:54 ` Laurent Vivier
2008-06-03 15:04 ` Ian Jackson
2008-06-03 15:17 ` Jamie Lokier
2008-06-03 15:27 ` Ian Jackson
2008-06-03 16:54 ` Anthony Liguori
2008-06-03 19:26 ` Jamie Lokier
2008-06-03 15:24 ` Laurent Vivier
2008-06-03 20:37 ` Anthony Liguori
2008-06-03 20:27 ` Anthony Liguori
2008-06-03 10:23 ` Andreas Färber
2008-06-03 11:09 ` [Qemu-devel] " Jan Kiszka
2008-06-03 12:36 ` Ian Jackson
2008-06-03 12:48 ` Daniel P. Berrange
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=20080603142617.GA32331@shareable.org \
--to=jamie@shareable.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.